On Wed, Jan 25, 2017 at 12:21:09PM +0200, Otto Kekäläinen wrote:
> I am sorry but we have basically been forbidden from using OpenSSL in
> Debian due to license reasons:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761911
>
> If you can get somebody to change their opinion, then we could us
2017-01-25 12:10 GMT+02:00 Matthew Sackman :
> On Wed, Jan 25, 2017 at 09:44:00AM +0200, Otto Kekäläinen wrote:
>> Ok, this is now figured out.
>>
>> To activate YaSSL you must have 'ssl=on' in the config and no
>> ssl_cipher defined.
>
> Erm, ok, but this is somewhat terrifying - I can't disable i
On Wed, Jan 25, 2017 at 09:44:00AM +0200, Otto Kekäläinen wrote:
> Ok, this is now figured out.
>
> To activate YaSSL you must have 'ssl=on' in the config and no
> ssl_cipher defined.
Erm, ok, but this is somewhat terrifying - I can't disable insecure and
broken ciphers? I basically would conside
Ok, this is now figured out.
To activate YaSSL you must have 'ssl=on' in the config and no
ssl_cipher defined.
50-server.cnf: ssl=on
=>
MariaDB [(none)]> SHOW VARIABLES LIKE '%ssl%';
+-+-+
| Variable_name | Value |
+-+
2017-01-15 11:49 GMT+02:00 Matthew Sackman :
> Hello,
>
> Thank you for your reply. I have read through the links you provided,
> though I'm afraid I'm still unable to fix this.
>
> I have ssl-ciphers set in my config, and I have even modified the init
> script so that --ssl is passed to mysql (tho
Hello!
Thanks for reporting. MariaDB 10.1 is built with a bundled YaSSL. I
don't directly see why you don't see the ciphers. Thanks if you can
help with bugging.
This issue might also be of interest as it explains why we have YaSSL
instead of OpenSSL:
https://bugs.debian.org/cgi-bin/bugreport.cgi
6 matches
Mail list logo
