Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

acme (189)

acme
  (email not shown publicly)
http://www.astray.com/

Leon Brocard (aka acme) is an orange-loving Perl eurohacker with many varied contributions to the Perl community, including the GraphViz module on the CPAN. YAPC::Europe was all his fault. He is still looking for a Perl Monger group he can start which begins with the letter 'D'.

Journal of acme (189)

Monday November 26, 2001
01:16 PM

Computers

[ #1374 ]
I have had a bad Monday.

My colocated box got hacked over the weekend and has been flaky all day. This means rhizomatic looses an IRC node and much more importantly neither I nor my friends can read their email while we bring it safely back up. It's really annoying. Why can't computers just work and never go down?

I haven't been without email for a while. I wonder how I'll cope? Will I go mad?

One of us is going down to the colocated place and reinstalling from scratch, which will be fun. It'll then be up to me to slowly install all the services, with an eye to security. Sysadmins rule. If only we had one ;-)

And after everything is up, we'll set up lots of monitoring as well as secondary MX etc. etc. so it never happens again and if it does we can do it all again quickly. At least the box has silly amounts of bandwith. Why does it always take an actual exploit to get me as worried about security as I should be?

Oh, and debugging SOAP::Lite stuff at work hasn't helped, either...

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I'm always interested in how these things get hacked, mostly so I can protect myself. What happened?
    • > What happened?

      We were still running a vulnerable version of sshd. The thing is, I'm always worried about upgrading sshd remotely, as it involves a trek down to my colocation place if I get it wrong. However, there are just too many sshd exploits these days and I recommend everyone to upgrade to the latest openssh all the time :-(...