Problem "unknown message digest algorithm" verifying server certificate from Perl OpenSSL client

I'm trying to use IO-Socket-SSL-1.13_5, Net-SSLeay 1.32 and OpenSSL 0.9.7j. I have the Perl module coded the following way. When $ssl_verify_mode = 0x01 to verify the peer certificate, I get the error below. I'm using the same self-signed certificate on the server as I'm using on the client

Re: Problem "unknown message digest algorithm" verifying server certificate from Perl OpenSSL client

Tim Hudson wrote: > > Try connecting with >openssl s_client -state -debug -connect hostname:port and see what > details > are returned in the server certificate - that will at least tell you what > algorithms are used by the server certificate. > > Are you sure you are actaully calling O

OpenSSL FIPS 1.2 availability?

Is there an estimated (planned) date for when the OpenSSL FIPS 1.2 module will be released? -- View this message in context: http://www.nabble.com/OpenSSL-FIPS-1.2-availability--tp19888614p19888614.html Sent from the OpenSSL - User mailing list archive at Nabble.com. ___

OpenSSL 0.9.7m Link Failure w/FIPS

I'm getting the following error after following the steps in the FIPS users guide to compile on Windows at this link: http://openssl.org/docs/fips/UserGuide-1.1.1.pdf. I'm using FIPS 1.1.2 with OpenSSL 0.9.7m. I do ms\do_ms (tried with ms\do_nasm as well), then nmake -f ms\ntdll.mak. The con

Perl enablement of OpenSSL FIPS

Hi, Does anyone know of any Perl modules already written that can call the native OpenSSL FIPS_mode_set and FIPS_mode APIs. I am using Perl's Net::SSLeay and IO::Socket::SSL modules but these do not appear to have any exposed APIs to enable FIPS mode. Thanks! Also, I assume if I enable FI

SSL_ERROR_SYSCALL, errlist: No such file or directory

Anyone know what could be the cause of this error?This error occurs on a Windows system. The calling system (which shouldn't matter) is Solaris. However, other Windows systems that call to this system succeed, although the only notable error is here. Calling SSL_accept. Error code: 5 erro

RE: SSL_ERROR_SYSCALL, errlist: No such file or directory

You are correct, it returns 0. RC=0 is a handshake failure?I think I need to debug this on the Solaris side then. Which makes sense.Thanks for the help! Calling SSL_accept. SSL_accept rc=0 Error code: 5 error::lib(0):func(0):reason(0) Error: SSL_ERROR_SYSCALL, errlist: No such

RE: SSL_ERROR_SYSCALL, errlist: No such file or directory

ocket::SSL=GLOB(0x29bdfe8)) READ: ReadyLine: . Agent Connecting... READ: pbirk wrote: > > You are correct, it returns 0. RC=0 is a handshake failure?I think I > need to debug this on the Solaris side then. Which makes sense.Thanks > for the help! > > Calling S

RE: SSL_ERROR_SYSCALL, errlist: No such file or directory

David, Sorry for the lack of information, let me try to fill in the blanks. We're using Perl (IO::Socket::SSL) on the sending side to establish a secure socket to a C agent on the receiving side. The C agent uses native OpenSSL APIs.On the Perl side, we create a TCP socket and then do a st

RE: SSL_ERROR_SYSCALL, errlist: No such file or directory

Posting a solution to this issue just in case it helps others with the same issue. The problem was solved by setting the socket to be non-blocking and then looping when the error is "SSL wants a read first". I try limit the number of loops to 10 before I give up. It takes 2 times in the loop