From: Willem Jan Withagen <wjw@digiware.nl>
To: Kyle Bader <kyle.bader@gmail.com>, Marcus Watts <mwatts@redhat.com>
Cc: Yehuda Sadeh-Weinraub <yehuda@redhat.com>,
ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: ceph + -lssl
Date: Thu, 3 Mar 2016 13:55:42 +0100 [thread overview]
Message-ID: <56D8344E.6060507@digiware.nl> (raw)
In-Reply-To: <CAFMfnwqfOs-VSUdS6kd=DM7TREi8GQze0nnv2SbSVM0ZEfU+Mg@mail.gmail.com>
On 2-3-2016 23:58, Kyle Bader wrote:
>> I looked at libressl a bit. It still has the same license emcumbrances
>> as openssl. So no real win there. And, since it's not packaged as part
>> of many linux distributions, the gpl/ssleay license incompatibility issue
>> becomes a real problem here. Hopefully a future version of libressl will
>> adopt a plain bsd license. I know they were working hard to discard
>> the crufty openssl build system, a good thing. When I worked with an
>> earlier version of openssl (adding a new hash or encryption algorithm,
>> I don't remember which today), I remember being disappointed at finding
>> internal interfaces that just assumed various max sizes of things. I hope
>> the libressl folks work on making those things better too.
>>
>> I'm not familiar with google's "boringSSL". Do you have some references
>> for it? I won't have the time to look at it right now - but I don't mind
>> learning at least a bit more about it. I see from wikipedia that it's
>> yet another fork of openssl - will they fix the license issue?
>>
>> I did look (mostly superficially) at,
>> botan libressl gnutls matrixssl mbed wolfssl cryptlib nss
>> & apple's "secure transport"
>> It was mostly superficial because my first question was "are there
>> a lot of other people using this" aka "am I going to be debugging
>> and supporting this myself"?
>
> BoringSSL
>
> https://boringssl.googlesource.com/boringssl/
>
> This might also be worth a look:
>
> https://github.com/awslabs/s2n
I myself have spoken to one of the people that works on integration of
LibreSSL in FreeBSD ports (he lives in town here). And yes he tells me
that it is a lot of work, but mainly because of the "liberties" that
openssl allows. And even though LibreSSL attempts to be a plugin
replacement, it are these edge corners which do work, but according the
API should not, that create the porting pain.
So that would be another argument of trying to see if you can hook this
in. I'm sure you will find odd bits and pieces that do not work as
expected. But in the end it will improve you code quality. Same feeling
I have trying to port to FreeBSD. 99,9% is compatible, and sometimes
Linuxisms creep in where the do not have to because POSIX is good enough.
But you are right, on occassion you will hit a wall and damage you nose.
On the other hand, I'm upgrading openssl in all environments I maintain
for the 3 or 4th time in 2 years, because of major bugs in openssl.
Doesn't say there are no bugs in the other implementations.
But it was just a things I was wondering when I saw the implementation
come by. And any implementation is beter than none. So thanx for doing
the work.
--WjW
prev parent reply other threads:[~2016-03-03 12:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 5:09 ceph + -lssl Marcus Watts
2016-02-26 20:43 ` Yehuda Sadeh-Weinraub
2016-02-27 7:50 ` Marcus Watts
2016-02-27 12:49 ` Willem Jan Withagen
2016-03-01 1:31 ` Marcus Watts
2016-03-02 22:58 ` Kyle Bader
2016-03-03 12:55 ` Willem Jan Withagen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56D8344E.6060507@digiware.nl \
--to=wjw@digiware.nl \
--cc=ceph-devel@vger.kernel.org \
--cc=kyle.bader@gmail.com \
--cc=mwatts@redhat.com \
--cc=yehuda@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox