Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
The same issue on rhel-6.
# rpm -q wireshark
wireshark-1.8.10-17.el6.x86_64
# tshark -o 'ssl.desegment_ssl_records:TRUE' -d tcp.port==4433,ssl -r capture-selfsrv-nss-3.16.2.3-el7.pcap -V | grep -A 6 'Server Key Exchange'
Running as user "root" and group "root". This could be dangerous.
Handshake Protocol: Server Key Exchange
Handshake Type: Server Key Exchange (12)
Length: 199
Handshake Protocol: Server Hello Done
Handshake Type: Server Hello Done (14)
Length: 0
+++ This bug was initially created as a clone of Bug #1222600 +++
Description of problem:
If the connection uses TLSv1.2 the Wireshark GUI can't decode the TLS Handshake Protocol Server Key Exchange messages in ECDHE key exchange, it can do that only if the connection uses TLSv1.0.
Decoding of Server Key Exchange using the CLI tshark command always fails
Version-Release number of selected component (if applicable):
wireshark-1.10.3-12.el7_0.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Open wireshark load sigalgs.pcapng
1. tshark -o 'ssl.desegment_ssl_records:TRUE' -d tcp.port==4433,ssl -r /tmp/capture-selfsrv-nss-3.16.2.3-el7.pcap -V | grep -A 6 'Server Key Exchange'
Actual results:
Handshake Protocol: Server Key Exchange
Handshake Type: Server Key Exchange (12)
Length: 199
Expected results:
Handshake Protocol: Server Key Exchange
Handshake Type: Server Key Exchange (12)
Length: 199
EC Diffie-Hellman Server Params
curve_type: named_curve (0x03)
named_curve: secp256r1 (0x0017)
Pubkey Length: 65
pubkey:
etc.
Additional info:
--- Additional comment from Hubert Kario on 2015-05-19 07:51:21 EDT ---
Wireshark GUI can't also decode Server Key Exchange with DHE-RSS and DHE-DSS key exchange in TLSv1.2.
tshark can't decode DHE or ECDHE key exchange, be it with RSA, DSS or ECDSA authentication and in TLSv1.0 or TLSv1.2
(omitting TLSv1.1 as it has the same message format as TLSv1.0)
The same issue on rhel-6. # rpm -q wireshark wireshark-1.8.10-17.el6.x86_64 # tshark -o 'ssl.desegment_ssl_records:TRUE' -d tcp.port==4433,ssl -r capture-selfsrv-nss-3.16.2.3-el7.pcap -V | grep -A 6 'Server Key Exchange' Running as user "root" and group "root". This could be dangerous. Handshake Protocol: Server Key Exchange Handshake Type: Server Key Exchange (12) Length: 199 Handshake Protocol: Server Hello Done Handshake Type: Server Hello Done (14) Length: 0 +++ This bug was initially created as a clone of Bug #1222600 +++ Description of problem: If the connection uses TLSv1.2 the Wireshark GUI can't decode the TLS Handshake Protocol Server Key Exchange messages in ECDHE key exchange, it can do that only if the connection uses TLSv1.0. Decoding of Server Key Exchange using the CLI tshark command always fails Version-Release number of selected component (if applicable): wireshark-1.10.3-12.el7_0.x86_64 How reproducible: Always Steps to Reproduce: 1. Open wireshark load sigalgs.pcapng 1. tshark -o 'ssl.desegment_ssl_records:TRUE' -d tcp.port==4433,ssl -r /tmp/capture-selfsrv-nss-3.16.2.3-el7.pcap -V | grep -A 6 'Server Key Exchange' Actual results: Handshake Protocol: Server Key Exchange Handshake Type: Server Key Exchange (12) Length: 199 Expected results: Handshake Protocol: Server Key Exchange Handshake Type: Server Key Exchange (12) Length: 199 EC Diffie-Hellman Server Params curve_type: named_curve (0x03) named_curve: secp256r1 (0x0017) Pubkey Length: 65 pubkey: etc. Additional info: --- Additional comment from Hubert Kario on 2015-05-19 07:51:21 EDT --- Wireshark GUI can't also decode Server Key Exchange with DHE-RSS and DHE-DSS key exchange in TLSv1.2. tshark can't decode DHE or ECDHE key exchange, be it with RSA, DSS or ECDSA authentication and in TLSv1.0 or TLSv1.2 (omitting TLSv1.1 as it has the same message format as TLSv1.0)