< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate-users] TLS mutual authentication issue


resiprocate should provide the certificate if it is requested.   What do you mean that it only sends a key and not a certificate?  It could be an issue with loading your certificates, or setting the domain on your TLS transport.    A wireshark trace and a DEBUG level resiprocate log would help narrow down what is happening.

Also - some certificate info is on wiki:  http://www.resiprocate.org/Certificates

Scott

On Sun, Jul 15, 2012 at 6:06 PM, Haugen Keith-CKH040 <Keith.Haugen@xxxxxxxxxxxxxxxxxxxxx> wrote:

I am having an issue where when my PBX sends a certificate request (after the client and server hello), my client using the resiprocate stack does not send back a certificate in its response (it only sends a key).  I am not sure where the issue lies (configuration, use of the stack, etc…), or where to look, and I am hoping can help me figure out what I am doing wrong.  Thanks!


_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/