Automatic table/field encryption #26

Closed
opened 2018-10-07 22:19:28 +00:00 by jamie · 7 comments
jamie commented 2018-10-07 22:19:28 +00:00 (Migrated from git.hazaar.io)

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:

{
  "development": {
    "encrypt": { 
      "wholetable" : true,
      "othertable" : true,
      "mytable: [ "myfield1", "myfield2" ]
    }
  }
}

The above will encrypt the whole tables called wholetable and othertable, while the table mytable will only have two fields encrypted called myfield1 and myfield2.

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: ```json { "development": { "encrypt": { "wholetable" : true, "othertable" : true, "mytable: [ "myfield1", "myfield2" ] } } } ``` The above will encrypt the whole tables called `wholetable` and `othertable`, while the table `mytable` will only have two fields encrypted called `myfield1` and `myfield2`.
jamie commented 2018-10-07 23:09:59 +00:00 (Migrated from git.hazaar.io)

changed the description

changed the description
jamie commented 2018-10-07 23:10:15 +00:00 (Migrated from git.hazaar.io)

changed the description

changed the description
jamie commented 2018-10-07 23:10:39 +00:00 (Migrated from git.hazaar.io)

changed the description

changed the description
jamie commented 2018-10-08 02:36:26 +00:00 (Migrated from git.hazaar.io)
created branch [`26-automatic-table-field-encryption`](https://git.hazaarlabs.com/hazaar/hazaar-dbi/compare/master...26-automatic-table-field-encryption)
jamie commented 2018-10-08 02:36:30 +00:00 (Migrated from git.hazaar.io)

mentioned in merge request !5

mentioned in merge request !5
jamie commented 2018-10-08 05:39:04 +00:00 (Migrated from git.hazaar.io)

closed via commit 1f56b5c2ba

closed via commit 1f56b5c2ba8f77d3da320898f6b05519a1a1a28e
jamie commented 2018-10-08 05:39:04 +00:00 (Migrated from git.hazaar.io)

closed via merge request !5

closed via merge request !5
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: hazaar/hazaar-dbi#26
No description provided.