CEPH filesystem development
 help / color / mirror / Atom feed
From: Willem Jan Withagen <wjw@digiware.nl>
To: Marcus Watts <mwatts@redhat.com>,
	Yehuda Sadeh-Weinraub <yehuda@redhat.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: ceph + -lssl
Date: Sat, 27 Feb 2016 13:49:08 +0100	[thread overview]
Message-ID: <56D19B44.9080005@digiware.nl> (raw)
In-Reply-To: <20160227075001.GA21701@degu.b.linuxbox.com>

On 27-2-2016 08:50, Marcus Watts wrote:
> On Fri, Feb 26, 2016 at 12:43:24PM -0800, Yehuda Sadeh-Weinraub wrote:
>> I rebased these 4 commits on top of a recent master, and here's the
>> new pull request:
>> https://github.com/ceph/ceph/pull/7825
>>
>> On Tue, Feb 23, 2016 at 9:09 PM, Marcus Watts <mwatts@redhat.com> wrote:
>>> I've been working on better integrating ssl int ceph.
> ...
> 
> Thanks Yehuda for doing this.
> 
> Matt pointed out in the pull request that cmake builds were failing
> on this branch.  I've pushed a commit to fix that.

I know I'm not doing the work, but would it be possible to base the work
on for example LibreSSL from OpenBSD or BoringSSL from Google.

From the things I've seen and read about it, these libraries are (good)
attempts to shed a lot of cruft of openssl resulting in a compacter and
better build lib.

Next to the history of OpenBSD which is "not all that bad" for security.
And I'd expect Ceph to only use the more modern parts of the lib, and
thus historical compatibility is not that important here.
--WjW



  reply	other threads:[~2016-02-27 12:49 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 [this message]
2016-03-01  1:31       ` Marcus Watts
2016-03-02 22:58         ` Kyle Bader
2016-03-03 12:55           ` Willem Jan Withagen

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=56D19B44.9080005@digiware.nl \
    --to=wjw@digiware.nl \
    --cc=ceph-devel@vger.kernel.org \
    --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