• Thumbs up

  It's cool and works very well in my Nokia 5800.

  posted by anonymous 41 days ago

  If you'd like to rate this review, please log in.

View all reviews

• freesafe 0.9.0 file released: jfreesafe-0.9.0.zip

  0.9.0 ------- Some new features by Mikhail Blinov: * Entry editor now supports changing the entry structure, i.e. adding new fields, renaming fields, moving fields, deleting fields. * Added a bunch of icons that you can now assign to entries ("Change icon" option in entry editor). * Added menu option "Create similar". So you can now use existing entries as templates for new ones. * Added an application icon. * Added "Edit" option to the entry viewer, so you can edit an entry directly from the details screen. * Added support for backup/restore to a file, if your mobile supports this. (In technical slang, this feature requires "JSR 75 support"). * Added menu option "Discard Changes and Exit". Until know, if you clicked Exit, all changes were saved to the Store. However, if you made a change by mistake (e.g. deleted the wrong entry), it is sometimes useful to have an option to exit without save. This is know possible by selecting the above option. * Added menu option "Add new profile" (in "Tools"). This is a basic * steganography feature, which means an attempt to hide the very existence of a secret in addition to encrypting it. In this day and age, it is almost impossible to break a good encryption. But it is relatively easy to break the person who knows the password. One can be beaten up, bullied, tricked into revealing the password, etc. What you can do now is to create a secondary profile (protected by secondary password) and fill it with rubbish. Now the list of entries you see depend on the password you typed in at the beginning. So if it comes to the worst, you can safely (with due resistance) give away the secondary password. And the point is that all profiles are absolutely identical from the UI experience point of view, the only difference is the password (and the content), so nothing should raise the suspicion that there is more in there than meets the eye. Note though that this protection works at the UI level only. If your adversaries are knowledgeable (and determined) enough to retrieve the actual store content, they'll see that there are hidden entries there. But even the UI-level protection should be sufficient in most practical cases. Note also that, in the current implementation, profiles are automatically deleted if they don't contain any entries. 0.2.8 ------- * Note and Credit Card type by Alexandre Kotchnev * Fixed OTP dialog so that it comes up with the stored hash type. (It was stored in the db but the dialog always came up with MD5 selected.) 0.2.7 ------- * ... Backup facility ... IN PROGRESS 0.2.6 ------- * (Re-)enabled SHA1 OTP generation. 0.2.5 ------- * Password entries are alphabetically sorted. * Added an 'About' dialog. * Implemented auto-logout feature. If jFreeSafe is left alone for 4 minutes, it will automatically exit. 0.2.4 and before: ------------------- * Implemented password change functionality. * build.xml: added usemixedClassNames="false" to the proguard task to make it work properly under widnows. * BUG found: empty stores can be opened with any password -> if the user mistypes the password on opening an empty store and then saves some new data then he will not be able to open the store with the correct password. Solution: delete the record store if the store is empty. * Implemented MD4 and SHA1 hashing based OTP.

  posted 251 days ago

