Some users are requesting that we implement key rotation for file_key_management plugin.

I'm not sure that it's practical. How would key rotation work in file_key_management plugin? The plugin has some serious limitations that would likely make it impractical to implement key rotation. Some open questions are listed below.

Generation of New Key Versions

How would new key versions be generated?

The file_key_management plugin currently doesn't generate any encryption keys itself, and it doesn't even have a backend KMS to generate encryption keys for it either.

With file_key_management plugin, any encryption keys currently need to be generated by the user with external tools, such as openssl. For example:

-- Generate a new 256-bit key

openssl rand -hex 32

And then the keys currently need to be manually saved to the key file.

See here:

https://mariadb.com/kb/en/library/file-key-management-encryption-plugin/#creating-the-key-file

Some possibilities:

• Would the user still have to manually generate the new key versions, and then manually save them to the key file?

• Would we implement a UDF in the file_key_management plugin that can be used to generate random keys, and a UDF that can save a key version to a key file? For example:

-- Generate a new 256-bit key

SELECT file_key_management_generate_key(256);

-- Write key to key file as key_version 2 of key ID 1

SELECT file_key_management_save_key_version(1, 2, '8ceb3336fa2a4bfacced7ea5dae17f246d93da44890386e2ce178453c4e9ba9e');

Format of Key File

How would the format of the key file change to allow different key versions of the same key ID?

The format of file_key_management plugin's key file is pretty simplistic. It simply stores encryption keys in a plain-text file that uses the format.

<encryption_key_id1>;<hex-encoded_encryption_key1>

<encryption_key_id2>;<hex-encoded_encryption_key2>

For example, if we had two keys with key ID 1 and 2, then the key file could look like this:

1;5d5f14b7262b8281e7d8bf17e53079c77f943b0a777659e14f368820975f4f34

2;c3ff5b5d1ae78a7898539db984df20b43d13bfb4de11a80cd0d1082845209222

This format currently has no way to store different versions of the same encryption key. However, this is something that it would need to support in order to support key rotation.

It's possible that we could extend the format, but it could get very ugly. For example:

<encryption_key_id1>;<encryption_key_id1_version1>;<hex-encoded_encryption_key1_version1>

<encryption_key_id1>;<encryption_key_id1_version2>;<hex-encoded_encryption_key1_version2>

...

<encryption_key_id1>;<encryption_key_id1_versionN>;<hex-encoded_encryption_key1_versionN>

<encryption_key_id2>;<encryption_key_id2_version1>;<hex-encoded_encryption_key2_version1>

<encryption_key_id2>;<encryption_key_id2_version2>;<hex-encoded_encryption_key2_version2>

...

<encryption_key_id2>;<encryption_key_id2_versionN>;<hex-encoded_encryption_key2_versionN>

For example, if we had two key versions of two different keys with key ID 1 and 2, then the key file could look like this:

1;1;5d5f14b7262b8281e7d8bf17e53079c77f943b0a777659e14f368820975f4f34

1;2;8ceb3336fa2a4bfacced7ea5dae17f246d93da44890386e2ce178453c4e9ba9e

2;1;c3ff5b5d1ae78a7898539db984df20b43d13bfb4de11a80cd0d1082845209222

2;2;f737cf391194d68c1a9c96b3d340e0b07464889171c061dd9cb95d3d61c765f2

Reloading Key Versions

If we decide that new key versions need to be manually generated, then how would the file_key_management plugin reload the new key versions?

Some possibilities:

• file_key_management plugin currently only parses the key file at startup. Would we still want to require a server restart to reload keys?

• Would we want to implement some FLUSH command? For example:

FLUSH ENCRYPTION KEYS;

• Would we want to implement some UDF? For example:

SELECT file_key_management_reload_keys();

Similar functionality in other databases?

Is there similar functionality in other databases that we could use as inspiration?

Users migrating from Oracle might have used Oracle Wallet:

https://docs.oracle.com/en/database/oracle/oracle-database/12.2/dbimi/using-oracle-wallet-manager.html