9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Francisco J Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] how to lock cpu console
Date: Tue, 31 Aug 2010 20:18:09 +0200	[thread overview]
Message-ID: <AANLkTi=dvoLASQswTqP1BAV1piZUOcLhBCR0LaXHqxWx@mail.gmail.com> (raw)
In-Reply-To: <80191640-DB1A-4681-9289-8C17E0ED21F9@gmail.com>

for cpu servers, I sometimes add cat /dev/kmesg /dev/kprint to cpurc.

as the console does not run rio and you can't hit Del to kill them,
they suffice to lock the keyboard.
there was also the lock program from Rob Pike, IIRC, posted here long
ago, I think.

perhaps not
On Tue, Aug 31, 2010 at 5:25 PM, Skip Tavakkolian
<skip.tavakkolian@gmail.com> wrote:
> Steve has a conslock in sources. I have a couple of CPUs in open areas that
> I lock using it. Put it as the last action in /cfg/machine/cpurc to lock on
> startup.
>
> Sent from my iPhone
>
> On Aug 31, 2010, at 8:04 AM, erik quanstrom <quanstro@quanstro.net> wrote:
>
>>> There is also, somewhere, a screen locker program that (I think) Rob
>>> wrote a few years back; I compiled it and used it successfully last
>>> year, and you could certainly stick that in your cpustart to
>>> automatically lock the screen. However, for the life of me I can't
>>> find the code right now, so maybe somebody else can point to it.
>>
>> i didn't suggest lock for cpu servers since it requires
>> rio.  seems silly to run rio on the console just to lock it.
>> and unfortunately, i think this method would also interfere
>> with the serial console.  and it wouldn't be immune to
>> a three-fingered salute, ^P, ^T^Tr, and other hilarity.
>>
>> since there are no interrupts on the console, it would seem
>> trivial to me to, ahem, lock down the console with a 10 line program.
>> you'd be left with defending against ^T^Tr, ^P, etc.
>> but then again, the power button or network cable is sooo
>> convienent.  heck, just take the machine home.  :-P.
>>
>> - erik
>>
>
>



  reply	other threads:[~2010-08-31 18:18 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31 14:20 baux80
2010-08-31 14:31 ` Robert Raschke
2010-08-31 14:55 ` John Floren
2010-08-31 15:04   ` erik quanstrom
2010-08-31 15:25     ` David Leimbach
2010-08-31 15:25     ` Skip Tavakkolian
2010-08-31 18:18       ` Francisco J Ballesteros [this message]
2010-08-31 19:54         ` andrey mirtchovski
2010-08-31 20:45       ` Skip Tavakkolian
2010-09-01  4:21         ` Federico G. Benavento
2010-09-01  4:44           ` John Floren
2010-09-01 15:11           ` erik quanstrom
2010-09-01 16:57             ` Federico G. Benavento
2010-09-01 17:22               ` erik quanstrom
2010-09-01 17:44                 ` John Floren
2010-09-01 18:14                   ` erik quanstrom
2010-09-01 18:31                     ` John Floren
2010-09-01 18:51                       ` erik quanstrom
2010-09-01 19:41                         ` John Floren
2010-09-01 18:24                   ` frank
2010-09-01 17:56                 ` Federico G. Benavento
2010-09-01 10:09         ` baux80 at gmail.com
2010-09-01 10:09         ` baux80
2010-09-01  9:56     ` baux80 at gmail.com
2010-09-01  9:56     ` baux80
     [not found]     ` <E1Oqk2g-0003Ze-1W@gouda.swtch.com>
2010-09-01 19:14       ` Corey
2010-09-01 19:52         ` erik quanstrom
2010-09-01 20:23           ` Corey
2010-09-01  9:48   ` baux80 at gmail.com
2010-09-01  9:48   ` baux80
     [not found] <E1OqRh3-0005IS-Hi@gouda.swtch.com>
2010-08-31 14:29 ` erik quanstrom
  -- strict thread matches above, loose matches on Subject: below --
2010-08-31 14:20 baux80 at gmail.com

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='AANLkTi=dvoLASQswTqP1BAV1piZUOcLhBCR0LaXHqxWx@mail.gmail.com' \
    --to=nemo@lsub.org \
    --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).