lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <200610011648.k91Gmtc4032526@turing-police.cc.vt.edu>
Date:	Sun, 01 Oct 2006 12:48:55 -0400
From:	Valdis.Kletnieks@...edu
To:	James Bottomley <James.Bottomley@...elEye.com>
Cc:	tridge@...ba.org, linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: GPLv3 Position Statement

On Sun, 01 Oct 2006 10:45:50 CDT, James Bottomley said:
> Erm ... I think you'll find there's already case law precedent on that:
> the SCO case.  The question there was could SCO sue IBM for copyright
> infringement after having distributed the kernel from their website.
> The answer, from the judge in the case, was yes.

(IANAL, just an interested amature bystander - if my explanation actually
matters to anybody, they should hire competent legal representation instead)

Note that the precedent set there was "Yes, you can *file suit* about it",
handed down by a judge that is being *very* careful to not leave *any*
possible reason for SCO to have grounds for an appeal (and "judge improperly
denied our cause of action" would likely qualify for an appeal).

(For those readers outside the US - due to quirks in the US legal system,
it *is* permissible to bankrupt yourself by filing pointless lawsuits that
have no chance of winning.  The truly dangerous part is that the people you
sue often countersue, and include "and attourney's fees" in the list of
damages they claim.  So if you sue somebody and it costs them $150K to
defend themselves against a pointless lawsuit, you can end up owing them
$150K....)

IBM recently filed a motion for summary judgement on one of their
counterclaims, which basically said "SCO isn't permitted to ask for it after
distributing it themselves".  Once that counterclaim is resolved, *then* we
will have a better precedent to cite (most likely changing "You can file suit
about it" into "You can file suit, but SCO v. IBM already said you can go stick
it in a pig, unless your lawyer can show how this case is *different* from SCO
v. IBM").  And that's the way the legal system works in the US - both sides
cite all the precedents they think support *their* view of the case, the
judge listens to all of them, and decides one of the following:

1) The case is basically the same as a precedent cited by one side or the other,
and therefor the ruling should be decided the same way.

2) The judge buys one side's claim that this is a *new* situation, and writes
a precedent-setting ruling for the situation.

3) Rarely, except in appelate courts, the judge will decide a prededent's
situation applies,  but that the previous judge got the ruling wrong, and
will overrule the prededent.  Most often, this happens when a lawyer cites
a precedent from a different "District" (the US is divided into a dozen or
so Districts, each of which has a semi-autonomous set of courts).  Occasionally,
the Supreme Court will take a case of the form "The Third District precedent
is this, and the Ninth Distric is that, and we need to know which one is
the Law of the Land".

And yes, every once in a while, a lawyer will even base a case on claiming
that a Supreme Court ruling is an incorrect precedent, usually by arguing
that the precedent was written in 1873, and that society has changed so much
that the ruling doesn't apply correctly anymore, or similar.

Content of type "application/pgp-signature" skipped

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