Users Guide 2.x
Installation and Initialization
Before you use PDS, please read this !
Preparing to Install PDS
The PDS application runs on Linux, Mac and Windows. It has even been used on other Operating Systems, including Solaris and the BSDs, though those OS's are not actively tested. To maintain this flexibility, it is expected that PDS will be configured appropriately.
1) Will PDS be configured as a Desktop application?
2) Will PDS run from a USB flash drive?
3) Will PDS be configured as both a Desktop application and a USB application?
4) Which Operating System(s) will PDS need to run on?
The answers to these question will drive the installation.
As you would expect, the configuration state is persistent across different invocations of the application. A Desktop installation/instance always has its own persistent state. A USB instance of PDS can use either the Desktop's persistent state or its own persistent state.
When a USB instance of PDS starts, it first looks for its own persistent state; if that is not found, it searches for the Desktop's persistent state. For this reason, it is recommended that the USB instance be initialized first. Should you need to add a USB instance after configuring a Desktop instance, please see the Tips and Tricks section of this Users Guide.
The state is kept in an appropriately named dot file, .pdsState. A Desktop instance of PDS will save/locate the state file in the HOME directory. A USB instance will save its instance in the same directory as the executable Jar file, pds.jar; but it will also search for and use a state file in the HOME directory as well. Thus, when using both a Desktop and a Thumbdrive instance on the same machine, and you want different configurations, you need to configure the Thumbdrive when there is not a state file in the HOME directory.
As mentioned elsewhere in this Wiki, state is tracked on a per-Operating System basis. Whereas PDS 1 tracked paths in the same KeyStore Search Path, PDS 2 maintains separate instances of the KeyStore Search Path (as well as other settings) for each Operating System.
Which version of PDS should I run ?
PDS 2 is packaged into different versions for Linux, Mac and Windows. The Linux and Windows version are very similar and inter-operate seamlessly. While the Linux and Windows versions will function on Mac, they will not provide the Look and Feel of a Mac. Thus:
1. If installing a Desktop instance, use the OS-appropriate release of PDS.
2. If installing a USB instance, if Mac is one of the OS's that the USB instance of PDS will run on, install the Mac release of PDS to the USB drive. You can copy the OS-appropriate startup scripts, if desired, from the other OS release(s).
3. If installing a USB instance of PDS and 1) you will not be using Mac, and 2) you will be using Windows, install the Windows release of PDS to the USB drive. Note that the differences between Windows and Linux release are that you get a PDS icon for Windows, the startup scripts, and the formatting (LF vs. CR+LF).
Summarizing the Selection of PDS Releases
1. If you plan to use PDS on a USB flash drive, install and configure the USB instance of PDS first.
1.a. If you plan to use a USB instance of PDS on Mac, install the Mac version of PDS on the USB drive.
1.b. If you will not be using Mac on a USB instance of PDS, but you will be using Windows, install the Windows version of PDS on the USB drive.
2. After the USB instance of PDS is configured, install the OS-appropriate release of PDS to the Desktop.
PDS and Java
As PDS is a Java application, you will need to have a Java Runtime Environment (JRE) installed on your system to run PDS.
PDS has been coded to run using Java 6 (1.6) or newer. Currently, this includes Java 6, 7, and 8. For reasons including bug fixes, performance and security, we recommend using the latest Java SE release from Oracle.
Mac users: If you attempt to run PDS on a Mac without "Apple Java", the current behavior is to prompt you to install an additional (and required) instance of Java called Java for OS X. The benefit of installing Java for OS X is that you will be installing a Java Development Kit (JDK) that provides you the jarsigner and keytool commands to validate the PDS binary in a small footprint (~75 MB vs. ~300+ MB from Oracle). Though the Mac requires you to install the legacy Java for OS X, PDS will run inside the newer JVM you have installed.
- For more about Mac and Java, please see the Release Notes.
Installing and Starting PDS
To install PDS, please follow these steps:
1. Download the application from https://www.trustpds.com/get.php.
2. Extract the contents of the downloaded file; the result will be a new "PDS2" directory. Note that Mac may decompress the application as part of the download.
3. Move the PDS2 directory to:
Linux: /home/account/ Mac: /Applications/ Windows: C:\Users\Account\
Per the "Preparing to Install" section above, if you will be using both a USB flash drive and a Desktop instance of PDS on the same computer, you should configure the USB drive instance first. To configure the USB drive, copy the PDS application to your USB drive and start it first, as shown below. Once the USB instance is initialized, then start/initialize your Desktop instance of PDS.
4. Start PDS by executing (2x-clicking) either the startup script (Linux/Windows), the PDS Jar file (Linux/Windows) or the PDS Application (Mac):
Linux: /home/account/PDS2/ - pds-startup.sh or pds.jar Mac: /Applications/PDS2.app Windows: C:\Users\Account\PDS2\ - pds-startup.bat or pds.jar
Note that Mac may require you to approve PDS before it will run. If so, this may be done at via System Preferences -> Security and Privacy on the General tab.
For starting a Mac USB instance of PDS when running on Linux or Windows, please see the "Tips and Tricks" section of the Users Guide.
On startup, PDS will confirm that you accept the End User License Agreement (EULA) (Fig 2). Check the "I agree" checkbox and click the "OK" button.
The next dialog (Fig 4) seen at startup is the Welcome dialog. This dialog describes the current configuration and provides a reference to the QuickStart documentation within the application. It is recommended that you read the QuickStart after clicking the "OK" button to dismiss the dialog.
Obtaining a PDS license is an important aspect of using this application. By obtaining a license, you become licensed to access the secure (TDEA) and highly secure (AES) encryption algorithms to protect your data.
PDS was developed to contain the full functionality set when delivered, but with selected functionality disabled. By obtaining and subsequently applying your PDS license, the features you have requested will be licensed and enabled within the application. For example, without importing a secure or highly secure license, PDS will only support data encryption using the DES algorithm. You will be able to generate Keys using the AES and TDEA algorithms, but you will not be able to use those Keys to protect your data within PDS. As the DES algorithm has not been considered secure for quite a while, the application as delivered (Basic) is recommended for evaluation purposes only.
For a comparison between PDS versions (Basic, Secure and Highly Secure), please see the latest PDS Feature Matrix.
Should you choose to purchase a PDS license, you will need to select the type(s) of Operating System (OS) on which PDS will be used. PDS has been tested on Linux, Mac and Windows. The PDS license you receive will enable support for data encryption using the algorithms supported by the type of release (Basic, Secure and High Security) on the desired OS version(s).
To obtain a PDS license, please visit the license page. Once you have obtained a PDS license, use the instructions below to import the license into your copy of PDS.
1. From within the PDS application, select Options -> Import License. Select the file chooser and navigate to the directory where you have saved your PDS license. Select that file (Figure 7).
2. The next dialog (Figure 8) will present the license information (Name, Email) and type of license (Security Mode, Operating System) selected. Review the information, acknowledge the terms and conditions, and click "Ok".
3. The license will be imported and PDS will have the newly licensed functionality (Figure 9).
4. You are now ready to protect your data using the secure and/or highly secure encryption algorithms. Before you do, please select the About dialog (Figure 10) to verify the licensed algorithm(s) and Operating System(s).
Create a KeyStore
Having fully digested the QuickStart, and registered your copy of PDS, you're almost ready to start encrypting. The two steps remaining are creating your Encryption Key, and creating a secure store for your Key(s) - a KeyStore. Let's begin with the KeyStore.
Select KeyStore -> New (or click the KeyStore icon on the tool bar). The Create New KeyStore dialog will pop-up (Figure 11).
You'll need to provide the name of the KeyStore and a complex (defined in the QuickStart) passphrase. Then select Create.
Congratulations, you've created a KeyStore (Figure 12).
Should you wish to edit the passphrase of your KeyStore, the KeyStore -> EditPassphrase option allows you to do so.
Should you wish to view the objects in your KeyStore, the KeyStore -> View option allows you to do so.
Create a Key
Now that we have a KeyStore created, it is time to populate it with an Encryption Key.
Select Key -> New (or click the Key icon on the tool bar). The Create New Encryption Key dialog (Figure 13) will pop-up.
Type in the Alias that will refer to the new Key.
Select the algorithm type (AES, 3DES, or DES) and size (in bits) of the new Key.
Type in a complex passphrase and confirmation passphrase for the new Key. Note that the Key passphrase may be the same as the KeyStore passphrase (and it is recommended; for simplicity, without loss of security).
Associate the Key with a KeyStore by clicking the File Chooser and selecting the KeyStore. Provide the passphrase for the KeyStore.
Set this Key as the Default Key. Having a default key simplifies the creation and encryption of files.
Select Create. Your KeyStore now holds one Encryption Key (Figure 14).
Select About. You now have defined your Default Encryption Key and KeyStore (Figure 15).