]> git.ipfire.org Git - thirdparty/linux.git/commit
crypto: x86/aes-xts - change license to Apache-2.0 OR BSD-2-Clause
authorEric Biggers <ebiggers@google.com>
Mon, 10 Feb 2025 17:17:40 +0000 (09:17 -0800)
committerHerbert Xu <herbert@gondor.apana.org.au>
Sat, 22 Feb 2025 07:56:03 +0000 (15:56 +0800)
commit0926d8ee088f67d9e4ea0da7efbe369da52e68a8
treecfd28b3e50e4675e8f9eca8ad1a5f137a071fa09
parent8c4fc9ce402cda3132273ea8a9ee4e0302296762
crypto: x86/aes-xts - change license to Apache-2.0 OR BSD-2-Clause

As with the other AES modes I've implemented, I've received interest in
my AES-XTS assembly code being reused in other projects.  Therefore,
change the license to Apache-2.0 OR BSD-2-Clause like what I used for
AES-GCM.  Apache-2.0 is the license of OpenSSL and BoringSSL.

Note that it is difficult to *directly* share code between the kernel,
OpenSSL, and BoringSSL for various reasons such as perlasm vs. plain
asm, Windows ABI support, different divisions of responsibility between
C and asm in each project, etc.  So whether that will happen instead of
just doing ports is still TBD.  But this dual license should at least
make it possible to port changes between the projects.

Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
arch/x86/crypto/aes-xts-avx-x86_64.S