Thanks. I wrote some simple tests to exercise this and it worked
correctly. I was just not seeing how.
Jay
On 10/3/2022 11:26 PM, Tomas Mraz wrote:
Your analysis is correct. However the library is still correct in
regards to refcounting even for an SSL BIO in the chain. The reason is
that the
Your analysis is correct. However the library is still correct in
regards to refcounting even for an SSL BIO in the chain. The reason is
that the decrement of refcount of the BIOs underlying the SSL BIO is
handled through the actual freeing of the SSL BIO. If the refcount for
the SSL BIO in the cha
Your response makes sense. I am a bit puzzled by the BIO reference
counting. For example
BIO_new() (or BIO_new_socket() which calls BIO_new()) produces a
BIO with a reference count of 1.
BIO_free() drops 1 reference and if the reference count is 0, frees
the BIO.
BIO_push() con
The SSL BIO should have the rbio from the SSL object as the next BIO.
If you create the SSL BIO and then BIO_push() the TCP socket BIO into
the SSL BIO, it will work correctly.
Otherwise, you can just fix the next BIO of the SSL BIO by using
BIO_up_ref(socketbio);
BIO_set_next(sslbio, socketbio);
I have an application that constructs a chain of BIOs. Sometimes this
chain also includes an SSL BIO. Years ago, I ran into a problem that
caused BIO_flush() to segfault on the SSL BIO. This turned out to
happen because the SSL BIO is added using SSL_set_bio() instead of
BIO_push(). SSL_set
N()*
> ===
>
> My *Makefile *looks like the following,
> ===
>
>
>
>
>
>
>
> *rsa-engine: gcc -g -fPIC -c rsa-engine.c gcc -g -shared -o
> librsa_engine.so -L./libdune rsa-engine.o -Bdynamic -lcrypto -lpth
==
My code compiles. When I try to do encryption using the following command,
=
*openssl rsautl -encrypt -inkey public.pem -pubin -in msg.txt -out msg.enc
-engine rsa-engine-new*
=
I get a segmentation fault,
0x71): warning: Using 'gethostbyname' in statically
linked applications requires at runtime the shared libraries from the glibc
version used for linking
*when i exec the test:*
$./test
[1]36025 segmentation fault (core dumped) ./test
*Use gdb for debug:*
gdb-
session but I always get segmentation fault during SSL_free.
If I remove SSL_free the segmentation fault goes away but I need to call it
in order to free up the ssl session memory.
While further debugging using GDB I found
(gdb) bt
#0 0xb6e3cc10 in dtls1_get_record () from /usr/lib/libssl.so.1.0.0
#1
> On May 2, 2017, at 2:02 PM, Michael Ströder wrote:
>
> I'm not sure whether OpenSSL 1.0.2k is even usable with this ancient OpenLDAP
> version.
> Especially it was set to historic status by the OpenLDAP project several
> years ago.
>
> I'd strongly recommend to use a recent OpenLDAP release
Sanjaya Joshi wrote:
> I use openldap_2.3.39 to initiate secure LDAP connection (starttls) to
> external LDAP
> server. The used openssl version is 1.0.2k.
I'm not sure whether OpenSSL 1.0.2k is even usable with this ancient OpenLDAP
version.
Especially it was set to historic status by the OpenL
LDAP server. The used openssl version is 1.0.2k.
> >
> > While establishing the secure connection from client, i observe the
> > following segmentation fault occasionally (Not always reproducible).
> >
> > Any pointers please ?
> >
>
> Are you able to compile openssl wit
On 16/04/17 20:17, Sanjaya Joshi wrote:
> Hello,
>
> I use openldap_2.3.39 to initiate secure LDAP connection (starttls) to
> external LDAP server. The used openssl version is 1.0.2k.
>
> While establishing the secure connection from client, i observe the
> followi
Hello,
I use openldap_2.3.39 to initiate secure LDAP connection (starttls) to
external LDAP server. The used openssl version is 1.0.2k.
While establishing the secure connection from client, i observe the
following segmentation fault occasionally (Not always reproducible).
Any pointers please
Oh! what a miss!! Signs of excessive pressure!!! When I divide the program in
multiple files, I create one of the functions like this-
char *dh_sender_pub(DH *dhPar)
{
char *pubinHex=NULL;
DH_generate_key(dhPar);
pubinHex=BN_bn2hex(dhPar->pub_key);
return pubinHex;
}
And I was
Ø These built-in functions do not return the size of the binary data, so how
can I get the length of the binary data?
BN_num_bytes() which you already used in your initial posting?
--
Principal Security Engineer
Akamai Technology
Cambridge, MA
These built-in functions do not return the size of the binary data, so how can
I get the length of the binary data? I need the length in some other parts of
my program. Do I need to convert them to Hex everytime to get the length? Or is
there any direct method to get the length? I want to use di
As two other people have already said, you cannot use strlen() on binary data.
> >BN_bin2bn(parmp,strlen(parmp), dhPar2->p);
> >BN_bin2bn(parmg,strlen(parmg), dhPar2->g);
/r$
--
Principal Security Engineer
Akamai Technology
Cambridge, MA
Hi,
Thank you all for your quick responses. I am using openssl 1.0.1 on a Linux
machine. The DH_new() works correctly in my machine. It does not return NULL.
Only the problem occurs in these lines-
> >
> > BN_bin2bn(parmp,strlen(parmp), dhPar2->p);
> > BN_bin2bn(parmg,strlen(parm
> From: owner-openssl-us...@openssl.org On Behalf Of Matt Caswell
> Sent: Monday, January 20, 2014 15:45
> On 20 January 2014 15:34, khan wahid wrote:
> > Hi,
> > I am trying to implement DH key exchage using openssl in the same
program,
> > so I generate DH parameters once, and then transfer th
On 20 January 2014 15:34, khan wahid wrote:
> Hi,
> I am trying to implement DH key exchage using openssl in the same program,
> so I generate DH parameters once, and then transfer the p and g to another
> DH object, here is my code-
>
> #include
> #include
> #include
> #include
> #includ
2);
printf("Secret Key 1: \n");
hexprint(dhSec1, 32);
printf("Secret Key 2: \n");
hexprint(dhSec2, 32);
free(dhSec1);
free(dhSec2);
DH_free(dhPar);
DH_free(dhPar2);
}
It gives me segmentation fault at
/gost2001_keyx.c call
parent method.
Does not check the result by NULL.
In the code
VKO_compute_key(shared_key,32,EC_KEY_get0_public_key(EVP_PKEY_get0(pubk)),EVP_PKEY_get0(sec_key),ukm);
gost_init(&cctx,param->sblock);
results in a segmentation fault.
Aleksey
On Sep 21, 2011, at 9:40 PM, Huaqing Wang wrote:
> Hi,
>
> I don't know if any other person met this issue.
> I use openssl1.0.0e, and working on dtls, in client side, if I set
> SSL_CTX_set_options(ssl_ctx, SSL_OP_NO_QUERY_MTU);
> SSL_set_mtu(ss_ssl, 1500);
> I m
Hi,
I don't know if any other person met this issue.
I use openssl1.0.0e, and working on dtls, in client side, if I
set SSL_CTX_set_options(ssl_ctx, SSL_OP_NO_QUERY_MTU);
SSL_set_mtu(ss_ssl, 1500);
I met a segmentation fault on the client side, using gdb I saw the error
happens in:
m
Hi everyone.
Any idea on this error?
I have run Apache with SSL due to this issue.
Thanks,
Mon
From: monloi perez
To: openssl-users@openssl.org
Sent: Wed, July 6, 2011 8:11:22 PM
Subject: Segmentation Fault when restarting apache with ssl
Hi,
I'm n
d apache I get an error
> "Segmentation Fault" below are the technical details.
>
>
> Server version: Apache/2.2.19 (Unix)
> Architecture: 64-bit
> OpenSSL 1.0.0d
>
> Loaded Modules:
> core_module (static)
> mpm_prefork_module (static)
> http_module (static)
&
Hi,
I'm new to the list and having this issue.
I installed apache + openssl. When i started apache I get an error
"Segmentation
Fault" below are the technical details.
Server version: Apache/2.2.19 (Unix)
Architecture: 64-bit
OpenSSL 1.0.0d
Loaded Modules:
core
I found where the segmentation fault happens. There is no link between SSL
function call and the seg fault. SSL functions work fine until now.
2011/3/1 ikuzar
> Hello,
> I develop a secure stack. This stack is between TCP and an application. The
> appli call my stack's function
Hello,
I develop a secure stack. This stack is between TCP and an application. The
appli call my stack's functions ( my_connect( ), my_listen( ), etc. ). I
have got segmentation fault after launching the the program.
SERVER SIDE :
my_recv( ) is like this :
int my_recv(my_cn sd, char
sl.org
Subject: Re: OCSP_BASICRESP_free() segmentation fault
On Wed, Dec 29, 2010, Bin Lu wrote:
> Hi Steve,
>
>
>
> My code looks like this(error checking is omitted):
>
>
>
> OCSP_BASICRESP* bs = OCSP_response_get1_basic(resp);
>
> OCSP_check_nonce(req
On Wed, Dec 29, 2010, Bin Lu wrote:
> Hi Steve,
>
>
>
> My code looks like this(error checking is omitted):
>
>
>
> OCSP_BASICRESP* bs = OCSP_response_get1_basic(resp);
>
> OCSP_check_nonce(req, bs);
>
> OCSP_basic_verify(bs, chain, store, verifyFlags);
>
> OCSP_resp_find_status(bs, id, &
!
-binlu
-Original Message-
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of Dr. Stephen Henson
Sent: Monday, December 13, 2010 11:49 AM
To: openssl-users@openssl.org
Subject: Re: OCSP_BASICRESP_free() segmentation fault
On Mon, Dec 13, 2010, Bin
On Mon, Dec 13, 2010, Bin Lu wrote:
> OK, let me look into this.
>
> But could you please let me know where these _free functions are defined, for
> OCSP_BASICRESP_free(), OCS_RESPONSE_free(), OCSP_REQUEST_free()?
>
The actual definition is in crypto/ocsp/ocsp_asn.c but that wont help much
bec
Behalf Of Dr. Stephen Henson
Sent: Saturday, December 11, 2010 5:21 AM
To: openssl-users@openssl.org
Subject: Re: OCSP_BASICRESP_free() segmentation fault
On Thu, Dec 09, 2010, Bin Lu wrote:
> Hi,
>
> I am getting the following crash in openssl-0.9.8d:
>
> #0 0x2332885e in ASN1
On Thu, Dec 09, 2010, Bin Lu wrote:
> Hi,
>
> I am getting the following crash in openssl-0.9.8d:
>
> #0 0x2332885e in ASN1_primitive_free ()
> #1 0x233288a4 in ASN1_primitive_free ()
> #2 0x23328935 in ASN1_primitive_free ()
> #3 0x23328b5a in ASN1_template_free ()
> #4 0x23328a74 in ASN1_primi
Hi,
I am getting the following crash in openssl-0.9.8d:
#0 0x2332885e in ASN1_primitive_free ()
#1 0x233288a4 in ASN1_primitive_free ()
#2 0x23328935 in ASN1_primitive_free ()
#3 0x23328b5a in ASN1_template_free ()
#4 0x23328a74 in ASN1_primitive_free ()
#5 0x23328b5a in ASN1_template_free ()
#6
Krishnappanaidu, Vasu wrote:
We are using your ssldump to decrypt the SSL traffic and we get
“segmentation fault” and also it core dumps.
Use wireshark (or the command line version tshark), ssldump is dead and
buried.
wireshark also has some bugs in this domain (less than ssldump, but
On Wed, Nov 18, 2009, Krishnappanaidu, Vasu wrote:
> Hi,
>
> We are using your ssldump to decrypt the SSL traffic and we get
> "segmentation fault" and also it core dumps.
>
It is not "our" ssldump, it isn't part of the OpenSSL project.
Steve.
--
Dr
On Wed, Nov 18, 2009 at 4:21 PM, Krishnappanaidu, Vasu
wrote:
> Hi,
>
> We are using your ssldump to decrypt the SSL traffic and we get
> “segmentation fault” and also it core dumps.
>
> - Operating system: Red Hat Linux el4 i386, update 4.
>
> - The key that’s bein
Hi,
We are using your ssldump to decrypt the SSL traffic and we get
"segmentation fault" and also it core dumps.
- Operating system: Red Hat Linux el4 i386, update 4.
- The key that's being used: 3 chained certificates as an extended
certificate signed by VeriSign C
I am getting a variety of stack traces that may all relate to one
cause. The packages runs fine in many instances but one particular
configuration gives problems:
=
=
=
=
=
=
=
=
=
=
=
=
S:Red Hat Enterprise
Hi,
I am facing some problem( segmentation fault) with the function call
X509_LOOKUP_add_dir.
I could not post the total code here but from the backtrace ( GDB) file I
could see it crashed with X509_LOOKUP_add_dir.
Can any one tell the possible cause of crash with the function call
>
> Program terminated with signal 11, Segmentation fault.
> #0 0xb7bf54e3 in ssl3_read_n () from /usr/lib/libssl.so.0.9.8
> (gdb) bt
> #0 0xb7bf54e3 in ssl3_read_n () from /usr/lib/libssl.so.0.9.8
> #1 0x in ?? ()
> (gdb) quit
>
> I'm digging into this issue more
wight Schauer
Sent: Thursday, October 01, 2009 11:07
To: 'openssl-users@openssl.org'
Subject: Segmentation fault in ssl3_read_n and shortened stack strace
We are using openssl-32bit-0.9.8a-18.26 on SLES 10.2 (x86_64).
This problem is only occurring on a very small percentage of our instal
We are using openssl-32bit-0.9.8a-18.26 on SLES 10.2 (x86_64).
This problem is only occurring on a very small percentage of our installs, and
is not readily repeatable, but is always results in the same back trace.
Program terminated with signal 11, Segmentation fault.
#0 0xb7bf54e3 in
client_method()
> i have a segmentation fault..what does it mean?which could be its causes?
> Thanks,
> Marina Russo
>
> --
> Preparati alla sfida all'ultima combinazione, gioca con
> Crosswire!<http://livesearch.games.msn.com/crosswire/default_it/>
>
--
IT Consultant
_client_method() i have a segmentation fault..what does it mean?which
> could be its causes?
> Thanks,
> Marina Russo
>
> _
> Naviga più semplice, più veloce e più sicuro. Scarica Internet Explorer 8
> per MSN!
>
Hi!
I'm trying to run a client server application using openssl library,but i've
got some problems because, when i use the method: SSLv3_client_method() i have
a segmentation fault..what does it mean?which could be its causes?
Thanks,
Ma
...ok, thank you very much, I appreciate everything you said to me...I've
learn a lot...
I've used a source code I've found on internet, but obviously, it was a toy
more than
mine... :)
Ah, allright, this is just a toy used to understand how works openssl and
it's cypher/decypher
routines, so DE
> From: owner-openssl-us...@openssl.org On Behalf Of SpikeSpiegel
> Sent: Monday, 07 September, 2009 15:23
> I'm writing a little program that encrypt/decrypt some text
> but I've found some troubles using the OpenSSL libraries...
> When I use between the encrypt() function and the decrypt()
>
Hi to everyone,
I'm writing a little program that encrypt/decrypt some text but I've found
some troubles
using the OpenSSL libraries...
When I use between the encrypt() function and the decrypt() function I
receive some
strange errors or segmentation faults..
I copy my source here so I can explai
did it get read properly?
I found that "PEM_write_RSA_PUBKEY(stdout, rsa);" does print the
correct key.
Now I have updated the code, to try and encrypt/decrypt some test
data. Why is it causing a segmentation fault at line 39 the
"RSA_private_decrypt(size, from, to, rsa, RSA_NO_PADD
id it get read properly?
I found that "PEM_write_RSA_PUBKEY(stdout, rsa);" does print the
correct key.
Why the two very similar functions? and why aren't they outputing the
same data?
Now I have updated the code, to try and encrypt/decrypt some test
data.
for encrypting the file, so output_enc.txt is generated
3. D for decrypting output_enc.txt so output_dec.txt is generated
In the third step I obtain a segmentation fault. A decrypted file is
generated but it differs in some characters from the original one. Any
ideas?
The segmentation fault
I make the openssl 0.9.8i or openssl 0.9.8k and build the libssl.so and
libcrypto.so in the arm-linux which kernel is version 2.6. When I will
deinit the SSL Ctx buffer and call the SSL_CTX_free() in my porting
eap_supplicant, the SSL_CTX_free() function will happen the "segmentation
fault&
AM
To: openssl-users@openssl.org
Subject: PEM_read_bio_X509 - Segmentation fault
Hi,
The function PEM_read_bio_X509 always create a Segmentatio Fault.
Code:
string certificateFile =
"/home/norm/Desktop/tmp/SSLServer_RootCertificate.pem";
X509* cert;
BIO* bio_cert = BI
o responsabile per queste
evenienze. Il mittente si riserva il diritto di archiviare, ritenere e
controllare i messaggi di posta elettronica.
- Original Message -
From: "BiGNoRm6969" <[EMAIL PROTECTED]>
To:
Sent: Monday, December 08, 2008 7:01 PM
Subject: [?? Probable Spa
, NULL);
Any idea whats causing the problem ? I tryed it on linux and also on
windows xp...same problem.
--
View this message in context:
http://www.nabble.com/PEM_read_bio_X509---Segmentation-fault-tp20900358p20900358.html
Sent from the OpenSSL - User mailing li
hi i have written a server client program .. in client using SSL_write im
writing some data in buffer and in server using SSL_read reading .. client
side wtite returns succesfully but at server SSL_read i get segmentation
fault ..
and Another question is after handshaking i am using
:error:0D0BF041:asn1 encoding routines:ASN1_item_dup:malloc
failure:a_dup.c:104:
problems making Certificate Request
Segmentation fault (core dumped)
Waiting responses.
Thanks a lot.
Regards,
Ahmed
_
Explore the s
c Ion
- Original Message
From: Kyle Hamilton <[EMAIL PROTECTED]>
To: openssl-users@openssl.org
Sent: Friday, April 18, 2008 5:32:49 PM
Subject: Re: Segmentation fault in SSL_read() (Re-post)
ergh. My apologies for not catching that. You're right, it shouldn't
matter on t
ergh. My apologies for not catching that. You're right, it shouldn't
matter on the client side.
Okay... going back to basics (I'm sorry if this seems a bit
patronizing, I honestly don't intend it to be such), a segfault occurs
on a pointer dereference, trying to gain access to memory which is
i
From: Kyle Hamilton <[EMAIL PROTECTED]>
To: openssl-users@openssl.org
Sent: Friday, April 18, 2008 2:33:03 PM
Subject: Re: Segmentation fault in SSL_read() (Re-post)
How are you creating an MFC executable on Linux?
-Kyle H
On Fri, Apr 18, 2008 at 4:29 AM, Ion Scerbatiuc <[EMAIL PROTECTED]
ds,
> Scerbatiuc Ion
>
>
> - Original Message
> From: Kyle Hamilton <[EMAIL PROTECTED]>
> To: openssl-users@openssl.org
>
> Sent: Friday, April 18, 2008 2:14:03 PM
> Subject: Re: Segmentation fault in SSL_read() (Re-post)
>
> My initial idea would be that
questions?
Thanks for your time!
Regards,
Scerbatiuc Ion
- Original Message
From: Kyle Hamilton <[EMAIL PROTECTED]>
To: openssl-users@openssl.org
Sent: Friday, April 18, 2008 2:14:03 PM
Subject: Re: Segmentation fault in SSL_read() (Re-post)
My initial idea would be that you're
very time in SSL_read()
> method.
> Here is a snippet from one of the core dumps:
>
> Core was generated by `/opt/whozin/wnsd_test -l'.
> Program terminated with signal 11, Segmentation fault.
> Reading
- Original Message
From: Ion Scerbatiuc <[EMAIL PROTECTED]>
To: openssl-users@openssl.org
Sent: Friday, April 18, 2008 1:15:35 PM
Subject: Segmentation fault in SSL_read() (Re-post)
Sorry for the fist post. It seems like I have some problems with the other
email client. A new try :)
signal 11, Segmentation fault.
Reading symbols from /usr/lib/libccext2-1.5.so.0...done.
Loaded symbols for /usr/lib/libccext2-1.5.so.0
Reading symbols from /usr/lib/libccgnu2-1.5.so.0...done.
Loaded symbols for /usr/lib/libccgnu2-1.5.so.0
Reading symbols from /usr/lib/libboost_regex.so.1...done.
Loaded s
is a snippet from one of the core dumps:
Core was generated by `/foo/bar -l'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/libccext2-1.5.so.0...done.
Loaded symbols for /usr/lib/libccext
Yes, there is copy&paste-in-email failure :)
- Original Message
From: "Ger Hobbelt"
To: openssl-users@openssl.org
Date: Tue, 8 Apr 2008 12:36:27 0200
Subject: Re: CRYPTO_add_lock() segmentation fault (core dump included)
On Tue, Apr 8, 2008 at 12:10 PM, Ion Scerbati
On Tue, Apr 8, 2008 at 12:10 PM, Ion Scerbatiuc <[EMAIL PROTECTED]> wrote:
> Oh :)
[...]
> for (i = 0; i < CRYPTO_num_locks(); i ) {
Erm, shouldn't those two loops have an increment (i++ instead of just
'i') there, or is this a copy&paste-in-email failure? ;-)
--> for (i = 0; i < CRYPTO_n
jimmy bahuleyan wrote:
Ion Scerbatiuc wrote:
Thank you for your reply!
I didn't find any refferences to CRYPTO_set_add_lock_callback() in
openssl man pages nor the meaning of this functions/callbacks.
I didn't understand what does CRYPTO_add_lock () do.
CRYPTO_add_lock() does atomic addition
Ion Scerbatiuc wrote:
Thank you for your reply!
I didn't find any refferences to CRYPTO_set_add_lock_callback() in
openssl man pages nor the meaning of this functions/callbacks.
I didn't understand what does CRYPTO_add_lock () do.
CRYPTO_add_lock() does atomic additions (or subtractions). It
On Tue, 2008-04-08 at 10:04 -0500, Ion Scerbatiuc wrote:
> Thank you for your reply!
You're welcome :-)
> I didn't find any refferences to CRYPTO_set_add_lock_callback() in
> openssl man pages nor the meaning of this functions/callbacks.
Ahh, well once you start to understand this stuff better,
es.
Thanks in advance
Best regards,
Ion
- Original Message
From: Geoff Thorpe
To: openssl-users@openssl.org
Date: Tue, 08 Apr 2008 10:44:35 -0400
Subject: Re: CRYPTO_add_lock() segmentation fault (core dump included)
On Tue, 2008-04-08 at 03:35 -0500, Ion Scerbatiuc wrote:
> Hello
On Tue, 2008-04-08 at 03:35 -0500, Ion Scerbatiuc wrote:
> Hello!
> I wrote a multithreaded server using OpenSSL v 0.9.7a (running on a RH
> Enterprise Linux 2.6.9-55.0.2.ELsmp).
> The problem is my server is crashing at random times (it could stay
> alive for 24 hours or can crash within 4 hours).
There seems to be an error in my email client. There is an i(plus)(plus).
- Original Message
From: [EMAIL PROTECTED]
To: openssl-users@openssl.org
Date: Tue, 8 Apr 2008 12:50:07 0200
Subject: RE: CRYPTO_add_lock() segmentation fault (core dump included)
Hello,
> Oh :)
> I for
Subject: RE: CRYPTO_add_lock() segmentation fault (core dump included)
Hello,
> Oh :)
> I forgot to mention that I instantiated those variables (it was like
obvious for me).
> Here is the initialization code:
>
> int Server::TLS_init()
> {
> int i;
>
> mut
Hello,
> Oh :)
> I forgot to mention that I instantiated those variables (it was like
obvious for me).
> Here is the initialization code:
>
> int Server::TLS_init()
> {
> int i;
>
> mutex_buf = (pthread_mutex_t*) malloc(CRYPTO_num_locks() *
sizeof(pthread_mutex_t));
> if (mutex_bu
Oh :)
I forgot to mention that I instantiated those variables (it was like obvious
for me). Here is the
initialization code:
int Server::TLS_init()
{
int i;
mutex_buf = (pthread_mutex_t*) malloc(CRYPTO_num_locks() *
sizeof(pthread_mutex_t));
if (mutex_buf == NULL) {
return -
> I wrote a multithreaded server using OpenSSL v 0.9.7a
> (running on a RH Enterprise Linux 2.6.9-55.0.2.ELsmp).
> The problem is my server is crashing at random times (it
> could stay alive for 24 hours or can crash within 4 hours).
> Inspecting the cores file I found that it crashes in the sam
e dump (some lines where trimmed) looks something like this:
Core was generated by '/foo/bar -args'.
Program terminated with signal 11, Segmentation fault.
Rea
Hi,
I had a re- look into the segmentation fault issue in my application. What I
observe is that OPENSSL_malloc returns NULL in the 'int EVP_DigestInit_ex'
function in digest.c:
if (ctx->digest != type)
{
if (ctx->digest && ctx->digest->ctx_size)
SHA_CTX *c is getting corrupted. GDB indicated ctx=0x0 in init(). However
it was not the case.
static int init(EVP_MD_CTX *ctx)
{
if(ctx != 0L)
{
return SHA1_Init(ctx->md_data);
}
else
{
printf("ctx is NULL\n"); //Never to be seen thou
At times The following traces as well are obtained:
(gdb) bt
#0 MD5_Init (c=0x0) at md5_dgst.c:75
#1 0x405b2a90 in init (ctx=0x0) at m_md5.c:73
#2 0x405afc91 in EVP_DigestInit_ex (ctx=0x8e29b44, type=0x4061f560,
impl=0x0) at digest.c:207
#3 0x403819f5 in ssl3_init_finished_mac (s=0x8e298c8) a
David,
The OpenSSL version that I use is openssl-0.9.8e. Your guess about methods
being called is right. It appears to be stack corruption.
Gayathri,
I don't suspect the gdb. I checked the CTX status in HASH_INIT (SHA_CTX *c)
under stress , 'c' was indeed NULL and the application immediately d
The stack trace showing a null sha1 transform kindof caught my attention
here, I wouldnt go by the the GDB call trace coz its obviously a memory
leak and the gdb stack could have been corrupted, many a times I see 0x0
in the frames but when you actually try to print the ctx address it would
be
> Even reducing the thread stack size didn't help.
> I observe that the thread creation as such is not
> a problem. I create about 1000 threads , delay in
> each thread the SSL_connect for about 10 sec.
> Once the delay expires and each client make connections
> to the server the seg fault occurs.
Even reducing the thread stack size didn't help. I observe that the thread
creation as such is not a problem. I create about 1000 threads , delay in
each thread the SSL_connect for about 10 sec.
Once the delay expires and each client make connections to the server the
seg fault occurs.
Regards,
Pr
> > 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.
> Just curious at how the number 750 was calculated or deduced. And
> is this a linux-specific limit?
On Windows, it's usually more like 800 on older v
--- David Schwartz <[EMAIL PROTECTED]> wrote:
>
> 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.
>
[snip]
>
> It may help to reduce the stack size for each thread. But you really should
> re-architect. Thread
On 10/16/07, Prabhu S <[EMAIL PROTECTED]> wrote:
> Hi David,
>
> Yes, the design of one thread per connection is bit odd. Our application is
> used to test a SSL server for its performance. The application would simulate
> hundreds of client and at a time try connecting to the server. The server
Hi David,
Yes, the design of one thread per connection is bit odd. Our application is
used to test a SSL server for its performance. The application would
simulate hundreds of client and at a time try connecting to the server. The
server would be thus tested for burst connection handling capabilit
Hi Gayathri,
I couldn't entirely grasp what you had mentioned. l didn't find sha1 in
lsmod command output.
If you could describe briefly the issue you had experienced that would be
very much helpful.
Thanks & Regards,
Prabhu. S
On 10/15/07, Gayathri S <[EMAIL PROTECTED]> wrote:
>
> Hi Prabhu,
>
> 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
> #
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 faults
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
Solved adding
SSL_library_init ();
thanks
Marek Marcola ha scritto:
Hello,
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 8321)]
0x4003f866 in SSL_CTX_load_verify_locations () from /usr/lib/libssl.so.0
Here is the code :
#define
CTX is NULL as you say!
-> (null)
Now say :
8423:error:140A90A1:SSL routines:SSL_CTX_new:library has no
ciphers:ssl_lib.c:1366:
Thanks
Marek Marcola ha scritto:
Hello,
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 8321)]
0x4003f866
1 - 100 of 127 matches
Mail list logo
