From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Authentication and "emu -d"
Date: Mon, 4 Jun 2001 07:56:35 -0400 [thread overview]
Message-ID: <20010604115636.BCBC019A01@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 141 bytes --]
If you want something running as a user that a system can't authenticate
as, you can always start it from cron instead of cpurc or listen.
[-- Attachment #2: Type: message/rfc822, Size: 2892 bytes --]
From: Lucio De Re <lucio@proxima.alt.za>
To: inferno@research.suspicious.org, 9fans mailing list <9fans@cse.psu.edu>
Subject: [9fans] Authentication and "emu -d"
Date: Mon, 4 Jun 2001 10:51:27 +0200
Message-ID: <20010604105127.C26399@cackle.proxima.alt.za>
Sorry about cross-posting, I'll try not to make a habit of it.
I would like to start Inferno services on my 3ed Plan 9 compute server
using "emu -d". Two things get in the way:
(a) the ID of the server is "proxima" not "inferno" and that means
that some facilities I previously set up are unavailable.
Authentication is one of these. If I can track down the
authentication keyfile, I may be able to change its permissions, but
that seems insecure _and_ requires me to put the fileserver in "allow"
mode, a mild pain. Is there a Plan 9 way of forcing "inferno" to
execute "emu" instead of "proxima", or should I resort to making
"inferno" the compute server owner (Plan 9 AUTH does not run on that
compute server, I still use 2ed AUTH)?
(hm: I did try auth/login - besides requiring to be interactive, it
complains about being run on a compute server :-(
OK, I have now reclassified the compute server so it is owned by
"inferno". I hope I don't have cause to regret this. Admittedly, it
does not seem important.
(b) The -d options is wrongly documented: it expects an argument, one
of 0, 1 or 2. It seems 1 works OK, but I'd like to know what the
other values do.
Also, starting "emu -d1" from cpurc seems to do ugly things to the
keyboard/input interface, the console no longer echoes. And output
should probably be redirected to a log file, too. Something for the
manual pages?
++L
next reply other threads:[~2001-06-04 11:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 11:56 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-04 10:06 forsyth
2001-06-04 10:36 ` Lucio De Re
2001-06-04 9:12 forsyth
2001-06-04 9:45 ` Lucio De Re
2001-06-04 8:51 Lucio De Re
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=20010604115636.BCBC019A01@mail.cse.psu.edu \
--to=presotto@plan9.bell-labs.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).