CEPH filesystem development
 help / color / mirror / Atom feed
From: "Matt W. Benjamin" <matt@linuxbox.com>
To: Sage Weil <sweil@redhat.com>
Cc: "Christopher R. Hertel" <crh@redhat.com>,
	ceph-devel@vger.kernel.org, Gregory Farnum <greg@inktank.com>
Subject: Re: Ceph authentication/authorization paradignms
Date: Thu, 21 Aug 2014 12:44:22 -0400 (EDT)	[thread overview]
Message-ID: <1335181891.101.1408639462374.JavaMail.root@thunderbeast.private.linuxbox.com> (raw)
In-Reply-To: <197304281.99.1408639382605.JavaMail.root@thunderbeast.private.linuxbox.com>

Sorry, s/RPCSEC_GSS/RPCSEC_GSSv3/.

----- "Matt W. Benjamin" <matt@linuxbox.com> wrote:

> This approach/family of approaches is certainly the one taken by all
> classical Kerberized file sharing systems, including AFS, DCE, and
> NFSv4.
> 
> There's a lot of new work just coming to fruition now in both the AFS
> and NFSv4 communities (rxgk and RPCSEC_GSS, respectively) that are
> specifically designed to handle important next-generation multi-party
> authorization scenarios, and which I think we would be wise to at
> least have a look at.
> 
> Regards,
> 
> Matt
> 
> > > 
> > > Right. But you'll either need to plug Kerberos into the
> > client<->mon
> > > authentication pathways, or (this would be my naive choice) have
> > some
> > > sort of agent that Kerberos authenticates and then gives the
> client
> > > its CephX shared secret for authenticating with the monitors
> > (without
> > > the users having to get involved). Either way, there's at least a
> > > little CephX integration going on, right?
> > > Or am I completely off the mark with what you're trying to do
> here?
> > 
> > My thought is the former.  We'd add a new CEPH_AUTH_* type, the
> client
> > 
> > side would call into kerberos and get a kerberos ticket to pass to
> the
> > 
> > mon, and the mon would call into kerberos to authenticate it.  That
> > would 
> > authenticate the session.
> > 
> > I assume there will then be some futzing around to make things
> behave
> > so 
> > that the mon will provide the client cephx tickets for interactions
> > with 
> > the rest of the cluster so that *only* the mon is doing non-cephx 
> > authentication.  The focus now is just to make the first step work,
> 
> > though...
> > 
> > sage
> > --
> > To unsubscribe from this list: send the line "unsubscribe
> ceph-devel"
> > in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> -- 
> Matt Benjamin
> The Linux Box
> 206 South Fifth Ave. Suite 150
> Ann Arbor, MI  48104
> 
> http://linuxbox.com
> 
> tel.  734-761-4689 
> fax.  734-769-8938 
> cel.  734-216-5309 
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel"
> in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Matt Benjamin
The Linux Box
206 South Fifth Ave. Suite 150
Ann Arbor, MI  48104

http://linuxbox.com

tel.  734-761-4689 
fax.  734-769-8938 
cel.  734-216-5309 

  reply	other threads:[~2014-08-21 16:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1288213759.97.1408639348899.JavaMail.root@thunderbeast.private.linuxbox.com>
2014-08-21 16:43 ` Ceph authentication/authorization paradignms Matt W. Benjamin
2014-08-21 16:44   ` Matt W. Benjamin [this message]
2014-08-21 17:56   ` Christopher R. Hertel
2014-08-28 17:55     ` Matt W. Benjamin
     [not found] <1642211910.31382003.1408036197918.JavaMail.zimbra@redhat.com>
2014-08-14 17:10 ` Christopher R. Hertel
2014-08-19 21:57   ` Gregory Farnum
2014-08-20 22:20     ` Christopher R. Hertel
2014-08-21 15:59       ` Gregory Farnum
2014-08-21 16:02         ` Sage Weil
2014-08-21 17:51           ` Christopher R. Hertel

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=1335181891.101.1408639462374.JavaMail.root@thunderbeast.private.linuxbox.com \
    --to=matt@linuxbox.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=crh@redhat.com \
    --cc=greg@inktank.com \
    --cc=sweil@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