9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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: Wed,  5 Aug 2009 23:30:38 -0700	[thread overview]
Message-ID: <7d3530220908052330i5a474ed5r27a266c082f1bd4d@mail.gmail.com> (raw)
In-Reply-To: <200908052315.35723.corey@bitworthy.net>

On Wed, Aug 5, 2009 at 11:15 PM, Corey<corey@bitworthy.net> wrote:
> On Wednesday 05 August 2009 19:42:54 Anthony Sorace wrote:
>> > * I hope I don't get beat up on this one (well, I hope I don't get too
>> > beat up on _any_ of these questions...), but it seems strange that
>> > something as important as a cpu/auth server would just go and boot up
>> > right into the hostowner... apparently this a non issue - so what am I
>> > not understanding?
>>
>> philosophy. plan9, like research unix before it, recognizes that if
>> you have physical access to the box, all bets are off anyway.
>>
>
> Well, sounds like a flawed philosophy taken too far.
>
> Flawed, because all bets are not necessarily off with physical access;
> and taken too far, because... dang, what harm is there in providing
> that last means of interference to a hostile?
>
> Cpu/Fs/Auth server says: "If you can touch me, I'm _all_ yours..."
>
> What a fascinatingly... loose... form of security, if you catch my drift.
>
>
>> security consists of locking your door.
>>
>
> ... which means bootes is just a quick hacksaw or boltcutter or
> crowbar away... so why even bother with a locked door?
>
> Security is ultimately about the price/time/effort/skills a potential
> attacker (or vandal) is willing (and able) to put forth in order to overcome
> a system's security measures. A password is amazingly effective for a
> vast number of the most common circumstances encountered in many
> typical environments.
>

I argued this once too, but eventually came around to the Plan 9 way
of thinking. Once you have physical access to the machine, it's yours
anyway. Just boot the Plan 9 CD and mount the fossil or any of the
other possibilities that arise when you are able to physically insert
bootable media into a system and force it to reboot.

If your Linux system is sitting out, oh no, there's a big scary login
prompt! First thing I try is rebooting and adding "single" to the end
of the kernel options. If that doesn't work, I grab a bootable Linux
CD, boot it, and mount your filesystem. Unless you're encrypting the
disk (probability: low), it's all mine now.

I don't remember the procedure, but I'm pretty sure VMS (reputedly one
of the most secure OSes, if not the most secure OS, in use today) has
a similar option for bypassing the console password on boot, and of
course you can always steal the disk and take it elsewhere, mount a
new boot tape, etc.


John
--
"Object-oriented design is the roman numerals of computing" -- Rob Pike



  reply	other threads:[~2009-08-06  6:30 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 [this message]
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
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=7d3530220908052330i5a474ed5r27a266c082f1bd4d@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).