All-
I am trying to evaluate the usage of TLS with SIPp, with no sucess (that is
without recompiling SIPp).
1. I had created a cacert.pem / cakey.pem pair using openSSL's utilities -
the CERT is also Signed by a CA as well.
NOTE: the cakey.pem is ENCRYPTED - as that is the default output of the
openssl key generation
utility.
2. Verified that the cacert.pem / cakey.pem is valid using openSSL's ssltest
test utility:
*ssltest -cert cacert.pem -key cakey.pem*
I am requested to enter the PEM pass phrase: And it validates OK.
3. When using the same cacert.pem / cakey.pem pair with SIPp, sipp fails
with the following error:
2008-01-21 16:45:31: FI_init_ssl_context: SSL_CTX_use_PrivateKey_file
failed.
I am NEVER requested to enter the PEM pass phrase to unlock the
cakey.pem file.
4. After looking into the 2.0x code as well as the 3.0x code, I noticed that
the
SSL_CTX_set_default_passwd_cb() and
SSL_CTX_set_default_passwd_cb_userdata()
are called - overriding the default SSL password callback routine + the
userdata is
*useless!!!
* if I used the -ab parameter to set the password via command line and
changed the
calls to SSL_CTX_set_default_passwd_cb_userdata() to use the
auth_password & recompiled
SIPp, I was able to run SIPp in TLS mode.
Is this by design? Is sipp expecting a NON ENCRYPTED cakey.pem file?
If so, this should be documented!!
-Mike
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
