From 04e149f840f04970f9c00da486694f99cb2a2d85 Mon Sep 17 00:00:00 2001 From: Adam Langley Date: Wed, 8 Aug 2018 11:17:05 -0700 Subject: [PATCH] Set the fuzzer PBKDF2 limit to 2048. Our test data uses values to up 2048 so the 1024 limit was causing tests to fail in fuzzing mode. Change-Id: I71b97be26376a04c13d1f438e5e36a5ffff1c1a4 Reviewed-on: https://boringssl-review.googlesource.com/30484 Commit-Queue: Adam Langley Commit-Queue: David Benjamin Reviewed-by: David Benjamin CQ-Verified: CQ bot account: commit-bot@chromium.org --- crypto/pkcs8/pkcs8_x509.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crypto/pkcs8/pkcs8_x509.c b/crypto/pkcs8/pkcs8_x509.c index 65389636..c5a06519 100644 --- a/crypto/pkcs8/pkcs8_x509.c +++ b/crypto/pkcs8/pkcs8_x509.c @@ -670,7 +670,7 @@ int PKCS12_get_key_and_certs(EVP_PKEY **out_key, STACK_OF(X509) *out_certs, } #if defined(BORINGSSL_UNSAFE_FUZZER_MODE) - static const uint64_t kIterationsLimit = 1024; + static const uint64_t kIterationsLimit = 2048; #else // Windows imposes a limit of 600K. Mozilla say: “so them increasing // maximum to something like 100M or 1G (to have few decades of breathing