We start a Jenkins instance on a Windows host as a Service. It looks like the server is correctly configured (
--httpPort=-1 --httpsPort=8080etc) and has an own key store. There is no proxy in front.
The server uses a certificate (A) that is derived from a self-signed one (B). The self-signed certificate (B) is also present in the client's Windows trust store (I've imported it).
Connecting from the client to the server with Chrome works and Chrome indicates that the connection is OK and secured. It correctly shows me the certificate chain.
The following confuses me: I cannot see any TLS-traffic using Wireshark.
I'm looking at the correct interface, and I've added the
ssl filter. I would have expected to see a TLS handshake. Despite the non-standard port, Chrome can know that this shall be a secured session because of the scheme
To test that Wireshark is not the problem, googling to e.g.
stackoverflow.com and I'm seeing lots of packets with Protocol
TLSv1.2 to the internet proxy.
I'm not aware that Jenkins is using STARTTLS. Chrome is sending the CSP header
Upgrade-Insecure-Requests:1 that seems to be superfluous, because this should be a secure connection anyway.
httpsbut Wireshark doesn't; Wireshark only sees the port and port 8080 is not standardly HTTPS or any other SSL. Rightclick on a message in the list pane, DecodeAs, adjust the selection to port 8080 and change the rightmost entry/column to SSL (which also covers TLS). Crossdupe stackoverflow.com/questions/41372311/…