Bug #89239 Check if we still need the special handling of reads with yaSSL
Submitted: 15 Jan 2018 11:48 Modified: 9 Jul 2019 17:30
Reporter: Georgi Kodinov Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Errors Severity:S4 (Feature request)
Version:8.0+ OS:Any
Assigned to: CPU Architecture:Any

[15 Jan 2018 11:48] Georgi Kodinov 
Description:
Currently we have two different versions of vio_ssl_read: one blocking one for yaSSL/wolfSSL and one non-blocking one for openssl.
Consider if we still need the two versions with wolf and remove as appropriate

How to repeat:
 grep -ri --exclude-dir=.git --exclude-dir=bld --exclude-dir=wolfssl* --exclude-dir=generated yassl and observe:
vio/viossl.cc:  // YASSL maps ETIMEOUT to EWOULDBLOCK and hence no need for retry here.
vio/viossl.cc:    Since yaSSL does not support non-blocking send operations, use

Suggested fix:
Preferably remove two vio_ssl_read() versions.
If that's not applicable remove all mentions of yaSSL and replace them with wolfSSL with an updated explanation.
[9 Jul 2019 17:30] Paul DuBois 
Posted by developer:
 
This is a yaSSL issue. yaSSL support is removed as of MySQL 5.6.46/5.7.28, so this bug is being closed with no action taken.