9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] a few Q's regarding cpu/auth server
Date: Fri,  7 Aug 2009 13:37:26 +0100	[thread overview]
Message-ID: <20090807133726.1c9f3dca.eekee57@fastmail.fm> (raw)
In-Reply-To: <509071940908061950g6eeca384u86abfb56c82ba8aa@mail.gmail.com>

On Thu, 6 Aug 2009 22:50:33 -0400
Anthony Sorace <anothy@gmail.com> wrote:

> this is silly. the philosophy has been explained. several people have
> given lots of "real world" usage where it holds up just fine. i'd go
> as far as to say the vast majority of plan9 installations are in such
> environments.

Oh God, not the everyday examples == proof argument, PLEASE. The common
case in the present time is that people EXPECT server terminals to be
password protected so they're not likely to bother looking. Suppose
it gets to be common knowlege that server terminals are rarely
password-protected. Now suppose co-lo host X is well-known for hosting
a large number of Plan 9 machines -- at the rate interest in Plan 9 is
growing this could happen in only a year or two from now. Now please
stretch your imagination to include Frank.

Frank is a contractor, called in to perform some maintenance in X's
cages. Frank is bored out of his skull. His wife hasn't left him
(yet), but there's no love left nor any real hate either; just cold
apathy. His workday has been flat-dull so far, he's had a succession
of extremely tedious jobs and now he has another one. Frank sees a lot
of Plan 9 machines next to him. Password cracking is time-consuming
and potentially very boring, but few Plan 9 machines have one. Frank
is on a schedule and already bored out of his skull, and best of all,
if he tampers no-one will ever know it wasn't a remote exploit!

Now here's the point. I and a billion other people HAVE MORE FUN THINGS TO
DO THAN FRET ABOUT SECURITY. A weak OS needs me to put in boring work...


--
Ethan Grammatikidis

Those who are slower at parsing information must
necessarily be faster at problem-solving.



  reply	other threads:[~2009-08-07 12:37 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 [this message]
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=20090807133726.1c9f3dca.eekee57@fastmail.fm \
    --to=eekee57@fastmail.fm \
    --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).