120a124a0e
crypto/external/bsd/openssl/dist/providers/implementations/digests/sha2_prov.c: revision 1.2 (applied to crypto/external/bsd/openssl/dist/crypto/evp/m_sha1.c) tests/crypto/libcrypto/t_sha512trunc.c: revision 1.1 tests/crypto/libcrypto/t_sha512trunc.c: revision 1.2 tests/crypto/libcrypto/Makefile: revision 1.16 distrib/sets/lists/tests/mi: revision 1.1311 distrib/sets/lists/debug/mi: revision 1.430 crypto/external/bsd/openssl/dist/include/crypto/sha.h: revision 1.2 crypto/external/bsd/openssl/lib/libcrypto/libc-sha2xx.c: revision 1.4 (all via patch) libcrypto: Add some trivial tests for truncated SHA-512 variants. These should use more of the test vectors from https://csrc.nist.gov/Projects/Cryptographic-Algorithm-Validation-Program/Secure-Hashing#Testing but this will do for now to detect the buffer overrun rake we left lying around for ourselves. PR lib/58039 libcrypto: Fix buffer overrun in truncated SHA-512 functions. Further fallout from the libc/openssl sha2 symbol collision. PR lib/58039 |
||
---|---|---|
.. | ||
bin | ||
crypto | ||
dev | ||
fs | ||
games | ||
include | ||
ipf | ||
kernel | ||
lib | ||
libexec | ||
modules | ||
net | ||
rump | ||
sbin | ||
share | ||
sys | ||
usr.bin | ||
usr.sbin | ||
Makefile | ||
Makefile.inc | ||
README | ||
h_macros.h |
README
$NetBSD: README,v 1.4 2012/05/18 15:36:21 jruoho Exp $ When adding new tests, please try to follow the following conventions. 1. For library routines, including system calls, the directory structure of the tests should follow the directory structure of the real source tree. For instance, interfaces available via the C library should follow: src/lib/libc/gen -> src/tests/lib/libc/gen src/lib/libc/sys -> src/tests/lib/libc/sys ... 2. Equivalently, all tests for userland utilities should try to follow their location in the source tree. If this can not be satisfied, the tests for a utility should be located under the directory to which the utility is installed. Thus, a test for env(1) should go to src/tests/usr.bin/env. Likewise, a test for tcpdump(8) should be in src/tests/usr.sbin/tcpdump, even though the source code for the program is located under src/external. 3. Otherwise use your own discretion.