Automatic table/field encryption #26
Labels
No labels
bug
confirmed
critical
discussion
documentation
Doing
enhancement
suggestion
support
To Do
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: hazaar/hazaar-dbi#26
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?
I had an idea about automatically encrypting fields or even whole tables (as in, all fields in a table). They can be configured somewhere like the
database.json
config file quite easily. Something like:The above will encrypt the whole tables called
wholetable
andothertable
, while the tablemytable
will only have two fields encrypted calledmyfield1
andmyfield2
.changed the description
changed the description
changed the description
created branch
26-automatic-table-field-encryption
mentioned in merge request !5
closed via commit
1f56b5c2ba
closed via merge request !5