I can't believe that you missed the display two years ago. That blew this one away.
A buddy of mine was at Eastern Michigan's observatory for the night and took a crap load of pictures. This was the only one I could find (not linked in an effort to save what little bandwidth they've got)
http://www.physics.emich.edu/sherzer/AuroraDome. jp g
(And since it was usually really Toronto in disguise, someone would put them in the blue box for recycling pickup.)
Nope, The original Robocop was filmed in Dallas. Robocop 2 was filmed in Houston, and the ill-advised Robocop 3 was filmed in Atlanta. I don't think there's enough urban decay in Toronto (or in all of canada combined) to simulate the really nasty parts of Detroit.
You know, I buy the whole "the patch broke something, so we can't apply the patch" argument up to a point. Usually when an iffy patch comes out, there's an update to it that patch comes out later on down the line. SP2 for XP is a good example. Several hotfixes were re-written as full blown patches once the SP2 went live.
Even if that's not the case, I get the feeling that far too many shops just decide "Oh well, the patch broke it and we don't feel like putting forth the effort to find a fix for it." Check with the vendor of the broken application, have your in-house staff look at the custom app, don't just about the boys from Redmond breaking your toys. I guess it's just easier to blame Microsoft and be done with it.
Buyer beware. You know the mess you're getting into when you decide to run Microsoft products. sort of a "If you can't do the time, don't do the crime" situation.
How do you ghost all these machines with a new fresh clean copy of the OS and apps and still retain the data and know that the virus isn't still embedded in the data someplace?
In this case, You don't know. Different ailments require different cures.
There's no indication of what virus they're dealing with. It sounds like Blaster/Sasser (since you've got a large number of machines down in an environment that probably consists of a bunch of windows machines running under the same policies) but it could be something else. Maybe they're running MsSQL and the server or servers got hit with slammer.
With a virus that infects just the data files (say, a word macro virus) cleanup would be easier. Clean the infected files and move on. If the virus is affecting just the operating system (like Sasser or Blaster) then ghosting with a patched may be the better solution.
As far as retaining the data, that's what network storage is for. Keeping valuable files on the local machine is just asking for trouble.
Ya you could do that, or you could do do things properly and have a firewall. Ya lets to the expensive reactionary-that-looks-like-proactive measures instead of the simple thing that would prevent 99% of problems before they occurred.
Odds are their network is firewalled, probably quite well. And that's *why* they are down now. It's the "our powerful lord and master the firewall will protect the whole network, so we don't need to patch!" line of thinking that may have landed them in this mess. That line of thinking was semi-validated when sasser made it's last run around. "We didn't get hit, we must be safe."
Flash forward to a few days ago when somebody brings in their infected laptop from home and.....hilarity ensues. It's all part of the grand process of security. Know what the bad stuff is, know how to keep the bad stuff out, be ready for the bad stuff if it gets in, have a method in place to rebuild everything from scratch if you have to.
Let's assume it's Sasser or blaster that's brought down the network. You'll have to go to each machine, run the removal tool to remove the virus, then patch the system so you don't get infected again. Wash rinse repeat for every infected machine on the on the system.
Or, you can eliminate the hassle of going to each system by mulitcasting a patched, clean, and perhaps improved system image using Ghost or something similar. Hell you can do that from a central console and never even see the remote machines. Why dick around cleaning up a virus and patching a single box when you can push out a clean image to all the machines remote site?
I'll wrestle with a virus when a machine absolutly can't be blown away. In an ideal world (where user files are on network drives and gumdrop fairys eat marmalade pies) that's never, but in reality it's once in a great while.
Now, they may not have the pipe to push an image to all the remote locations, so they're probably stuck sending the lackeys out into the field. That's going to take considerably longer (say, a couple days), but it's a small price for knowing the job is done right, and you're not just fixing up an old home for the same virus.
You're thinking of the old Corona missions, Story which used C-123 cargo planes as a means of recovery. They were run from 1959 through 1972, and you can order copies of the images taken through the USGS.
I should point out, of course, that the 4-seconds-to-0wn time is from the results of testing they did. None of the system administrators there would ever plug in a unpatched machine they weren't planning on immediately wiping.
If their systems are as tight as they seem, then perhaps they just caught a "magic bullet" (that system had the right IP at the right time). I'd like to have seen what the rest of the world was dealing with at the time of this test. Was this done during the first week blaster was spreading (when it seemed like every machine on earth was infected and broadcasting), or during the lull between blaster and sasser?
Walk down the street in downtown Detroit counting $20 dollar bills and see how long it takes for you to get mugged. Then do the same on mainstreet in West Bumblefuck, Iowa (population 15, if'n Pastor Smith isn't out of town). Betcha you last longer in Iowa. In other words that time is probably dependant on how nasty the computing environment is.
IIRC Sasser and Blaster chose their target IP's at random, starting with IP addresses in the same subnet then moving to random IP's. So if a machine gets infected four seconds after it's plugged in, that's not just a product of how poorly secured windows is, it's also a product of U of Alberta having a network chock full of RPC 'sploiting goodness. Now, if they'd have plugged in the same in an environment that had been properly patched, firewalled, etc. The box would've been fine for hours, days, or maybe it would've never been comprimised at all.
Firewall and Snort logs can give you the true tale of the tape. Some days my home firewall (SBC residential DSL) is turning away worm attempts like a goalie on speed. Other days I go 10-12 hours without so much as a nibble or a port scan.
But it is so much fun to talk about how "WIUNDOWS IS TEH GHEY! IT GOTS PWN3D IN TEH SECONZ!!LOL!!!11ONE@!!!@!
From Airsnort.shmoo.com: AirSnort requires approximately 5-10 million encrypted packets to be gathered.
Wanna tell me how you're gonna grab 5 million packets (not counting SSID broadcasts) from a single network whist wardriving? You need quite a few users going for a long time to generate that much traffic.
Yes WPA is bettter, and it's nice to see it becoming a standard. But despite the FUD, WEP is not some disgustingly horribly insecure protocol that's gonna get hacked in 15 seconds by any script kiddie with a wifi card. It takes a *long-ass time* to gather the amount of data needed to crack WEP. There's far easier ways into a network. But then again, it's so much fun to play baby seal and arp away about WEP totally sucking ass.
Try a capture on a home network and see how long it takes. My own net is four machines, including two always-on boxes. It still takes days to generate enough traffic to make an attempt at cracking WEP.
For home (house) use, 128-bit WEP will work just fine. For office environments or apartment buildings, you should still crank things up a notch with MAC whitelisting etc.
Re:Microsoft and Britney Spears connection ....
on
IT's Musical Habits
·
· Score: 1
It's true - they both have a lot of exploitable holes.
Bah, I won't believe that any of those holes have been exploited until I can see some documentation.
Until there's some proof, you've got nothing but a bunch of no talent kiddies claiming a 0-day 'sploit.
Or so the government claimed. Some people think otherwise. In July of the preceding year, the Port Chicago military base near San Francisco had been destroyed in a massive explosion. The government claimed an ammunition boat full of TNT had exploded, but in retrospect, many questions arose. The boat itself was completely vaporized in the blast. More than 300 people were killed, and much of the base was reduced to dust and slag. Even the nearby town was damaged and hundreds of civilians were injured.
The government subsequently lied about the atomic weapons research going on at Port Chicago and the weapons capacity it had at the time, lies which were only exposed in 1981 under a mountain of declassified documents. Coincidentally, the Navy even filmed the explosion, and the film shows a billowing mushroom cloud.
Wow, Nothing like some good old fashioned FUD for breakfast.
If Port Chicago were in fact a nuclear test, it must have amounted to one of the most phenominal fizzles in history. Nevermind the fact that the Navy had other motives for covering up the facts (namely, the mistreatment of African American Sailors by white officers and the blatant disregard for safety procedures which lead to the explosion)
Those in charge of company security should remember that these same employees bringing in iPods are the ones who were issued key cards to get into the building. Companies have no choice but to give their workers the benefit of the doubt.
There's "benefit of the doubt" and there's "say, Bob doesn't usually show up carrying a belt-fed weapon, maybe I shouldn't let him in the door."
Companies have to form some kind of a policy regarding their data. Who can have it, why they have it, what those have have access to the data can do with it. To be useful, those policies have to be updated. 15 years ago a watch was just a timepiece, a walkman played cassette tapes, and a camera had 35mm film. Now any of those devices can easily carry 4 gigs of data or more.
Beyond just saying "i don't trust my employees to carry these devices in the workplace" we should think about why do we need them in the workplace. Does this person *need* an iPod, or a digital camera as part of their job? No? Then there's really no reason for it to be there.
Trust is not absolute, it is relative. There are people I trust, those I have to trust, those who I don't need to trust, and then those that I don't trust.
So it stops at the las vegas hilton, huh? Too bad, I was hoping to be able to pull into the Paris Hilton.....perhaps the 'service entrance' to the Paris Hilton...
1. Make sure the robot does not take an interest in finding Sarah Conner.
2. Should you be enjoying a lazy day in the hammock while the mower does its job, and you hear some incidental music start up that sounds very 'AC/DC-ish', Get your sledgehammer or other non-complex machine based method of destruction ready.
3. Do not power the robot with alcohol. Take extra care not to power the robot with malt liquors such as 'Olde Fortran', lest your robot develope a penchant for petty theft.
4. klaatu barada nikto
5. Consider brushing up on Asimov's laws of robotics, just so's you get them right.
BOINC isn't nearly as usful to society as Folding@home, AIDS research@home, help feed starving disabled puppies in war torn african nations@home, etc.
BOINC != Seti@Home. BOINC is a step up the ladder from Seti, it provides the infrastructure for multiple projects. *you* choose the project to attach yourself to and contribute time to. In an ultra-perfect hippie world, Folding@home would use the BOINC infrastructure. Instead you get to help out who you want.
I ain't trustin no Berkeley hippies to silently install no black helicopter, tinfoil hat disablin' technology on my system.
Then don't use it. If you ran seti, you really had no way of knowing what was coming down the pipe now did you? You opened up a nice big gaping connection into your system while trusting that the work units weren't poison pills and that Berkeley's infrastructure hadn't been comprimised. Run the client on a non-critical machine, put it outside your firewall if it makes you happy.
Scientific progress goes BOINC!
You're very clever. You're the only person that ever thought of that.
Aliens will enslave the earth when we make contact!!!!!
You really shouldn't have rented Battlefield Earth.
There really isn't anything they can do to help, except warn the pilot that something has gone wrong.
They can also do handy things like make sure the pilot isn't incapacitated, make better judgement calls on an aircraft's condition, etc..Chuck Yeager detailed several stories of just how valuable a chase plane is.
On one occasion his windshield defroster failed, leaving him flying exceptionally blind. His chase plane helped talk him down by flying parallel to him and directing the plane in. (I know, he had instruments, but think about a frost covered windshield on a bright sunny day. You're pretty much flying with your eyes closed)
In another case a pilot yeager was flying chase for neglected to turn his oxygen up. Yeager conned the pilot into returning to a safe altitude.
My firewall sounds like a really bad techno song. It starts with a nice driving rythem with hits on 137 that come out like:
bump-bump-bump-bump-bump-bump-bump-bump-bump
Then maybe a few attempts at an SQL worm on 1433-1434 so i get the second layer of the track; that's sound like 'dittlit-bump' so the track now becomes
bump-bump-bump-dittlit-bump-dittlit-bump
Now we've got some rythem going, but we there's always that annoying yet musical sound that comes interrupts the song the first time you hear it, but then you get used to it. We'll call that a portscan. ports 135-137-445-3127-5000
dah-dah-dahdah-dah-dah-dahdahdah
But at just that moment I get a fresh IP from my DSL provider, and the last guy who had it was running eDonkey, AIM file transfers, and bittorrent (as happened to my a couple days ago) and all the crap clients for said programs don't realize the old client died, so they keep trying said addresses.....we'll call that a big-ass bass hit that starts the loop over again.
BOOOOOOOOOOOOOM-BOOOOOOOOOOOOOM-BOOOOOOOOOOOOOOO M
Holy crap, my firewall sounds exactly like the Strong Bad techno song, minus the 'the system is down' quote. (ahhh the benfits of coyote linux. or IPcop.)
Host george.w.bush (bonging420.whitehouse.gov) appears to be down, or doesn't have a brain. If you know the host is up, or you think the host doesn't have a brain try -B0
Host george.w.bush (bonging420.whitehouse.gov) appears to be up, good. Beginning brain scan. (bonging420.whitehouse.gov); Class: Incremental Interesting ports on bonging420.whitehouse.gov: (The 65531 ports scanned but not shown below are in state: closed) Port State Service 21/tcp open ftp 25/tcp open smtp 1027/tcp open IIS 5000/tcp open uPnP 5631/tcp open pcanywheredata
Nmap run completed -- 1 IP address (1 host up) scanned in 2594.472 seconds
Slashdot Mirror
I can't believe that you missed the display two years ago. That blew this one away.
. jp g
A buddy of mine was at Eastern Michigan's observatory for the night and took a crap load of pictures. This was the only one I could find (not linked in an effort to save what little bandwidth they've got)
http://www.physics.emich.edu/sherzer/AuroraDome
(And since it was usually really Toronto in disguise, someone would put them in the blue box for recycling pickup.)
Nope, The original Robocop was filmed in Dallas. Robocop 2 was filmed in Houston, and the ill-advised Robocop 3 was filmed in Atlanta. I don't think there's enough urban decay in Toronto (or in all of canada combined) to simulate the really nasty parts of Detroit.
Filming locations for Robocop
You know, I buy the whole "the patch broke something, so we can't apply the patch" argument up to a point. Usually when an iffy patch comes out, there's an update to it that patch comes out later on down the line. SP2 for XP is a good example. Several hotfixes were re-written as full blown patches once the SP2 went live.
Even if that's not the case, I get the feeling that far too many shops just decide "Oh well, the patch broke it and we don't feel like putting forth the effort to find a fix for it." Check with the vendor of the broken application, have your in-house staff look at the custom app, don't just about the boys from Redmond breaking your toys. I guess it's just easier to blame Microsoft and be done with it.
Buyer beware. You know the mess you're getting into when you decide to run Microsoft products. sort of a "If you can't do the time, don't do the crime" situation.
How do you ghost all these machines with a new fresh clean copy of the OS and apps and still retain the data and know that the virus isn't still embedded in the data someplace?
In this case, You don't know. Different ailments require different cures.
There's no indication of what virus they're dealing with. It sounds like Blaster/Sasser (since you've got a large number of machines down in an environment that probably consists of a bunch of windows machines running under the same policies) but it could be something else. Maybe they're running MsSQL and the server or servers got hit with slammer.
With a virus that infects just the data files (say, a word macro virus) cleanup would be easier. Clean the infected files and move on. If the virus is affecting just the operating system (like Sasser or Blaster) then ghosting with a patched may be the better solution.
As far as retaining the data, that's what network storage is for. Keeping valuable files on the local machine is just asking for trouble.
Ya you could do that, or you could do do things properly and have a firewall. Ya lets to the expensive reactionary-that-looks-like-proactive measures instead of the simple thing that would prevent 99% of problems before they occurred.
Odds are their network is firewalled, probably quite well. And that's *why* they are down now. It's the "our powerful lord and master the firewall will protect the whole network, so we don't need to patch!" line of thinking that may have landed them in this mess. That line of thinking was semi-validated when sasser made it's last run around. "We didn't get hit, we must be safe."
Flash forward to a few days ago when somebody brings in their infected laptop from home and.....hilarity ensues. It's all part of the grand process of security. Know what the bad stuff is, know how to keep the bad stuff out, be ready for the bad stuff if it gets in, have a method in place to rebuild everything from scratch if you have to.
It's fun to play armchair QB.
Let's assume it's Sasser or blaster that's brought down the network. You'll have to go to each machine, run the removal tool to remove the virus, then patch the system so you don't get infected again. Wash rinse repeat for every infected machine on the on the system.
Or, you can eliminate the hassle of going to each system by mulitcasting a patched, clean, and perhaps improved system image using Ghost or something similar. Hell you can do that from a central console and never even see the remote machines. Why dick around cleaning up a virus and patching a single box when you can push out a clean image to all the machines remote site?
I'll wrestle with a virus when a machine absolutly can't be blown away. In an ideal world (where user files are on network drives and gumdrop fairys eat marmalade pies) that's never, but in reality it's once in a great while.
Now, they may not have the pipe to push an image to all the remote locations, so they're probably stuck sending the lackeys out into the field. That's going to take considerably longer (say, a couple days), but it's a small price for knowing the job is done right, and you're not just fixing up an old home for the same virus.
I guess that's why I've never recieved any of those e-mails.
Here's to you, Mr. Organizer-of-real-men-of-genius-posts.
Mr. Organizer-of-real-men-of-genius-posts
You spend minutes toiling away trying to bring order to chaos. Grinding your fingers to the bone.
Grind down those digits!
Without you, there'd be scattered ramblings all over the site, with no real rhyme or reason
it's like that every day now...
So crack open a cold bud light and relax, you've made slashdot safe.......for parodies.
You're thinking of the old Corona missions, Story which used C-123 cargo planes as a means of recovery. They were run from 1959 through 1972, and you can order copies of the images taken through the USGS.
I should point out, of course, that the 4-seconds-to-0wn time is from the results of testing they did. None of the system administrators there would ever plug in a unpatched machine they weren't planning on immediately wiping.
If their systems are as tight as they seem, then perhaps they just caught a "magic bullet" (that system had the right IP at the right time). I'd like to have seen what the rest of the world was dealing with at the time of this test. Was this done during the first week blaster was spreading (when it seemed like every machine on earth was infected and broadcasting), or during the lull between blaster and sasser?
Walk down the street in downtown Detroit counting $20 dollar bills and see how long it takes for you to get mugged. Then do the same on mainstreet in West Bumblefuck, Iowa (population 15, if'n Pastor Smith isn't out of town). Betcha you last longer in Iowa. In other words that time is probably dependant on how nasty the computing environment is.
IIRC Sasser and Blaster chose their target IP's at random, starting with IP addresses in the same subnet then moving to random IP's. So if a machine gets infected four seconds after it's plugged in, that's not just a product of how poorly secured windows is, it's also a product of U of Alberta having a network chock full of RPC 'sploiting goodness. Now, if they'd have plugged in the same in an environment that had been properly patched, firewalled, etc. The box would've been fine for hours, days, or maybe it would've never been comprimised at all.
Firewall and Snort logs can give you the true tale of the tape. Some days my home firewall (SBC residential DSL) is turning away worm attempts like a goalie on speed. Other days I go 10-12 hours without so much as a nibble or a port scan.
But it is so much fun to talk about how "WIUNDOWS IS TEH GHEY! IT GOTS PWN3D IN TEH SECONZ!!LOL!!!11ONE@!!!@!
it is damned hard to root a CD
Not when the CD uses a blank password for root....
From Airsnort.shmoo.com: AirSnort requires approximately 5-10 million encrypted packets to be gathered.
Wanna tell me how you're gonna grab 5 million packets (not counting SSID broadcasts) from a single network whist wardriving? You need quite a few users going for a long time to generate that much traffic.
Yes WPA is bettter, and it's nice to see it becoming a standard. But despite the FUD, WEP is not some disgustingly horribly insecure protocol that's gonna get hacked in 15 seconds by any script kiddie with a wifi card. It takes a *long-ass time* to gather the amount of data needed to crack WEP. There's far easier ways into a network. But then again, it's so much fun to play baby seal and arp away about WEP totally sucking ass.
Try a capture on a home network and see how long it takes. My own net is four machines, including two always-on boxes. It still takes days to generate enough traffic to make an attempt at cracking WEP.
For home (house) use, 128-bit WEP will work just fine. For office environments or apartment buildings, you should still crank things up a notch with MAC whitelisting etc.
It's true - they both have a lot of exploitable holes.
Bah, I won't believe that any of those holes have been exploited until I can see some documentation.
Until there's some proof, you've got nothing but a bunch of no talent kiddies claiming a 0-day 'sploit.
Out on the road today I saw a deadhead sticker on a checkpoint box,
A little voice inside my head said don't look back you can never look back....
Funny, that's where i get all my computer junk.
hey!!!!
Or so the government claimed. Some people think otherwise. In July of the preceding year, the Port Chicago military base near San Francisco had been destroyed in a massive explosion. The government claimed an ammunition boat full of TNT had exploded, but in retrospect, many questions arose. The boat itself was completely vaporized in the blast. More than 300 people were killed, and much of the base was reduced to dust and slag. Even the nearby town was damaged and hundreds of civilians were injured.
The government subsequently lied about the atomic weapons research going on at Port Chicago and the weapons capacity it had at the time, lies which were only exposed in 1981 under a mountain of declassified documents. Coincidentally, the Navy even filmed the explosion, and the film shows a billowing mushroom cloud.
Wow, Nothing like some good old fashioned FUD for breakfast.
If Port Chicago were in fact a nuclear test, it must have amounted to one of the most phenominal fizzles in history. Nevermind the fact that the Navy had other motives for covering up the facts (namely, the mistreatment of African American Sailors by white officers and the blatant disregard for safety procedures which lead to the explosion)
Those in charge of company security should remember that these same employees bringing in iPods are the ones who were issued key cards to get into the building. Companies have no choice but to give their workers the benefit of the doubt.
There's "benefit of the doubt" and there's "say, Bob doesn't usually show up carrying a belt-fed weapon, maybe I shouldn't let him in the door."
Companies have to form some kind of a policy regarding their data. Who can have it, why they have it, what those have have access to the data can do with it. To be useful, those policies have to be updated. 15 years ago a watch was just a timepiece, a walkman played cassette tapes, and a camera had 35mm film. Now any of those devices can easily carry 4 gigs of data or more.
Beyond just saying "i don't trust my employees to carry these devices in the workplace" we should think about why do we need them in the workplace. Does this person *need* an iPod, or a digital camera as part of their job? No? Then there's really no reason for it to be there.
Trust is not absolute, it is relative. There are people I trust, those I have to trust, those who I don't need to trust, and then those that I don't trust.
So it stops at the las vegas hilton, huh? Too bad, I was hoping to be able to pull into the Paris Hilton. ....perhaps the 'service entrance' to the Paris Hilton...
What? At least it's not a Simpsons reference
points to consider:
1. Make sure the robot does not take an interest in finding Sarah Conner.
2. Should you be enjoying a lazy day in the hammock while the mower does its job, and you hear some incidental music start up that sounds very 'AC/DC-ish', Get your sledgehammer or other non-complex machine based method of destruction ready.
3. Do not power the robot with alcohol. Take extra care not to power the robot with malt liquors such as 'Olde Fortran', lest your robot develope a penchant for petty theft.
4. klaatu barada nikto
5. Consider brushing up on Asimov's laws of robotics, just so's you get them right.
Lets see what we can cover:
BOINC isn't nearly as usful to society as Folding@home, AIDS research@home, help feed starving disabled puppies in war torn african nations@home, etc.
BOINC != Seti@Home. BOINC is a step up the ladder from Seti, it provides the infrastructure for multiple projects. *you* choose the project to attach yourself to and contribute time to. In an ultra-perfect hippie world, Folding@home would use the BOINC infrastructure. Instead you get to help out who you want.
I ain't trustin no Berkeley hippies to silently install no black helicopter, tinfoil hat disablin' technology on my system.
Then don't use it. If you ran seti, you really had no way of knowing what was coming down the pipe now did you? You opened up a nice big gaping connection into your system while trusting that the work units weren't poison pills and that Berkeley's infrastructure hadn't been comprimised. Run the client on a non-critical machine, put it outside your firewall if it makes you happy.
Scientific progress goes BOINC!
You're very clever. You're the only person that ever thought of that.
Aliens will enslave the earth when we make contact!!!!!
You really shouldn't have rented Battlefield Earth.
Ya know, it might just be some personal expereicen talking here but ummm......
A BEING ABLE TO LOOK OUT A FUCKING WINDOW ONCE IN A WHILE JUST MIGHT MAKE ME A LITTLE LESS VOILENT GOD FUCKING DAMNIT!
Just a little sunshine, that's all I ask. and not the liquid kind the white coats keep bringing me.
There really isn't anything they can do to help, except warn the pilot that something has gone wrong.
They can also do handy things like make sure the pilot isn't incapacitated, make better judgement calls on an aircraft's condition, etc..Chuck Yeager detailed several stories of just how valuable a chase plane is.
On one occasion his windshield defroster failed, leaving him flying exceptionally blind. His chase plane helped talk him down by flying parallel to him and directing the plane in. (I know, he had instruments, but think about a frost covered windshield on a bright sunny day. You're pretty much flying with your eyes closed)
In another case a pilot yeager was flying chase for neglected to turn his oxygen up. Yeager conned the pilot into returning to a safe altitude.
My firewall sounds like a really bad techno song. It starts with a nice driving rythem with hits on 137 that come out like:
O M
bump-bump-bump-bump-bump-bump-bump-bump-bump
Then maybe a few attempts at an SQL worm on 1433-1434 so i get the second layer of the track; that's sound like 'dittlit-bump' so the track now becomes
bump-bump-bump-dittlit-bump-dittlit-bump
Now we've got some rythem going, but we there's always that annoying yet musical sound that comes interrupts the song the first time you hear it, but then you get used to it. We'll call that a portscan. ports 135-137-445-3127-5000
dah-dah-dahdah-dah-dah-dahdahdah
But at just that moment I get a fresh IP from my DSL provider, and the last guy who had it was running eDonkey, AIM file transfers, and bittorrent (as happened to my a couple days ago) and all the crap clients for said programs don't realize the old client died, so they keep trying said addresses.....we'll call that a big-ass bass hit that starts the loop over again.
BOOOOOOOOOOOOOM-BOOOOOOOOOOOOOM-BOOOOOOOOOOOOOO
Holy crap, my firewall sounds exactly like the Strong Bad techno song, minus the 'the system is down' quote. (ahhh the benfits of coyote linux. or IPcop.)
http://www.homestarrunner.com/sbemail.html
A Brain scan of every living person on earth?! Brilliant!
root@kerryforprez>nmap -sB -vv george.w.bush -D dick.cheney, donald.rumsfeld
Starting nmap V. 3.60 ( www.insecure.org/nmap/ )
Host george.w.bush (bonging420.whitehouse.gov) appears to be down, or doesn't have a brain. If you know the host is up, or you think the host doesn't have a brain try -B0
root@kerryforprez>nmap -sB -vv george.w.bush -D dick.cheney, donald.rumsfeld -B0
Starting nmap V. 3.60 ( www.insecure.org/nmap/ )
Host george.w.bush (bonging420.whitehouse.gov) appears to be up, good. Beginning brain scan.
(bonging420.whitehouse.gov); Class: Incremental
Interesting ports on bonging420.whitehouse.gov:
(The 65531 ports scanned but not shown below are in state: closed)
Port State Service
21/tcp open ftp
25/tcp open smtp
1027/tcp open IIS
5000/tcp open uPnP
5631/tcp open pcanywheredata
Nmap run completed -- 1 IP address (1 host up) scanned in 2594.472 seconds