From: John Floren <slawmaster@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] a few Q's regarding cpu/auth server
Date: Thu, 6 Aug 2009 20:36:10 -0700 [thread overview]
Message-ID: <7d3530220908062036j149ca98djf90932e10beec4e7@mail.gmail.com> (raw)
In-Reply-To: <8F852AD3-7E7D-4731-9AC6-598092D81427@storytotell.org>
On Thu, Aug 6, 2009 at 8:04 PM, Daniel Lyons<fusion@storytotell.org> wrote:
>
> On Aug 6, 2009, at 6:59 PM, hiro wrote:
>
>> don't forget to take away the connectors from the power and reset
>> buttons, otherwise good security concepts;)
>
> Just out of curiosity, is it possible to simply unbind the console on one of
> these servers after bootup in some startup script? Or perhaps unbind the
> keyboard device, so you can see messages but not type anything in? Maybe use
> cat /dev/kprint instead of rc? It seems like it ought to be possible to
> disable the physical console this way. I ask simply as a way of reducing
> worry about passerby, not as a security solution.
>
You should be able to hack /sys/src/cmd/init.c to make it start
whatever you want after booting, based on init(8), but I haven't tried
it. The man page says it prompts for a password on the cpu server, but
that doesn't happen; the source has a pass function but it's not
called anywhere.
I don't have a real terminal or cpu server at my apartment, so I can't
test it right now.
John
--
"Object-oriented design is the roman numerals of computing" -- Rob Pike
next prev parent reply other threads:[~2009-08-07 3:36 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 2:20 Corey
2009-08-06 2:42 ` Anthony Sorace
2009-08-06 6:15 ` Corey
2009-08-06 6:30 ` John Floren
2009-08-06 7:52 ` Corey
2009-08-06 8:19 ` Robert Raschke
2009-08-06 23:28 ` Corey
2009-08-07 0:01 ` John Floren
2009-08-07 0:14 ` ron minnich
2009-08-07 0:17 ` John Floren
2009-08-07 8:55 ` Steve Simon
2009-08-07 1:00 ` Corey
2009-08-06 10:33 ` Steve Simon
2009-08-07 1:34 ` blstuart
2009-08-07 2:50 ` Anthony Sorace
2009-08-07 12:37 ` Ethan Grammatikidis
2009-08-07 14:37 ` Anthony Sorace
2009-08-07 14:53 ` David Leimbach
2009-08-07 12:05 ` Ethan Grammatikidis
2009-08-07 12:29 ` Iruata Souza
2009-08-07 12:39 ` Ethan Grammatikidis
2009-08-07 13:02 ` Iruata Souza
2009-08-07 13:27 ` Ethan Grammatikidis
2009-08-07 14:44 ` Wes Kussmaul
2009-08-06 12:54 ` erik quanstrom
2009-08-06 15:16 ` David Leimbach
2009-08-06 11:47 ` erik quanstrom
2009-08-07 0:25 ` Roman Shaposhnik
2009-08-07 0:59 ` hiro
2009-08-07 3:04 ` Daniel Lyons
2009-08-07 3:36 ` John Floren [this message]
2009-08-07 9:51 ` erik quanstrom
2009-08-08 4:12 ` lucio
2009-08-07 1:29 ` blstuart
2009-08-10 10:06 ` Corey
2009-08-10 10:33 ` Steve Simon
2009-08-10 10:43 ` Corey
2009-08-10 16:01 ` ron minnich
2009-08-10 20:43 ` Corey
2009-08-11 1:18 ` erik quanstrom
2009-08-07 4:19 lucio
2009-08-07 5:04 ` Corey
2009-08-08 4:26 ` lucio
2009-08-07 4:19 lucio
2009-08-07 4:19 lucio
2009-08-07 4:55 ` Daniel Lyons
2009-08-08 4:08 ` lucio
2009-08-08 7:42 ` Daniel Lyons
2009-08-07 4:56 ` Corey
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=7d3530220908062036j149ca98djf90932e10beec4e7@mail.gmail.com \
--to=slawmaster@gmail.com \
--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).