1. 04 Jan, 2017 1 commit
    • davidben's avatar
      Remove the password parameter for ECPrivateKey::ExportEncryptedPrivateKey. · 1c02c94c
      davidben authored
      Even with a password, the encryption scheme used here is really not what
      we'd want people to use. This does two things:
      
      1. Cut down on the number of ways to use ExportEncryptedPrivateKey and
         makes it less likely someone will mistakenly use it for security
         purposes.
      
      2. When we ported to BoringSSL, we added "raw" versions of
         PKCS8_{encrypt,decrypt} to account for confusion about two ways to
         encode the empty password. But PKCS8_{encrypt,decrypt} already
         handled this by treating NULL and "" differently. Limiting to just
         the empty password lets us trim BoringSSL's API surface in
         preparation for decoupling it from crypto/asn1.
      
      BUG=603319
      
      Review-Url: https://codereview.chromium.org/2608453002
      Cr-Commit-Position: refs/heads/master@{#441365}
      1c02c94c
  2. 28 Jun, 2016 1 commit
  3. 07 Jun, 2016 1 commit
  4. 20 Apr, 2016 1 commit
  5. 08 Apr, 2016 1 commit
  6. 01 Mar, 2016 1 commit
    • davidben's avatar
      Cut down on usage of deprecated APIs in //crypto. · 7dad2a3e
      davidben authored
      SSL_library_init is deprecated. It's CRYPTO_library_init. Switch from the
      legacy ASN.1 APIs to the new parsers where feasible.
      ECPrivateKey::CreateFromEncryptedPrivateKeyInfo is left alone for now as we
      still need a new version of those APIs.
      
      This also adds a scoper for CBB for use in later CLs.
      
      BUG=499653
      
      Review URL: https://codereview.chromium.org/1739403002
      
      Cr-Commit-Position: refs/heads/master@{#378610}
      7dad2a3e
  7. 21 Dec, 2015 1 commit
  8. 12 May, 2015 1 commit
  9. 06 Aug, 2014 1 commit
  10. 24 Jun, 2014 1 commit
  11. 22 Mar, 2014 1 commit
  12. 17 Oct, 2013 1 commit
  13. 09 Apr, 2013 3 commits
  14. 09 Nov, 2011 1 commit