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 14:27:05 +0100 [thread overview]
Message-ID: <20090807142705.e657444f.eekee57@fastmail.fm> (raw)
In-Reply-To: <d1c554290908070602o7d12db50v4cb798aaaa13838e@mail.gmail.com>
On Fri, 7 Aug 2009 10:02:27 -0300
Iruata Souza <iru.muzgo@gmail.com> wrote:
> On Fri, Aug 7, 2009 at 9:39 AM, Ethan Grammatikidis<eekee57@fastmail.fm> wrote:
> > On Fri, 7 Aug 2009 09:29:25 -0300
> > Iruata Souza <iru.muzgo@gmail.com> wrote:
> >
> >> On Fri, Aug 7, 2009 at 9:05 AM, Ethan Grammatikidis<eekee57@fastmail.fm> wrote:
> >> > On Thu, 6 Aug 2009 11:33:18 +0100
> >> > "Steve Simon" <steve@quintile.net> wrote:
> >> >
> >> >> I cannot imageine the senario where random people will have access
> >> >> to the cpu/auth/file server's consoles. It just doesn't happen
> >> >> if you are serious about security.
> >> >>
> >> >> However if you want to protect your console against your friends
> >> >> I wrote a script to do it /n/sources/contrib/steve/rc/conslock
> >> >> you may also want to look at screenlock(1)
> >> >>
> >> >> Incidentially I may use this at home to protect my servers console
> >> >> against my 2 year old who rather likes keyboards, though this is
> >> >> a different type of security.
> >> >>
> >> >> -Steve
> >> >>
> >> >
> >> > Speaking of family, I'd imagine a little password protection might go a long way to keeping > the peace in many families. Respect for siblings' property isn't exactly hard-wired into
> >> > human nature, is it?
> >>
> >> no password protection will suffice when ethics fails.
> >
> > ETHICS? In a SEVEN YEAR OLD who knows what rm does????? What the fuck planet are you from? Don't get me started on my teenage years.
> >
>
> having respect for the shared (or private if you wish) stuff is
> ethical. if only prohibition is applied, no password protection will
> work.
>
> a seven year old in anger can surely set fire on the computer or
> whatnot if ethics fails him.
Again, what planet are you from?! :) Setting fire to the computer will get him in so much trouble it'll hurt nastily, but a little messing with big bro's hobby, while risky, doesn't seem to be anywere near as bad.
--
Ethan Grammatikidis
Those who are slower at parsing information must
necessarily be faster at problem-solving.
next prev parent reply other threads:[~2009-08-07 13:27 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 [this message]
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=20090807142705.e657444f.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).