search for: client_hello

I am trying to debug a comm-problem between Jitsi running on my CentOS-6.6 workstation and Asterisk running on A CentOS-6.5 based distro from FreePBX. I want to view the contents of the following parts of the TLS session setup: CLIENT_HELLO, SERVER_HELLO and CHANGE_CIPHERSPEC. However, I have no idea how to actually do this with Wireshark. I would like some guidance on how to proceed if someone would be so kind. -- *** E-Mail is NOT a SECURE channel *** James B. Byrne mailto:ByrneJB at Harte-Lyne.c...

...p server. When an SSL TCP connection is established on port 993, the server program will know the IP # that was used for the connection and can use getnameinfo to extract the domain name (%d). This can then be used to build a specific reference to the certificate to be used, prior to responding to CLIENT_HELLO. Something like /etc/ssl/%d/[certs|private]/dovecot.pem One technique would be to include this in multiple dovecot.conf listen parameters read on startup, similar to tpop3d: listen = ###.###.###.1:993(domain1.tld);tls=stls,\ /etc/ssl/domain1.tld/certs/dovecot.pem,\ /etc/ssl/doma...