kris
/
boringssl
1
0
Fork 0
Código Issues 0 Pull requests 0 Versões 0 Wiki Atividade
Você não pode selecionar mais de 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.
5157 Commits
12 Branches
38 MiB
Tag: 6ae7ddb755
Branches Tags
${ item.name }
Criar branch ${ searchTerm }
de 6ae7ddb755
${ noResults }
boringssl/sources.cmake

sources.cmake 3.1 KiB
Original Visão normal Histórico

Convert aes_test to GTest. This introduces machinery to start embedding the test data files into the crypto_test binary. Figuring out every CI's test data story is more trouble than is worth it. The GTest FileTest runner is considerably different from the old one: - It returns void and expects failures to use the GTest EXPECT_* and ASSERT_* macros, rather than ExpectBytesEqual. This is more monkey work to convert, but ultimately less work to add new tests. I think it's also valuable for our FileTest and normal test patterns to align as much as possible. The line number is emitted via SCOPED_TRACE. - I've intentionally omitted the Error attribute handling, since that doesn't work very well with the new callback. This means evp_test.cc will take a little more work to convert, but this is again to keep our two test patterns aligned. - The callback takes a std::function rather than a C-style void pointer. This means we can go nuts with lambdas. It also places the path first so clang-format doesn't go nuts. BUG=129 Change-Id: I0d1920a342b00e64043e3ea05f5f5af57bfe77b3 Reviewed-on: https://boringssl-review.googlesource.com/16507 Reviewed-by: Adam Langley <agl@google.com>
7 anos atrás
​
​
​
​
​
​
​
Convert a number of tests to GTest. BUG=129 Change-Id: Ifcdacb2f5f59fd03b757f88778ceb1e672208fd9 Reviewed-on: https://boringssl-review.googlesource.com/16744 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
7 anos atrás
​
​
​
Add AES_128_CCM AEAD. Change-Id: I830be64209deada0f24c3b6d50dc86155085c377 Reviewed-on: https://boringssl-review.googlesource.com/25904 Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
6 anos atrás
Add M=8 L=2 AES-128-CCM as well. The Bluetooth Mesh spec uses both apparently. Also extract a pile of test vectors from that document (thanks to Kyle Lund for showing me which to extract). Change-Id: I04a04fafb7386ca28adfe1446fa388e841778931 Reviewed-on: https://boringssl-review.googlesource.com/26324 Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
6 anos atrás
Convert a number of tests to GTest. BUG=129 Change-Id: Ifcdacb2f5f59fd03b757f88778ceb1e672208fd9 Reviewed-on: https://boringssl-review.googlesource.com/16744 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
7 anos atrás
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
​
Convert ed25519_test to GTest. BUG=129 Change-Id: I784a745f102d9d09d35b27542d94b2b85dfb332e Reviewed-on: https://boringssl-review.googlesource.com/16508 Reviewed-by: Adam Langley <agl@google.com>
7 anos atrás
Convert a number of tests to GTest. BUG=129 Change-Id: Ifcdacb2f5f59fd03b757f88778ceb1e672208fd9 Reviewed-on: https://boringssl-review.googlesource.com/16744 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
7 anos atrás
Convert evp_test to GTest. This is a fairly shallow conversion because of the somewhat screwy Error lines in the test which may target random functions like EVP_PKEY_CTX_set_signature_md. We probably should revise this, perhaps moving those to normal tests and leaving error codes to the core operation itself. BUG=129 Change-Id: I27dcc945058911b2de40cd48466d4e0366813a12 Reviewed-on: https://boringssl-review.googlesource.com/16988 Commit-Queue: David Benjamin <davidben@google.com> Commit-Queue: Steven Valdez <svaldez@google.com> Reviewed-by: Steven Valdez <svaldez@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
7 anos atrás
Implement scrypt from RFC 7914. This imports upstream's scrypt implementation, though it's been heavily revised. I lost track of words vs. blocks vs. bigger blocks too many times in the original code and introduced a typedef for the fixed-width Salsa20 blocks. The downside is going from bytes to blocks is a bit trickier, so I took advantage of our little-endian assumption. This also adds an missing check for N < 2^32. Upstream's code is making this assumption in Integerify. I'll send that change back upstream. I've also removed the weird edge case where a NULL out_key parameter means to validate N/r/p against max_mem and nothing else. That's just in there to get a different error code out of their PKCS#12 code. Performance-wise, the cleanup appears to be the same (up to what little precision I was able to get here), but an optimization to use bitwise AND rather than modulus makes us measurably faster. Though scrypt isn't a fast operation to begin with, so hopefully it isn't anyone's bottleneck. This CL does not route scrypt up to the PKCS#12 code, though we could write our own version of that if we need to later. BUG=chromium:731993 Change-Id: Ib2f43344017ed37b6bafd85a2c2b103d695020b8 Reviewed-on: https://boringssl-review.googlesource.com/17084 Reviewed-by: Adam Langley <agl@google.com>
7 anos atrás
Convert aes_test to GTest. This introduces machinery to start embedding the test data files into the crypto_test binary. Figuring out every CI's test data story is more trouble than is worth it. The GTest FileTest runner is considerably different from the old one: - It returns void and expects failures to use the GTest EXPECT_* and ASSERT_* macros, rather than ExpectBytesEqual. This is more monkey work to convert, but ultimately less work to add new tests. I think it's also valuable for our FileTest and normal test patterns to align as much as possible. The line number is emitted via SCOPED_TRACE. - I've intentionally omitted the Error attribute handling, since that doesn't work very well with the new callback. This means evp_test.cc will take a little more work to convert, but this is again to keep our two test patterns aligned. - The callback takes a std::function rather than a C-style void pointer. This means we can go nuts with lambdas. It also places the path first so clang-format doesn't go nuts. BUG=129 Change-Id: I0d1920a342b00e64043e3ea05f5f5af57bfe77b3 Reviewed-on: https://boringssl-review.googlesource.com/16507 Reviewed-by: Adam Langley <agl@google.com>
7 anos atrás
Convert bn_test to GTest. BUG=129 Change-Id: I21570257c2f40a2c65587d30dbf249a546aa7d8e Reviewed-on: https://boringssl-review.googlesource.com/16885 Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
7 anos atrás
Add some EC base point multiplication test vectors. Probably worth having actual test vectors for these, rather than checking our code against itself. Additionally, small negative numbers have, in the past been valuable test vectors (see long comment in point_add from OpenSSL's ecp_nistp521.c). Change-Id: Ia5aa8a80eb5b6d0089c3601c5fec2364e699794d Reviewed-on: https://boringssl-review.googlesource.com/26848 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
6 anos atrás
Convert p256-x86_64_test to GTest. BUG=129 Change-Id: Ieda2c2cc08f83ae24a2dfdb243dc17b4c15ed5b2 Reviewed-on: https://boringssl-review.googlesource.com/16993 Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
7 anos atrás
Convert ECDSA tests to GTest. BUG=129 Change-Id: Ia8b0639489fea817be4bb24f0457629f0fd6a815 Reviewed-on: https://boringssl-review.googlesource.com/16947 Reviewed-by: David Benjamin <davidben@google.com> Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
7 anos atrás
​
Convert a number of tests to GTest. BUG=129 Change-Id: Ifcdacb2f5f59fd03b757f88778ceb1e672208fd9 Reviewed-on: https://boringssl-review.googlesource.com/16744 Reviewed-by: Adam Langley <agl@google.com> Commit-Queue: Adam Langley <agl@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
7 anos atrás
​
​
​
Add a test for lots of names and constraints. Change-Id: I0ad593cb5c73d61391aa7513054e5cf102334817 Reviewed-on: https://boringssl-review.googlesource.com/20524 Reviewed-by: Martin Kreichgauer <martinkr@google.com> Commit-Queue: Martin Kreichgauer <martinkr@google.com>
7 anos atrás
​
​
​
​
​
​
Add ECDSA and RSA verify Wycheproof drivers. Along the way, add some utility functions for getting common things (curves, hashes, etc.) in the names Wycheproof uses. Change-Id: I09c11ea2970cf2c8a11a8c2a861d85396efda125 Reviewed-on: https://boringssl-review.googlesource.com/27786 Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
6 anos atrás
​
​
​
​
​
​
Add a test driver for Wycheproof's x25519_test.json. FileTest and Wycheproof express more-or-less the same things, so I've just written a script to mechanically convert them. Saves writing a JSON parser. I've also left a TODO with other files that are worth converting. Per Thai, the webcrypto variants of the files are just a different format and will later be consolidated, so I've ignored those. The curve/hash-specific ECDSA files and the combined one are intended to be the same, so I've ignored the combined one. (Just by test counts, there are some discrepancies, but Thai says he'll fix that and we can update when that happens.) Change-Id: I5fcbd5cb0e1bea32964b09fb469cb43410f53c2d Reviewed-on: https://boringssl-review.googlesource.com/27785 Commit-Queue: David Benjamin <davidben@google.com> CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org> Reviewed-by: Adam Langley <agl@google.com>
6 anos atrás
Convert aes_test to GTest. This introduces machinery to start embedding the test data files into the crypto_test binary. Figuring out every CI's test data story is more trouble than is worth it. The GTest FileTest runner is considerably different from the old one: - It returns void and expects failures to use the GTest EXPECT_* and ASSERT_* macros, rather than ExpectBytesEqual. This is more monkey work to convert, but ultimately less work to add new tests. I think it's also valuable for our FileTest and normal test patterns to align as much as possible. The line number is emitted via SCOPED_TRACE. - I've intentionally omitted the Error attribute handling, since that doesn't work very well with the new callback. This means evp_test.cc will take a little more work to convert, but this is again to keep our two test patterns aligned. - The callback takes a std::function rather than a C-style void pointer. This means we can go nuts with lambdas. It also places the path first so clang-format doesn't go nuts. BUG=129 Change-Id: I0d1920a342b00e64043e3ea05f5f5af57bfe77b3 Reviewed-on: https://boringssl-review.googlesource.com/16507 Reviewed-by: Adam Langley <agl@google.com>
7 anos atrás
 12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970 
  1. # This file contains source lists that are also consumed by

  2. # generate_build_files.py.

  3. #

  4. # TODO(davidben): Move the other source lists into this file.

  5. 

  6. set(

  7.   CRYPTO_TEST_DATA

  8. 

  9.   crypto/cipher_extra/test/aes_128_cbc_sha1_ssl3_tests.txt

  10.   crypto/cipher_extra/test/aes_128_cbc_sha1_tls_implicit_iv_tests.txt

  11.   crypto/cipher_extra/test/aes_128_cbc_sha1_tls_tests.txt

  12.   crypto/cipher_extra/test/aes_128_cbc_sha256_tls_tests.txt

  13.   crypto/cipher_extra/test/aes_128_ccm_bluetooth_tests.txt

  14.   crypto/cipher_extra/test/aes_128_ccm_bluetooth_8_tests.txt

  15.   crypto/cipher_extra/test/aes_128_ctr_hmac_sha256.txt

  16.   crypto/cipher_extra/test/aes_128_gcm_siv_tests.txt

  17.   crypto/cipher_extra/test/aes_128_gcm_tests.txt

  18.   crypto/cipher_extra/test/aes_256_cbc_sha1_ssl3_tests.txt

  19.   crypto/cipher_extra/test/aes_256_cbc_sha1_tls_implicit_iv_tests.txt

  20.   crypto/cipher_extra/test/aes_256_cbc_sha1_tls_tests.txt

  21.   crypto/cipher_extra/test/aes_256_cbc_sha256_tls_tests.txt

  22.   crypto/cipher_extra/test/aes_256_cbc_sha384_tls_tests.txt

  23.   crypto/cipher_extra/test/aes_256_ctr_hmac_sha256.txt

  24.   crypto/cipher_extra/test/aes_256_gcm_siv_tests.txt

  25.   crypto/cipher_extra/test/aes_256_gcm_tests.txt

  26.   crypto/cipher_extra/test/chacha20_poly1305_tests.txt

  27.   crypto/cipher_extra/test/cipher_tests.txt

  28.   crypto/cipher_extra/test/des_ede3_cbc_sha1_ssl3_tests.txt

  29.   crypto/cipher_extra/test/des_ede3_cbc_sha1_tls_implicit_iv_tests.txt

  30.   crypto/cipher_extra/test/des_ede3_cbc_sha1_tls_tests.txt

  31.   crypto/cipher_extra/test/nist_cavp/aes_128_cbc.txt

  32.   crypto/cipher_extra/test/nist_cavp/aes_128_ctr.txt

  33.   crypto/cipher_extra/test/nist_cavp/aes_128_gcm.txt

  34.   crypto/cipher_extra/test/nist_cavp/aes_192_cbc.txt

  35.   crypto/cipher_extra/test/nist_cavp/aes_192_ctr.txt

  36.   crypto/cipher_extra/test/nist_cavp/aes_256_cbc.txt

  37.   crypto/cipher_extra/test/nist_cavp/aes_256_ctr.txt

  38.   crypto/cipher_extra/test/nist_cavp/aes_256_gcm.txt

  39.   crypto/cipher_extra/test/nist_cavp/tdes_cbc.txt

  40.   crypto/cipher_extra/test/nist_cavp/tdes_ecb.txt

  41.   crypto/curve25519/ed25519_tests.txt

  42.   crypto/ecdh/ecdh_tests.txt

  43.   crypto/evp/evp_tests.txt

  44.   crypto/evp/scrypt_tests.txt

  45.   crypto/fipsmodule/aes/aes_tests.txt

  46.   crypto/fipsmodule/bn/bn_tests.txt

  47.   crypto/fipsmodule/ec/ec_scalar_base_mult_tests.txt

  48.   crypto/fipsmodule/ec/p256-x86_64_tests.txt

  49.   crypto/fipsmodule/ecdsa/ecdsa_sign_tests.txt

  50.   crypto/fipsmodule/ecdsa/ecdsa_verify_tests.txt

  51.   crypto/fipsmodule/modes/gcm_tests.txt

  52.   crypto/fipsmodule/rand/ctrdrbg_vectors.txt

  53.   crypto/hmac_extra/hmac_tests.txt

  54.   crypto/poly1305/poly1305_tests.txt

  55.   crypto/x509/many_constraints.pem

  56.   crypto/x509/many_names1.pem

  57.   crypto/x509/many_names2.pem

  58.   crypto/x509/many_names3.pem

  59.   crypto/x509/some_names1.pem

  60.   crypto/x509/some_names2.pem

  61.   crypto/x509/some_names3.pem

  62.   third_party/wycheproof/ecdsa_secp224r1_sha224_test.txt

  63.   third_party/wycheproof/ecdsa_secp224r1_sha256_test.txt

  64.   third_party/wycheproof/ecdsa_secp256r1_sha256_test.txt

  65.   third_party/wycheproof/ecdsa_secp384r1_sha384_test.txt

  66.   third_party/wycheproof/ecdsa_secp384r1_sha512_test.txt

  67.   third_party/wycheproof/ecdsa_secp521r1_sha512_test.txt

  68.   third_party/wycheproof/rsa_signature_test.txt

  69.   third_party/wycheproof/x25519_test.txt

  70. )