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 text was updated successfully, but these errors were encountered:
Mesalink has stopped development. We can no longer encourage use of it.
It seems to be continued under the name TabbySSL, but no attempts have
(yet) been to make curl support it.
Fixes#8188
Mesalink has ceased development. We can no longer encourage use of it.
It seems to be continued under the name TabbySSL, but no attempts have
(yet) been to make curl support it.
Fixes#8188Closes#8191
Mesalink has ceased development. We can no longer encourage use of it.
It seems to be continued under the name TabbySSL, but no attempts have
(yet) been to make curl support it.
Fixes#8188Closes#8191
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 text was updated successfully, but these errors were encountered: