1. 21 3月, 2018 1 次提交
  2. 13 2月, 2018 1 次提交
  3. 10 2月, 2018 1 次提交
  4. 21 11月, 2017 1 次提交
    • P
      Support multi-prime RSA (RFC 8017) · 665d899f
      Paul Yang 提交于
      * Introduce RSA_generate_multi_prime_key to generate multi-prime
        RSA private key. As well as the following functions:
          RSA_get_multi_prime_extra_count
          RSA_get0_multi_prime_factors
          RSA_get0_multi_prime_crt_params
          RSA_set0_multi_prime_params
          RSA_get_version
      * Support EVP operations for multi-prime RSA
      * Support ASN.1 operations for multi-prime RSA
      * Support multi-prime check in RSA_check_key_ex
      * Support multi-prime RSA in apps/genrsa and apps/speed
      * Support multi-prime RSA manipulation functions
      * Test cases and documentation are added
      * CHANGES is updated
      Reviewed-by: NTim Hudson <tjh@openssl.org>
      Reviewed-by: NBernd Edlinger <bernd.edlinger@hotmail.de>
      (Merged from https://github.com/openssl/openssl/pull/4241)
      665d899f
  5. 08 6月, 2017 1 次提交
    • R
      make error tables const and separate header file · 52df25cf
      Rich Salz 提交于
      Run perltidy on util/mkerr
      Change some mkerr flags, write some doc comments
      Make generated tables "const" when genearting lib-internal ones.
      Add "state" file for mkerr
      Renerate error tables and headers
      Rationalize declaration of ERR_load_XXX_strings
      Fix out-of-tree build
      Add -static; sort flags/vars for options.
      Also tweak code output
      Moved engines/afalg to engines (from master)
      Use -static flag
      Standard engine #include's of errors
      Don't linewrap err string tables unless necessary
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      (Merged from https://github.com/openssl/openssl/pull/3392)
      52df25cf
  6. 06 6月, 2017 1 次提交
  7. 27 4月, 2017 1 次提交
  8. 08 4月, 2017 2 次提交
  9. 18 1月, 2017 2 次提交
  10. 08 1月, 2017 10 次提交
  11. 10 12月, 2016 1 次提交
  12. 08 11月, 2016 1 次提交
    • D
      Implement RSASSA-PKCS1-v1_5 as specified. · 608a0264
      David Benjamin 提交于
      RFC 3447, section 8.2.2, steps 3 and 4 states that verifiers must encode
      the DigestInfo struct and then compare the result against the public key
      operation result. This implies that one and only one encoding is legal.
      
      OpenSSL instead parses with crypto/asn1, then checks that the encoding
      round-trips, and allows some variations for the parameter. Sufficient
      laxness in this area can allow signature forgeries, as described in
      https://www.imperialviolet.org/2014/09/26/pkcs1.html
      
      Although there aren't known attacks against OpenSSL's current scheme,
      this change makes OpenSSL implement the algorithm as specified. This
      avoids the uncertainty and, more importantly, helps grow a healthy
      ecosystem. Laxness beyond the spec, particularly in implementations
      which enjoy wide use, risks harm to the ecosystem for all. A signature
      producer which only tests against OpenSSL may not notice bugs and
      accidentally become widely deployed. Thus implementations have a
      responsibility to honor the specification as tightly as is practical.
      
      In some cases, the damage is permanent and the spec deviation and
      security risk becomes a tax all implementors must forever pay, but not
      here. Both BoringSSL and Go successfully implemented and deployed
      RSASSA-PKCS1-v1_5 as specified since their respective beginnings, so
      this change should be compatible enough to pin down in future OpenSSL
      releases.
      
      See also https://tools.ietf.org/html/draft-thomson-postel-was-wrong-00
      
      As a bonus, by not having to deal with sign/verify differences, this
      version is also somewhat clearer. It also more consistently enforces
      digest lengths in the verify_recover codepath. The NID_md5_sha1 codepath
      wasn't quite doing this right.
      Reviewed-by: NKurt Roeckx <kurt@roeckx.be>
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      
      GH: #1474
      608a0264
  13. 21 7月, 2016 1 次提交
  14. 28 6月, 2016 1 次提交
  15. 27 6月, 2016 1 次提交
  16. 16 6月, 2016 1 次提交
  17. 06 6月, 2016 1 次提交
  18. 24 5月, 2016 1 次提交
  19. 18 5月, 2016 2 次提交
  20. 06 4月, 2016 2 次提交
  21. 21 3月, 2016 1 次提交
  22. 08 3月, 2016 1 次提交
  23. 27 1月, 2016 1 次提交
    • R
      Remove /* foo.c */ comments · 34980760
      Rich Salz 提交于
      This was done by the following
              find . -name '*.[ch]' | /tmp/pl
      where /tmp/pl is the following three-line script:
              print unless $. == 1 && m@/\* .*\.[ch] \*/@;
              close ARGV if eof; # Close file to reset $.
      
      And then some hand-editing of other files.
      Reviewed-by: NViktor Dukhovni <viktor@openssl.org>
      34980760
  24. 08 1月, 2016 1 次提交
  25. 03 12月, 2015 1 次提交
  26. 02 12月, 2015 1 次提交
  27. 18 11月, 2015 1 次提交