This should be fixed in 0.9.8 . As we don't want to backport the
necessary changes to 0.9.7 I close this ticket.
Cheers,
Nils
__
OpenSSL Project http://www.openssl.org
Development Mailing List
OK, what's the status on this ticket?
[bodo - Tue Feb 4 17:30:23 2003]:
Arne Ansper [EMAIL PROTECTED]:
Like I say, they should only do this if there was an error reported,
surely?
No. Take a look at the SSL_CTX_use_certificate_chain_file:
ret=SSL_CTX_use_certificate(ctx,x);
Arne Ansper [EMAIL PROTECTED]:
Like I say, they should only do this if there was an error reported, surely?
No. Take a look at the SSL_CTX_use_certificate_chain_file:
ret=SSL_CTX_use_certificate(ctx,x);
if (ERR_peek_error() != 0)
ret = 0; /* Key/certificate mismatch
In message [EMAIL PROTECTED] on Fri, 31 Jan 2003 15:50:06
+0100 (MET), Bodo Moeller via RT [EMAIL PROTECTED] said:
rt A second theory is that OpenSSL should always clear the error queue by
rt calling ERR_clear_error() if stuff left in the error queue might cause
rt confusion later.
The problem
Any more thoughts on this issue?
--
Richard Levitte
__
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager
On Thu, Jan 30, 2003 at 10:09:22PM +0100, Richard Levitte via RT wrote:
Any more thoughts on this issue?
The problem is not yet solved. Using the global error stack as error indicator
instead of correctly passing state back via return values is a design flaw.
It happend to make problems in
OK...
[jaenicke - Thu Jan 30 22:21:50 2003]:
On Thu, Jan 30, 2003 at 10:09:22PM +0100, Richard Levitte via RT
wrote:
Any more thoughts on this issue?
The problem is not yet solved. Using the global error stack as error
indicator
instead of correctly passing state back via return
There was no time to solve this problem before the release of 0.9.7.
The ticket is therefore moved forward to 0.9.7a.
Best regards,
Lutz
__
OpenSSL Project http://www.openssl.org
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_errors()
[[EMAIL PROTECTED] - Sun Nov 24 19:52:37 2002]:
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
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,
11 matches
Mail list logo
