At first login a wizard will open which guides through the creation of a key pair for encrypting and decrypting files. This pair comes with a private (secret) key and a public (not secret) key.
While the public key will be saved in the server's database ("anybody may encrypt files for me"), the private key must be kept secret ("only I may decrypt files").
After the welcome screen you choose the key storage, where your keys will be saved.
The select box provides all available key storages, as they were set up by the administrator.
Depending on the system settings you can choose if and where the private key is saved and how you want the decryption to be performed. This depends on your security requirements and possibilities:
| Description | Usability | Security | ||
|---|---|---|---|---|
| Your Computer/Device | The private key is stored in the browser local storage (similar to a cookie) |  |  | |
| External Key/Smartcard | The private key is available through an external process running on the client machine. Then the browser can only request decryption.
| | | |
| Manual input for each download | When downloading an E2EE file, the private key has to be copy/pasted into a browser form. The key is never saved in the browser. | | | |
| Local decryption | The E2EE file is downloaded locally and a secondary tool is required to decrypt (E2EE Reader). The E2EE Reader supports both file and Smart Card decryption (currently Windows only). The key is never saved in the browser. | / | |
For the External Key/Smartcard key storage, a key server URL has to be provided. In most cases this will be the default value http://localhost:9080.
By clicking the Test Connection button you will receive a message whether the key server was found or not. You will be asked to register your Smartcard when it had been found.
An additional button Connection Info will show up which either opens the key server's status information or a browser error page, in case the key server did not respond.
Except of the variant External Key/Smartcard, where the key is retrieved from the hardware, in any other keys a new key pair will be generated.
The public key will be uploaded to the server's database, the private key is show in the next step.
From now on you are able to create or read end-to-end encrypted files.
Be sure to save the private key and store it at a secure location (e.g. in a safe). Make a backup of this key. Without the private key you cannot open any files, e.g. when the web browser was reinstalled. The private key is never sent to the server. The private key cannot be restored. In case this key is lost, you have to create a new one. However, you only can access files encrypted for your old key when
|
After you are done with the wizard, the key management is always available in your Personal Settings - section Security |
Click Yes, take me there to find the section Security in your Personal Settings.
User can have multiple private keys assigned to their accounts i.e. for multiple devices. Files uploaded into one of their encrypted folders will automatically be encrypted for ALL of their private keys. |
Both storage options require, that your public key is available on the server. It will be used for encrypting files.
In the Security section of your Personal settings you find a text area:
You might already have keys when
Files will be decrypted on the fly. No interaction is required.
The key server pops up a notification that you are about to decrypt a file. You must confirm the decryption.
When re-encrypting a folder you will be asked for a confirmation as well.
Every time you want to open an encrypted file the browser opens a modal window where you have to provide your private key.
The file is decrypted in the browser only, the private key is never sent to the server.
The raw E2EE file will be downloaded. You need the E2EE Reader to be able to decrypt those files.