January 14th, 2011· Minor enhancements.
January 10th, 2011· Refactoring, bug fixes & minor enhancements.
January 6th, 2011· Jar is "finally" signed with the final self-certified key.
December 30th, 2010· Dialog "Create New Encryption Key" defaults to AES-128.
· Pressing after typing in the confirmation passphrase now submits.
· Dependency on the original "mydata" directory structure is now eliminated. For thumb drive installations, PDS state is now saved in the same directory as the JAR; for JNLP/JWS installations, PDS state is now saved in the users home directory. See Known Issues above.
· KeyStore in Search Path now selectable by double-click.
· File choosers have more appropriate titles and buttons.
· File viewer and editor panes now titled with full path to open file.
· Confirmation dialog shown after saving a file now contains the full path to the file.
· When the application initializes on the "first run", a dialog shows the initialized status and default locations of files and KeyStores.
· When unsaved changes exist in the Options dialog (KSP) and another tab is selected, a confirmation/warning dialog is displayed.
· The PDS icon is now packaged with the zip release.
April 30th, 2010· Added support for writing external files and directories to tape.
· Refactoring of Gui.java subclasses into Top-level classes
· Bug fixes and other clean up.
April 30th, 2010· Numerous bug fixes. Just as many minor enhancements.
April 30th, 2010· Added the ability to encrypt an existing directory.
· Directory encryption is done with Zip, and provides the user with a choice on the level of compression that should be applied.
· The directory is encrypted to a single file.
· The directory (single file) can be decrypted and extracted to the filesystem, or it can be decrypted to a Zip file.
· New Default KeyStore directories are added to the KeyStore Search Path
· When defining a new default KeyStore directory, that directory is now added to the KeyStore Search Path.
April 30th, 2010· Options dialog now supports defining a Default KeyStore directory.
· Application now defines a default KeyStore directory at initialization if it does not yet exist.
· Application uses the default KeyStore directory for all file choosers that are created to search for a KeyStore.
April 30th, 2010· Encryption of External files now supports binary mode along with Base64
· Previously, all encrypted files were encoded with Base64. This adds about 35% to the size of the file and is significant with large files.
· Native files (those edited and viewed) remain as Base64 encoded only.
· Updated the Base64.java file from iharder.net.
· In testing a range of files, one file produced inaccurate results. This was resolved by switching to the newer file.
· Added a prompt to create non-existent directories
· In various locations throughout the application, a directory can be provided as input to the dialogs. In these cases, have added a test to confirm that the path actually exists. Where it does not, the user is prompted to create the dir.
· Set the default action on all "Save on Close" operations to YES.
· Added option to have the currently selected button be the default button.
· Added additional filters to the File Choosers.
· Updated the internal documentation.
April 30th, 2010· Selection of Destination Directories
· Added the ability to select destination directories when encrypting and decrypting external files.
· Added the ability to delete a file
· Confirmation Dialogs
· Added confirmation dialog after successful encryption or decryption of external files.
· Better Clarity on Files that will be Overwritten
· Better clarification of what files will be overwritten during the encryption and decryption of external files.
April 30th, 2010· Checks for PDS "native" file format prior to viewing/editing
· Previous releases would allow the encryption of a zip file, and allow the user to attempt to load it into the editor. Obviously, this is a bad idea.
· Now, when the PDS file is created, the application marks it as "native" in the header; this value is checked prior to viewing or editing the file.
· This breaks earlier PDS files, and an appropriate error message is displayed.
· The workaround is to add the line "CryptoFile#NATIVE" to the metadata section of the PDS file header. Do so only after making a backup copy of the original.
· KeyStore / Key values in Create New File Dialog now read-only
· Changes weren't captures, so why allow changes.
· Better error reporting dialogs for encryption jobs.
April 30th, 2010· New Thread Support for Encryption and Decryption Jobs.
· Application now supports multiple simultaneous Threads of Execution.
· Now Jobs are submitted to a new Thread of the CryptoEngine class.
· A Progress Monitor has been added to long running Encryption Jobs.
· Have an option on the Progress Monitor to Cancel the Job.
· Using the Progress Monitor InputStream class.
· Support for tracking multiple simultaneous Threads of Execution
· The new CryptoState class and the StateObject class provide new support for tracking multiple simultaneous Threads via unique IDs in each CryptoFile type of class - CryptoFile, CryptoFileNative and CryptoFileExternal.
· IDs are added in new Constructors.
April 30th, 2010· Encrypt External File Dialog now supports CR/Enter key stroke to Encrypt.
· Changed (the final) two confirmation dialogs to have NO as the default action.
· Fixed bugs that caused erroneous error Dialogs after canceling.
· After canceling encryption/decryption of external file rather than overwriting an existing file, an erroneous error Dialog would appear. Resolved.
April 30th, 2010· Each Editor now has its own data for Undo and Redo
April 30th, 2010· Provided the ability to define multiple KeyStore Search paths
· The KeyStore Search Path will be used when the Application does not find the KeyStore as explicitly coded into the encrypted PDS file.
· This greatly adds support to mobile users, as well as users who use the application on multiple machines. For example, one could define a KeyStore path for their Linux machine, another path for their Windows and a third path for another machine. If the KeyStore was not found at the last known path, all other paths will be searched.
· If multiple matches are found, all are displayed. One must be selected.
· If not defined, the KeyStore Search Path will be initialized at startup.
· See Tools->Options->KeyStore Search Path
· Provide a the ability to browse for a KeyStore if the KeyStore is not found. As a fallback to the definition of multiple KeyStore paths, if a KeyStore is still not found, a File Chooser Dialog is presented so that the user may browse for the KeyStore.
· Added the ability to define a Default Directory for Encrypted PDS Files.
· Appropriate Dialogs (create file, edit file, view file, etc.) make use of the Default Directory.
· If not defined, the Default Directory will be initialized at startup.
· See Tools->Options->Default Directory for Encrypted Files
· Implemented the editing options "undo", "redo", "cut", "copy" and "paste" in the Application Menu.
· After encrypting an existing file, the user is now prompted to confirm whether the original file should be deleted or not.
· Fixed a bug in the KeySelector Dialog where the wrong Key could be deleted if multiple key were deleted in the same instance of the Key Edit Dialog.
· Improved the KeySelector Dialog
· Added the ability to sorting by Date and Key Name
· Added dynamic resizing of the table.
· Authorization Dialogs support the CR/Enter KeyStroke in Text Fields
· When providing credentials in the Authorization Dialog, the operator is now permitted to use the carriage return key, in either the KeyStore or Key passphrase fields, to submit the credentials for Authorization
· Additional Dialogs support CR/Enter KeyStrokes
· The Key passphrase field is disabled by default in the Authorization Dialog
· This is more of a bug fix, as it should have been done previously.
· Operator is able to submit a Key passphrase, but as before, must select the radio button indicating that the KeyStore and Key passphrases are not identical.
· Changed confirmation dialogs to have NO as the default action.
· Added "Read-Only" to the title bar when "viewing" files.
· Fixed an issue where an invalid JInternalFrame was displayed after an attempt to create a new PDS file failed to complete.
· Fixed an obscure bug where a path could be prefixed "//" instead of "/".
· Support website was redefined from http://brettlee.com/pds to the Java package structure: http://crypto.brettlee.com
December 28th, 2009· Failed authentication no longer results in a edit/view window being opened
· Prior to this, a indeterminate warning dialog was displayed prior to opening an invalid view/edit window
· Edit window now opens with the cursor at the beginning of the first line
· Editing for uniformity in both website & email for application support
· Editing of selected text as appropriate
· Application self-signed with a new key
December 28th, 2009· Creating a new keystore now supports manually entering the keystore name
· New KeyStore names may now be provided manually or using the FileChooser
· If "path" is not provided, the keystore will be created in the default location
· Creating a new file now supports manually entering the file name
· New File names may now be provided manually or using the FileChooser
· If "path" is not provided, the file will be created in the default location
December 28th, 2009Minor cosmetic changes:
· Updated text in some dialogs
· Additional use of PDS logos in dialogs
· Re-added support for key sizes greater than 56 bits
· This application does NOT provide FULL support for generating keys
· Instead, it USES the existing Java runtime, and thus this application alone does NOT deliver full support for cryptography and thus does not seem to be
· a breach of current US export restrictions on cryptography
Find us on Google+
