[MDEV-26797] unknown variable 'file_key_management_filename=C:/Program Files/MariaDB 10.4/data/key_maria_nbc.txt' Created: 2021-10-11  Updated: 2021-11-15  Resolved: 2021-11-15

Status: Closed
Project: MariaDB Server
Component/s: Encryption
Affects Version/s: 10.4.20
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: febriyant Assignee: Sergei Golubchik
Resolution: Not a Bug Votes: 0
Labels: encryption, key_management, need_feedback
Environment:

Windows Server 2016

Attachments: Text File mysql_error.log    

 Description   

I already install mariadb version 10.4.20
and add config for encryption

plugin-load-add = file_key_management
 
file_key_management_filename = C:/Program Files/MariaDB 10.4/data/key_maria_nbc.txt
 
file_key_management_encryption_algorithm = AES_CTR
 
innodb-encrypt-tables

but I got this error message 

2021-10-11 14:07:23 0 [ERROR] C:\Program Files\MariaDB 10.4\bin\mysqld.exe: Error while setting value 'AES_CTR' to 'file-key-management-encryption-algorithm'
 
2021-10-11 14:07:23 0 [ERROR] Parsing options for plugin 'file_key_management' failed.
 
2021-10-11 14:07:23 0 [ERROR] InnoDB: cannot enable encryption, encryption plugin is not available
 
2021-10-11 14:07:23 0 [ERROR] Plugin 'InnoDB' init function returned error.
 
2021-10-11 14:07:23 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
 
2021-10-11 14:07:23 0 [Note] Plugin 'FEEDBACK' is disabled.
 
2021-10-11 14:07:23 0 [ERROR] C:\Program Files\MariaDB 10.4\bin\mysqld.exe: unknown variable 'file_key_management_filename=C:/Program Files/MariaDB 10.4/data/key_maria.txt'



 Comments   
Comment by Sergei Golubchik [ 2021-10-13 ]

please, provide the complete error log

Comment by febriyant [ 2021-10-15 ]

I already attach for error log

Comment by Sergei Golubchik [ 2021-11-15 ]

Sorry, missed that.

The documentation says

The recommended algorithm is AES_CTR, but this algorithm is only available when MariaDB is built with recent versions of OpenSSL. If the server is built with wolfSSL or yaSSL, then this algorithm is not available. See TLS and Cryptography Libraries Used by MariaDB for more information about which libraries are used on which platforms.

And if you follow the link, you'll see that MariaDB on Windows is linked with yaSSL or wolfSSL (depending on MariaDB version). That is, AES_CTR is not available in MariaDB on Windows

Generated at Thu Feb 08 09:48:01 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.