1. 16 3月, 2016 1 次提交
    • F
      General verify options to openssl ts · 08538fc0
      fbroda 提交于
      This commit adds the general verify options of ocsp, verify,
      cms, etc. to the openssl timestamping app as suggested by
      Stephen N. Henson in [openssl.org #4287]. The conflicting
      "-policy" option of "openssl ts" has been renamed to
      "-tspolicy". Documentation and tests have been updated.
      
      CAVE: This will break code, which currently uses the "-policy"
      option.
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      08538fc0
  2. 11 3月, 2016 1 次提交
  3. 10 3月, 2016 1 次提交
  4. 08 3月, 2016 3 次提交
  5. 05 3月, 2016 1 次提交
  6. 04 3月, 2016 4 次提交
  7. 24 2月, 2016 1 次提交
  8. 23 2月, 2016 2 次提交
  9. 18 2月, 2016 1 次提交
  10. 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
  11. 12 2月, 2016 2 次提交
  12. 11 2月, 2016 3 次提交
  13. 10 2月, 2016 1 次提交
  14. 09 2月, 2016 1 次提交
    • V
      Suppress DANE TLSA reflection when verification fails · c0a445a9
      Viktor Dukhovni 提交于
      As documented both SSL_get0_dane_authority() and SSL_get0_dane_tlsa()
      are expected to return a negative match depth and nothing else when
      verification fails.  However, this only happened when verification
      failed during chain construction.  Errors in verification of the
      constructed chain did not have the intended effect on these functions.
      
      This commit updates the functions to check for verify_result ==
      X509_V_OK, and no longer erases any accumulated match information
      when chain construction fails.  Sophisticated developers can, with
      care, use SSL_set_verify_result(ssl, X509_V_OK) to "peek" at TLSA
      info even when verification fail.  They must of course first check
      and save the real error, and restore the original error as quickly
      as possible.  Hiding by default seems to be the safer interface.
      
      Introduced X509_V_ERR_DANE_NO_MATCH code to signal failure to find
      matching TLSA records.  Previously reported via X509_V_ERR_CERT_UNTRUSTED.
      
      This also changes the "-brief" output from s_client to include
      verification results and TLSA match information.
      
      Mentioned session resumption in code example in SSL_CTX_dane_enable(3).
      Also mentioned that depths returned are relative to the verified chain
      which is now available via SSL_get0_verified_chain(3).
      
      Added a few more test-cases to danetest, that exercise the new
      code.
      
      Resolved thread safety issue in use of static buffer in
      X509_verify_cert_error_string().
      
      Fixed long-stating issue in apps/s_cb.c which always sets verify_error
      to either X509_V_OK or "chain to long", code elsewhere (e.g.
      s_time.c), seems to expect the actual error.  [ The new chain
      construction code is expected to correctly generate "chain
      too long" errors, so at some point we need to drop the
      work-arounds, once SSL_set_verify_depth() is also fixed to
      propagate the depth to X509_STORE_CTX reliably. ]
      Reviewed-by: NRich Salz <rsalz@openssl.org>
      c0a445a9
  15. 08 2月, 2016 1 次提交
    • R
      more doc fixes · a173a7ee
      Rich Salz 提交于
      dgst: using digest instead of specific digest commands
      the digest list specified in man dgst may be inaccurate, hence using
      digest and referring to the list in digest-commands
      
      'sha' as a digest name is no longer supported
      
      dgst,pkeyutl cmds help cleanup
      - In dgst, pkeyutl cmds, some options help was missing.
      - fixed a minor typo in openssl.pod, that fixes make install.
      - digest-commands was showing ‘sha’, which is not a supported digest
      anymore.
      Signed-off-by: NRich Salz <rsalz@openssl.org>
      Reviewed-by: NTim Hudson <tjh@openssl.org>
      a173a7ee
  16. 07 2月, 2016 1 次提交
  17. 06 2月, 2016 8 次提交
  18. 04 2月, 2016 1 次提交
  19. 03 2月, 2016 2 次提交
  20. 02 2月, 2016 1 次提交
  21. 01 2月, 2016 2 次提交
  22. 21 1月, 2016 1 次提交
    • V
      Multiple -trusted/-untrusted/-CRLfile options in verify · feb2f53e
      Viktor Dukhovni 提交于
      It is sometimes useful (especially in automated tests) to supply
      multiple trusted or untrusted certificates via separate files rather
      than have to prepare a single file containing them all.
      
      To that end, change verify(1) to accept these options zero or more
      times.  Also automatically set -no-CAfile and -no-CApath when
      -trusted is specified.
      
      Improve verify(1) documentation, which could still use some work.
      Reviewed-by: NRichard Levitte <levitte@openssl.org>
      feb2f53e