Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.1.7
-
None
Description
There are many *-encrypt- options and they *all have to be enabled to prevent data leaks.
A possible solution could be a “meta-option” --encryption that would enable or disable all other encryption-related options.
Attachments
Activity
Field | Original Value | New Value |
---|---|---|
Fix Version/s | 10.1 [ 16100 ] |
Affects Version/s | 10.1.7 [ 19604 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | Stalled [ 10000 ] |
Component/s | Encryption [ 11200 ] | |
Fix Version/s | 10.1.8 [ 19605 ] | |
Fix Version/s | 10.1 [ 16100 ] | |
Resolution | Fixed [ 1 ] | |
Status | Stalled [ 10000 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 71422 ] | MariaDB v4 [ 149596 ] |
A much simpler solution is to provide a "preset" file, lilke
/etc/my.cnf.d/enable_encryption.preset
[mariadb]
aria-encrypt-tables
encrypt-binlog
encrypt-tmp-disk-tables
encrypt-tmp-files
loose-innodb-encrypt-log
loose-innodb-encrypt-tables
and let the user !include it into his my.cnf as needed.