- 28 12月, 2004 2 次提交
-
-
由 Richard Levitte 提交于
-
由 Andy Polyakov 提交于
PR: 949
-
- 26 12月, 2004 3 次提交
-
-
由 Andy Polyakov 提交于
essentially cosmetic modification...
-
由 Andy Polyakov 提交于
from platform to platform and can be as large as 20%.
-
由 Andy Polyakov 提交于
-
- 24 12月, 2004 4 次提交
-
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
- 20 12月, 2004 2 次提交
-
-
由 Andy Polyakov 提交于
-
由 Dr. Stephen Henson 提交于
-
- 14 12月, 2004 2 次提交
-
-
由 Richard Levitte 提交于
-
由 Richard Levitte 提交于
make update
-
- 12 12月, 2004 1 次提交
-
-
由 Dr. Stephen Henson 提交于
-
- 10 12月, 2004 1 次提交
-
-
由 Andy Polyakov 提交于
-
- 09 12月, 2004 3 次提交
-
-
由 Andy Polyakov 提交于
-
由 Dr. Stephen Henson 提交于
are performed.
-
由 Andy Polyakov 提交于
-
- 07 12月, 2004 1 次提交
-
-
由 Andy Polyakov 提交于
-
- 05 12月, 2004 3 次提交
-
-
由 Dr. Stephen Henson 提交于
-
由 Dr. Stephen Henson 提交于
failure and freeing up memory if a failure occurs. PR:620
-
由 Dr. Stephen Henson 提交于
-
- 03 12月, 2004 1 次提交
-
-
由 Dr. Stephen Henson 提交于
-
- 02 12月, 2004 2 次提交
-
-
由 Andy Polyakov 提交于
-
由 Dr. Stephen Henson 提交于
-
- 01 12月, 2004 2 次提交
-
-
由 Andy Polyakov 提交于
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 提交于
-
- 30 11月, 2004 4 次提交
-
-
由 Andy Polyakov 提交于
-
由 Richard Levitte 提交于
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().
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
- 29 11月, 2004 1 次提交
-
-
由 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)
-
- 27 11月, 2004 1 次提交
-
-
由 Andy Polyakov 提交于
-
- 26 11月, 2004 2 次提交
-
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
- 24 11月, 2004 1 次提交
-
-
由 Dr. Stephen Henson 提交于
-
- 23 11月, 2004 1 次提交
-
-
由 Andy Polyakov 提交于
-
- 21 11月, 2004 1 次提交
-
-
由 Andy Polyakov 提交于
apparently impossible to compose blended code with would perform satisfactory on all x86 and x86_64 cores, an extra RC4_CHAR code-path is introduced and P4 core is detected at run-time. This way we keep original performance on non-P4 implementations and turbo-charge P4 performance by factor of 2.8x (on 32-bit core).
-
- 10 11月, 2004 1 次提交
-
-
由 Andy Polyakov 提交于
results in even higher performance gain of 3.3x:-) At least on Opteron...
-
- 03 11月, 2004 1 次提交
-
-
由 Richard Levitte 提交于
if $(EXHEADER) is empty. Notified by many, solution suggested by Carson Gaspar <carson@taltos.org>
-