The corresponding DECLARE_... statements are in pcy_int.h and x509v3.h
respectively BTW.
--- \\Debbie\ger\prj\1original\openssl\openssl\crypto\x509v3\pcy_lib.c
2008-11-12
20:36:05.0 +-0100
+++ \\Debbie\ger\prj\3actual\openssl\crypto\x509v3\pcy_lib.c2008-11-12
22:12:48.0
Hi All,
I am not sure if this question has been asked earlier, I didn't find
anything relevant while searching the mail archive.
My question is related to symmetric ey operation hardware accleration at
record layer:
a) Is there a clear interface(hooks etc) from where we actually offload
Hi All,
I am not sure if this question has been asked earlier, I didn't find
anything relevant while searching the mail archive.
My question is related to symmetric ey operation hardware accleration at
record layer:
a) Is there a clear interface(hooks etc) from where we actually offload
Hello,
appro added assembly support for mingw64 at [1].
I've succeeded in compiling this with the following patch.
Thank you!
Alon.
[1] http://cvs.openssl.org/chngview?cn=17619
---
--- openssl-SNAP-20081113/Configure 2008-11-12 22:00:07.0 +0200
+++ openssl-SNAP-20081113.new
I do not see any specific test in NIST's Conformance Testing of Relying
Party Client Certificate Path Processing Logic that says *fail* if a CA has
no associated CRL. If that is the case, then won't ignoring this failure
during cert-verification be okay in context of NIST tests?
Thanks in
