From: David Howells <dhowells@warthog.cambridge.redhat.com>
To: Chris Wright <chris@wirex.com>
Cc: David Howells <dhowells@cambridge.redhat.com>,
Christoph Hellwig <hch@infradead.org>,
David Howells <dhowells@redhat.com>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
arjanv@redhat.com, viro@parcelfarce.linux.theplanet.co.uk,
drepper@redhat.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC] New authentication management syscalls
Date: Fri, 09 May 2003 21:06:46 +0100 [thread overview]
Message-ID: <2973.1052510806@warthog.warthog> (raw)
In-Reply-To: <20030509113916.A29208@figure1.int.wirex.com>
> > I think this might be a better idea than the name of a mountpoint as it
> > would then be possible to set the tokens prior to mounting, maybe so that
> > you _can_ mount.
> >
> > I'm thinking a bit of samba here, where authentication information needs
> > to be passed upon mounting (workstation/domain, username, password).
>
> How does this map up with Viro's idea of a two stage mount. IIRC, it
> was someting akin to:
>
> fsfd = open(/dev/fs_type/ext2)
> write(fd, "device and options, potentially including auth...");
> mntfd = open("mntpt");
> newmount(fd, mntfd, MNT_ATTACH);
>
> or something like that. Wouldn't that give you a free form abiility to
> talk to the fs driver and authenticate as needed? Is this plan still
> alive?
Then you end up with a copy of the token for every mountpoint, which may not
be what you want.
With my AFS client for instance, you want at most one token per cell per
PAG. Each cell contains potentially lots of volumes, and each volume is
mounted as a separate mount.
OTOH, with OpenAFS, you get one mount for everything and everyone, and that
contains all cells and all volumes, and so will almost certainly have the
tokens uploaded post-mount.
David
prev parent reply other threads:[~2003-05-09 19:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 13:11 [RFC] New authentication management syscalls David Howells
2003-05-09 13:31 ` Christoph Hellwig
2003-05-09 17:44 ` David Howells
2003-05-09 18:39 ` Chris Wright
2003-05-09 20:06 ` David Howells [this message]
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=2973.1052510806@warthog.warthog \
--to=dhowells@warthog.cambridge.redhat.com \
--cc=arjanv@redhat.com \
--cc=chris@wirex.com \
--cc=dhowells@cambridge.redhat.com \
--cc=dhowells@redhat.com \
--cc=drepper@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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