clean up encryption key generation #2

Closed
opened 2007-04-24 02:28:55 +00:00 by warner · 1 comment

The spec calls for consistent encryption. The use case calls for optional per-user encryption keys. We could even just generate random ones each time we go to upload a file.

The implementation is currrently stubbed out to use a key of all zeros.

The spec calls for consistent encryption. The use case calls for optional per-user encryption keys. We could even just generate random ones each time we go to upload a file. The implementation is currrently stubbed out to use a key of all zeros.
warner added the
major
defect
labels 2007-04-24 02:28:55 +00:00
Author

Fixed, now we're creating deterministic keys. Needs some tests, though.

Fixed, now we're creating deterministic keys. Needs some tests, though.
warner added the
fixed
label 2007-04-26 01:34:19 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#2
No description provided.