Most variants of copyright infringement are a civil, not criminal matter.
This means the state has no interest in enforcing the, it's your job to sue
for damages and a restraining order if you want to exercise these rights
(some people choose not to), and you have to have standing (I.E. be a holder
of one of the infringed copyrights, or a designated legal representative
thereof) in order to sue. If none of the copyright holders sue to stop it,
then it doesn't get stopped no matter how blatantly infringing it is. Did
anybody even bother to send Tivo a cease and desist?
Erik Andersen burned himself out trying to enforce the copyrights on BusyBox
before Pamela Jones hooked that project (and uClibc) up with the SFLC.
Harald Welte's been burning the candle at both ends with gpl-violations.org,
but he's focusing on stuff sold in Germany.
As for anti-tivoisation, you can make a case that your signed binary is a
derived work of the GPL source code just like a non-signed binary is,
therefore the signing key is part of the source code used to create that
binary, therefore GPLv2 requires the signing key be handed over on request.
(I don't know if you'd WIN, I just know you could reasonably argue it in
court and probably get past the inevitable initial motions to dismiss.)
GPLv2 is a nice, elegant license. It's not perfect but it's very simple for
what it does.
GPLv3 is not simple, not elegant, and contains numerous of special cases.
Lots of the programmers here have an instinctive aversion to it because it
reads like bad code. We don't necessarily have to program in legalese to
sense bad code in that language, at least compared to a "good code" example
we've been using for some time.
