boringssl/crypto/pkcs8
Adam Langley c81965a8ad Set PBKDF2 limit in PKCS#12 to 100M.
The previous limit was |UINT_MAX|. Windows limits to 600K, but that's
already causing issues. This seems like a balance between being
completely crazy and still large enough not to have to worry for a long
time. It's still probably too large for backend systems wanting to
process arbitrary PKCS#12, but I don't think any fixed value will
satisfy all desires.

Change-Id: I01a3f78d5f2df086f8dbc0e8bacfb95153738f55
Reviewed-on: https://boringssl-review.googlesource.com/30424
Commit-Queue: David Benjamin <davidben@google.com>
Reviewed-by: David Benjamin <davidben@google.com>
CQ-Verified: CQ bot account: commit-bot@chromium.org <commit-bot@chromium.org>
2018-08-08 17:09:36 +00:00
..
CMakeLists.txt Convert remaining pkcs8 tests to gtest 2017-06-07 17:30:27 +00:00
internal.h Add PKCS12_create. 2018-05-11 21:59:34 +00:00
p5_pbev2.c Run the comment converter on libcrypto. 2017-08-18 21:49:04 +00:00
pkcs8_test.cc Don't crash if asked to treat PBES2 as a PBES1 scheme. 2018-05-11 22:00:04 +00:00
pkcs8_x509.c Set PBKDF2 limit in PKCS#12 to 100M. 2018-08-08 17:09:36 +00:00
pkcs8.c Don't crash if asked to treat PBES2 as a PBES1 scheme. 2018-05-11 22:00:04 +00:00
pkcs12_test.cc Add a PKCS#12 fuzzer. 2018-05-15 23:58:32 +00:00