Thank you all of you. It would not have been possible without the help
from this list. Special thanx to Dr. Henson, whose comments were
really helpful.
Just for record. Extra DH session keys have to be initialized to
handle ADH (or may be DH as well) ciphers. This is very poorly
mentioned in the
Dear Users,
I am in urgent need of help. If anyone can guide, I will be very
thankful. I have given problem details below after necessary
introduction.
I have scanned through the list archive as much as possible and I
could only find one message with similar problem. The message is
The most intriguing part is when I was writing this server, I
developed a small client just to test connectivity. That client
succeeds. However, when doing live testing not a single connection was
accepted from outside. The test client was run on the same host. I
obtained network traffic
Hello
Thanx for replying. By live testing I mean, actual client connections
that a server is supposed to accept. The client I developed is a very
basic one and I have only tested it from localhost. I dont know if it
will work from outside or not.
Additionally, I have already deployed latest
Thanx for replying. By live testing I mean, actual client connections
that a server is supposed to accept. The client I developed is a very
basic one and I have only tested it from localhost. I dont know if it
will work from outside or not.
So you have no idea whether the client you
when you say it works on localhost but not 'live', i wonder:
is your firewall blocking the port you're trying to connect to?
Aka: can you connect to the server using a
different clinet, eg: telnet directly to the port
and see if the connection is accepted, just
to make sure the basic
Hello Guys
Let me explain the whole problem again.
- My server accepts plain socket connection. That is for sure so there
is no issue of port blocking.
- Right after accepting a plain socket connection, the server
constructs an SSL object as required and goes for SSL_accept.
SSL_accept fails.
-
On Thu, Feb 10, 2005, Nauman Akbar wrote:
Hello Guys
Let me explain the whole problem again.
- My server accepts plain socket connection. That is for sure so there
is no issue of port blocking.
- Right after accepting a plain socket connection, the server
constructs an SSL object as
Dear Dr. Henson!
Yes I am using ERR_print_errors but it doesnot print anything. As far
as the ERR functions are concerned, I used SSL_ERROR_SSL there. If
thats not the case, what should I use there. Perhaps proper value can
lead me to a better insight.
Regards
Nauman Akbar
Concise Solutions
dn Wed, Feb 09, 2005, Nauman Akbar wrote:
Dear Users,
I am in urgent need of help. If anyone can guide, I will be very
thankful. I have given problem details below after necessary
introduction.
I have scanned through the list archive as much as possible and I
could only find one message
Dear Dr. Henson,
Yes now I can simulate the problem in local client/s. There is
definitely a problem of cipher suite in negotiation.
Now, the next problem has this leads to. I have explicitely told my
server to support all cipher using
SSL_CTX_set_cipher_list(m_ctxServerContext, ALL). Later on I
Dear Dr. Henson
I just used SSL_CTX_set_msg_callback. But it is of not much help.
First of all, how do I interpret values in buffer? Byte or Integer? I
tried both but the values dont make sense. Is there any way to decypt
these numeric values to corresponding Protocol variables like cipher
names,
Hi,
I have a small program silimar to FTP running on Solaris 2.6 and Windows NT.
IT was working fine
until I replaced my 40-bit Verisign certificate with 128-bit global secure
ID. I got the following error
message:
[Server]
SSL_accept failed: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3
gang zhong wrote:
Hi,
I have a small program silimar to FTP running on Solaris 2.6 and Windows NT.
IT was working fine
until I replaced my 40-bit Verisign certificate with 128-bit global secure
ID. I got the following error
message:
[Server]
SSL_accept failed: error:14094412:SSL
14 matches
Mail list logo
