9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Corey <corey@bitworthy.net>
To: 9fans@9fans.net
Subject: Re: [9fans] a few Q's regarding cpu/auth server
Date: Thu,  6 Aug 2009 16:28:14 -0700	[thread overview]
Message-ID: <200908061628.14132.corey@bitworthy.net> (raw)
In-Reply-To: <6a3ae47e0908060119s431551e1ge53d11bf0b2e477a@mail.gmail.com>

On Thursday 06 August 2009 01:19:35 Robert Raschke wrote:
> On Thu, Aug 6, 2009 at 8:52 AM, Corey <corey@bitworthy.net> wrote:
<snip>
> > That wasn't a rhetorical question.  Why bother locking your door?
> >
> > Any intruder worth his weight in salt can circumvent such a simple
> > security mechanism with ease.
>
> Why lock your door, when you're living in a gated community?
>

A few possible answers:

Because I'm convinced that multiple redundant layers of security is
most effective.

Because I _don't_ live in a gated community.

Because anyone can hop a fence, the silly pathetic lock (password) on
my front door (auth server) is my last line of defense; and it will be
immediately and clearly obvious that someone broke in because... well..
they _broke_ in (turned off and dismantled the server)... they didn't
just walk in without further ado (began issuing commands as hostowner
on the open terminal) and leave without immediate and clear evidence
(no broken/missing case, no powered off server and missing drives, etc)


> Your cpu/auth/filesystem machines can be somewhere safe, with as much
> physical safety as you need (physical barriers are much easier to set up
> and administer that electronic ones). If all is set up properly, you will
> never have to touch those machines again. Unless the machines break and
> you need to look at the hardware.
>

Meanwhile, here on terra firma, I would like to be able to have my
Plan 9 servers sitting on a rack in a common affordable co-lo somewhere.


I think the actual root of the situation, is simply that Plan 9 currently
tends to reside within domains with much more strict and secure
or trustworthy environments vs. being prevalent within the sphere of
the great unwashed masses of the industry where strong physical
security is either unobtainable, unaffordable, and/or unreliable at best.

_Within_such_environments_, simple passwords remain an effective and
proven means of _deterrent_ from the most common, random, unforeseen
encounters that may occur on a near every day situation.


The phone guys have to enter the server room - you trust them with bootes?

Various contractors have to enter the server room - you trust them with
bootes?

The sysadmin forgets to lock the door to the server room before heading
out for lunch - you trust all your visitors, customers, affiliates and
employees with a terminal sitting at a bootes prompt?

The hosting provider has all number of people walking in and out of the
server room constantly, every day - you trust each and every one of these
random unknown people with a bootes prompt to your co-lo'd cpu server?

Now here's the important part -- in each of these cases (those are just a few,
it doesn't take much of an imagination - or much actual experience - to come
up with countless more), the _real_ concern is _not_ over that rare motivated,
focused, risk-taking bad guy with a plan who's come prepared with a
screwdriver and usb rootkit and assorted bootdisks... the concern is all the
ad-hoc opportunistic, curious and/or malicious passer-by's, armed with
nothing more than their fingers, who just might take up the chance to goof
around with that open terminal connected to the server.

I have a much higher level of trust that X person won't walk off with or
dismantle a server vs. the level of trust I have that X person won't execute
commands on an open terminal. It's really quite simple.

If your servers aren't under you direct control, and they're not guaranteed
continually locked behind a bio-metrically secured room under constant video
surveillance - then you don't have physical security.

If you don't operate within a contained, peer-based trusted environment (lab,
research center, spec. dept., etc), then you don't have physical security.

Most of the industry at large... does _not_ have trusted physical security.

And if you don't have trusted physical security, then an open terminal is
beyond the pale of recklessness.

Passwords make an excellent form of _additional_deterrent_ under the sort
of lowest common denominator environment that tends to comprise the
industry at large. (from AnyTec, to Bob's coffee house, to Standford & Son's
automotive repair, to The Law Offices Of Larry H. Parker, to Data Entry Inc.)

I honestly can't believe that this is even up for debate!  <grin>

It's just bizarre.

> I think the bit you are leaving out is the fact that a "proper" Plan 9
> installation "needs" terminals.
>
> Your terminal, on the other hand is ephemeral and you have go through the
> usual security checks if you want to access your cpu and filesystem
> servers.
>

That's understood; and I'm well impressed by the way that particular portion
of the model works.


Ok, well I think I've said all I can possible say -- so unless I get any
direct questions I won't follow up on this; I don't want to annoy the list -
9fans is my only means of assistance for this interesting os - plus, I've
already been provided with solutions from which I can roll my own.


Cheers,

Corey





  reply	other threads:[~2009-08-06 23:28 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 [this message]
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=200908061628.14132.corey@bitworthy.net \
    --to=corey@bitworthy.net \
    --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).