From: plan9fans@ntlworld.nospam.com
To: 9fans@cse.psu.edu
Subject: [9fans] confusion re auth and cpu
Date: Fri, 5 Mar 2004 16:53:03 +0000 [thread overview]
Message-ID: <61139cdd71fe9cb1943f4a4a676ea91c@snellwilcox.com> (raw)
Hi,
I don't understand quite what is happening here.
I have an account steve on my machine. I have run the cpu and
keyfs listners so I can cpu to this machine.
Now I cpu to one of the 9grid machines - where I am known as
steve.simon.
term% cat /dev/user
steve
term% cpu -h g.grid.bell-labs.com
cpu% bind /mnt/term/net /net
cpu% cpu larch.snellwilcox.com
term% cat /dev/user
steve.simon
term%
IE. I have come back to my machine, authenticated via the auth server on
a.grid.bell-labs.com - though I don't know how, only to appear as somone
else and of no-longer the owner of my files.
How did I authenticate for this reverse connection?
If I had the same username at both end would I have
rights to my files? (and should I have?)!
confused
-Steve
next reply other threads:[~2004-03-05 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 16:53 plan9fans [this message]
2004-03-05 17:06 ` andrey mirtchovski
2004-03-06 1:17 David Presotto
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=61139cdd71fe9cb1943f4a4a676ea91c@snellwilcox.com \
--to=plan9fans@ntlworld.nospam.com \
--cc=9fans@cse.psu.edu \
/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).