Re: SSL_accept doesn't retry BIO_write

On 5/6/24 11:48, Michael Richardson wrote: > Now I treat the flush as 'OpenSSL isn't interested in the result > of the last write anymore'. I'm not sure this assumption is correct, > but it seems to work... (Well, it could cause duplicate messages It does not sound correct. I

Re: SSL_accept doesn't retry BIO_write

> Now I treat the flush as 'OpenSSL isn't interested in the result > of the last write anymore'. I'm not sure this assumption is correct, > but it seems to work... (Well, it could cause duplicate messages It does not sound correct. Might be true for a read. But, for a write, I'd

SSL_accept doesn't retry BIO_write

a function is called that calls the OpenSSL again that then retries the write. This time the BIO's write returns '1'. Now it turns out that at the end of the DTLS handshake (even after SSL_accept returned success, in Wireshark it looks like the session key) OpenSSL still send data via the BIO's write

Re: [openssl-users] ssl_accept failure

On Fri, 2018-10-26 at 10:07 +0100, Matt Caswell wrote: > How did you generate this error string? It looks like you might have > taken the return value (5) from SSL_get_error() and stuffed it into > ERR_error_string() or a similar function. That would give you output > like this - but is the

Re: [openssl-users] ssl_accept failure

On 24/10/2018 23:34, Skip Carter wrote: > I have a server-side application that fails when some clients connect: > > waiting for SSL accept()... > SSL_accept() (0) failure -1 > SSL_accept() (1) failure 5 How did you obtain the error number 5? Is this the return value fro

Re: [openssl-users] ssl_accept failure

On Thu, 2018-10-25 at 19:58 +0200, Jakob Bohm via openssl-users wrote: > First, note the OpenSSL FAQ about how to turn on readable error > messages. I am already using the ERR_error_string(), but the result is still opaque to me. Error string : error:0005:lib(0):func(0):DH lib  The FAQ

Re: [openssl-users] ssl_accept failure

On 25/10/2018 00:34, Skip Carter wrote: I have a server-side application that fails when some clients connect: waiting for SSL accept()... SSL_accept() (0) failure -1 SSL_accept() (1) failure 5 [DEBUG] Error string : error:0005:lib(0):func(0):DH lib SSL_accept() sockerrno is: 0 I think

[openssl-users] ssl_accept failure

I have a server-side application that fails when some clients connect: waiting for SSL accept()... SSL_accept() (0) failure -1 SSL_accept() (1) failure 5 [DEBUG] Error string : error:0005:lib(0):func(0):DH lib SSL_accept() sockerrno is: 0 I think that something earlier failed silently

Re: [openssl-users] Lock for SSL_accept method

On 08/02/18 00:43, Yan, Bob via openssl-users wrote: > I used a mutex lock to prevent the SSL_accept() method being called by > multiple thread concurrently since it may get coredump if there is no > lock on SSL_accept() method. I am just wondering is the lock is still > needed

[openssl-users] Lock for SSL_accept method

Hi All, I used a mutex lock to prevent the SSL_accept() method being called by multiple thread concurrently since it may get coredump if there is no lock on SSL_accept() method. I am just wondering is the lock is still needed for openssl 1.0.2e version? mutex.lock(); int rt

[openssl-users] “no shared cipher” at ssl_accept, why?

function calls only. Error handling code has been applied where applicable to make sure calls before SSL_accept / SSL_connect does not return any failure codes. I have also left out initialization methods. I do not know if it matters, but I run both server and client on localhost. There might

Re: [openssl-users] SSL_accept returning error

On 10/03/16 04:43, Sahib Jakhar wrote: > On Wed, Mar 9, 2016 at 9:21 PM, Matt Caswell wrote: >> >> The problem is caused by the client complaining that the server has sent >> it an unexpected message. What is the client here? Is that OpenSSL too? > > Yes the client is OpenSSL

Re: [openssl-users] SSL_accept returning error

On Wed, Mar 9, 2016 at 9:21 PM, Matt Caswell wrote: > > The problem is caused by the client complaining that the server has sent > it an unexpected message. What is the client here? Is that OpenSSL too? Yes the client is OpenSSL too. > Are there any errors reported client side

Re: [openssl-users] SSL_accept returning error

On 09/03/16 12:51, Sahib Jakhar wrote: > Hi, > > I am getting the following error while doing SSL_accept on the server > side. It comes once in many tries. The error seems to come only on > windows, Linux and other platforms seem to do well. > > The error is: > >

[openssl-users] SSL_accept returning error

Hi, I am getting the following error while doing SSL_accept on the server side. It comes once in many tries. The error seems to come only on windows, Linux and other platforms seem to do well. The error is: .\ssl\s3_pkt.c:1146 error:140943F2:SSL routines:SSL3_READ_BYTES:sslv3 alert unexpected

Re: [openssl-users] SSL_accept error code

-users] SSL_accept error code On 08/03/16 01:04, Yan, Bob wrote: > Hi All, > > I have a SSL server application which use SSL_accept to accept the > connections from client, see the code below: > > int retcode = SSL_accept(mSsl); > unsigned long error = SSL_ge

Re: [openssl-users] SSL_accept error code

On 08/03/16 01:04, Yan, Bob wrote: > Hi All, > > I have a SSL server application which use SSL_accept to accept the > connections from client, see the code below: > > int retcode = SSL_accept(mSsl); > unsigned long error = SSL_get_error(mSsl, retcode); > ERR_erro

[openssl-users] SSL_accept error code

Hi All, I have a SSL server application which use SSL_accept to accept the connections from client, see the code below: int retcode = SSL_accept(mSsl); unsigned long error = SSL_get_error(mSsl, retcode); ERR_error_string_n(error, errmsg, sizeof(errmsg)); When something

[openssl-users] SSL_accept appears to be stuck

I have an SSL server, which has, suddenly stopped processing client requests. I see the following error. >> SSL_GET_NEW_SESSION:ssl session id callback failed. Exactly after 15 seconds of calling SSL_accept, the error is seen. The socket is non-blocking. The application was runnin

[openssl-users] Encryption/decryption using parameters obtained via handshake (SSL_accept/SSL_connect)

()); if(!SSL_CTX_use_certificate_file(context, certFile, SSL_FILETYPE_PEM)) ... if(SSL_CTX_use_PrivateKey_file(context, keyFile, SSL_FILETYPE_PEM)<0 ) ... ssl = SSL_new(context); SSL_set_fd(ssl,fd); /// fd is an open socket descriptor SSL_accept(ssl); // or SSL_connect(ssl); in client and then

