Slash Boxes
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 ]

Beatnik (493)

  (email not shown publicly)

A 29 year old belgian who likes Mountain Dew, Girl Scout Cookies, Tim Hortons French Vanilla Flavoured Cappucinno, Belgian beer, Belgian chocolate, Belgian women, Magners Cider, chocolate chipped cookies and Perl. Likes snowboarding, snorkling, sailing and silence. Bach can really cheer him up! He still misses his dog.

Project Daddy of Spine [], a mod_perl based CMS.

In his superhero time (8.30 AM to 5.30 PM), he works on world peace.

Journal of Beatnik (493)

Tuesday September 25, 2007
03:25 PM

Colored Hats

[ #34543 ]
One of the guys at work went to a few security conferences and he gave a quick talk about it. I took one of my co-workers along. He was quite shocked and awed afterwards. Novices normally never realize what potential security risks are and how easy it is to screw things up. Topics of the talk included XSS, SQL Injections, SideJacking and a dissection of a 0 day buffer overflow. There were plenty of demos. All in all, it was very interesting, even if you're already familiar with a lot of security issues.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Paying attention to security is like buying fire insurance. You may never need it, but if you do and you don't have it, you're in serious trouble. It's not an easy thing to explain to management. I've worked at several companies where there were serious pushes to deal with security, but always after the fire.

    • Luckily, we have a separate security department. They do stuff like training, pro-active security assesments, application security assesments, best practice documents, define security standards.. The works.