Repository navigation
New license request: BSD-3-Clause Cryptogams #5253
Description
Activity
Commenting here in this issue and will link to this issue in the PR #5288
License text
The copyright years differ between:- https://openssl-library.org/cryptogams/ says
Copyright (c) 2006-2017, CRYPTOGAMS by <appro@openssl.org> - https://raw.githubusercontent.com/dot-asm/cryptogams/master/LICENSE says
Copyright (c) 2006, CRYPTOGAMS by <appro@openssl.org>
Apart from that, the licenses are the same. I'd rather not add two licenses, e.g.
LicenseRef-scancode-bsd-3-clause-cryptogams-2006andLicenseRef-scancode-bsd-3-clause-cryptogams-2017, so we need to add rules to detect both year declarations.License applications
The license is applied differently, which needs to be addressed in a PR.
ia64/keccak1600-ia64.pl
URL: https://github.com/dot-asm/cryptogams/blob/master/ia64/keccak1600-ia64.pl
# ==================================================================== # Written by Andy Polyakov, @dot-asm, initially for use in the OpenSSL # project. The module is dual licensed under OpenSSL and CRYPTOGAMS # licenses depending on where you obtain it. For further details see # https://github.com/dot-asm/cryptogams/. # ====================================================================src/crypto/fipsmodule/sha/asm/sha512-armv4.pl
URL: https://github.com/google/boringssl/blob/688fc5cf5428868679d2ae1072cad81055752068/src/crypto/fipsmodule/sha/asm/sha512-armv4.pl#L10-L17# ==================================================================== # Written by Andy Polyakov <appro@openssl.org> 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/. # # Permission to use under GPL terms is granted. # ====================================================================Thanks to @tsteenbe
cryptogams/arm/sha512-armv8.pl
URL: https://github.com/dot-asm/cryptogams/blob/master/arm/sha512-armv8.pl
# SPDX-License-Identifier: GPL-1.0+ OR BSD-3-Clause # # ==================================================================== # Written by Andy Polyakov, @dot-asm, initially for the OpenSSL # project. # ====================================================================Note: The author refers to
BSD-3-Clause, does the author mean the cryptogram license? SinceBSD-3-Clauseis clearly stated above my take is that we can assume thatBSD-3-Clauseis the license. So, no need to add a rule for this file (and similar).- https://openssl-library.org/cryptogams/ says
This license has been added as
bsd-3-clause-cryptogams/LicenseRef-scancode-bsd-3-clause-cryptogams. @AyanSinhaMahapatra please add it to the scancode db
License Name
TBD, BSD-3-Clause Cryptogams?
License Homepage URL
https://openssl-library.org/cryptogams/
Reference URLs