From: Marcus Watts <mwatts@redhat.com>
To: ceph-devel@vger.kernel.org
Subject: ceph + -lssl
Date: Wed, 24 Feb 2016 00:09:12 -0500 [thread overview]
Message-ID: <20160224050912.GA6585@degu.b.linuxbox.com> (raw)
I've been working on better integrating ssl int ceph.
Currently, I have a branch, "wip-openssl" which I've pushed to
github, which builds using gitbuilder, also builds with cmake.
I haven't done much testing with this, so there may be some other
business (with certs and such) to make this actually useful.
commits to make this build:
1/ ba8bfab15255d4b321f200a617bc2e0335676482
automake: -lssl
2/ 5188536a6e42d9207d45dadc86700546ac12b1a2
cmake: ssl + crypto
3/ 96fe7c5745584158aa69223e3b2482fc9dcfc8fe
automake: -lssl -lcrypto (not just -lssl)
4/ a23e063a7db4780f120a2199db55ce5ae816b829
git: used fixed version of civetweb.
fixes a warning.
There are some additional commits in wip-openssl to support
build "out of tree". I'll post a separate message about that.
-Marcus Watts
next reply other threads:[~2016-02-24 5:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 5:09 Marcus Watts [this message]
2016-02-26 20:43 ` ceph + -lssl 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
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=20160224050912.GA6585@degu.b.linuxbox.com \
--to=mwatts@redhat.com \
--cc=ceph-devel@vger.kernel.org \
/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