Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934269AbdC3Q0o (ORCPT ); Thu, 30 Mar 2017 12:26:44 -0400 Received: from mx0b-001b2d01.pphosted.com ([148.163.158.5]:40044 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S933864AbdC3Q0m (ORCPT ); Thu, 30 Mar 2017 12:26:42 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Date: Thu, 30 Mar 2017 13:30:17 -0300 From: Paulo Flabiano Smorigo To: Tyrel Datwyler Cc: =?UTF-8?Q?Michal_Such=C3=A1nek?= , Greg Kroah-Hartman , "Leonidas S. Barbosa" , Herbert Xu , Geert Uytterhoeven , linux-kernel@vger.kernel.org, Paul Mackerras , linux-crypto@vger.kernel.org, Mauro Carvalho Chehab , linuxppc-dev@lists.ozlabs.org, "David S. Miller" Subject: Re: [PATCH] crypto: vmx: Remove dubiously licensed crypto code In-Reply-To: <7ec54553-610c-a5dc-d4d9-3c83f6a161d9@linux.vnet.ibm.com> References: <20170329125639.14288-1-msuchanek@suse.de> <20170329145135.GA28057@kroah.com> <20170329171327.38d4fdd6@kitsune.suse.cz> <7ec54553-610c-a5dc-d4d9-3c83f6a161d9@linux.vnet.ibm.com> User-Agent: Roundcube Webmail/1.0.1 X-TM-AS-GCONF: 00 x-cbid: 17033016-2213-0000-0000-00000179DF91 X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00006875; HX=3.00000240; KW=3.00000007; PH=3.00000004; SC=3.00000206; SDB=6.00840844; UDB=6.00413909; IPR=6.00618856; BA=6.00005248; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00014865; XFM=3.00000013; UTC=2017-03-30 16:26:39 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17033016-2214-0000-0000-00005517DAE2 Message-Id: <8591ac8ff6ef6fa9c4bd264017ac360d@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-03-30_13:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1702020001 definitions=main-1703300144 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2636 Lines: 64 On 2017-03-29 20:08, Tyrel Datwyler wrote: > On 03/29/2017 08:13 AM, Michal Suchánek wrote: >> On Wed, 29 Mar 2017 16:51:35 +0200 >> Greg Kroah-Hartman wrote: >> >>> On Wed, Mar 29, 2017 at 02:56:39PM +0200, Michal Suchanek wrote: >>>> While reviewing commit 11c6e16ee13a ("crypto: vmx - Adding asm >>>> subroutines for XTS") which adds the OpenSSL license header to >>>> drivers/crypto/vmx/aesp8-ppc.pl licensing of this driver came into >>>> qestion. The whole license reads: >>>> >>>> # 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 >>>> >>>> # >>>> # >>>> ==================================================================== >>>> # Written by Andy Polyakov 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/. # >>>> ==================================================================== >>>> >>>> After seeking legal advice it is still not clear that this driver >>>> can be legally used in Linux. In particular the "depending on where >>>> you obtain it" part does not make it clear when you can apply the >>>> GPL and when the OpenSSL license. >>>> >>>> I tried contacting the author of the code for clarification but did >>>> not hear back. In absence of clear licensing the only solution I >>>> see is removing this code. > > A quick 'git grep OpenSSL' of the Linux tree returns several other > crypto files under the ARM architecture that are similarly licensed. > Namely: > > arch/arm/crypto/sha1-armv4-large.S > arch/arm/crypto/sha256-armv4.pl > arch/arm/crypto/sha256-core.S_shipped > arch/arm/crypto/sha512-armv4.pl > arch/arm/crypto/sha512-core.S_shipped > arch/arm64/crypto/sha256-core.S_shipped > arch/arm64/crypto/sha512-armv8.pl > arch/arm64/crypto/sha512-core.S_shipped > > On closer inspection of some of those files have the addendum that > "Permission to use under GPL terms is granted", but not all of them. > > -Tyrel In 2015, Andy Polyakov, the author, replied in this mailing list [1]: "I have no problems with reusing assembly modules in kernel context. The whole idea behind cryptogams initiative was exactly to reuse code in different contexts." [1] https://patchwork.kernel.org/patch/6027481/ -- Paulo Flabiano Smorigo IBM Linux Technology Center