Improve encryption for sensitive data in db #5
Labels
No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: eelke/IdentityShroud#5
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Use simple binary storage
Probable need some rule that sizes can become variable length in the future by having first n bytes have highest bit set.
We might want to do AAD later on, this will be a new version so that could easily allow an extra size and field. If we want it
really future proof we could start with a bit mask.
With each key store
In future maybe other parameters