The TLS library mesalink is no longer being developed. It seems the continuation is now called TabbySSL.
Mesalink has not seen a source code change in over a year.
I propose we drop support for Mesalink because of this. Someone interested could try tabbyssl with the same backend code, or if the OpenSSL API really is good enough, the regular OpenSSL backend code could be used with tabbyssl!
The TLS library mesalink is no longer being developed. It seems the continuation is now called TabbySSL.
Mesalink has not seen a source code change in over a year.
I propose we drop support for Mesalink because of this. Someone interested could try tabbyssl with the same backend code, or if the OpenSSL API really is good enough, the regular OpenSSL backend code could be used with tabbyssl!