Become a fan of Slashdot on Facebook


Forgot your password?

Submission Summary: 0 pending, 3 declined, 0 accepted (3 total, 0.00% accepted)


Submission + - Aiport security continues to miss explosives (

Alpha830RulZ writes: According to a story in the Seattle PI today,, investigators were successful in getting components for so called liquid explosives past airport security in 19 different airports in the US. This raises the interesting question, since airport security is demonstrably porous to the motivated and educated person, and yet we have had no explosions on planes, does this not indicate that we are chasing terrorists that aren't there?

This will no doubt cause a hue and cry to develop to tighten security further("Sir, will you please remove your trousers and place your hands on this table?"), I think it actually demonstrates the opposite. Airport security is simply expensive theatre, which serves our government in keeping us concerned. If 19 airports are able to be circumvented, and yet no planes have dropped out of the sky, a reasonable conclusion might be that there are relatively few attempts being made to blow up such planes.


Submission + - How to detect 'Botted' machines

Alpha830RulZ writes: "A couple of us at work are pretty sure that we have at least one compromised machine inside our firewall. We get a lot of SPAM that has contiguous email addresses from our company address book, and they have shown up in enough ways that it looks like some user's machine has been pretty well read over. This is happening repeatedly enough, and new employee's addresses are showing up, so I am concerned that we have some botted machines. We run current Symantec AV, corporate version, on all machines.

Everything I read about the Storm Worm and similar just scares the piss out of me. Is there any way for a normal sysadmin type to detected a Storm botted machine? We are familiar with the likes of rootkit revealer, and when we have had suspicions about a particular box, we run that, Kaspersky, Symantec, and Bitdefender. We haven't found anything definitive, but we have found:

— one machine that prevents Kaspersky from being installed on it. The install hangs on an access violation of a directory newly created by the Kaspersky installer during the install. Symantec, Rootkit Revealer, and Bitdefender find nothing on this machine.

— one machine that has entries deep in the user's temp directories which can't be deleted. These were found by Rootkit Revealer, but we haven't been able to remove them.

We've got the machines segregated for now, and are wondering what we can do to get a handle on this. Help me, my geek brethren."

Slashdot Top Deals

On a clear disk you can seek forever.