SCO code to be protected in closed court

Andrew Colley,

16 December 2003 05:20 PM

Tags: ibm, sco, source, open, code

When the SCO Group finally lays its cards on the table in its upcoming lawsuit against IBM, the open source community won't be given the opportunity to see them.

IBM last week successfully persuaded the judge presiding over the case to give SCO 30 days to reveal the code that forms the basis for its US$3 billion lawsuit against Big Blue for alleged copyright infringements. The judge originally placed no restrictions on public disclosure of the disputed code and it's understood IBM's filing insisted that the code be revealed publicly.

SCO has brought forward allegations that IBM illegally included its Unix System V code in freely distributed versions of Linux. On the strength of those allegations, SCO has made further claims against commercial users of Linux kernel 2.4.x and later for license fees.

SCO has violently opposed public disclosure of the code at the heart of the dispute, claiming that doing so would damage its ability to leverage its intellectual property in future.

"We can't just open this up to the public. The minute we open it up we have in fact opened it up to the public and we can't restrict it in the future from a proprietary standpoint," said SCO CEO Darl McBride at conference in August this year.

However, SCO public relations director Blake Stowell today said that the company had secured permission to present the code to a closed court.

"In other words, SCO will present this evidence to the jury, the judge and to the defendant (IBM), but it will remain confidential. No one in the public will get to see this code," said Stowell.

It's the first clear sign that the open source community, which has long been frustrated with SCO's secrecy over the code, will never get a chance to see the code nipping at the heart of its development ethos.

SCO has to date only allowed individuals to view the code subject to a non-disclosure agreement (NDA). The NDA has the effect of restricting the release of information that may allow the code to be removed from distributions of Linux.

The situation is frustrating for open source proponents, who believe that SCO has calculated its license claims to extract profit from the legal Catch-22 presented by the situation.

While the situation denies commercial Linux users and the open source community the opportunity to free the operating system from the legal encumbrance brought on by SCO's claims, those facing license demands are being forced to judge the quality of its claims before the court has had the opportunity to test them.

SCO characterises the licenses as a source of "immunity" from future intellectual property claims.

Advertisement

