If you had any respect for your friends over there, you wouldn't be making the comments you have. I deal with active and retired military people all day long. I've learned that when it comes to OPSEC and PERSEC, you ALWAYS err on the side of caution because their lives are on the line. Since you're interested, here's the email I received. He seems to like me and my site more than you. As for me not posting my site URL, that's slashdot 101.

Recently one of my soldiers put a *deleted* video on your website. Specialist *deleted* is his name. He neglected to comply with
Operational Security standards set fourth by his chain of command and the Geneva Convention laws of war. He is in severe trouble,
and our *deleted* soldiers are in grave danger if your website does not remove that video. I know this website is very
responsible and a patriotic link to the war, but I must beg you to remove the *deleted* video or lives are risked when the
wrong people learn how we do things. Please help me with this.

Thank you
SSG *deleted*

You have to wonder how OpenBSD audits allowed thoroughly discredited coding idioms to remain in critical security software. Manual buffer and string management is the principal cause of overflow grief. Yet here we have at least five examples (as of the 3.7.1 patch) of both manual and repeated abuse. The latter is more troubling: apparently there was not even incentive to abstract these routines and fix them centrally, but to sprinkle such pre-1980 thinking throughout.

If only Dan would write a secure shell package.