ESR: Let SCO hang itself
From: | "Eric S. Raymond" <esr@snark.thyrsus.com> | |
To: | wire-service@snark.thyrsus.com | |
Subject: | Let SCO hang itself | |
Date: | Sat, 23 Aug 2003 20:10:18 -0400 |
The confrontation between SCO and the open-source community has now escalated to open war. I suppose, in retrospect, that this was inevitable once SCO announced its intention to sue on a theory that would make all open-source licenses invalid. And we all know who's lurking like Emperor Palpatine behind Darl Vader, funding his lawsuit to the tune of at least $6,000,000[1] even if not otherwise pulling his strings. SCO/Caldera's site is being hit by a massive denial-of-service attack today. The timing, the scuttlebutt on Slashdot and elsewhere, and the contents of my mailbox all suggest strongly that the DOS attack was triggered by Darl McBride's slanderous interview[2] accusing the community of being IBM's sock puppets, and my response[3] to it. It appears that my response articulated what many of us have been feeling for months as SCO's public rantings grew ever wilder and more destructive. McBride's personal accusations against me bother me very little, but I am nevertheless honored and humbled by the heartfelt support many of you have emailed. A good number of you seem to want to elect me your war-leader in this crisis -- maybe it's time for me to dust off that Obi-Wan Kenobi costume the SVLUG people made for me to wear on the original Windows Refund Day :-). I will strive to be worthy of your trust. With whatever authority I have, I ask that the DOS attack cease immediately. Please stand down *now*. We have better ways to win this fight. There are at least three reasons running a denial-of-service against SCO is a bad idea: First: We're the good guys. But that doesn't matter if we aren't *seen* to be the good guys. We cannot fight our war using vandalism and trespass and the suppression of speech, or SCO will paint us as crackers and maybe win. Let's keep the moral high ground here. Second: We have other tools that are more powerful. We have an astonishingly strong set of facts on our side. SCO has been caught in multiple lies, wholesale IP violations, and defamatory statements. The way to destroy them is with legal weapons. We can do that. Third: SCO is its own worst enemy. Every time its spokespeople open their mouths, they dig their company's grave a little deeper. Consider their statements at SCOforum and what followed. We're in an even stronger position than we were three days ago. We *want* them raving in public. It helps us. Everything they say is more rope to hang them with in a courtroom, but they're too trapped in their own propaganda-based strategy to do the smart thing and shut up. Their problem is that the moment they stop FUDding long enough for people to get a clear-eyed look at the facts[4] their credibility will evaporate and their stock price will crash hard. Even all the legions of Microsoft's press shills, captive analysts, and astroturfers won't be able to rescue them. Stop the DOS attack. Let SCO speak out and hang itself. Right now, the most helpful thing you can do is collect SCO's published statements and show how they have repeatedly contradicted themselves and lied about the facts. I've received some genuinely useful stuff by email describing factual and legal vulnerabilities that the research team[5] here at Alliance HQ didn't spot on its own -- papers like Greg Lehey's analysis[6] of the code SCO revealed at SCOforum showing that they must have stripped BSD copyrights out of their kernel tree. The reports indicating reason to believe that there is probably GPLed code in Unixware's Linux Personality Module were helpful too. One of our big advantages over SCO is distributed brainpower. There are a lot of us, and we have excellent Internet-research skills. Want to strike a blow against SCO? Help convict them using their own public statements, their own 10Ks and 10Qs, all the press coverage, the material that's in their web and FTP sites. Collate. Assemble dossiers. The facts are with us, so gather and use the facts. All cheesy Star Wars references aside, this is info-war. Truth -- believable and provable truth -- is the weapon. This is why sites like the IWeThey SCOvsIBM page[7] and WeLoveTheSCOInformationMinister[8] aren't just good clean fun; they're valuable references to help lawyers demonstrate SCO's record of bad faith, lies, and massive intellectual-property theft. Do more of that; in particular. the IWeThey wiki badly needs updating and better cross-references. These things will be used to defeat SCO -- and sooner than you probably think. I'm organizing a conference call early this coming week among a few key leaders to decide on the next stage of our response. Have patience. There is a plan developing, which I can't talk about because the element of surprise is part of it. We will counterattack at a time and place of our choosing and we will win. Rebel Alliance provisional command, over and out... :-) [1] http://www.infoworld.com/article/03/08/08/31OPcringely_1.html [2] http://www.nwfusion.com/news/2003/0825scoatta.html [3] http://www.catb.org/esr/writings/mcbride.html [4] http://www.opensource.org/sco-vs-ibm.html [5] The research team: myself, Rob Landley, and Catherine Raymond, esq. [6] http://www.lemis.com/grog/SCO/code-comparison.html [7] http://twiki.iwethey.org/twiki/bin/view/Main/SCOvsIBM [8] http://www.anerispress.com/wltsim/ -- <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
Posted Aug 24, 2003 16:00 UTC (Sun)
by dwalters (guest, #4207)
[Link] (1 responses)
Come on guys. We're better than this! This isn't the way to win this fight!
Posted Aug 24, 2003 17:13 UTC (Sun)
by proski (subscriber, #104)
[Link]
Posted Aug 24, 2003 17:30 UTC (Sun)
by rst (guest, #5098)
[Link] (2 responses)
Posted Aug 24, 2003 18:13 UTC (Sun)
by fLameDogg (guest, #11305)
[Link]
Okay, maybe that's a little off the deep end...
Posted Aug 24, 2003 19:59 UTC (Sun)
by ccchips (subscriber, #3222)
[Link]
It's not so much that somebody involved with Linux did it, as that we won't tolerate such behavior.
Posted Aug 24, 2003 21:53 UTC (Sun)
by bojan (subscriber, #14302)
[Link] (6 responses)
This is where it ends. You can also read about this here: http://news.netcraft.com/. It isn't clear at this point that this is a DOS attack. So, unless ESR knows something we don't (I certainly hope he doesn't), it would be better if he didn't come out with things like this.
Posted Aug 25, 2003 0:12 UTC (Mon)
by namaseit (guest, #13940)
[Link]
Posted Aug 25, 2003 5:14 UTC (Mon)
by bojan (subscriber, #14302)
[Link] (4 responses)
Apparently he does know more: http://linuxtoday.com/infrastructure/2003082501026NWCYLL
Posted Aug 25, 2003 9:42 UTC (Mon)
by antonio (guest, #4712)
[Link] (2 responses)
Eric, please think twice before speaking for us (or ask somebody for advice before doing it)
Posted Aug 25, 2003 11:45 UTC (Mon)
by WRatzka (guest, #912)
[Link]
Posted Aug 25, 2003 16:38 UTC (Mon)
by jeff@uclinux.org (guest, #8024)
[Link]
Eric is however a part of "the community" that often speaks. Jeff.
Posted Aug 25, 2003 15:01 UTC (Mon)
by dwalters (guest, #4207)
[Link]
I trust Eric will do the right thing and co-operate with the authorities in telling them everything he knows about this "associate" of the attacker.
Posted Aug 25, 2003 16:23 UTC (Mon)
by walterbyrd (guest, #11620)
[Link]
Posted Aug 25, 2003 17:40 UTC (Mon)
by strombrg (subscriber, #2178)
[Link]
If someone cracks it, SCO will be able to say "Look at those mean linux people attacking us again!" and "Look how insecure linux is. You wouldn't have this problem if you bought our products..." Further, rumor has it that someone has been trying to alert SCO to this problem, and SCO has been deftly ignoring it. The question then is, "Has SCO intentionally left that vulnerability, so they can spread FUD with righteous indignation?" Seems like maybe they want us to hang ourselves. If you're interested in some more information on this, check out an archive of the full-disclosure mailing list.
Posted Aug 25, 2003 18:05 UTC (Mon)
by wwns (guest, #14443)
[Link]
I still can't reach sco.com (Sunday 16:00 GMT), so it looks like the DOS attack (if indeed that's what's responsible for the outage) is still going on.ESR: Let SCO hang itself
It's an insult for LWN readers to imply that those responsible for the DoS attack read LWN. Try posting on Slashdot, it may be more effective :-)
ESR: Let SCO hang itself
Further analysis by folks in this comment thread on
GrokLaw suggests that this is more likely some sort
of routing anomaly than anything else. Eric may well be jumping the gun here...
Not clearly DDOS
Or SCO is doing it to themselves, with hopes of giving the OSS/FS community a black eye.Re: Not clearly DDOS
Nonetheless, it's good to see that there are people who will stand up for proper behavior.Not clearly DDOS
9 137.39.31.190 182.438 ms 179.052 ms 179.155 msFYI: traceroute from down under
10 152.63.0.114 176.487 ms 152.63.0.150 179.120 ms 178.973 ms
11 152.63.1.26 218.494 ms 152.63.2.37 200.979 ms 203.032 ms
12 152.63.123.221 226.429 ms 152.63.89.233 218.978 ms 219.149 ms
13 152.63.72.77 218.351 ms 219.054 ms 152.63.72.81 217.111 ms
14 157.130.162.54 210.334 ms 211.010 ms 212.945 ms
15 * * *
I have actually seen this happen before earlier this week. Exact same thing happened to FYI: traceroute from down under
homelan.com
It wasnt a DOS attack. Just a drop off.
> So, unless ESR knows something we don't (I certainly hope he doesn't), it would be better if he didn't come out with things like this.FYI: traceroute from down under
I don't think Eric's letter was a good idea. Can you imagine the headlines that SCO and other Open Source opponents can make out of this? FYI: traceroute from down under
There was no need to establish in public a connection between our community and the DOS attack.
Sorry, but the link between the DOS attack and the Linux community would have FYI: traceroute from down under
been made anyway.
So it is important to emphasize, that such actions are not condoned by the
community.
Silence is golden... facts speak for themselves. Eric doesn't speak for "the community".FYI: traceroute from down under
With friends like this, who needs enemies!Eric's source
Apparently it was embarassing to scox to run their own web servers on mandrake linux. Scox is trying to switch over to unix, and having some trouble.Scox "upgrading" service from Linux to "real" UNIX
Rumor has it that SCO has an ftp server up that's vulnerable to a remote-root exploit.ESR: Let SCO hang itself
I assume that SCO was just cleaning various useful things from their web servers this weekend. With all the anti SCO evidence they had on their site I would not be surprised. My thoughts on the controversy and the outcome can
be found here
After that there is a test :-). I hope others find in worthwhile.
Dave
ESR: Let SCO hang itself