Talkback 13 comments

  1. Well this is just sickening. The Linux leaders (eg, Linus Torvalds) have repeatedly stated that if SCO's code is in Linux then they want it OUT. A tainted Linux is useless to both the developers and to the end-users. The uncertainty is harmful to the pros Nathan Hand -- 16/12/03

    Well this is just sickening. The Linux leaders (eg, Linus Torvalds) have repeatedly stated that if SCO's code is in Linux then they want it OUT. A tainted Linux is useless to both the developers and to the end-users. The uncertainty is harmful to the prosperity of Linux. Without any indecision or uncertainty, the rightful owners of Linux want SCO's code REMOVED from Linux.

    So the Linux leaders have been asking for months for SCO to identify the infringement so Linux can be repaired and life can go on. SCO consistently refuses to help with the reparation process.

    Now IBM has managed to force SCO's hand open - SCO must at last identify the code that they claim is improperly within Linux - yet SCO again manages to negotiate a situation where the infringement, if any, STILL cannot be repaired.

    Does SCO want the alleged infringement fixed? All of their actions suggest that they do not! SCO seems content to delay forever the reparation of Linux. Why? A cynical person might say that SCO wants to hitch their failing flagship products, ruined by years of neglect, to the rising success of Linux. In biological terms, SCO is a parasite.

    This is a travesty. The true owners of Linux - Linus Torvalds and Co - have the legal and moral right to use their independently developed Linux as they see fit. SCO is effectively stealing Linux from the rightful owners, slapping a price tag on it, and using morally corrupt legal manoeuvres to prevent alleged infringements from being fixed.

    SCO has the right to defend their intellectual property but why does SCO refuse to honour the intellectual property rights of Linus Torvalds? Linus wants to distribute Linux as free software with source code, as is his right. SCO wants to stop Linus from exercising his internationally granted and recognised rights to Linux, all under the guise of defending SCO's own rights to UNIX SYSV.

    If there is conflict between Linus's rights and SCO's rights then the judge will find an equitable solution. But SCO wants to create a situation that benefits only SCO. A tainted Linux is harmful to Linus Torvalds and the entire Linux community. SCO must, in their self-appointed role as "defenders of the US constitution", cease their hypocritical actions and allow Linus to have his Linux back, unencumbered by SCO's code.

  2. It is sickening. It's an example of what happens when there are too many lawyers looking for work... Anonymous -- 16/12/03

    It is sickening. It's an example of what happens when there are too many lawyers looking for work...

  3. I am at something of a loss to see how this affects us in any real sense. Although the SysV code may be proprietary knowledge belonging to SCO (albeit, a VERY open secret) the Linux code that they claim infringes upon their copyrights is open source, publ Anonymous -- 16/12/03

    I am at something of a loss to see how this affects us in any real sense. Although the SysV code may be proprietary knowledge belonging to SCO (albeit, a VERY open secret) the Linux code that they claim infringes upon their copyrights is open source, public knowledge, and freely available. As such, it is difficult to imagine that any judge would be dumb enough to claim it should be "kept secret".

    So, SCO tells IBM, "These are the lines we say are ours." Then, when the case comes to trial, SCO offers their proof - and then IBM shows the real history of the code, right back to its first iteration by Thompson and Ritchie.

    [Exit all, laughing]

  4. Won't work... Sco can't have the cake and eat it too. This will never work. The GPL doesn't allow tainted code into the kernel. If SCO claims to owns part of it, Linus is forced to remove it. But if SCO doesn't want to identify it, Linus can't r Anonymous -- 16/12/03

    Won't work... Sco can't have the cake and eat it too.

    This will never work. The GPL doesn't allow tainted code into the kernel. If SCO claims to owns part of it, Linus is forced to remove it. But if SCO doesn't want to identify it, Linus can't remove it.. One could argue that as SCO doesn't identify their property Linus can claim that there is no property of SCO inside the kernel.

  5. Maybe SCO doesn't want the open source community to see their code because they're concerned that they could be found to be infringing on other people's copyrights. SCO has angered so many people by their actions, that any of their hidden source that's re Anonymous -- 17/12/03

    Maybe SCO doesn't want the open source community to see their code because they're concerned that they could be found to be infringing on other people's copyrights. SCO has angered so many people by their actions, that any of their hidden source that's revealed will immediately be scrutinized by an army talented people. If they are found to have significant violations, any chance they have of extorting money through the threat of legal action will evaporate. If that happens a significant part of their business model falls apart.

  6. SCO says their source code is used in linux. Linux is open source and the source code is freely available. Therefore the (alleged) Source code is already released to the public. So not releasing the code publicly at trial doesn't make any sense unless Anonymous -- 17/12/03

    SCO says their source code is used in linux. Linux is open source and the source code is freely available. Therefore the (alleged) Source code is already released to the public. So not releasing the code publicly at trial doesn't make any sense unless it isn't really used in Linux.

  7. This is a litigation ploy. Ryan Tibbitts, counsel for the SCO Group, wrote a very interesting article in the October 2000 issue of the "Utah State Bar Journal." In it, he comments on the lessons learned from the Cal M. Leo Cooper -- 17/12/03

    This is a litigation ploy.

    Ryan Tibbitts, counsel for the SCO Group,
    wrote a very interesting article in the October 2000
    issue of the "Utah State Bar Journal."
    In it, he comments on the lessons learned from
    the Caldera vs. Microsoft case.
    ---
    Point 8 of the article starts:
    "8. Never Agree to an Overly Complicated Protective Order."
    Microsoft caused problems for Caldera with this particular stratagem.
    Now, the SCO Group is attempting to pull off the
    very same shenanigans against IBM.

  8. SCO is highly, highly misleading. I submitted this to the article's author by email as well. +++ Blake Stowell today said that the company had secured permission to present the code to a closed court. +++ "secured p Anonymous -- 17/12/03

    SCO is highly, highly misleading.
    I submitted this to the article's author by email as well.

    +++
    Blake Stowell today said that the company had secured permission to present the code to a closed court.
    +++

    "secured permission" makes it sound like SCO Group approached the judge for special treatment, and after due consideration the judge granted the special treatment.

    No such thing occurred. In the recent orals the judge asked

    "is there a protective order in place?"

    That's IT. She did not even know what was in it, she knew that this was one of the issues in the motions and ONLY wanted to know if IBM and SCOG had reached agreement.

    ++
    SCO will present this evidence to the jury, the judge and to the defendant (IBM)
    ++

    One out of 3 correct. 33%. That's usually a failing mark.

    IBM will see the current submissions. That's the party to which SCO Group has been ORDERED to present evidence.

    The current submissions are NOT to a judge.
    The current submissions are NOT be presented to a jury.

    As a final note, there are many judicial decisions regarding what SCO Group is currently attempting with their NDA show (attempting to put "trade secrets" back in a bottle after they've been distributed far and wide.)

    All the decisions say "too bad".

  9. is the judge asleep? SCO wants to secretly present code that has been published in the widest possible way for the past 10 years. code that's available on hundreds of FTP servers, that's been published on millions of CDROMs. Mark Hahn -- 17/12/03

    is the judge asleep? SCO wants to secretly present code that has been published in the widest possible way for the past 10 years. code that's available on hundreds of FTP servers, that's been published on millions of CDROMs.

  10. The logic behind this is baffling, SCO’s argument is like saying that we can’t let the horse out of the barn because it will runaway. When they are claming that IBM didn’t just leave the door open; but they took the horse and set it free. If the horse is Anonymous -- 17/12/03

    The logic behind this is baffling, SCO’s argument is like saying that we can’t let the horse out of the barn because it will runaway. When they are claming that IBM didn’t just leave the door open; but they took the horse and set it free. If the horse is out, then let everybody know so that appropriate action can be taken to resolve the situation.

  11. Same thing happened with AT&T vs BSD. Closed court, sealed results. Anonymous -- 17/12/03

    Same thing happened with AT&T vs BSD. Closed court, sealed results.

  12. AT&T was different 99% of what USL was claiming as their property was made public. AND There was no decision from the judge - the judge issued a ruling on USL's request for a preliminary injuction. In that ruling was so Anonymous -- 17/12/03

    AT&T was different

    99% of what USL was claiming as their property was made public.

    AND

    There was no decision from the judge - the judge issued a ruling on USL's request for a preliminary injuction. In that ruling was some language that was VERY, VERY bad for USL and with this to motivate USL the parties settled and both parties agreed to keep the settlement (BUT NOT THE CODE) secret.

    So the only thing that was "secret " at the end of the AT&T / USL vs Regents of UCB was the settlement.

    ALL THE CODE WAS RELEASED. (except I believe 3 files)

  13. Where do you get this information from, Echalon? This article is a waste of bandwidth Anonymous -- 17/12/03

    Where do you get this information from, Echalon? This article is a waste of bandwidth

Add your opinion


Latest Videos

ZDNet's CIO Vision Series

Department of Defence | Greg Farr, CIO (part two)

In the second part of his interview, Defence CIO Greg Farr talks about outsourcing, the skills crisis and reveals his most urgent IT priority.

Sponsored content

Power Centre - Content from our premier sponsors

Blogs

  • Angus Kidman I'm a celebrity, don't back me up
    Celebrity comes with its perks — free alcohol, better-looking partners, lots of holiday time — and disadvantages — constant media intrusions, being forced to appear in films with Eddie Murphy for the long-term good of your career, and having to do mindless radio interviews with angry men who've been awake since 4am.
  • Array Lies, damned lies and telco stupidity
    Earlier this month, Telstra put out a press release trumpeting that it's come up with a new phone coaching service to help people who are "bamboozled" by their mobiles. Another excellent example of wrongheaded thinking from the mobile industry.
  • Array Dear carriers: More walking, less talking
    Sometimes, a well-placed and well-timed letter can make all the difference. Other times, it can make no difference at all — and even hurt your case. This week's missive by the Competitive Carriers' Coalition, I would suggest, falls into the latter category.
  • More blogs »

Tags

Back to top

Featured