linux-kernel - Re: [2.6 patch] binfmt_som.c: add MODULE

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:	Mon, 11 Aug 2008 10:56:51 -0400 (EDT)
From:	"John David Anglin" <dave@...uly1.hia.nrc.ca>
To:	bunk@...nel.org (Adrian Bunk)
Cc:	grundler@...isc-linux.org, kyle@...artin.ca, matthew@....cx,
	linux-parisc@...r.kernel.org, linux-kernel@...r.kernel.org,
	akpm@...ux-foundation.org, bdale@...com
Subject: Re: [2.6 patch] binfmt_som.c: add MODULE_LICENSE

> On Sun, Aug 10, 2008 at 06:10:15PM -0600, Grant Grundler wrote:
> > On Sun, Aug 10, 2008 at 05:11:59PM +0300, Adrian Bunk wrote:
> > > On Sat, Aug 09, 2008 at 06:55:11PM -0600, Grant Grundler wrote:
> > ...
> > > > Someone from HP needs to ACK this patch since I believe HP funded the code
> > > > changes made during the parisc-linux port. This should be a no-brainer
> > > > and I expect Bdale Garbee can quickly take care of this.
> > > 
> > > Either the file is available since the beginning under the terms of the 
> > > GPLv2 (or a compatible license that can be reduced to GPLv2) or it's 
> > > addition to the kernel was a huge mistake.
> > 
> > As a former HP employee who was one of the several parisc-linux developers,
> > I'm certain the intent was to release this as GPL. That's why I said
> > "this should be a no-brainer".
> > 
> > However, it's still HP's (and not my) right to assert that.
> 
> If it wasn't already 100% clear that the file was released under
> the terms of the GPLv2 (or a compatible license that can be reduced
> to GPLv2) at the day when it was included into the kernel something
> went horribly wrong back then.
> 
> Otherwise HP would have the situation SCO was desperately searching for...

This file was included before the SCO situation arose.  The copyright
notice is similar to most.  Checking 2.6.22.19, I see that more than
half the .c files lack MODULE_LICENSE("GPL") lines.

I don't understand why we are talking about HP here.  According to
Matthew, his last commit to this file occured while he worked for
Genedata.  It is my understanding that copyright normally acrues
to employers in employment situations.  If Matthew was an employee
and not an independent contractor at the time, then why are we not
talking about Genedata, or its subsequent owner?  Subsequent
employment at HP or their funding of the parisc port shouldn't
affect the licensing of a file that was previously contributed.
The file appears to be a derived work.  This may also affect its
copyright status.  The only reason HP should be involved is if the
file somehow contains material copyrighted by HP.

The whole licensing issue for the linux program and modules,
particularly for individual files, appears to be a mess.  The
COPYING file is vague on the licensing for files.   The recommended
wording suggested by the FSF isn't used.  I can't see that adding
MODULE_LICENSE("GPL") lines is going to help much.

There are several GPL licenses and versions.  The line isn't
going to mean much to a lawyer.  I really think each file should
be specific about its licensing in words that can be clearly
understood.

Dave
-- 
J. David Anglin                                  dave.anglin@...-cnrc.gc.ca
National Research Council of Canada              (613) 990-0752 (FAX: 952-6602)
--
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/