SSL_accept creating latency ?

Folks I noticed that in certain cases - SSL_accept call gets hung forever and I had to restart my process to fix the issue. I also observe that the SSL_accept creates some latency, is that possible and if any one of you faced these problems before ? If so , can you please suggest what could

Re: Is it possible that calling ssl_accept in multi-threading circumstance will result in app to crash?

that although the stacks vary, the ssl_accept function is found on all of them, below are some of exmaples. I google the related information about this, looks like there is some problem when calling ssl_accept under multi-thread circumstance. My question is, is it possible that calling ssl_accept in multi

SSL_accept error on AIX multithreads server application

Hello, We used gsoap server with openssl in our application server and encountered SSL_accept error when the server threads was pooled to limit the number of threads serving the requests simultaneously. Here is the excerpt of our log: Request #1 accepted on socket 4 connected from IP

Is it possible that calling ssl_accept in multi-threading circumstance will result in app to crash?

Dear users, I keep getting some application crash in openssl module, I checked the dumps and stacks and found that although the stacks vary, the ssl_accept function is found on all of them, below are some of exmaples. I google the related information about this, looks like there is some problem

Re: Is it possible that calling ssl_accept in multi-threading circumstance will result in app to crash?

jeff jeff.2234...@gmail.com: I keep getting some application crash in openssl module, I checked the dumps and stacks and found that although the stacks vary, the ssl_accept function is found on all of them, below are some of exmaples. I google the related information about this, looks like

