content_image/781056.jpg content_image/781066.jpg content_image/781063.jpg
table. To specify the default directory for the file explicitly if you are building from source, use the INSTALL_MYSQLKEYRINGDIR CMake  option. 

<img src='content_image/781056.jpg'>

At plugin startup, if the value assigned to keyring_encrypted_file_data  specifies a file that does not exist, the keyring_encrypted_file  plugin attempts to create it (as well as its parent directory, if necessary). 

If you create the directory manually, it should have a restrictive mode and be accessible only to the account used to run the MySQL server. For example, on Unix and Unix-like systems, to use the /usr/ local/mysql/mysql-keyring  directory, the following commands (executed as root ) create the directory and set its mode and ownership: 

cd /usr/local/mysql mkdir mysql-keyring chmod 750 mysql-keyring chown mysql mysql-keyring chgrp mysql mysql-keyring 

If the keyring_encrypted_file  plugin cannot create or access its data file, it writes an error message to the error log. If an attempted runtime assignment to keyring_encrypted_file_data results in an error, the variable value remains unchanged. 

<img src='content_image/781066.jpg'>

• keyring_encrypted_file_password 

## Important 

Once the keyring_encrypted_file  plugin has created its data file and started to use it, it is important not to remove the file. Loss of the file causes data encrypted using its keys to become inaccessible. (It is permissible to rename or move the file, as long as you change the value of keyring_encrypted_file_data  to match.) 

<img src='content_image/781063.jpg'>

