Re: [openssl.org #359] Calling SSL_read and SSL_write with non-empty error stack may cause an error

> Adding ERR_clear_errors() into SSL_read() etc seems to be the correct > approach. It is already handled this way in _accept(), _connect(), but > not that obvious, because it is found e.g. in ssl3_accept() which is > called depending on the method selected. > > You will often find ERR_clear_err

[openssl.org #359] Calling SSL_read and SSL_write with non-empty error stack may cause an error

Hi! I have a small problem with SSL_get_error. This function starts like this: int SSL_get_error(SSL *s,int i) { int reason; unsigned long l; BIO *bio; if (i > 0) return(SSL_ERROR_NONE); /* Make things return SSL_ERROR_SYSCALL when doing SSL_do_handshake * etc, w

[openssl.org #130] openssl ciphers is broken?

ukik:/home/arne/b2l-infra/root>bin/openssl ciphers -v HIGH+RSA AESdraft256-SHA SSLv3 Kx=RSA Au=RSA Enc=AESdraft(256) Mac=SHA1 DES-CBC3-SHASSLv3 Kx=RSA Au=RSA Enc=3DES(168) Mac=SHA1 NULL-SHASSLv3 Kx=RSA Au=RSA Enc=None Mac=SHA1 NULL-MD5