[jitsi-dev] [jitsi] Display TLS information (#11)


As a first step towards the support for configuring TLS protocols and cipher suites, I have created a patch which adds logging of the available protocols/algorithms and finally the chosen ones. The patch also adds the ability to access the protocol and algorithm used as well as the server certificate chain.

At the moment this information will be available in the call information frame.

Currently this patch only implements support for getting the TLS information from the Jabber ProtocolProviderService.
You can merge this Pull Request by running:

  git pull https://github.com/netmackan/jitsi master

Or you can view, comment on it, or merge it online at:


-- Commit Summary --

  * Logging of TLS protocols and cipher suites available during connection establishment and then the chosen ones.
  * Add ability to access TLS cipher suite, protocol name and server certificate chain at any time. Only implemented for XMPP so far. Also makes this information available in the call information frame.

-- File Changes --

    M src/net/java/sip/communicator/impl/gui/main/call/CallInfoFrame.java (64)
    M src/net/java/sip/communicator/impl/protocol/jabber/ProtocolProviderServiceJabberImpl.java (102)
    M src/net/java/sip/communicator/impl/protocol/mock/MockProvider.java (38)
    M src/net/java/sip/communicator/impl/protocol/sip/ProtocolProviderServiceSipImpl.java (16)
    M src/net/java/sip/communicator/service/protocol/AbstractProtocolProviderService.java (47)
    M src/net/java/sip/communicator/service/protocol/ProtocolProviderService.java (26)

-- Patch Links --



Fixed some code convention problems and added internationalization for the strings presented in the GUI.


Reply to this email directly or view it on GitHub:


I'll close this as the issues discussed in the thread http://lists.jitsi.org/pipermail/dev/2013-November/018802.html need to be addressed first. Feel free to create a new request once this is done.


Reply to this email directly or view it on GitHub:


Closed #11.


Reply to this email directly or view it on GitHub: