From: Per Olofsson <pelle@dsv.su.se>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Paul Jakma <paul@clubi.ie>, nfs@lists.sourceforge.net
Subject: Re: NFSv3+Krb5 and mountd
Date: Mon, 30 Aug 2004 17:45:41 +0200 [thread overview]
Message-ID: <20040830154541.GA3671@nasse> (raw)
In-Reply-To: <20040830020132.GA28919@fieldses.org>
J. Bruce Fields:
> This doesn't fix the problem Per Olofsson describes, which is that
> unless you use nfsv4, there's no way to export to krb5 without also
> exporting vi auth_sys.
>
> Since mountd itself doesn't currently have rpcsec_gss support (and, on
> the client side, neither does mount), MOUNT requests are going to use
> auth_sys. So mountd is going to decide whether to respond based on
> their IP address.
>
> It'd seem that the right solution is to add rpcsec_gss support to mount
> and mountd, which shouldn't be a big project, so if you export only to
> krb5 then you also answer krb5-protected mount requests. I don't know
> whether other clients will like that, though.
OK, I understand. I don't really need authenticated mount requests
though, I only need authenticated file system accesses. In other
words, I don't care who mounts the file system as long as they can't
impersonate a user without a valid ticket. Is this easier to
implement? Does it have any other security implications?
--
Pelle
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-08-30 15:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-24 18:41 NFSv3+Krb5 and mountd Per Olofsson
2004-08-30 1:41 ` Paul Jakma
2004-08-30 2:01 ` J. Bruce Fields
2004-08-30 15:45 ` Per Olofsson [this message]
2004-08-30 16:45 ` Trond Myklebust
2004-08-30 17:17 ` J. Bruce Fields
2004-08-30 17:45 ` Trond Myklebust
2004-08-30 18:04 ` J. Bruce Fields
2004-08-30 22:25 ` Trond Myklebust
2004-09-02 15:39 ` J. Bruce Fields
2004-08-30 21:54 ` Per Olofsson
2004-08-30 21:25 ` Per Olofsson
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=20040830154541.GA3671@nasse \
--to=pelle@dsv.su.se \
--cc=bfields@fieldses.org \
--cc=nfs@lists.sourceforge.net \
--cc=paul@clubi.ie \
/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.