Re: OpenSSL error information queue

> On Tue, 18 Dec 2007 09:15:42 +0100, Jurko Gospodnetić said: > >Hi Martin. > >Thank you for replying. > > > Yes, sometimes there is nothing on the error queue after SSL_get_error() has > > returned SSL_ERROR_SYSCALL. > >That's what I assumed. > > > Also, if your app is multit

OpenSSL FIPS Object Module v1.2 snapshots

Snapshots from the OpenSSL-fips-0_9_8-stable branch where development for FIPS 140-2 currently takes place are now being posted in the snapshot area, ftp://ftp.openssl.org/snapshot/. These will have names of the form openssl-0.9.8-fips-test-SNAP-MMDD.tar.gz

RE: OpenSSL proxy server could not restart after killing

> I have a problem about OpenSSL proxy server rebooting. > OpenSSL proxy server could not be restarted after killing, > and I find the root cause: > On Linux OS, if there is a socket binding a port, after the socket > is closed or the program exit normally, the port could not be release > at onc

Re: OpenSSL error information queue

Hi Martin. Thank you for replying. Yes, sometimes there is nothing on the error queue after SSL_get_error() has returned SSL_ERROR_SYSCALL. That's what I assumed. Also, if your app is multithreaded then don't forget to implement all of the crypto locking/threadid functions, otherwise

OpenSSL proxy server could not restart after killing

Hi All I have a problem about OpenSSL proxy server rebooting. OpenSSL proxy server could not be restarted after killing, and I find the root cause: On Linux OS, if there is a socket binding a port, after the socket is closed or the program exit normally, the port could not be release at