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]
Message-ID: <20100315182338.GG4484@thunk.org>
Date:	Mon, 15 Mar 2010 14:23:38 -0400
From:	tytso@....edu
To:	Evgeniy Ivanov <lolkaantimat@...il.com>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: Using parts of ext2_fs.h in BSD licensed code

On Mon, Mar 15, 2010 at 08:26:16PM +0300, Evgeniy Ivanov wrote:
> Just found, that recently FreeBSD got this:
> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/fs/ext2fs/ext2fs.h
> It looks like I can easily include it to the BSD-licensed project and
> no GPL violation. But I dunno how did they wrote ext2fs.h, since it
> still must be based on ext2_fs.h

Constants and code points aren't subject to copyright, so they don't
have ask any question.  The places where things start to get dicy is
with inline function and CPP macros, especially when the code starts
become non-trivial.  i.e., there's only one way to do "(foo & MASK) !=
0", so that's probably not subject to copyright.  A complicated 20
line function, even if it's in a header file, is probably going to be
subject to copyright.  What is and isn't a matter of copyright is
something you'd have to get a lawyer to answer for you.

You can of couse also request permission, but that can get tricky,
especially if the person who originally wrote it can't easily be
tracked down (I haven't talked or e-mailed with Remy in years), or if
it was done by someone while being paid by their employer, in which
case some corporate lawyers might have to be dragged in to give
permission.

Fortunately I don't think there's much in the way of complicated code
in the header files that you would have to deal with.

Best regards,

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