it's too bad you have such an inept attitude my friend. You learn more about security by breaking into systems than just reading how to do it :-)... Yes what Kevin did in the past (and I stress past) was perhaps wrong, but this board isn't here for your own personal attacks. It's about time you grow up and disgard grudges or any preconcieved opinions :-).

I'm an SysAdmin that understands the pains of dealing with "crackers" (not hackers - they're different), and script kiddies... it comes with the territory so you have to expect it.

I use to be on the other side of the fence too, just wasn't as noticable.

Yes what Kevin and several others have done is wrong, and I only thank God for where I am now since I became a Christian. But the point is this:

The best person to protect and secure a network is someone who already knows the ropes about how to get in, so the holes can be patched **beforehand** both by patches, proper systems administration, and common sense.

Just because someone may have some so called security credentials with lettered abreviations doesn't make someone a security expert or even qualified in computer security.

Someone who has cracked into a server before (especially with his own software tools) and is **truly reformed**, combined with good indepth knowledge of some os'es like UNIX, WinNT/2000, and Linux and they're corresponding filesystems, plus a solid grasp on the TCP/IP stack, and coupled with programming skills, would be much better suited to the task.

Now I don't know what skills you may have, but I forgive Kevin, and it's time everyone else does too - everyone needs a second chance.

Did he take anything from the conference? Most likely not (I doubt he's stupid), did he belong in the room? Yes - he just forgot his i.d. badge! He's just commenting on how lax the physical security of the room where thousands of dollars worth of computer gear is left in the open at a security conference for any one to steal! That's laughingly ironic and see I Kevin's point.

[ reply ]

Link to this comment: http://www.securityfocus.com/comments/articles/199/5549#5549