SCO Madness Reigns Supreme
Roblimo knows good, honest Constitutional argumentation when he sees it, and over on NewsForge amplifies SCO's claims that the GPL is unconstitutional.
Dopey Panda writes "Looks like SCO has become just a bit worried about their liabilities for distributing the Linux kernel. Starting November 1 you will have to be a registered SCO customer to be able to access their FTP site. So that leaves just a couple days for you to download your own genuine SCO-approved GPL code!"
And perhaps today's most interesting SCO submission: 1HandClapping writes "In alwayson-network.com, Mark F. Radcliffe (HIAL) writes about a little-reported aspect of the SCO vs IBM case: 'Novell, as part of its sale of the UNIX licenses to SCO, retained the right to require SCO to "amend, supplement, modify or waive any right" under the license agreements (and if SCO did not comply, Novell could exercise those rights itself on SCO's behalf). At IBM's request, Novell employed this right and demanded that SCO waive IBM's purported violations. When SCO did not do so, Novell exercised its right to waive the violations on SCO's behalf. Basically, this defense destroys the core of the SCO case: IBM's violation of its UNIX license with SCO.'"
Consider that Noorda has been around the tech industry a LONG time, that he has been involved in a lot of companys, he presumably knows who the A-team and B-team players are, and that he appears to dislike Microsoft a little bit.
So - he takes one of the organizations under his control. He fills it with C-team players. He fills (or prompts someone to fill) the C-team with truthful but misleading information about SCO's purported "intellectual property". He advises them to go after the biggest target first.
Then he sits back and watches while SCO leads a hopeless charge against IBM. This has the dual effect of (a) laying down case law _supporting_ the GPL that Microsoft will have a very hard time overturning (b) smoking out various linkages and anti-competitive behaviour on Microsoft's part.
Crazy, but I have a hard time seeing why else SCO is being so incompetent.
I posted this to LWN earlier....
It's important to understand that this really is a war, and SCO has a point, albeit not one that sane people should accept.
The GPL is a truly revolutionary license, it is *designed*, as SCO says, to reduce the financial value of proprietary software. Yes, GPL software is freer than public domain, in the sense that the source code can never be taken proprietary (other than by the original author) and redistributed.
SCO's argument will likely be that this contravenes Congress's will, by creating a commons under rules other than those established by law.
SCO will say that GPLed code cannot be restricted by export controls, thus violates national security laws.
According to SCO, GPL purports to grant *too much freedom* and therefore, according to this argument, the lesser freedom of the public domain is and should be the appropriate terms by which previously GPLed code should be distributable.
By this reasoning, then, SCO will claim it has every right to use GPL code in its proprietary distributions, but on the other hand, can contend that its own code (or code which IBM created under a license which grants SCO ownership of their code) was never intended (by SCO) to be released under GPL nor public domain.
Now, to fully understand these arguments, you must put yourself in the mindset of a madman. Which, undoubtedly, Darl McBride is. Microsoft and others have surely encouraged his delusional state, and given him the resources he needs to pursue his dreams of world domination, with the understanding that even if SCO has no chance of succeeding in the final analysis, the legal case can and will create FUD to slow the adoption of Linux and buy time for proprietary firms.
If this is a war, SCO is a foot soldier. SCO will die, of course, but that's what foot soldiers are expected to do.
Peace and love, y'all
Right, the biggest problem with SCO's case is that they refuse to mitigate their damages by telling the Linux community what the parts of the code alleged to infringe are.
It is very clear that the minute SCO reveals that information that the code will be yanked and replaced by non infringing code, most likely within hours, days at the outside.
This limits the damages that SCO can claim, since it is very clear that the infringement is not only not willful, it is involuntary. The only reason why the infringement is continuing is because SCO refuses to release that information.
The analogy would be to the distributor of a compilation 'best of hits' CD consisting of a selection from the distributor's archives, being challenged by a record label claiming that it is actually the legitimate owner of the rights to one of the songs on the compilation but refusing to specify which song is in dispute. The distributor of the compilation is then given the choice between not distributing the CD at all and risking a possibly bogus infringement claim. If the distributor is told the song that is in dispute they can easily swap it for a different one, it is the refusal to be specific that is the only reason that the plaintif's claim has standing.
This is not estoppel, but estoppel could also apply. SCO has allowed Linux to be distributed for many years and is in fact a distributor itself. Failure to enforce claims can result in them being lost. In fact this is the same claim that SCO is making against the GPL.
I don't think that the SCO objection holds because it is the behavior of IBM that is at issue, not the FSF. In this case IBM does not appear to have a history of failure to enforce its limited reciprocal rights under the GPL for the simple reason that SCO is the first company to attempt to sue...
Looking for an Information Security student project suggestion?
Try http://dotcrimeManifesto.com/