SNI and NPN timing in relation to SSL_accept(), SSL_connect()

of the SSL_read()/write(), as long as it makes sure to receive success from SSL_accept() or SSL_connect() beforehand ?

RE: SSL_accept fails with bad certificate error

structure everything goes fine, but when I call SSL_accept() on it, I get a return of zero, which when I read the error queue says sslv3 alert bad certificate What does this error mean exactly? Is it a problem with my server certificate itself, the client certificate returned on the verify

Re: SSL_accept fails with bad certificate error

everything goes fine, but when I call SSL_accept() on it, I get a return of zero, which when I read the error queue says sslv3 alert bad certificate What does this error mean exactly? Is it a problem with my server certificate itself, the client certificate returned on the verify, or what

SSL_accept fails with bad certificate error

everything goes fine, but when I call SSL_accept() on it, I get a return of zero, which when I read the error queue says sslv3 alert bad certificate What does this error mean exactly? Is it a problem with my server certificate itself, the client certificate returned on the verify, or what?

SSL_accept seg fault when adding extra chain cert

I'm using libssl0.9.8 0.9.8o-3 on Debian Lenny 5.0.3. When I use SSL_CTX_use_certificate then SSL_CTX_add_extra_chain_cert, I get random seg faults when calling SSL_accept for subsequent connections that reuse the SSL_CTX. However, I stopped getting the errors when I replaced

Re: DTLS cookies rendered useless by SSL_accept behavior

in the cookie_verify_cb, if this flag is missing after SSL_accept, the ClientHello had no cookie, and I can discard the session (after flushing the bio). Markus __ OpenSSL Project http

DTLS cookies rendered useless by SSL_accept behavior

Hi, I got some code which uses nonblocking dtls via self fed bios. If a unknown session comes up, I create a new session, feed/drain the sessions bios from/to the wire until SSL_accept returns success. Now, I added DTLS cookies. I expected SSL_accept to return an error if a ClientHello

Re: DTLS cookies rendered useless by SSL_accept behavior

On Jul 24, 2011, at 12:40 AM, com...@gmx.ch wrote: Hi, I got some code which uses nonblocking dtls via self fed bios. If a unknown session comes up, I create a new session, feed/drain the sessions bios from/to the wire until SSL_accept returns success. Now, I added DTLS cookies. I

Re: DTLS cookies rendered useless by SSL_accept behavior

, SSL_OP_COOKIE_EXCHANGE); s-d1-listen = 1; ret = SSL_accept(s); if (ret = 0) return ret; (void) BIO_dgram_get_peer(SSL_get_rbio(s), client); return 1; } Correct me if I'm wrong, but I don't see how DTLSv1_listen could work with nonblocking io at all. Besides

RE: SSL_ERROR_SYSCALL in SSL_accept

