On 05/12/2014 08:32 AM, Jürgen Schmidt wrote:
> On 5/6/14 12:49 AM, Kay Schenk wrote:
>> On Wed, Apr 30, 2014 at 1:53 AM, Jürgen Schmidt wrote:
>>
>>> Hi,
>>>
>>> for AOO 3.4 we had already discussed and later on reverted a change to
>>> enable the ODF Document encryption AES-256 by default.
>>>
On 5/6/14 12:49 AM, Kay Schenk wrote:
> On Wed, Apr 30, 2014 at 1:53 AM, Jürgen Schmidt wrote:
>
>> Hi,
>>
>> for AOO 3.4 we had already discussed and later on reverted a change to
>> enable the ODF Document encryption AES-256 by default.
>>
>> Some time ago I played with a new option field to all
On Wed, Apr 30, 2014 at 1:53 AM, Jürgen Schmidt wrote:
> Hi,
>
> for AOO 3.4 we had already discussed and later on reverted a change to
> enable the ODF Document encryption AES-256 by default.
>
> Some time ago I played with a new option field to allow the user to
> enable this option as new defau
On 30/04/2014 Jürgen Schmidt wrote:
for AOO 3.4 we had already discussed and later on reverted a change to
enable the ODF Document encryption AES-256 by default.
Some time ago I played with a new option field to allow the user to
enable this option as new default, see [1] ...
[1] http://people.ap
On 4/30/14 10:53 AM, Jürgen Schmidt wrote:
> Hi,
>
> for AOO 3.4 we had already discussed and later on reverted a change to
> enable the ODF Document encryption AES-256 by default.
>
> Some time ago I played with a new option field to allow the user to
> enable this option as new default, see [1]
Hi,
for AOO 3.4 we had already discussed and later on reverted a change to
enable the ODF Document encryption AES-256 by default.
Some time ago I played with a new option field to allow the user to
enable this option as new default, see [1]
By default the office still uses the old blowfish algor
