Encrypter-X User Guide
Managing & Using Vaults
|
Different vaults can be defined for different projects and the relationship between the vault location, the workspace and the files involved must be specified for each vault. The function for this can be reached via the main menu item Accessories and the menu item Vaults ▶ Manage ... can be reached. |
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
When the vault is closed, first a backup of the current vault contents is created so that the last state is still available in case something should go wrong. Then the currently selected key is used to encrypt the files in the workspace and transfer them to the vault. After that, a cleaning of the size of ten times the workspace size is performed on the drive where the workspace is located. However, before the vault is closed, it is monitored whether there are still enough unused keys in the key bundle, because each file is encrypted with its own, different key and it is additionally checked whether the keys are long enough to encrypt all files without repeating the byte sequence of the key. |
||||||||||||
|
||||||||||||
If some data is larger than the maximum key length from the current key bundle, it is the user's responsibility to decide whether to select a different key bundle first or to perform encryption with the current key bundle anyway. If the current key bundle is already relatively large and some files are only a little larger, it is actually no problem to cyclically extend the key used in these cases. However, if you are very particular about OTP and want to be absolutely sure that the data is encrypted without being decrypted, you have to generate or select a new key bundle whose keys are long enough to encrypt even the largest of the files without being extended. If a vault is open and the application is to be closed, the user must first confirm that the application can be closed even if the vault is open. This is to prevent data that should actually be kept under lock and key from accidentally remaining unencrypted in the workspace. |
||||||||||||
|
||||||||||||
Double-clicking with the left mouse button on the closed vault door opens the safe. However, this only works if the defined workspace is completely empty. After closing a vault, the unencrypted files and folders are removed from the workspace and the workspace must remain empty until the files are decrypted again. When trying to open the vault if new files have been copied to the workspace in the meantime, the user receives an error message and must first empty the workspace again. |
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
|
||||||||||||
To edit an existing vault use the button . It is activated when one of the opened vaults is selected in the list. Then the specifications of this vault can be changed. |
||||||||||||
|
||||||||||||
Workspaces can be added and removed using the and functions. At least one workspace must be defined and the workspaces must not be located in the root directory of a medium. This is monitored during selection. |
||||||||||||
|
||||||||||||
|
||||||||||||
|