From: owner-openssl-us...@openssl.org On Behalf Of Saikat Debnath Sent: Wednesday, 15 June, 2011 10:59 I am using openssl-1.0.0d version and having error in SSL_accept. SSL_accept() returns -1 which is SSL_ERROR_SYSCALL with errno 2 (No such file or directory

SSL_ERROR_SYSCALL in SSL_accept

Hi, I am using openssl-1.0.0d version and having error in SSL_accept. SSL_accept() returns -1 which is SSL_ERROR_SYSCALL with errno 2 (No such file or directory) and ERR_error_string() retuns error::lib(0):func(0):reason(0) Can anyone help please to find where is the problem and how

RE: OpenSSL SSL_Accept Error

be interrupting with the way openssl works, in the code i am doing accept, then created SSL and CTX and then calling SSL_Accept. I am NOT using OpenSSL callbacks. Okay, that rules out all my obvious candidates for corruption. Regarding code, the library i am using is 1.0.0a

Re: OpenSSL SSL_Accept Error

Server is Single Threaded and is handling all the connections in while(1) loop, the sockets are blocking but I am using FD_SET options, not sure if that could be interrupting with the way openssl works, in the code i am doing accept, then created SSL and CTX and then calling SSL_Accept. I am

OpenSSL SSL_Accept Error

Hi, I am trying to write the server side code using OpenSSL. I am getting the following error on SSL_Accept. error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac I tried to google on this, everywhere they were mentioning that there was some build error

Re: OpenSSL SSL_Accept Error

at 10:08 AM, Harshvir Sidhu hvssi...@gmail.com wrote: Hi, I am trying to write the server side code using OpenSSL. I am getting the following error on SSL_Accept. error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac I tried to google on this, everywhere

RE: OpenSSL SSL_Accept Error

alert number 20. Not able to find anything useful for this. I am trying to write the server side code using OpenSSL. I am getting the following error on SSL_Accept. error:1408F119:snip:decryption failed or bad record mac s_client got the alert BECAUSE the server got

Re:about ssl_accept and memory leak

dear all: No one encountered this problem? From: lizhip...@cnnic.cn Reply-To: openssl-users@openssl.org To: openssl-users@openssl.org Subject: about ssl_accept and memory leak Date:Mon, 27 Dec 2010 13:38:49 +0800 Dear openssl-users£¬ When using the openssl and found a large number

about ssl_accept and memory leak

(their_addr.sin_addr), ntohs(their_addr.sin_port), new_fd); /* 基于 ctx 产生一个新的 SSL */ ssl = SSL_new(ctx); /* 将连接用户的 socket 加入到 SSL */ SSL_set_fd(ssl, new_fd); /* 建立 SSL 连接 */ if (SSL_accept(ssl) == -1) { perror(accept); close

Re: about ssl_accept and memory leak

Stop opressing women. Girls should NOT be married at puberty to men, men should NOT be happy for the rest of their lives. --- On Mon, 12/27/10, lizhiping lizhip...@cnnic.cn wrote: From: lizhiping lizhip...@cnnic.cn Subject: about ssl_accept and memory leak To: openssl-users openssl-users

about ssl_accept and memory leak

); SSL_set_fd(ssl, new_fd); if (SSL_accept(ssl) == -1) { perror(accept); close(new_fd); continue; } bzero(buf, MAXBUF + 1); // scanf(%[^\n],buf); // // len = SSL_write(ssl, buf, strlen(buf

Re: SSL_connect and SSL_accept deadlock!

This may be a stretch, but did you confirm the socket is within the range of sockets your platform allows you to 'select' on? For example, Linux by default doesn't permit you to 'select' on socket numbers 1,025 and up, though you can have more than 1,024 file descriptors in use without a

Re: SSL_connect and SSL_accept deadlock!

to indicate a fatal error? The code in ssl_retry doesn't seem to follow this rule. (For example, consider if 'select' returns zero and errno is zero. That would indicate a timeout, not a fatal error.) int time0 = time(NULL); timeout=10 seconds; while (ttimeout) { r = SSL_accept(m_ssl

Re: SSL_connect and SSL_accept deadlock!

