linux-kernel - Re: GPL Violation: Compro Technology Inc, 2.6.17 modified binary-only kernel distribution

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 30 May 2008 08:33:23 +0100
From:	Jo Shields <directhex@...box.org>
To:	David Newall <davidn@...idnewall.com>
Cc:	linux-kernel@...r.kernel.org, license-violation@...-violations.org
Subject: Re: GPL Violation: Compro Technology Inc, 2.6.17
	modified	binary-only kernel distribution

On Fri, 2008-05-30 at 13:19 +0930, David Newall wrote:
> Jo Shields wrote:
> > The infringing drivers have been removed from Compro's website, and
> > replaced with the following message:
> 
> I'd like to know how you achieved that result.  Netcomm, an Australian
> manufacturer of modems, use Linux in a number of their ADSL products,
> for example their NB5 range but I suppose, also, all of their modern
> products.  They provide no acknowledgement on the box, nor in the
> documentation, nor on their web.  I've exchanged emails with David
> Stewart <davids@...comm.com.au>, their Managing Director, in which I
> explained the legal requirements, and also pointed out some high profile
> companies that had been sued over their violations.  He certainly
> understood the situation and promised to have the box and documentation
> modified appropriately, but that was a year ago and nothing has been
> done.  What can be done?

It sounds like I got off lightly - I simply contacted them via their
support email address (to which I've still received no reply), then
followed up a few days later by going to the tech press in an effort to
embarrass them into action. An associate also bought a card to determine
whether their infringing kernel image is on the driver CD as well as the
website, but the CD hasn't been looked at yet. I suppose it doesn't make
much difference now, and given they've publicly acknowledged the problem
I don't feel like chasing them over the CD issue (if it is indeed an
issue)

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/