-
Notifications
You must be signed in to change notification settings - Fork 36
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Create MariaDB encryption keys in buendia-mysql postinst.
- Loading branch information
Showing
2 changed files
with
26 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
81d4197
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the thinking behind having two separate keys (system and mysql)?
81d4197
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems to be a best practice recommended by the MariaDB documentation. I think the primary reasons are that MariaDB AES keys must be a specific length (64 bits) and that MariaDB is designed to permit multiple encryption keys to be registered. Their solution to having all the database secrets stored securely at rest is to encrypt them with a separate key.
https://mariadb.com/kb/en/file-key-management-encryption-plugin/#encrypting-the-key-file
I intend to write a project-wide document on the design of the encryption-at-rest and data theft prevention set up.