[PATCH 1/5] PowerPC optimized routines for AES and SHA2 using PowerISA
jussi.kivilinna at iki.fi
Tue Aug 20 19:55:42 CEST 2019
I've start implementing PowerPC vector crypto AES implementation without
cryptogams on top of your patch "re-implement single-block mode, and
implement OCB block cipher". I expect AES work to be completed by the end
of this month, SHA2 in September and GHASH in Sep~Oct.
On 18.7.2019 2.41, Shawn Landden wrote:
> 09.07.2019, 16:05, "Werner Koch" <wk at gnupg.org>:
>> On Tue, 9 Jul 2019 09:58, shawn at git.icu said:
>>> From CRYPTOGAMS https://www.openssl.org/~appro/cryptogams/
>> I had a quick look at the license and I can't see that this license
>> allows the inclusuon int Libcgrypt which is available under the GNU
>> Copyright (c) 2006-2017, CRYPTOGAMS by <appro at openssl.org>
>> All rights reserved.
>> The copyright line does not seem to identify a holder of the copyright.
>> Weel, unless "CRYPTOGAMS by <appro at openssl.org>" is a legal entity.
>> Redistribution and use in source and binary forms, with or without
>> modification, are permitted provided that the following conditions are
>> * Redistributions of source code must retain copyright notices, this
>> list of conditions and the following disclaimer.
>> * Redistributions in binary form must reproduce the above copyright
>> notice, this list of conditions and the following disclaimer in the
>> documentation and/or other materials provided with the distribution.
>> * Neither the name of the CRYPTOGAMS nor the names of its copyright
>> holder and contributors may be used to endorse or promote products
>> derived from this software without specific prior written
>> This looks like a standard BSD licese but I didn't checked it.
> No, this does not require attribution. It is not the dreaded old OpenSSL license. You are looking right at it,
> and it does not have the line you are imagining, which looks like this:
> 3. All advertising materials mentioning features or use of this software
> must display the following acknowledgement:
> This product includes software developed by the Reagents of The University of California, Berkeley.
>> 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.
>> Problems with this: It allows only GNU GPL, does not provide a version
>> of it, and seems to be invalidating itself because it adds a further
>> restriction to the GPL, namely that "this notice is retained in full".
>> Anyway GPL is too restrictive for Libgcrypt.
>> Whether we can exceptionally add BSD code needs to be discussed but has
>> the very practical problem that all users of Libcgrypt need to update all
>> their documentation to include the required statements and copyright
>> notices for the BSD license.
>> I am sorry for these bad news and I hope a solution can be found.
>> Either by removing all OpenSSL code or by asking the original author to
>> change to a better usable and more standard license.
>> Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
More information about the Gcrypt-devel