[MDEV-9061] Better diagnostics for unavailable AES_CTR would be useful Created: 2015-11-02  Updated: 2016-07-09

Status: Open
Project: MariaDB Server
Component/s: Encryption, Plugins
Affects Version/s: 10.1
Fix Version/s: 10.1

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Sergei Golubchik
Resolution: Unresolved Votes: 0
Labels: None


 Description   

Currently if file-key-management-encryption-algorithm is set to AES_CTR and the SSL library does not support it, the plugin fails to initialize with 

2015-11-02 16:00:31 139793997289312 [ERROR] /data/repo/git/10.1-bug/sql/mysqld: Error while setting value 'aes_ctr' to 'file-key-management-encryption-algorithm'
 
2015-11-02 16:00:31 139793997289312 [ERROR] Parsing options for plugin 'file_key_management' failed.

For example, it happens with the bundled YaSSL.

The limitation is documented, but it would be nice to have a clearer error message if possible.



 Comments   
Comment by Sergei Golubchik [ 2016-07-09 ]

That's a standard my_getopt error when you set an ENUM-style variable to an incorrect value. AES_CTR or FOO_BAR, doesn't matter. mysqld --help or INFORMATION_SCHEMA.SYSTEM_VARIABLES should show the list of valid values.

Generated at Thu Feb 08 07:31:50 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.