summaryrefslogtreecommitdiffstats
path: root/crypto/rsa_private_key_unittest.cc
Commit message (Collapse)AuthorAgeFilesLines
* Switch to standard integer types in crypto/.avi2015-12-211-298/+207
| | | | | | | | | | BUG=138542 TBR=rsleevi@chromium.org NOPRESUBMIT=true Review URL: https://codereview.chromium.org/1539353003 Cr-Commit-Position: refs/heads/master@{#366460}
* increase crypto_unittest key sizes to satisfy NSS 3.19.1mostynb2015-06-091-1/+2
| | | | | | | | | | | | | | | | | | | NSS version 3.19.1 added minimum key size constraints to avoid the Logjam attack: > The minimum size of keys that NSS will generate has been raised: > The minimum modulus size for RSA keys is now 512 bits > The minimum modulus size for DSA keys is now 1023 bits > The minimum modulus size for Diffie-Hellman keys is now 1023 bits https://developer.mozilla.org/en-US/docs/Mozilla/Projects/NSS/NSS_3.19.1_release_notes https://bugzilla.mozilla.org/show_bug.cgi?id=1138554 BUG=490240 Review URL: https://codereview.chromium.org/1148193006 Cr-Commit-Position: refs/heads/master@{#333554}
* Initial support for using BoringSSL with NSS certificates.davidben2015-04-221-4/+0
| | | | | | | | | | | | | | | | | | | | | | | This switches the USE_OPENSSL Linux and CrOS builds to continue setting USE_NSS_CERTS. This lets it use BoringSSL for the crypto and SSL stack and NSS for certificate verification. See design doc for details on the flags: https://docs.google.com/document/d/1x4DOCKwFkAxl9MGfd6snIzFigO4ku6Shuci0r5BzasQ/edit On Linux, only client auth and OCSP stapling are missing. On ChromeOS, there are some problematic USE_NSS_CERTS APIs in RSAPrivateKey to resolve. We also still need to resolve crbug.com/347404 to maintain parity. As a follow-up, USE_OPENSSL_CERTS on non-Android can now be removed (it was never supported anyway). BUG=462040 Review URL: https://codereview.chromium.org/881213004 Cr-Commit-Position: refs/heads/master@{#326222}
* Rename USE_NSS to USE_NSS_CERTS.davidben2015-04-171-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | USE_NSS is confusing because it's not actually the analog of USE_OPENSSL; it's the analog to USE_OPENSSL_CERTS. This is in preparation for the chimera build which will set USE_OPENSSL and USE_NSS(_CERTS). This CL was partially done automatically by the following command: git grep -l USE_NSS | xargs sed -i -e 's/defined(USE_NSS)/defined(USE_NSS_CERTS)/' The remaining were caught by the following command and fixed manually: git grep 'USE_NSS\([^_]\|$\)' Finally, the following command verified nothing in a separate repository was sensitive to this change: find . -name '*.cc' -o -name '*.h' | xargs grep 'USE_NSS\([^_]\|$\)' For now, the old name is still defined, but not used within Chromium. A follow-up CL will remove deprecated use_nss and USE_NSS #defines together which will then cause downstream churn. Though from a grep of known downstreams, the churn seems to be fairly minimal. The removal is split from this CL so that, if we need to revert, the CL to revert is small. TBR=pneubeck@chromium.org BUG=462040 Review URL: https://codereview.chromium.org/1082123003 Cr-Commit-Position: refs/heads/master@{#325710}
* Don't allow importing non-RSA keys from ↵eroman2015-01-021-0/+27
| | | | | | | | | | crypto::RSAPrivateKey::CreateFromPrivateKeyInfo(). BUG=445927 Review URL: https://codereview.chromium.org/805193004 Cr-Commit-Position: refs/heads/master@{#309854}
* Don't allow trailing data when creating an RSAPrivateKey.davidben2014-11-241-0/+14
| | | | | | | | | | | CreateFromPrivateKeyInfo should not silently discard data after the PrivateKeyInfo. BUG=432279 Review URL: https://codereview.chromium.org/713523004 Cr-Commit-Position: refs/heads/master@{#305503}
* Allow a crypto::RSAPrivateKey object to be wrapped round a pre-existingdougsteed2014-09-101-0/+27
| | | | | | | | | | | | | | openssl key, as is currently supported for NSS. Change-Id: I36c848884273fe8e23451259655680b6b7d46a98 BUG=412427 R=davidben@chromium.org Review URL: https://codereview.chromium.org/559623002 Cr-Commit-Position: refs/heads/master@{#294254}
* clean up code at crypto folder.rucifer1217@gmail.com2014-07-221-158/+158
| | | | | | | | BUG=none Review URL: https://codereview.chromium.org/407713002 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@284547 0039d316-1c4b-4281-b951-d872f2087c98
* Implement RSAPrivateKey::Copy()sergeyu@chromium.org2011-12-031-106/+125
| | | | | | | | BUG=105220 Review URL: http://codereview.chromium.org/8727014 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@112837 0039d316-1c4b-4281-b951-d872f2087c98
* Move crypto files out of base, to a top level directory.rvargas@google.com2011-04-141-0/+386
src/crypto is now an independent project that contains our cryptographic primitives (except md5 and sha1). This removes the base dependency from nss, openssl and sqlite. BUG=76996 TEST=none Review URL: http://codereview.chromium.org/6805019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@81611 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-04-01 09:15:03 +0000