Feature #65
closed
Added by Sancho Fock about 1 year ago.
Updated about 1 year ago.
Description
Do this for the session key as well as the DropKeys
Use the same password as for the client protection
- Due date set to 02/16/2024
- Start date changed from 10/18/2023 to 02/16/2024
- Follows Feature #64: Encrypt Session Keys in the Database added
- Due date changed from 02/19/2024 to 02/20/2024
- Target version changed from 0.6.x to 0.5.x
- Due date changed from 11/17/2023 to 11/21/2023
- Start date changed from 11/16/2023 to 11/20/2023
- Due date changed from 11/21/2023 to 11/22/2023
- Start date changed from 11/20/2023 to 11/21/2023
- Due date changed from 11/22/2023 to 11/20/2023
- Start date changed from 11/21/2023 to 11/17/2023
- Status changed from New to In Progress
- Status changed from In Progress to Rejected
- Target version changed from 0.5.x to open
This feature does not make sense. The client keys will be encrypted anyway if the password is set. so encrypting then again with the same password makes no sense.
However if this would be changed to a new feature to protect secure drops seperatly with another password, this could be done
Also available in: Atom
PDF