1. 14 5月, 2015 2 次提交
  2. 11 5月, 2015 1 次提交
  3. 07 5月, 2015 1 次提交
  4. 05 5月, 2015 1 次提交
    • R
      Use safer sizeof variant in malloc · b4faea50
      Rich Salz 提交于
      For a local variable:
              TYPE *p;
      Allocations like this are "risky":
              p = OPENSSL_malloc(sizeof(TYPE));
      if the type of p changes, and the malloc call isn't updated, you
      could get memory corruption.  Instead do this:
              p = OPENSSL_malloc(sizeof(*p));
      Also fixed a few memset() calls that I noticed while doing this.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      b4faea50
  5. 01 5月, 2015 3 次提交
  6. 30 4月, 2015 1 次提交
    • R
      free NULL cleanup 8 · 2ace7450
      Rich Salz 提交于
      Do not check for NULL before calling a free routine.  This addresses:
          ASN1_BIT_STRING_free ASN1_GENERALIZEDTIME_free ASN1_INTEGER_free
          ASN1_OBJECT_free ASN1_OCTET_STRING_free ASN1_PCTX_free ASN1_SCTX_free
          ASN1_STRING_clear_free ASN1_STRING_free ASN1_TYPE_free
          ASN1_UTCTIME_free M_ASN1_free_of
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      2ace7450
  7. 29 4月, 2015 1 次提交
  8. 17 4月, 2015 1 次提交
  9. 01 4月, 2015 2 次提交
  10. 27 3月, 2015 1 次提交
    • D
      Simplify DSA public key handling. · ea6b07b5
      Dr. Stephen Henson 提交于
      DSA public keys could exist in two forms: a single Integer type or a
      SEQUENCE containing the parameters and public key with a field called
      "write_params" deciding which form to use. These forms are non standard
      and were only used by functions containing "DSAPublicKey" in the name.
      
      Simplify code to only use the parameter form and encode the public key
      component directly in the DSA public key method.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      ea6b07b5
  11. 25 3月, 2015 3 次提交
  12. 24 3月, 2015 4 次提交
  13. 12 3月, 2015 1 次提交
    • M
      Fix dsa_pub_encode · 0c7ca403
      Matt Caswell 提交于
      The return value from ASN1_STRING_new() was not being checked which could
      lead to a NULL deref in the event of a malloc failure. Also fixed a mem
      leak in the error path.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      0c7ca403
  14. 09 3月, 2015 1 次提交
  15. 29 1月, 2015 1 次提交
  16. 28 1月, 2015 1 次提交
    • R
      OPENSSL_NO_xxx cleanup: SHA · 474e469b
      Rich Salz 提交于
      Remove support for SHA0 and DSS0 (they were broken), and remove
      the ability to attempt to build without SHA (it didn't work).
      For simplicity, remove the option of not building various SHA algorithms;
      you could argue that SHA_224/256/384/512 should be kept, since they're
      like crypto algorithms, but I decided to go the other way.
      So these options are gone:
      	GENUINE_DSA         OPENSSL_NO_SHA0
      	OPENSSL_NO_SHA      OPENSSL_NO_SHA1
      	OPENSSL_NO_SHA224   OPENSSL_NO_SHA256
      	OPENSSL_NO_SHA384   OPENSSL_NO_SHA512
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      474e469b
  17. 27 1月, 2015 1 次提交
    • R
      OPENSSL_NO_xxx cleanup: many removals · a00ae6c4
      Rich Salz 提交于
      The following compile options (#ifdef's) are removed:
          OPENSSL_NO_BIO OPENSSL_NO_BUFFER OPENSSL_NO_CHAIN_VERIFY
          OPENSSL_NO_EVP OPENSSL_NO_FIPS_ERR OPENSSL_NO_HASH_COMP
          OPENSSL_NO_LHASH OPENSSL_NO_OBJECT OPENSSL_NO_SPEED OPENSSL_NO_STACK
          OPENSSL_NO_X509 OPENSSL_NO_X509_VERIFY
      
      This diff is big because of updating the indents on preprocessor lines.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      a00ae6c4
  18. 23 1月, 2015 1 次提交
  19. 22 1月, 2015 4 次提交
  20. 15 1月, 2015 1 次提交
    • R
      Cleanup OPENSSL_NO_xxx, part 1 · 4b618848
      Rich Salz 提交于
      OPENSSL_NO_RIPEMD160, OPENSSL_NO_RIPEMD merged into OPENSSL_NO_RMD160
      OPENSSL_NO_FP_API merged into OPENSSL_NO_STDIO
      Two typo's on #endif comments fixed:
      	OPENSSL_NO_ECB fixed to OPENSSL_NO_OCB
      	OPENSSL_NO_HW_SureWare fixed to OPENSSL_NO_HW_SUREWARE
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      4b618848
  21. 13 1月, 2015 1 次提交
  22. 05 1月, 2015 1 次提交
    • D
      Fix various certificate fingerprint issues. · 684400ce
      Dr. Stephen Henson 提交于
      By using non-DER or invalid encodings outside the signed portion of a
      certificate the fingerprint can be changed without breaking the signature.
      Although no details of the signed portion of the certificate can be changed
      this can cause problems with some applications: e.g. those using the
      certificate fingerprint for blacklists.
      
      1. Reject signatures with non zero unused bits.
      
      If the BIT STRING containing the signature has non zero unused bits reject
      the signature. All current signature algorithms require zero unused bits.
      
      2. Check certificate algorithm consistency.
      
      Check the AlgorithmIdentifier inside TBS matches the one in the
      certificate signature. NB: this will result in signature failure
      errors for some broken certificates.
      
      3. Check DSA/ECDSA signatures use DER.
      
      Reencode DSA/ECDSA signatures and compare with the original received
      signature. Return an error if there is a mismatch.
      
      This will reject various cases including garbage after signature
      (thanks to Antti Karjalainen and Tuomo Untinen from the Codenomicon CROSS
      program for discovering this case) and use of BER or invalid ASN.1 INTEGERs
      (negative or with leading zeroes).
      
      CVE-2014-8275
      Reviewed-by: NEmilia Käsper <emilia@openssl.org>
      684400ce
  23. 31 12月, 2014 1 次提交
  24. 19 12月, 2014 2 次提交
  25. 09 12月, 2014 1 次提交
  26. 08 12月, 2014 2 次提交