Encryption: Difference between revisions
No edit summary |
|||
Line 18: | Line 18: | ||
==Troubleshooting== | ==Troubleshooting== | ||
''Problem:'' Maps encrypted with FreeMind running on Java Runtime Environment '''JRE 1.4''' cannot be opened with FreeMind running on Java Runtime Environment '''JRE 1.6'''. (Is the problem there | ''Problem:'' Maps encrypted with FreeMind running on Java Runtime Environment '''JRE 1.4''' cannot be opened with FreeMind running on Java Runtime Environment '''JRE 1.6'''. (Is the problem there with all the operating systems? TODO) | ||
''Solution:'' A provisional solution is to stick with Java Runtime Environment '''JRE 1.4'''. (Or even 1.5? TODO) | ''Solution:'' A provisional solution is to stick with Java Runtime Environment '''JRE 1.4'''. (Or even 1.5? TODO) |
Revision as of 09:00, 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 encryptionTODO: Menu entries. Format: To achieve this, do that. Encryption algorithmThe 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". TroubleshootingProblem: Maps encrypted with FreeMind running on Java Runtime Environment JRE 1.4 cannot be opened with FreeMind running on Java Runtime Environment JRE 1.6. (Is the problem there with all the operating systems? TODO) Solution: A provisional solution is to stick with Java Runtime Environment JRE 1.4. (Or even 1.5? TODO) Detail: There is a bug in the PBE key getkey.getAlgorithm() method in JRE 1.4> key.getAlgorithm() returns PBEWithMD5AndDES instead of PBEWithMD5AndDES. File formatThe encrypted branches are stored in FreeMind XML as follows. TODO. Links
Implementation
|