Date: Fri, 27 Oct 2017 19:24:30 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Ben Laurie <ben@links.org> Cc: Eric McCorkle <eric@metricspace.net>, "freebsd-security@freebsd.org security" <freebsd-security@freebsd.org>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: Crypto overhaul Message-ID: <13959.1509132270@critter.freebsd.dk> In-Reply-To: <CAG5KPzws=jmF2wLeEAz8Lzn7Ugude=0w5neoQjeDjYnGtJpS9Q@mail.gmail.com> References: <dc08792a-3215-611c-eb9f-4936a0d621f9@metricspace.net> <CAG5KPzws=jmF2wLeEAz8Lzn7Ugude=0w5neoQjeDjYnGtJpS9Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-------- In message <CAG5KPzws=3DjmF2wLeEAz8Lzn7Ugude=3D0w5neoQjeDjYnGtJpS9Q@mail.g= mail.com> , Ben Laurie writes: >OpenSSL includes (and is used for) lots of crypto that is not used in >SSL - since BearSSL targets SSL/TLS only, it can't, presumably, be >used to replace all uses of OpenSSL. Which implicitly raises the question if we really need all the boatloads of crap OpenSSL drags in, or if we would be in a better position with something simpler and saner ? -- = Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe = Never attribute to malice what can adequately be explained by incompetence= .
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?13959.1509132270>