linux-kernel - Re: [PATCH 6/6] crypto: add jitterentropy RNG

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: <1429798711.2927.8.camel@x220>
Date:	Thu, 23 Apr 2015 16:18:31 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Stephan Mueller <smueller@...onox.de>
Cc:	herbert@...dor.apana.org.au,
	Andreas Steffen <andreas.steffen@...ongswan.org>,
	Theodore Ts'o <tytso@....edu>,
	Sandy Harris <sandyinchina@...il.com>,
	linux-crypto@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 6/6] crypto: add jitterentropy RNG

On Thu, 2015-04-23 at 16:08 +0200, Stephan Mueller wrote:
> Other patches that are in the kernel that I wrote (e.g. 
> the crypto/drbg.c) have the same license as above, but use 
> MODULE_LICENSE("GPL") -- Thus I would think that leaving it as is should be 
> ok.

Why not submit the trivial patches to make the license comment and the
MODULE_LICENSE() macro match in those files too?

Thanks,


Paul Bolle

--
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/