Wed, Jul 13, 2016 at 01:05:03PM +1000, Stewart Smith wrote: > Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> writes: > > On Mon, 11 Jul 2016 16:07:39 -0300 Paulo Flabiano Smorigo <pfsmorigo@xxxxxxxxxxxxxxxxxx> wrote: > >> > >> diff --git a/drivers/crypto/vmx/aesp8-ppc.pl b/drivers/crypto/vmx/aesp8-ppc.pl > >> index 2280539..813ffcc 100644 > >> --- a/drivers/crypto/vmx/aesp8-ppc.pl > >> +++ b/drivers/crypto/vmx/aesp8-ppc.pl > >> @@ -1,4 +1,11 @@ > >> -#!/usr/bin/env perl > >> +#! /usr/bin/env perl > >> +# Copyright 2014-2016 The OpenSSL Project Authors. All Rights Reserved. > >> +# > >> +# Licensed under the OpenSSL license (the "License"). You may not use > >> +# this file except in compliance with the License. You can obtain a copy > >> +# in the file LICENSE in the source distribution or at > >> +# https://www.openssl.org/source/license.html > > > > So, I assume that this license is compatible with the GPLv2? Andy released this code under the cryptogams license: # ==================================================================== # Written by Andy Polyakov <appro@xxxxxxxxxxx> for the OpenSSL # project. The module is, however, dual licensed under OpenSSL and # CRYPTOGAMS licenses depending on where you obtain it. For further # details see http://www.openssl.org/~appro/cryptogams/. # ==================================================================== The license is GPL compatible: ALTERNATIVELY, provided that this notice is retained in full, this product may be distributed under the terms of the GNU General Public License (GPL), in which case the provisions of the GPL apply INSTEAD OF those given above. > > https://people.gnome.org/~markmc/openssl-and-the-gpl.html has an > explanation and points to: > https://www.openssl.org/docs/faq.html#LEGAL2 > > which makes it anything but clearer. > > it appears the answer is "probably not, unless you have an explicit > exemption in your license" > > -- > Stewart Smith > OPAL Architect, IBM. -- Paulo Flabiano Smorigo IBM Linux Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
