From: Daniel Lyons <fusion@storytotell.org>
To: lucio@proxima.alt.za,
Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] a few Q's regarding cpu/auth server
Date: Thu, 6 Aug 2009 22:55:46 -0600 [thread overview]
Message-ID: <3A197D36-CE21-4D9B-B57F-BD133AFE46DE@storytotell.org> (raw)
In-Reply-To: <3b4e65462cfd5539606cdee9efae9e65@proxima.alt.za>
On Aug 6, 2009, at 10:19 PM, lucio@proxima.alt.za wrote:
>> I have direct experience as a contractor where I have entered
>> many a co-lo; and was unimpressed with their security to say the
>> least.
>> I had constant and easy access to a large number of nameless servers,
>> it's a nobrainer to access keyboard/monitor pairs in many of these
>> places.
>
> That would be vandalism. You didn't indulge in it, why would you
> expect someone else in your situation to do differently? Or are you
> lying to us?
Story time. :)
Several years ago I worked for a company here that had decided to
colocate a server locally (yeah, brilliant, in Albuquerque) instead of
getting a hosted server somewhere with better access. I wound up going
down there a few times to add RAM to the system. Apart from my
company, there were a smattering of other smalltimers with big tower
computers from Dell on this rack and off on the other side of the
facility was a fenced off area with four or five racks of Dell
hardware. The owner casually mentioned to me that the company who
owned the racks had something to do with airline ticket sales. I guess
because I chuckled at that, he also mentioned to me that the computer
next to ours was hosting the governor's re-election website. I thought
about doing something malicious, because I'm not a big fan of
Richardson, but decided it wasn't worth the trouble.
Later on one of the owners of the colo facility got bought out and
blew up. He went into the facility and ripped out the primary router,
then took the upstream cable and plugged it into another port on the
backup router such that the packets wound up going in a cycle. Then he
damaged the backup power system and flew out the door with the primary
router.
Not really taking a position here but your comments reminded me of the
story. I guess there's always a bigger jerk out there and sometimes he
runs your colo facility.
—
Daniel Lyons
next prev parent reply other threads:[~2009-08-07 4:55 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 4:19 lucio
2009-08-07 4:55 ` Daniel Lyons [this message]
2009-08-08 4:08 ` lucio
2009-08-08 7:42 ` Daniel Lyons
2009-08-07 4:56 ` Corey
-- strict thread matches above, loose matches on Subject: below --
2009-08-07 4:19 lucio
2009-08-07 4:19 lucio
2009-08-07 5:04 ` Corey
2009-08-08 4:26 ` lucio
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
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
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=3A197D36-CE21-4D9B-B57F-BD133AFE46DE@storytotell.org \
--to=fusion@storytotell.org \
--cc=9fans@9fans.net \
--cc=lucio@proxima.alt.za \
/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).