From: grarpamp <gra...@gm...> - 2017-02-20 19:49:54
|
On Mon, Feb 20, 2017 at 3:40 AM, Matthias Andree <mat...@gm...> wrote: > I will not support "old" libraries that have gone out of their > respective vendor's support (the 6.4.x branch refuses to build against I wouldn't either, it just holds you back. Though I meant 'designs / api of old libraries' can be hard to deal with. > as long as OpenSSL is alive. As long as any particular library is leading in use, well maintained, etc, and expected to continue that way. LibreSSL hasn't been around long enough compared to others to establish that. The OpenBSD spinoff projects are interesting though... smtp, bgp, ntp, ssl, ssh, ike, mandoc, etc. > https://blog.cloudflare.com/ietf-hackathon-getting-tls-1-3-working-in-the-browser-2/ I see, ok. https://github.com/bifurcation/mint https://tls13.cloudflare.com/ > https://www.wolfssl.com/wolfSSL/Docs-wolfssl-changelog.html Looks like it's just a WIP at the moment... https://github.com/wolfSSL/wolfssl/pull/661 > value, 0 "OK", 23 for "REJECT", anything else for "ERROR=DUNNO", or > possibly sysexits. I'm not familiar with use of 23 for that in sysexits(3) or intro(2), of course people often use locally defined codes as relavant to them. > Only their names suck. --sslcert vs. --sslcertfile? Uh. Not easily > changed unless you want to have duplicate names for the same option for > compatibility. I don't mind breaking backward compatibility in order to move forward with something better. |