From: Daniel Oliveira <doliveira@suse.com>
To: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Cephx kerberization support
Date: Tue, 23 Aug 2016 20:34:12 -0600 [thread overview]
Message-ID: <1472006052.10929.0.camel@suse.com> (raw)
Hi All,
We have been *brainstorming* on how to get "Cephx kerberization
support" done. From the initial ideas: a) GSSAPI based protocol; b)
Some sort of native Krb5 Cephx support, which means a need for a Krb5
authorizer along with some channel bindings (due to ULP principals),
where the latter seems to be a good/best approach.
As this is an important topic and we would like to discuss it during
our next CDM, your ideas and interest are greatly appreciated.
Thanks,
-Daniel
next reply other threads:[~2016-08-24 2:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 2:34 Daniel Oliveira [this message]
2016-09-01 19:41 ` Cephx kerberization support Sage Weil
2016-09-02 4:58 ` Marcus Watts
2016-09-02 14:14 ` Sage Weil
2016-09-02 17:26 ` Matt Benjamin
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=1472006052.10929.0.camel@suse.com \
--to=doliveira@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.