In message <[EMAIL PROTECTED]> on Fri, 04 Jul 2003 18:34:42 +0530,Fri, 4 Jul 2003 
19:01:21 +0530, "arun" <[EMAIL PROTECTED]> said:

arunks> I am using "OpenSSL 0.9.6b [engine] 9 Jul 2001" on Red Had
arunks> Linux. I have compiled it with my application. Things were
arunks> fine until I added singal handling code for my application. I
arunks> blocked all signals at application startup and have handling
arunks> code for SIGINT alone. After the addition of signal handling
arunks> code, SSL_connect fails. Does openssl need any signal that I
arunks> am masking ?. or could something else have caused this
arunks> problem.

The only piece of code that does any signal handling in OpenSSL up to
and not including 0.9.7 is crypto/des/read_pwd.c (in 0.9.7 and on,
it's crypto/ui/ui_openssl.c instead).  The code there basically
handles all signals but USR1, USR2 and KILL, but will ignore all but
SIGINT.  Note that this happens around prompting, and all signal
handler get restored when prompting is done.  I've no idea what part
of SSL_connect() would be broken by doing this.

Note that it's quite possible that the underlying network
reading/writing calls use signals for some things, and that may depend
on your platform.  I've no idea what the needs of RH is at this level,
but blockign *all* signals may not always be the best idea.

-- 
Richard Levitte   \ Tunnlandsvägen 3  \ [EMAIL PROTECTED]
[EMAIL PROTECTED]  \ S-168 36  BROMMA  \ T: +46-8-26 52 47
                    \      SWEDEN       \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis                -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/

Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to