Encryption: Difference between revisions

From FreeMind
Jump to navigationJump to search
Line 24: Line 24:
''Solution:'' A provisional solution is to stick with Java Runtime Environment '''JRE 1.4''' or '''JRE 1.5'''.
''Solution:'' A provisional solution is to stick with Java Runtime Environment '''JRE 1.4''' or '''JRE 1.5'''.


''Detail:'' There is a bug in the PBE key getkey.getAlgorithm() method in JRE 1.4> key.getAlgorithm() returns PBEWithMD5AndDES instead of PBEWithMD5And3DES.
''Detail:'' There is a bug in the PBE key getkey.getAlgorithm() method in JRE 1.4> key.getAlgorithm() returns PBEWithMD5AndDES instead of PBEWithMD5AndTripleDES.


==File format==
==File format==

Revision as of 11:41, 22 August 2007

 

In FreeMind, the whole map or single branches may be encrypted. An encrypted branch has a padlock icon. Encryption is available since FreeMind 0.8.0.

Using encryption

TODO: Menu entries. Format: To achieve this, do that.

Encryption algorithm

The encryption algorith used in FreeMind is Triple DES or DES, depending on JRE version[TODO]. Both are symmetric-key algorithms built in Java.

For details, please search for "PBEWithMD5AndTripleDES".

Troubleshooting

Problem: Maps encrypted with FreeMind running on Java Runtime Environment JRE 1.4 and JRE 1.5 cannot be opened with FreeMind running on Java Runtime Environment JRE 1.6.

Concerned operating systems: Linux, Windows, and possibly other.
Concerned FreeMind versions: 0.8.0, 0.9.0 beta 9.

Solution: A provisional solution is to stick with Java Runtime Environment JRE 1.4 or JRE 1.5.

Detail: There is a bug in the PBE key getkey.getAlgorithm() method in JRE 1.4> key.getAlgorithm() returns PBEWithMD5AndDES instead of PBEWithMD5AndTripleDES.

File format

The encrypted branches are stored in FreeMind XML as follows. TODO.

Links

Implementation