Macro encryption different in between 4.2 and 5.1

[Michael Stahl]

On 12.07.2016 08:57, SOS wrote:
> sorry i mixed up the situation
> extension *Build in 4.2 and used in 5.1*:
> must be:
> extension *Build in 5.1 and used in 4.2*: the functions and Sub's in the
> libraries are not available,  its only after opening the library 
> "manualy" and after entering the password that make the functions and
> the sub's available in memory.
> Build in 4.2 and used in 5.1 gives no problems
> 
> On 11/07/2016 17:05, SOS wrote:
>> A extension made with password protected Basic Libraries using LO 5.1 
>> do not "load" properly the libraries under LO 4.2
>>
>> We load a  password protected library using the folowing code.
>> If (Not GlobalScope.BasicLibraries.isLibraryLoaded("DbUtils")) Then
>> GlobalScope.BasicLibraries.LoadLibrary("DbUtils")
>> End If
>> extension Build and used in 4.2  makes all functions and sub's
>> available in memory.
>> extension Build and used in 5.1  makes all functions and sub's
>> available in memory.
>> extension Build in 4.2 and used in 5.1: the functions and Sub's in the
>> libraries are not available,  its only after opening the library 
>> "manualy" and after entering the password that make the functions and
>> the sub's available in memory.
>>
>> The extensions are build under Windows
>> There is a difference in size between the extension build in 5.1 and 4.2
>> 5.1 gives 69 KB
>> 4.2 gives 67 KB
>> There is no error after
>> "GlobalScope.BasicLibraries.LoadLibrary("DbUtils")
>> once the librarie is opened with the password, then
>> "GlobalScope.BasicLibraries.LoadLibrary("DbUtils")"  is working fine
>> even after closing LO !!!!!!
>>
>> Can someone confirm this behavior and sould i filled a issue ?

hi Fernand,

there were numerous bugfixes for password protected libraries during
that time, like tdf#87530 tdf#68983 tdf#67685 tdf#52076 tdf#40173

but all those bugs were about just using the UI, probably nobody has
tested what happens when calling LoadLibrary() from a macro.

perhaps there is a new bug in LO 5.1 and we can fix it, or perhaps the
bug was in LO 4.2 which means it can't be fixed now, hard to tell
without a more thorough investigation - please file a bug with exact
steps to reproduce the problem.