Hi,
We have checked for proper library files usage during the signature
verification. Even we have compared the file size of the library used in
working and non- working machine and found both are exactly same. Even
the checksum matches for the files.
In Solaris 5.7 also it works fine. The
Hi,
Any idea on the next release of openssl version in 0.9.7 series?
Thanks,
Prathima.
_
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Prathima Dandapani -X
(pdandapa - HCL at Cisco)
Sent: Saturday, October 06, 2007 11:42 AM
To: openssl-users@openssl.org
Belliappa, Ashith Muddiana (HP Software) wrote:
Hi,
We have checked for proper library files usage during the signature
verification. Even we have compared the file size of the library used in
working and non- working machine and found both are exactly same. Even
the checksum matches for
Hi,
My application will act as tls server and tls client. Whether I can use
same
SSL_CTX object for both client and server.
Whether
1) it is thread safe?
2) how to configure different verify_callback for client and server
3) any known issues in using same SSL_CTX for tls client and server
Hi,
The SSL enabled client application seg faults when too many threads are
created. Each thread is a SSL client attempting a connection with Server.
The application sets the static call back functions.:
static void locking_function(int mode, int n, const char * file, int line)
static unsigned
Hi Prabhu,
Can you check the sha1 usage count in the lsmod?
I am thinking you have not freed the sha tfm and eventually run out of it.
I hit a similar issue when making use of linux sha1.
Thanks
--Gayathri
On Mon, 15 Oct 2007, Prabhu S wrote:
Hi,
The SSL enabled client application seg
The application creates about 800 threads in a Linux 2.6 Kernel.
This is really one of those don't do that then things.
Thread-per-connection is well-known to break down at about 750 connections.
#0 SHA1_Init (c=0x0) at sha_locl.h:150
#1 0x405b2bb0 in init (ctx=0x0) at m_sha1.c:72
#2