Slashdot Mirror

Link didn't work. Is the last octet really supposed to be 4? Try this one instead on the exploit.

Here is a short article on presumption of innocence. I love love LOVE the official Slashdot forced assumption of treating everyone like criminals being OK. Slashdot was purchased to force a political agenda, and I am here to call attention to it. Next up, you're ARRESTED because this software says that you're going to JAYWALK and cause a distracted Prius driver to swerve and mow over a 51-year-old lesbian crone instead.

Yes to both. Found the ancient "flowchart" if that is what you want to call it and the retarded Labview 1.0 reference. Go on and downmod me...

I'll add the RSS feedreader newsbeuter to that list (OK, I'm biased...).

Psssst, look here.

Sometimes, too many links can obfuscate important content instead of helping to direct interested parties to it.

and got this.

The mistake you make is that you don't care about security in multiple layers. Additionally, I would recommend to use a ProProlice-enabled gcc to compile your server applications, to enable (if your OS provides it) non-executable-stack features, and (when it's finished) my self-written ContraPolice, which adds protection against heap overflows to your applications. Additionally, systrace might also be a good feature against possible attacks against your system.

Of course, the things I presented here are only for a small percentage of all services and machines in "big" production environment. So, for more protection, a close look at the client has to be done, too.