1. 21 1月, 2007 1 次提交
  2. 25 12月, 2006 1 次提交
  3. 19 12月, 2006 1 次提交
  4. 06 12月, 2006 1 次提交
  5. 30 11月, 2006 1 次提交
  6. 27 11月, 2006 1 次提交
  7. 22 11月, 2006 1 次提交
  8. 06 10月, 2006 1 次提交
  9. 15 9月, 2006 1 次提交
  10. 10 9月, 2006 1 次提交
  11. 24 7月, 2006 1 次提交
  12. 07 3月, 2006 1 次提交
  13. 13 2月, 2006 2 次提交
  14. 04 2月, 2006 1 次提交
  15. 30 1月, 2006 1 次提交
  16. 09 1月, 2006 1 次提交
  17. 05 8月, 2005 1 次提交
  18. 27 7月, 2005 1 次提交
  19. 26 7月, 2005 5 次提交
  20. 24 7月, 2005 2 次提交
  21. 22 6月, 2005 1 次提交
  22. 17 5月, 2005 1 次提交
  23. 16 5月, 2005 1 次提交
  24. 11 5月, 2005 1 次提交
    • B
      Fix more error codes. · 8afca8d9
      Bodo Möller 提交于
      (Also improve util/ck_errf.pl script, and occasionally
      fix source code formatting.)
      8afca8d9
  25. 13 4月, 2005 1 次提交
  26. 11 4月, 2005 1 次提交
  27. 10 4月, 2005 1 次提交
  28. 30 3月, 2005 1 次提交
  29. 18 1月, 2005 1 次提交
    • R
      Changes concering RFC 3820 (proxy certificates) integration: · a7201e9a
      Richard Levitte 提交于
       - Enforce that there should be no policy settings when the language
         is one of id-ppl-independent or id-ppl-inheritAll.
       - Add functionality to ssltest.c so that it can process proxy rights
         and check that they are set correctly.  Rights consist of ASCII
         letters, and the condition is a boolean expression that includes
         letters, parenthesis, &, | and ^.
       - Change the proxy certificate configurations so they get proxy
         rights that are understood by ssltest.c.
       - Add a script that tests proxy certificates with SSL operations.
      
      Other changes:
      
       - Change the copyright end year in mkerr.pl.
       - make update.
      a7201e9a
  30. 28 12月, 2004 1 次提交
  31. 05 12月, 2004 1 次提交
  32. 03 12月, 2004 1 次提交
  33. 30 11月, 2004 1 次提交
  34. 29 11月, 2004 1 次提交
    • R
      Make an explicit check during certificate validation to see that the · 30b415b0
      Richard Levitte 提交于
      CA setting in each certificate on the chain is correct.  As a side-
      effect always do the following basic checks on extensions, not just
      when there's an associated purpose to the check:
      - if there is an unhandled critical extension (unless the user has
        chosen to ignore this fault)
      - if the path length has been exceeded (if one is set at all)
      - that certain extensions fit the associated purpose (if one has been
        given)
      30b415b0