Slashdot Mirror
Security Experts Doubt SCO's Claims of DoS
devilkin writes "As a recent Slashdot story indicates, SCO claims their website was the target of a DoS (Denial of Service) attack. Was it really? The people at Groklaw think otherwise..."
← Back to Stories (view on slashdot.org)
It wouldn't be an over-exaggeration to say that a bulk of SCO-related talks happen here on Slashdot. Even NY Times and other mainstream media frequently refer to Slashdot, when they need a quote from "open-source community", "Linux users" and other group that is mentioned in the article. Thus any DDOS attack organization wouldn't probably go unnoticed on this site.
So here's a question - have you or any friends of yours taken part in SCO DDOS attack? If the overwhelming answer on Slashdot is no, then I guess we know the value of SCO's claims.
SCO will sue Groklaw for illegal use of the term "DDoS", which of course SCO lays claim to.
"Armed forces abroad are of little value unless there is prudent counsel at home" - Cicero
But I sure know that groklaw is DOS'd.
Connection refused.
That just causes more problems for their servers.
When in doubt, parenthesize. At the very least it will let some poor schmuck bounce on the % key in vi. (Larry Wall)
"SCO claims their website was the target of a DoS (Denial of Service) attack. Was it really?"
;)
Groklaw certainly has just been
Cheers,
rob.
Security Expert: "Oh, so um, you claim malicious linux users who you wanted to sue are DDoSing your servers Mr. McBride? Well, let me get out my laptop and check it out."
*boots up linux distro of choice*
"Nope, doesn't look like it was that at all, sorry!"
*evil snicker*
Buy Steampunk Clothing Online!
First they claim they own Linux, and now DOS! What's next, CP/M?
sulli
RTFJ.
I'm being told that Linux has a very simple preventative built in. Linux comes with the ability to block ALL SYN attacks.
all forms of LINUX too bad they are using UNIX
SCO's web site was only designed to handle one person at a time. Until recently, it worked well enough, but recently two people tried to access the web site simultaneoulsy. This, of course, brought down their server. And since the two people were located at different locations, it was distributed; hence, we have a distributed denial of service (DDoS) attack.
And now you know the real story.
For every post, there is an equal and opposite re-post.
SCO probably submitted this story to Slashdot in order to DDoS GrokLaw's web site.... It's working, isn't it?
who in their right mind merges the public internet server and internal intranet server ???
who in their right mind sues IBM???
I'm sure this is just an overture to...
Step 2: "Hackers" infiltrate SCO and maliciously make off with all of the supporting evidence for their suits against IBM. Sorry judge!
Why don't we SYN flood their FTP server? If their claims are correct, it should go offline, right?
But there is another kind of evil that we must fear most... and that is the indifference of good men.
-SCO sold all their servers to increase revenue.
-They took everything down to install MS Windows Advanced Server 2004
- The guy that took over for the sysadmin, after they fired him, tripped and spilled coffee all over the cisco rack. They're waiting for replacements, shipped Express.
- Daryl opened an attachment
~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
Coming up in 2006 release of openserver: SYN flood protection...
What's that, a pair of SCO branded scissors to cut the CAT5?
Trolling is a art,
Later SCO will claim that this is the same server that held the only copy of their moutain of evidence and all of their source code too.
It makes sense to me that they would claim it's a "SYN flood" simply because SYN has a similar sound to "sin" - it sounds evil! A "ping" flood sounds about as threatening to the average person as a pair of daffy duck children's socks.
~/ssh slashdot.org ssh: connect to host slashdot.org port 22: too many beers
It was all their remaining technical people sending out floods of job applications.
One line blog. I hear that they're called Twitters now.
Dear Mr. Judge,
I am sorry but we are unable to provide the source code examples you have requested. These examples were stored on our web server and were lost in a recent DDoS attack on these servers.
By my reckoning, that means we win. Tell IBM to pay up.
-D. McBride
CEO, SCO Group
Punctanym: alternate spelling of words using punctuation or numerals in place of some or all of its letters; see 'leet'
On a different note, perhaps we should all (all /. readers) visit the SCO site each day, maybe even multiple times a day, to make sure we don't miss out on some important information.
And remember, you'll want to disable your cache to do this. Oh, and if you have a browser that allows you to set it to auto refresh, that would be a good idea too. It would really be a shame to miss an important press release just because you forgot to hit Refresh often enough...
Unfortunately, SCO's unknown (linux) server is having some difficulty right now.
What (obviously) amuses me is that this frequent refreshing of their news page would be justified, given their proclivity for using press releases to disseminate important information.
.sigs are for post^Hers.
They forgot to buy a liscense from themselves, and were forced to shut their server down to keep from getting sued by themselves?
Good idea, but just to make sure you get it all, you should mirror the contents. "wget -m" should do the trick, and when the site does get hosed, you'll already have a mirror to share with /. readers!
Looks like both to me. Someone at SCO has a cron job running that starts a DDoS (SYN) attack against www.sco.com from their internal network, and sends out a press release at the same time.
That way Darl doesn't even have to climb out of his lawyers' lap, where he spends the day happily napping and dreaming of Linus as his shoe shine boy.