From: Latchesar Ionkov <lucho@ionkov.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] v9fs question
Date: Tue, 14 Jul 2009 08:33:43 -0600 [thread overview]
Message-ID: <f158dc670907140733n153c39b4jed63ee3337a31823@mail.gmail.com> (raw)
In-Reply-To: <140e7ec30907140034j5a206e44oc36cc19fa805d63c@mail.gmail.com>
Hmm, I don't understand how this works. v9fs should issue its own
Tversion and Tattach and discard the previously authenticated session,
right? Or I am missing something?
Thanks,
Lucho
On Tue, Jul 14, 2009 at 1:34 AM, sqweek<sqweek@gmail.com> wrote:
> 2009/7/13 Latchesar Ionkov <lucho@ionkov.net>:
>> On Mon, Jul 13, 2009 at 2:24 AM, sqweek<sqweek@gmail.com> wrote:
>>> Anyway, note that if you auth you'll need supporting software from
>>> p9p also. Factotum and srv -a, in particular, then give v9fs a -o
>>> trans=unix.
>>
>> I don't think that auth is working with v9fs at all. The auth support
>> got dropped accidentally with some of the changes, probably when
>> access=user|any|<uid> was introduced. I.e. my fault.
>
> I didn't realise v9fs ever had auth support. Here is how I've been
> getting an authenticated mount for years:
>
> # create mountpoint
> $ n=$HOME/n
> $ mkdir -p $n/wren
>
> # need factotum running to do the dirty work
> $ factotum
>
> # srv -a posts a pre-authenticated socket in the p9p ns directory
> # wren is my fileserver
> $ srv -a wren
> !adding key: role=client proto=p9sk1 dom=sqweek.dnsdojo.org
> user[sqweek]:
> password:
>
> $ 9mount -i 'unix!/tmp/ns.sqweek.:0/wren' $n/wren
> (or)
> $ mount -t 9p -o uname=sqweek,trans=unix,noextend,dfltuid=$(id
> -u),dfltgid=$(id -g) /tmp/ns.sqweek.:0/wren $n/wren
> # I'm not sure if uname is strictly necessary
>
> $ 9bind $n/wren/home/sqweek/mail $HOME/sqweek/mail
> # various other binds
>
> Jorden mentioned it's a bad idea to let anyone mount anything because
> everyone shares the same namespace. 9mount does have some sanity
> checks for that environment, it will only let you mount over a
> directory you have write access to (and isn't sticky) or is under your
> home dir. Never really been field tested though :)
>
>> Adding the support we had before the access= support is probably easy,
>> but I would like to make it better and support authentication for
>> multiple users. Still no idea what is the correct way. :( Any
>> suggestions are welcome.
>
> Can't help you there - I'm not sure it makes sense to try and put
> factotum's functionality in the linux kernel... Is there some problem
> with the private namespace/individual user mount approach?
> -sqweek
>
>
next prev parent reply other threads:[~2009-07-14 14:33 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-11 18:46 Tim Newsham
2009-07-11 18:50 ` Eric Van Hensbergen
2009-07-11 19:03 ` Tim Newsham
2009-07-11 19:47 ` Eric Van Hensbergen
2009-07-11 20:03 ` J.R. Mauro
2009-07-12 3:19 ` Uriel
2009-07-13 8:24 ` sqweek
2009-07-13 8:51 ` hiro
2009-07-13 14:20 ` Eric Van Hensbergen
2009-07-13 20:44 ` hiro
2009-07-13 21:45 ` hiro
2009-07-13 22:05 ` Eric Van Hensbergen
2009-07-13 22:18 ` J.R. Mauro
2009-07-13 23:16 ` ron minnich
2009-07-13 23:22 ` Eric Van Hensbergen
2009-07-13 23:37 ` ron minnich
2009-07-13 23:47 ` Eric Van Hensbergen
2009-07-13 23:41 ` J.R. Mauro
2009-07-13 23:50 ` erik quanstrom
2009-07-14 0:00 ` J.R. Mauro
2009-07-14 0:06 ` erik quanstrom
2009-07-14 0:01 ` Eric Van Hensbergen
2009-07-14 0:08 ` ron minnich
2009-07-14 0:46 ` J.R. Mauro
2009-07-14 0:42 ` J.R. Mauro
2009-07-14 0:58 ` Eric Van Hensbergen
2009-07-14 1:28 ` Latchesar Ionkov
2009-07-14 1:35 ` Devon H. O'Dell
2009-07-14 2:05 ` Tim Newsham
2009-07-14 0:42 ` Tim Newsham
2009-07-14 0:50 ` erik quanstrom
2009-07-14 0:56 ` Eric Van Hensbergen
2009-07-14 4:51 ` lucio
2009-07-14 4:29 ` lucio
2009-07-14 4:26 ` lucio
2009-07-13 22:00 ` Eric Van Hensbergen
2009-07-14 19:05 ` sqweek
2009-07-14 20:11 ` Eric Van Hensbergen
2009-07-13 14:59 ` lucio
2009-07-13 15:04 ` Eric Van Hensbergen
2009-07-13 15:08 ` Latchesar Ionkov
2009-07-13 19:51 ` Tim Newsham
2009-07-14 7:34 ` sqweek
2009-07-14 11:08 ` roger peppe
2009-07-14 11:20 ` hiro
2009-07-14 12:48 ` Eric Van Hensbergen
2009-07-14 15:45 ` ron minnich
2009-07-14 16:31 ` Tim Newsham
2009-07-14 20:21 ` roger peppe
2009-07-14 13:10 ` Eric Van Hensbergen
2009-07-14 13:23 ` erik quanstrom
2009-07-14 14:26 ` Eric Van Hensbergen
2009-07-14 14:44 ` erik quanstrom
2009-07-14 14:33 ` Latchesar Ionkov [this message]
2009-07-14 14:54 ` Eric Van Hensbergen
2009-07-14 15:01 ` erik quanstrom
2009-07-14 15:13 ` Eric Van Hensbergen
2009-07-14 15:19 ` erik quanstrom
2009-07-14 15:37 ` Eric Van Hensbergen
2009-07-14 16:12 ` erik quanstrom
2009-07-14 16:19 ` Eric Van Hensbergen
2009-07-14 15:06 ` Latchesar Ionkov
2009-07-14 15:48 ` ron minnich
2009-07-14 15:59 ` Eric Van Hensbergen
2009-07-14 14:37 ` Latchesar Ionkov
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=f158dc670907140733n153c39b4jed63ee3337a31823@mail.gmail.com \
--to=lucho@ionkov.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).