...
the ammount of registered users.
Key Storage Options
The handling of the private key is - from a security perspective - the most important part. The private key must be kept safe but still be used when you want to decrypt data.
There is a clear tradeoff between security and usability, depending on which option you want:
| Description | Usability | |
|---|---|---|
| Local Storage | The private key is stored in the browser local storage (similar to a cookie) |  |
| Key Server | The private key is available thorugh an external process running on the client machine. The Browser has only request decryption | |
| Ask | When downloading a e2ee file, the privat key has to be copy/pasted into a browser form. The key is not saved. | |
| Download only | The e2ee file is downloaded locally and a second tool is required to decrypt (e2ee reader) | / |
General info about security:
- Even with access to a server backup no data can be decrypted (you need a private key)
- Access to a private key only allows to decrypt that users data
- When a private key is removed, all decryptable information is purged from the server (i.e. even if recovered, it cannot be used to decrypt data any more)
Multiple Keys
Per default, every user can only have one public key assigned to him. This is a security feature. If you want users to have multiple keys (i.e. one for each of their device or for backup purposes) you can enable this option.
Report
You can generate an admin report which will be mailed to the current users email address. This includes the current license information and the used licenses.