public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chris@wirex.com>
To: David Howells <dhowells@warthog.cambridge.redhat.com>
Cc: 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, 9 May 2003 11:39:16 -0700	[thread overview]
Message-ID: <20030509113916.A29208@figure1.int.wirex.com> (raw)
In-Reply-To: <552.1052502290@warthog.warthog>; from dhowells@warthog.cambridge.redhat.com on Fri, May 09, 2003 at 06:44:50PM +0100

* David Howells (dhowells@warthog.cambridge.redhat.com) wrote:
> 
> 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?

thanks,
-chris
-- 
Linux Security Modules     http://lsm.immunix.org     http://lsm.bkbits.net

  reply	other threads:[~2003-05-09 18:27 UTC|newest]

Thread overview: 6+ 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 15:39   ` Bryan Henderson
2003-05-09 17:44   ` David Howells
2003-05-09 18:39     ` Chris Wright [this message]
2003-05-09 20:06       ` David Howells

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=20030509113916.A29208@figure1.int.wirex.com \
    --to=chris@wirex.com \
    --cc=arjanv@redhat.com \
    --cc=dhowells@redhat.com \
    --cc=dhowells@warthog.cambridge.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