There are other out of band mechanisms where a CRL might be available but
not mentioned in a CRLDP. OpenSSL has no way of telling what those might be
and if the absence is really an error or not.
The best you can do is trap the issuer error in the verify callback and ignore
it if
With great many thanks to Dr. Henson for not only responding to every
post I have had so far but also for providing solid guidance on how to
address the problem leading to the heading of this thread, I am adding
some extra material and some verbatim quotes from Dr. Henson here so
that they might
Ok. Thank everybody for your help.
Now it works.
2011/3/17 Ryan Pfeifle r...@vpi-corp.com
Yes, if SSL_write() sends 5 bytes, SSL_read() will return 5 bytes even
though the passed buffer is 10 bytes (SSL does NOT expect \0 to stop
reading). But like David said, you are ignoring the return
This was mentioned briefly in another thread by myself. I thought it
deserved its own discussion. The copies of how it went on are pasted below.
Section 6.3.3. of RFC 5280 - CRL Processing
This algorithm begins by assuming that the certificate is not revoked
For each distribution point (DP)
Jeff Saremi jsar...@morega.com writes:
[...]
Section 6.3.3. of RFC 5280 - CRL Processing
This algorithm begins by assuming that the certificate is not revoked
For each distribution point (DP) in the certificate's CRL distribution
points extension, for each corresponding CRL
So my
Hello,
I have installed Win32OpenSSL-1_0_0d and net-snmp-5.5.0-1.x86 on a Windows
server.
When I launch Net-SNMP, it stop immediately and I have this message on event
log :
Faulting application snmpd.exe, version 0.0.0.0, faulting module unknown,
version 0.0.0.0, fault address 0x.
On 3/18/2011 10:10 AM, Samuel Mutel wrote:
Hello,
I have installed Win32OpenSSL-1_0_0d and net-snmp-5.5.0-1.x86 on a Windows
server.
When I launch Net-SNMP, it stop immediately and I have this message on event
log :
Faulting application snmpd.exe, version 0.0.0.0, faulting module unknown,
