Kernel developers' position on GPLv3

Posted Sep 24, 2006 18:37 UTC (Sun) by msbrown (guest, #38262)
In reply to: Kernel developers' position on GPLv3 by k8to
Parent article: Kernel developers' position on GPLv3

Refutation:

I point you to FIPS 140-2 ( http://csrc.nist.gov/cryptval/140-2.htm ).

Yes, GPLv3 (draft 2) code cannot be used in FIPS 140 environments.

You really _don't_ want crypto modules that can be modified by third-parties, not all of whom intend to _improve_ your your module.

to post comments

Kernel developers' position on GPLv3

Posted Sep 24, 2006 23:04 UTC (Sun) by k8to (guest, #15413) [Link]

That GPLv3 draft two requires it be possible that code be modified and
still perform in its primary function does not require that the crypto
module itself which is used in conjunction with GPLv3 code be modifiable.

I am uncertain if that makes the code usable in a FIPS 140-2 context, but
your comment seems overbroad.

Separately it seems to me an open question whether making it possible to
run code on such a platform after modification, but with a flag that
indicates that it is not original code, would satisfy the GPLv2
provisions as writtten. It is also an interesting question whether it is
desirable that it be possible for same to satisfy these conditions.