1. 07 1月, 2018 1 次提交
  2. 08 12月, 2017 1 次提交
  3. 12 11月, 2017 1 次提交
  4. 18 10月, 2017 1 次提交
  5. 23 8月, 2017 1 次提交
  6. 12 8月, 2017 1 次提交
  7. 13 6月, 2017 1 次提交
  8. 13 4月, 2017 1 次提交
  9. 15 10月, 2016 1 次提交
  10. 20 9月, 2016 1 次提交
  11. 18 8月, 2016 1 次提交
  12. 17 8月, 2016 1 次提交
  13. 16 8月, 2016 1 次提交
  14. 25 7月, 2016 1 次提交
  15. 17 6月, 2016 1 次提交
  16. 18 5月, 2016 1 次提交
  17. 12 5月, 2016 1 次提交
  18. 04 5月, 2016 1 次提交
  19. 20 4月, 2016 1 次提交
  20. 18 4月, 2016 1 次提交
  21. 06 4月, 2016 1 次提交
  22. 22 3月, 2016 1 次提交
  23. 23 2月, 2016 1 次提交
  24. 20 2月, 2016 1 次提交
  25. 19 2月, 2016 1 次提交
  26. 15 2月, 2016 1 次提交
  27. 13 2月, 2016 1 次提交
    • B
      GH650: Minor tidying around the ocsp app · 21c6c50f
      Benjamin Kaduk 提交于
      The ocsp utility is something of a jack-of-all-trades; most anything
      related to the OCSP can be done with it.  In particular, the manual
      page calls out that it can be used as either a client or a server
      of the protocol, but there are also a few things that it can do
      which do not quite fit into either role, such as encoding an OCSP
      request but not sending it, printing out a text form of an OCSP
      response (or request) from a file akin to the asn1parse utility,
      or performing a lookup into the server-side revocation database
      without actually sending a request or response.  All three of these
      are documented as examples in the manual page, but the documentation
      prior to this commit is somewhat misleading, in that when printing
      the text form of an OCSP response, the code also attempts to
      verify the response, displaying an error message and returning
      failure if the response does not verify.  (It is possible that
      the response would be able to verify with the given example, since
      the default trust roots are used for that verification, but OCSP
      responses frequently have alternate certification authorities
      that would require passing -CAfile or -CApath for verification.)
      
      Tidy up the documentation by passing -noverify for the case of
      converting from binary to textual representation, and also
      change a few instances of -respin to -reqin as appropriate, note
      that the -url option provides the same functionality as the -host
      and -path options, clarify that the example that saves an OCSP
      response to a file will also perform verification on that response,
      and fix a couple grammar nits in the manual page.
      
      Also remove an always-true conditional for rdb != NULL -- there
      are no codepaths in which it could be initialized at the time of
      this check.
      Signed-off-by: NRich Salz <rsalz@openssl.org>
      Reviewed-by: NKurt Roeckx <kurt@openssl.org>
      21c6c50f
  28. 21 1月, 2016 1 次提交
  29. 14 1月, 2016 1 次提交
  30. 17 12月, 2015 1 次提交
    • R
      Rename some BUF_xxx to OPENSSL_xxx · 7644a9ae
      Rich Salz 提交于
      Rename BUF_{strdup,strlcat,strlcpy,memdup,strndup,strnlen}
      to OPENSSL_{strdup,strlcat,strlcpy,memdup,strndup,strnlen}
      Add #define's for the old names.
      Add CRYPTO_{memdup,strndup}, called by OPENSSL_{memdup,strndup} macros.
      Reviewed-by: NTim Hudson <tjh@openssl.org>
      7644a9ae
  31. 10 11月, 2015 1 次提交
  32. 24 10月, 2015 1 次提交
  33. 18 10月, 2015 2 次提交
  34. 13 10月, 2015 1 次提交
    • M
      Centralise loading default apps config file · a0a82324
      Matt Caswell 提交于
      Loading the config file after processing command line options can
      cause problems, e.g. where an engine provides new ciphers/digests
      these are not then recoginised on the command line. Move the
      default config file loading to before the command line option
      processing. Whilst we're doing this we might as well centralise
      this instead of doing it individually for each application. Finally
      if we do it before the OpenSSL_add_ssl_algorithms() call then
      ciphersuites provided by an engine (e.g. GOST) can be available to
      the apps.
      
      RT#4085
      RT#4086
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      a0a82324
  35. 25 9月, 2015 1 次提交
    • M
      Add support for -no-CApath and -no-CAfile options · 2b6bcb70
      Matt Caswell 提交于
      For those command line options that take the verification options
      -CApath and -CAfile, if those options are absent then the default path or
      file is used instead. It is not currently possible to specify *no* path or
      file at all. This change adds the options -no-CApath and -no-CAfile to
      specify that the default locations should not be used to all relevant
      applications.
      Reviewed-by: NAndy Polyakov <appro@openssl.org>
      2b6bcb70
  36. 06 9月, 2015 1 次提交
    • R
      Change the way apps open their input and output files · bdd58d98
      Richard Levitte 提交于
      The different apps had the liberty to decide whether they would open their
      input and output files in binary mode or not, which could be confusing if
      two different apps were handling the same type of file in different ways.
      
      The solution is to centralise the decision of low level file organisation,
      and that the apps would use a selection of formats to state the intent of
      the file.
      Reviewed-by: NTim Hudson <tjh@openssl.org>
      bdd58d98
  37. 11 8月, 2015 1 次提交
  38. 09 8月, 2015 1 次提交
  39. 31 7月, 2015 1 次提交