On Wed, Nov 3, 2010 at 9:12 AM, David Schwartz dav...@webmaster.com wrote: On 11/2/2010 6:25 PM, Md Lazreg wrote:         r=select(m_sock_fd + 1, fds, 0, 0, ptv);         if (r = 0 (Errno == EAGAIN || Errno == EINTR))/*if we timed out with EAGAIN try again*/         {             r = 1;  

SSL_connect and SSL_accept deadlock!

= 0) { break; } t = time(NULL) - time0; } if (t=timeout) { I timed out:( } if (r0) { We are connected. Do work. } else { Some kind of an issue. } server code: - int time0 = time(NULL); timeout=10 seconds; while (ttimeout) { r = SSL_accept(m_ssl

SSL_connect, and SSL_accept

Where are SSL_accept, and SSL_connect defined? Specifically for TLSv1, and SSLv3 connections. I found the definition in ssl_lib.c but then that calls s-method-ssl_accept(s). From here the only mention I could find of an ssl3_accept is in s3_srvr.c which to my understanding is not part

RE: SSL_connect, and SSL_accept

From: owner-openssl-us...@openssl.org On Behalf Of Sam Jantz Sent: Tuesday, 07 September, 2010 17:29 Where are SSL_accept, and SSL_connect defined? Specifically for TLSv1, and SSLv3 connections. I found the definition in ssl_lib.c but then that calls s-method

'decryption failed or bad record mac' during SSL_accept

in ssl3_get_cert_verify (s=0x82524c8) at s3_srvr.c:2676 #4 0x08082df8 in ssl3_accept (s=0x82524c8) at s3_srvr.c:581 #5 0x0806f749 in SSL_accept (s=0x82524c8) at ssl_lib.c:924 #6 0x080609cf in TcpClient::sslNegotiate (this=0x8206960) ... Any idea what might cause this issue

SSL_accept holding the connection

: this client connection (IP) were used by me in 3000 users test done #1 above). After looking at the /var/log/messages I could see server was trying to do SSL connection (SSL_accept) with this non-existing clients. I did netstat for the IP's I have used for my testing and this IP's were seen in netstat

setting an SSL_accept(...) timeout

hello, is there a way i can set a timeout for an SSL_accept, either if the handshake does not complete within X seconds (prefered), or even if it is waiting on a blocking socket and no data comes in for X seconds. I know i can use alarms, but i was wondering (hoping), there was a mechanism

Re: setting an SSL_accept(...) timeout

On Sun, Apr 04, 2010, Adam Grossman wrote: hello, is there a way i can set a timeout for an SSL_accept, either if the handshake does not complete within X seconds (prefered), or even if it is waiting on a blocking socket and no data comes in for X seconds. I know i can use alarms, but i

RE: setting an SSL_accept(...) timeout

Peter-Michael, thanks for the info, but this is on linux. -=- adam grossman On Sun, 2010-04-04 at 19:40 +0200, PMHager wrote: Adam Grossman wrote: is there a way i can set a timeout for an SSL_accept, either if the handshake does not complete within X seconds (prefered), or even

RE: setting an SSL_accept(...) timeout

Adam Grossman wrote: thanks for the info, but this is on linux. The socket interface is almost the same on linux: #include sys/socket.h int hSocket; int dwTimeout=1000; // milliseconds setsockopt(hSocket,SOL_SOCKET,SO_RCVTIMEO,(void*)dwTimeout,sizeof dwTimeout);

RE: setting an SSL_accept(...) timeout

i have done networking programming for a while, and i have never run across that before. thank you so much, you have just saved me a lot of development time! -=- adam grossman On Sun, 2010-04-04 at 22:34 +0200, PMHager wrote: Adam Grossman wrote: thanks for the info, but this is on linux.

RE: SSL_accept error: smtpd client alert 48

Linux AS release 4 (Nahant Update 8) I've got the following error message: snip SSL_accept error from 85-18-95-44.ip.fastwebnet.it[85.18.95.44]: 0 SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca:s3_pkt.c:1052:SSL alert number 48: This is FROM the other system (85-etc) saying

Re: SSL_accept error: smtpd client alert 48

On Fri, Dec 18, 2009 at 07:56:05PM -0500, Dave Thompson wrote: On postfix 2.5.7 running on Red Hat Enterprise Linux AS release 4 (Nahant Update 8) I've got the following error message: snip SSL_accept error from 85-18-95-44.ip.fastwebnet.it[85.18.95.44]: 0 SSL

SSL_accept error

connection from 85-18-95-44.ip.fastwebnet.it[85.18.95.44] Dec 15 12:09:57 lin2a postfix/smtpd[14097]: SSL_accept error from 85-18-95-44.ip.fastwebnet.it[85.18.95.44]: 0 Dec 15 12:09:57 lin2a postfix/smtpd[14097]: warning: TLS library problem: 14097:error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert

SSL_accept hanging with blocking socket

indefinitely looking for a initiated handshake from the client. Is there a way to timeout blocking socket without alarm ? 2 - How come when one thread is blocked by SSL_accept, every thread are also blocked waiting for the blocking thread to timeout ? Any help would be appreciated ! We have looked

RE: SSL_accept hanging with blocking socket

? It's hanging indefinitely because you asked it to. A blocking socket operation blocks as long as it takes to complete the operation. If that's not what you want, why did you do it? 2 - How come when one thread is blocked by SSL_accept, every thread are also blocked waiting for the blocking

SSL_accept hanging with blocking socket

indefinitely looking for a initiated handshake from the client. Is there a way to timeout blocking socket without alarm ? 2 - How come when one thread is blocked by SSL_accept, every NEW thread are also blocked at SSL_accept waiting for the blocking thread to timeout ? Any help would be appreciated

Re: SSL_accept hanging with blocking socket

with a sleep() inside (the factor tries*sleeped-second will count as a timeout). 2 - How come when one thread is blocked by SSL_accept, every NEW thread are also blocked at SSL_accept waiting for the blocking thread to timeout ? You may find an answer in the above link. If you are using ssl_accept

RE: SSL_Accept() failing with error SSL_ERROR_SSL

, then SSL_Accept() ) Yes this is the (or at least a) correct sequence. By 'second or third [fails]' I guess you mean it always works for the first connection in a given server process? Code trimmed to vital bits because I'm having to quote by hand: sock = accept (tls_socket, (struct

Re: SSL_Accept() failing with error SSL_ERROR_SSL

      I'm trying to understand why this following code is failing the second or third time... Is it a good way ( meaning first accept() without ssl, then do those association, then SSL_Accept() ) Yes this is the (or at least a) correct sequence. By 'second or third [fails]' I guess you mean

SSL_Accept() failing with error SSL_ERROR_SSL

Hi, I'm trying to understand why this following code is failing the second or third time... Is it a good way ( meaning first accept() without ssl, then do those association, then SSL_Accept() ) tls_socket is just a plain listner socket sock = accept (tls_socket, (struct sockaddr *) sa

Asynchronous SSL_accept error. Openssl documentation not clear.

Hi, I am trying to develop a SSL server with asynchronous socket. I am able to make the asynchronous socket connection but it failed at the handshake step. In fact, SSL_accept returns 0 error. In the OpenSSL documentation, for the 0 error of the SSL_accept function, we can read It can also

RE: Non-blocking windows socket cause SSL_accept error (SSL_ERROR_WANT_READ)

Is it possible to configure OpenSSL to allow the use of a non-blocking socket ? I red things about BIO* object but I am not sure if it's the good way to do it. Thanks. Normand David Schwartz wrote: SSL_accept always returns 0 error. With SSL_get_error I found that the error

Non-blocking windows socket cause SSL_accept error (SSL_ERROR_WANT_READ)

Hi, SSL_accept always returns 0 error. With SSL_get_error I found that the error is SSL_ERROR_WANT_READ. During debugging and troubleshooting, I realised that when I use normal blocking windows socket, SSL_accept works fine. Why using non-blocking windows socket caused that error ? Thanks

RE: Non-blocking windows socket cause SSL_accept error (SSL_ERROR_WANT_READ)

SSL_accept always returns 0 error. With SSL_get_error I found that the error is SSL_ERROR_WANT_READ. During debugging and troubleshooting, I realised that when I use normal blocking windows socket, SSL_accept works fine. Why using non-blocking windows socket caused that error

Problem in using SSL_accept on vxWorks 5.5 (Pentium)

Hi, I am trying to use SSL_accept on vxWorks 5.5 (Pentium). But when the SSL client sends the initial handshake message (Client Hello), then SSL_accept returns failure with error as SSL_ERROR_WANT_READ. The same code works fine when used on Linux platform and handshake completes successfully

RE: Problem in using SSL_accept on vxWorks 5.5 (Pentium)

Hi, I am trying to use SSL_accept on vxWorks 5.5 (Pentium). But when the SSL client sends the initial handshake message (Client Hello), then SSL_accept returns failure with error as SSL_ERROR_WANT_READ. The same code works fine when used on Linux platform and handshake completes

RE: Problem in using SSL_accept on vxWorks 5.5 (Pentium)

You are right that I am making a non-blocking SSL_accept call. The problem is on vxWorks when 'select' states that some connection request is present, SSL_accept returns failure with error code as SSL_ERROR_WANT_READ. But if I add some delay in between this 'select' and 'SSL_accept

RE: Problem in using SSL_accept on vxWorks 5.5 (Pentium)

You are right that I am making a non-blocking SSL_accept call. The problem is on vxWorks when 'select' states that some connection request is present, SSL_accept returns failure with error code as SSL_ERROR_WANT_READ. That's because the connection request was present but the negotiation

RE: Problem in using SSL_accept on vxWorks 5.5 (Pentium)

Hi, I replaced the call to SSL_select to this one and it worked !!! Thanks for your help. int i =0; while(1 == i) { dRetVal = SSL_accept(pSsl); if(!(SSL_ERROR_WANT_READ == SSL_get_error(pSsl,dRetVal))) i=0; } So

RE: Problem in using SSL_accept on vxWorks 5.5 (Pentium)

[Corrected] Hi , I replaced the call to SSL_accept to this one and it worked !!! Thanks for your help. int i =0; while(1 == i) { dRetVal = SSL_accept(pSsl); if(!(SSL_ERROR_WANT_READ == SSL_get_error(pSsl,dRetVal))) i=0

RE: Problem in using SSL_accept on vxWorks 5.5 (Pentium)

Hi, I replaced the call to SSL_select to this one and it worked !!! Thanks for your help. int i =0; while(1 == i) { dRetVal = SSL_accept(pSsl); if(!(SSL_ERROR_WANT_READ == SSL_get_error(pSsl,dRetVal))) i=0

RE: SSL_ACCEPT...!!! failure

Hello i am using SSL_CTX_load_verify_locations() to load the CA certs. I have another question that .. How actually the SSL_accept get the client certificate ?? Is its internal function also fetch the CA certificate of the client or it check the CA list of its own that is set by the above

Re: SSL_ACCEPT...!!! failure

Vinni a écrit : Hello i am using SSL_CTX_load_verify_locations() to load the CA certs. I have another question that .. How actually the SSL_accept get the client certificate ?? Is its internal function also fetch the CA certificate of the client or it check the CA list of its own that is set

SSL_ACCEPT...!!! failure

hi, i am stuck with the error Unable to get local issuer certificate and then SSL3_GET_CLIENT_CERTIFICATE: peer certificate not return. I have created my own certificates using Openssl.exe . I have created CACert.pem which is self signed CA certificate and then two other certificates one is

Re: SSL_ACCEPT...!!! failure

Hi vinni, As a hint i will reformulate how i understand your problem The server cannot accept the client certificate because it cannot check that the certificate have been issued by a trusted CA. This arise because the CA certificate is not available so the questios are 1) Is the CA

RE: SSL_ACCEPT...!!! failure

vinni rathore a écrit : hi, i am stuck with the error Unable to get local issuer certificate and then SSL3_GET_CLIENT_CERTIFICATE: peer certificate not return. I have created my own certificates using Openssl.exe . I have created CACert.pem which is self signed CA certificate and then

Re: SSL_accept hangs

On Thu, Mar 20, 2008 at 9:29 PM, David Schwartz [EMAIL PROTECTED] wrote: To Md Lazreg: I think I found it. I think you did find it. Now I am able to process more than 1000 clients without hanging. This is great. Thanks a lot for your expertise.

Re: SSL_accept hangs

Thanks Steve. If this helps anyone fixing this issue here is the backtrace once SSL_accept hangs: SSL_accept ssl23_accept ssl23_get_client_hello ssl23_read_bytes BIO_read sock_read __read_nocancel Thanks On Thu, Mar 20, 2008 at 8:22 AM, Steve West [EMAIL PROTECTED] wrote: We experienced

RE: SSL_accept hangs

Hi, I have setup an SSL server that works fine up to 400 connected clients. When I try to have more then 400 clients, then my server hangs in the SSL_accept call This happens very randomly, sometimes beyond 1000 connected clients... The server is dead once this happen and no other

Re: SSL_accept hangs

Hi David, My code looks like this: 1 while(1) 2 { 3r = SSL_accept(m_ssl); 4if (r 0) 5{ 6 break; 7} 8r = ssl_retry(r); 9if ( r = 0) 10 { 11

RE: SSL_accept hangs

Hi David, My code looks like this: 1 while(1) 2 { 3r = SSL_accept(m_ssl); 4if (r 0) 5{ 6 break; 7} 8r = ssl_retry(r); 9if ( r = 0) 10 { 11

Re: SSL_accept hangs

Hi David, On Thu, Mar 20, 2008 at 12:38 PM, David Schwartz [EMAIL PROTECTED] wrote: Hi David, My code looks like this: 1 while(1) 2 { 3r = SSL_accept(m_ssl); 4if (r 0) 5{ 6 break; 7} 8

RE: SSL_accept hangs

)) { call the code above which will call SSL_accept } else { /*error handling*/ } Where is the call to 'accept' (the system's 'accept')? Did you cut out a line before 'new_s-set_non_blocking'? Is 's-accept

Re: SSL_accept hangs

-accept(new_s)) { call the code above which will call SSL_accept } else { /*error handling*/ } Where is the call to 'accept' (the system's 'accept')? Did you cut out a line before 'new_s-set_non_blocking

RE: SSL_accept hangs

)) { /* HERE */ call the code above which will call SSL_accept } else { /*error handling*/ } The line marked with the 'GAK' should be: s-set_non_blocking(true); You don't want the listening socket to block when

SSL_accept hangs

Hi, I have setup an SSL server that works fine up to 400 connected clients. When I try to have more then 400 clients, then my server hangs in the SSL_accept call This happens very randomly, sometimes beyond 1000 connected clients... The server is dead once this happen and no other client

SSL_accept, wrong version number, safari browser

simple embedded webserver. I have one up and running which works with Firefox and IE. However Safari is giving me some problems. Safari occasionally causes SSL_accept to give error error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong version number. It only seems to happen if there are multiple

Re: openSSL SSL_accept problem on AIX 5.3

Hello, I am having some issues with a server application that is based on openSSL. Here are the details: The server application uses OpenSSL ver. 0.9.7g and runs on AIX 5.3. Sometimes when it processes a client request the SSL_accept() function returns an error -1 and the SSL_get_error

openSSL SSL_accept problem on AIX 5.3

Hi there, I am having some issues with a server application that is based on openSSL. Here are the details: The server application uses OpenSSL ver. 0.9.7g and runs on AIX 5.3. Sometimes when it processes a client request the SSL_accept() function returns an error -1 and the SSL_get_error

Re: SSL_accept Failure error:FFFFFFFF:lib(255):func(4095):reason(4095)

error. I could not find the reason string for error code 4095. return code from SSL_accept (rr = -1) SSL_get_error = 1 ERROR_LOG sip_main.c: 1989 SSL_accept Failure error::lib(255):func(4095):reason(4095) Can you guide me how to handle this case ? Try to initialize OpenSSL library

SSL_accept Failure error:FFFFFFFF:lib(255):func(4095):reason(4095)

it throws the following error. I could not find the reason string for error code 4095. return code from SSL_accept (rr = -1) SSL_get_error = 1 ERROR_LOG sip_main.c: 1989 SSL_accept Failure error::lib(255):func(4095):reason(4095) Can you guide me how to handle this case ? Thanks

Re: SSL_accept Failure error:FFFFFFFF:lib(255):func(4095):reason(4095)

, but for linux it throws the following error. I could not find the reason string for error code 4095. return code from SSL_accept (rr = -1) SSL_get_error = 1 ERROR_LOG sip_main.c: 1989 SSL_accept Failure error::lib(255):func(4095):reason(4095) Can you guide me how to handle this case

  1   2   3   >