• freesafe 0.9.0 file released: jfreesafe-0.9.0.tar.gz

  0.9.0 ------- Some new features by Mikhail Blinov: * Entry editor now supports changing the entry structure, i.e. adding new fields, renaming fields, moving fields, deleting fields. * Added a bunch of icons that you can now assign to entries ("Change icon" option in entry editor). * Added menu option "Create similar". So you can now use existing entries as templates for new ones. * Added an application icon. * Added "Edit" option to the entry viewer, so you can edit an entry directly from the details screen. * Added support for backup/restore to a file, if your mobile supports this. (In technical slang, this feature requires "JSR 75 support"). * Added menu option "Discard Changes and Exit". Until know, if you clicked Exit, all changes were saved to the Store. However, if you made a change by mistake (e.g. deleted the wrong entry), it is sometimes useful to have an option to exit without save. This is know possible by selecting the above option. * Added menu option "Add new profile" (in "Tools"). This is a basic * steganography feature, which means an attempt to hide the very existence of a secret in addition to encrypting it. In this day and age, it is almost impossible to break a good encryption. But it is relatively easy to break the person who knows the password. One can be beaten up, bullied, tricked into revealing the password, etc. What you can do now is to create a secondary profile (protected by secondary password) and fill it with rubbish. Now the list of entries you see depend on the password you typed in at the beginning. So if it comes to the worst, you can safely (with due resistance) give away the secondary password. And the point is that all profiles are absolutely identical from the UI experience point of view, the only difference is the password (and the content), so nothing should raise the suspicion that there is more in there than meets the eye. Note though that this protection works at the UI level only. If your adversaries are knowledgeable (and determined) enough to retrieve the actual store content, they'll see that there are hidden entries there. But even the UI-level protection should be sufficient in most practical cases. Note also that, in the current implementation, profiles are automatically deleted if they don't contain any entries. 0.2.8 ------- * Note and Credit Card type by Alexandre Kotchnev * Fixed OTP dialog so that it comes up with the stored hash type. (It was stored in the db but the dialog always came up with MD5 selected.) 0.2.7 ------- * ... Backup facility ... IN PROGRESS 0.2.6 ------- * (Re-)enabled SHA1 OTP generation. 0.2.5 ------- * Password entries are alphabetically sorted. * Added an 'About' dialog. * Implemented auto-logout feature. If jFreeSafe is left alone for 4 minutes, it will automatically exit. 0.2.4 and before: ------------------- * Implemented password change functionality. * build.xml: added usemixedClassNames="false" to the proguard task to make it work properly under widnows. * BUG found: empty stores can be opened with any password -> if the user mistypes the password on opening an empty store and then saves some new data then he will not be able to open the store with the correct password. Solution: delete the record store if the store is empty. * Implemented MD4 and SHA1 hashing based OTP.

  posted 251 days ago

• freesafe 0.9.0 file released: jfreesafe-0.9.0-src.zip

  0.9.0 ------- Some new features by Mikhail Blinov: * Entry editor now supports changing the entry structure, i.e. adding new fields, renaming fields, moving fields, deleting fields. * Added a bunch of icons that you can now assign to entries ("Change icon" option in entry editor). * Added menu option "Create similar". So you can now use existing entries as templates for new ones. * Added an application icon. * Added "Edit" option to the entry viewer, so you can edit an entry directly from the details screen. * Added support for backup/restore to a file, if your mobile supports this. (In technical slang, this feature requires "JSR 75 support"). * Added menu option "Discard Changes and Exit". Until know, if you clicked Exit, all changes were saved to the Store. However, if you made a change by mistake (e.g. deleted the wrong entry), it is sometimes useful to have an option to exit without save. This is know possible by selecting the above option. * Added menu option "Add new profile" (in "Tools"). This is a basic * steganography feature, which means an attempt to hide the very existence of a secret in addition to encrypting it. In this day and age, it is almost impossible to break a good encryption. But it is relatively easy to break the person who knows the password. One can be beaten up, bullied, tricked into revealing the password, etc. What you can do now is to create a secondary profile (protected by secondary password) and fill it with rubbish. Now the list of entries you see depend on the password you typed in at the beginning. So if it comes to the worst, you can safely (with due resistance) give away the secondary password. And the point is that all profiles are absolutely identical from the UI experience point of view, the only difference is the password (and the content), so nothing should raise the suspicion that there is more in there than meets the eye. Note though that this protection works at the UI level only. If your adversaries are knowledgeable (and determined) enough to retrieve the actual store content, they'll see that there are hidden entries there. But even the UI-level protection should be sufficient in most practical cases. Note also that, in the current implementation, profiles are automatically deleted if they don't contain any entries. 0.2.8 ------- * Note and Credit Card type by Alexandre Kotchnev * Fixed OTP dialog so that it comes up with the stored hash type. (It was stored in the db but the dialog always came up with MD5 selected.) 0.2.7 ------- * ... Backup facility ... IN PROGRESS 0.2.6 ------- * (Re-)enabled SHA1 OTP generation. 0.2.5 ------- * Password entries are alphabetically sorted. * Added an 'About' dialog. * Implemented auto-logout feature. If jFreeSafe is left alone for 4 minutes, it will automatically exit. 0.2.4 and before: ------------------- * Implemented password change functionality. * build.xml: added usemixedClassNames="false" to the proguard task to make it work properly under widnows. * BUG found: empty stores can be opened with any password -> if the user mistypes the password on opening an empty store and then saves some new data then he will not be able to open the store with the correct password. Solution: delete the record store if the store is empty. * Implemented MD4 and SHA1 hashing based OTP.

  posted 251 days ago

