From: Matthew Dharm <mdharm-kernel@one-eyed-alien.net>
To: Gidon <gidon@warpcore.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel GPL Violations and How to Research
Date: Tue, 10 Feb 2004 13:52:13 -0800 [thread overview]
Message-ID: <20040210215213.GA8092@one-eyed-alien.net> (raw)
In-Reply-To: <1076449796.6373.3.camel@CPE-65-26-89-23.kc.rr.com>
[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]
On Tue, Feb 10, 2004 at 03:49:56PM -0600, Gidon wrote:
> On Tue, 2004-02-10 at 13:20, Matthew Dharm wrote:
> > As a final level of analysis, you can always look at the compiled binary
> > code -- if you think they are using a _reasonably_ compatible compiler, you
> > might actually be able to find long sections of identical or near-identical
> > assembly (modulo loop unrolling, etc. which you should be able to identify
> > by hand.)
>
> Your advice is appreciated. I will do some further research using
> objdump. I believe they use gcc.
>
> One thing I am unsure of is how to approach them and ensure at the same
> time that the problem is taken care of. Another words, if I show them
> what's wrong, they may simply obfuscate it (although at this time I hope
> not) and then I have no way to easily prove anything anymore...
Obfuscation can obscure the names of functions, but generally not string
constants or the structure of functions calling other functions.
Tho, if it comes to that point, you need a lawyer.
Matt
--
Matthew Dharm Home: mdharm-usb@one-eyed-alien.net
Maintainer, Linux USB Mass Storage Driver
What, are you one of those Microsoft-bashing Linux freaks?
-- Customer to Greg
User Friendly, 2/10/1999
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-02-10 21:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 4:53 Kernel GPL Violations and How to Research Gidon
2004-02-10 19:20 ` Matthew Dharm
2004-02-10 21:49 ` Gidon
2004-02-10 21:52 ` Matthew Dharm [this message]
2004-02-10 22:07 ` Gidon
2004-02-13 19:02 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040210215213.GA8092@one-eyed-alien.net \
--to=mdharm-kernel@one-eyed-alien.net \
--cc=gidon@warpcore.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox