[MDEV-7450] file_example_key_management_plugin and example_key_management_plugin don't work with yassl Created: 2015-01-13  Updated: 2015-03-17  Resolved: 2015-03-17

Status: Closed
Project: MariaDB Server
Component/s: Encryption
Affects Version/s: 10.1.3
Fix Version/s: 10.1.4

Type: Bug Priority: Major
Reporter: Sergei Golubchik Assignee: Jan Lindström (Inactive)
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-7772 SIGSEGV on my_aes_encrypt_cbc when -D... Closed

 Description   

For some strange reason, when compiling with OpenSSL, more internal encryption functions are exported. These plugins use them directly. So, when compiled with YaSSL these symbols aren't available and plugins don't load.

We need to
1. consistently export or hide (preferrably) these symbols both with OpenSSL and YaSSL
2. export the encryption as a service for key management plugins to use or change plugins not to use it.

When fixed a workaround from plugins' CMakelIsts.txt files should be removed

 Comments   
Comment by Sergei Golubchik [ 2015-02-13 ]

I've fixed symbol visibility, but plugins still fail. jplindst, could you please take a look at that?

Comment by Jan Lindström (Inactive) [ 2015-03-17 ]

After

commit 5e6905bb7f1c80e5cc368bb917f6e15afc73a269
 
Author: Jan Lindström <jan.lindstrom@mariadb.com>
 
Date:   Tue Mar 17 10:59:25 2015 +0200
 
 
 
    Replace static usage of AES_CTR with current encryption algorithm.

Tests seem to work on openSSL with ctr, cbc and ecb modes and on yassl with cbc and ecb modes. Removed static ctr method usage from example_key_management_plugin.

I do not follow point 2. What should be done for that ?

Comment by Sergei Golubchik [ 2015-03-17 ]

Never mind, I'll do it later, it's only a cleanup.
This bug is only about "file_example_key_management_plugin and example_key_management_plugin don't work with yassl", so as long as they do it can be closed.

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