Dear Users,
Here is the ChangeLog entry:
Version 4.11, 2005.07.09, urgency: MEDIUM:
* New features
- New ./configure option --with-threads to select thread model.
- ./configure option --with-tcp-wrappers renamed to --disable-libwrap.
I hope the meaning of the option is much more clear, n
Jagannadha Bhattu wrote:
Can some one answer the 4th and 5th questions
Why not read the source?
ssl3_send_server_key_exchange() would call SSL->cert->rsa_tmp_cb()
set by ssl3_callback_ctrl(, SSL_CRTL_SET_TMP_RSA_CB, )
or by ssl3_ctx_callback_ctrl().
SSL_CTX_set_tmp_rsa_callback() is just
SSL_
I truely appreciate the help.
I reviewed the certsc.cnf file and made sure I exactly duplicated the
recommended additions including using "engines" instead of "engine."
But I am still having a few problems...
Here is what I have in my config file (certsc.cnf):
---
openssl_conf = openssl_init
1. If we do not set SSL_OP_SINGLE_DH_USE then the same public and
private keys are used for all connections? If so how can this provide
security at all as one client can decrypt other client's messages?
2. Is it required to seed the random number generator whenever we use
SSL? or only in cases whe
Can some one answer the 4th and 5th questions
On 7/8/05, Vadym Fedyukovych <[EMAIL PROTECTED]> wrote:
> Jagannadha Bhattu wrote:
> > Hi,
> >
> > I have some questions on ephemeral keying.
> >
> > 1. In the man page for SSL_CTX_set_tmp_dh_callback the example shows
> > that the same params are used
Robinson, Richard L (Rick) wrote:
I am still running into a few problems and am hoping for a little more
debugging assistance.
I created these entries in my configuration file (certsc.cnf):
engine = engine_section
[ engine_section ]
smartcard = smartcard_engine
[ smartcard_engine ]
engin
