- Dec 26, 2004
-
-
Andy Polyakov authored
-
- Dec 23, 2004
-
-
Andy Polyakov authored
-
Andy Polyakov authored
-
Andy Polyakov authored
-
Andy Polyakov authored
-
- Dec 20, 2004
-
-
Andy Polyakov authored
-
Dr. Stephen Henson authored
-
- Dec 19, 2004
-
-
Dr. Stephen Henson authored
-
- Dec 17, 2004
-
-
Geoff Thorpe authored
Submitted by: Nils Larsch
-
- Dec 13, 2004
-
-
Richard Levitte authored
-
Richard Levitte authored
make update
-
Dr. Stephen Henson authored
-
Richard Levitte authored
programs.
-
- Dec 12, 2004
-
-
Dr. Stephen Henson authored
-
- Dec 10, 2004
-
-
Andy Polyakov authored
-
- Dec 09, 2004
-
-
Andy Polyakov authored
-
Dr. Stephen Henson authored
are performed.
-
Andy Polyakov authored
-
- Dec 07, 2004
-
-
Andy Polyakov authored
-
- Dec 05, 2004
-
-
Dr. Stephen Henson authored
and zero assurance demontrations CAs to 'demo'.
-
Dr. Stephen Henson authored
-
Dr. Stephen Henson authored
-
Dr. Stephen Henson authored
failure and freeing up memory if a failure occurs. PR:620
-
Dr. Stephen Henson authored
-
- Dec 04, 2004
-
-
Dr. Stephen Henson authored
-
- Dec 03, 2004
-
-
Dr. Stephen Henson authored
-
Dr. Stephen Henson authored
-
- Dec 02, 2004
-
-
Andy Polyakov authored
-
- Dec 01, 2004
-
-
Dr. Stephen Henson authored
-
Andy Polyakov authored
certain mix of calls to RC4 routine not covered by rc4test.c. It's fixed now. In addition this patch inadvertently fixes minor performance problem: in 0.9.7 context P4 was performing 12% slower than the original implementation...
-
Dr. Stephen Henson authored
-
- Nov 30, 2004
-
-
Andy Polyakov authored
-
Mark J. Cox authored
listed on the web site for easy finding and downloading
-
Richard Levitte authored
check_ca(), to resolve constness issue. check_ca() is called from the purpose checkers instead of X509_check_ca(), since the stuff done by the latter (except for calling check_ca()) is also done by X509_check_purpose().
-
- Nov 29, 2004
-
-
Andy Polyakov authored
-
Andy Polyakov authored
-
Richard Levitte authored
-
Richard Levitte authored
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)
-
- Nov 27, 2004
-
-
Andy Polyakov authored
-
- Nov 26, 2004
-
-
Andy Polyakov authored
-