From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] auth change? / auth for u9fs on a mac
Date: Mon, 4 Jul 2011 12:36:30 -0700 [thread overview]
Message-ID: <8C234322-65CF-438A-87BA-03EC3ED33644@9srv.net> (raw)
In-Reply-To: <42401a89b8a91e398df526dfedbcc1ea@quintile.net>
I do what you describe on several macs; it works fine. I haven't updated in a while, but what your describing is my understanding of the standard way to use p9any auth with u9fs. I use a special user created for this purpose as well.
On Jul 4, 2011, at 4:53, "Steve Simon" <steve@quintile.net> wrote:
> This is probably my finger trouble but just in
> case I am not going mad and sothing has changed
> in the last couple of months...
>
> I have a mac running u9fs (marlin).
>
> I don't like the idea of putting bootes password in /etc on the
> mac so I give it its own host owner and secret
>
> $ cat /etc/u9fs.conf
> random-secret
> mac-owner
> home.quintile.net
>
> then I have a factotum key of the form:
>
> hugo% grep mac-owner /mnt/factotum/ctl
> key proto=p9sk1 dom=home.quintile.net user=mac-owner !password?
>
> I am pretty sure this has worked for several years but now it is broken:
>
> hugo% srv -m marlin
> post...
> srv net!marlin!9fs: mount failed: authentication failed
>
> This should work shouldn't it?
>
> Is there another way to do this? I tried adding another
> clause to my secstore with a server=marlin tuple hoping that this
> would be chosen in preference to my default p9sk1 key but it didn't
> seem to work either.
>
> how do peple do this? Are you all happy to sprinkle bootes
> key onto unix machines (hard to believe)?
>
> -Steve
prev parent reply other threads:[~2011-07-04 19:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 11:53 Steve Simon
2011-07-04 12:14 ` Yaroslav
2011-07-04 19:36 ` Anthony Sorace [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=8C234322-65CF-438A-87BA-03EC3ED33644@9srv.net \
--to=a@9srv.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).