TODO

- linker version script - how do I do that with meson?

- Linux kernel Makefile: make clean does not prune files generated by sources
  wrapped in ifdefs in Makefile

- how to detect ARMv6 (in contrast to ARMv7) such that ARMv7 Neon code is only
  compiled for target host ARMv7 - at the moment compiling on ARMv6 fails
  because the Neon code is compiled (which should not be compiled)

- provide version numbers in one place (currently found in meson.build, leancrypto.spec and Kbuild.version)

- BIKE: add self tests

- BIKE: add timecop

- ARMv8: enable ARMv8 intrinsics in the kernel (SHAKE2x and by extension SLH-DSA)

- RISCV64: update internal/src/cpufeatures_riscv_auxv.c once kernels report ZBB correctly

- SHA2 Neon: check whether it works on ARMv7

- RISCV asm: check whether it works for RISCV32

- Add SLH-DSA-Ascon to Linux kernel

- Linux kernel: x86 accelerated implementations of xts, chacha20, gcm(aes), rfc4106(gcm(aes)), rfc7539(chacha20,poly1305), rfc7539esp(chacha20,poly1305) do not pass the extended/full kernel self tests. The issue is that the the test harness creates SGLs which are not aligned to cra_blocksize. Thus I am not sure whether the test harness is broken or whether leancrypto should handle such very strange (and not real-life scenarios).

- Add AES-GCM decryption support in FIPS mode (which requires an external IV to be set).

- sbkeysync: develop proper tests and verify

- HQC: add lc_hqc_pk_from_sk

- BIKE: add lc_bike_pk_from_sk

- Tests: reenable OpenSSL checker code in csr_tester.sh and siggen_tester.sh (it seems OpenSSL has some problem as sometimes the thrown error is "unsupported algorithm")

- X.509: Name Constraint not enforced yet (RFC5280 section 4.2.1.10)