• freesafe 0.9.0 file released: jfreesafe-0.9.0-src.tar.gz

  0.9.0 ------- Some new features by Mikhail Blinov: * Entry editor now supports changing the entry structure, i.e. adding new fields, renaming fields, moving fields, deleting fields. * Added a bunch of icons that you can now assign to entries ("Change icon" option in entry editor). * Added menu option "Create similar". So you can now use existing entries as templates for new ones. * Added an application icon. * Added "Edit" option to the entry viewer, so you can edit an entry directly from the details screen. * Added support for backup/restore to a file, if your mobile supports this. (In technical slang, this feature requires "JSR 75 support"). * Added menu option "Discard Changes and Exit". Until know, if you clicked Exit, all changes were saved to the Store. However, if you made a change by mistake (e.g. deleted the wrong entry), it is sometimes useful to have an option to exit without save. This is know possible by selecting the above option. * Added menu option "Add new profile" (in "Tools"). This is a basic * steganography feature, which means an attempt to hide the very existence of a secret in addition to encrypting it. In this day and age, it is almost impossible to break a good encryption. But it is relatively easy to break the person who knows the password. One can be beaten up, bullied, tricked into revealing the password, etc. What you can do now is to create a secondary profile (protected by secondary password) and fill it with rubbish. Now the list of entries you see depend on the password you typed in at the beginning. So if it comes to the worst, you can safely (with due resistance) give away the secondary password. And the point is that all profiles are absolutely identical from the UI experience point of view, the only difference is the password (and the content), so nothing should raise the suspicion that there is more in there than meets the eye. Note though that this protection works at the UI level only. If your adversaries are knowledgeable (and determined) enough to retrieve the actual store content, they'll see that there are hidden entries there. But even the UI-level protection should be sufficient in most practical cases. Note also that, in the current implementation, profiles are automatically deleted if they don't contain any entries. 0.2.8 ------- * Note and Credit Card type by Alexandre Kotchnev * Fixed OTP dialog so that it comes up with the stored hash type. (It was stored in the db but the dialog always came up with MD5 selected.) 0.2.7 ------- * ... Backup facility ... IN PROGRESS 0.2.6 ------- * (Re-)enabled SHA1 OTP generation. 0.2.5 ------- * Password entries are alphabetically sorted. * Added an 'About' dialog. * Implemented auto-logout feature. If jFreeSafe is left alone for 4 minutes, it will automatically exit. 0.2.4 and before: ------------------- * Implemented password change functionality. * build.xml: added usemixedClassNames="false" to the proguard task to make it work properly under widnows. * BUG found: empty stores can be opened with any password -> if the user mistypes the password on opening an empty store and then saves some new data then he will not be able to open the store with the correct password. Solution: delete the record store if the store is empty. * Implemented MD4 and SHA1 hashing based OTP.

  posted 251 days ago

• File released: /freesafe/0.9.0/jfreesafe-0.9.0.zip

  posted 251 days ago

• File released: /freesafe/0.9.0/jfreesafe-0.9.0.tar.gz

  posted 251 days ago

• File released: /freesafe/0.9.0/jfreesafe-0.9.0-src.zip

  posted 251 days ago

• File released: /freesafe/0.9.0/jfreesafe-0.9.0-src.tar.gz

  posted 251 days ago

• Tracker artifact added

  Anonymous created the OTP SEQ 0 entry patch... artifact

  posted by nobody 552 days ago

• Tracker artifact added

  Anonymous created the Category for each record artifact

  posted by nobody 803 days ago