| Summary: | wireshark new release 3.0.12 fixes bugs | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Walser <luigiwalser> |
| Component: | RPM Packages | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | andrewsfarm, mageia, sysadmin-bugs, tarazed25 |
| Version: | 7 | Keywords: | advisory, has_procedure, validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | MGA7-64-OK | ||
| Source RPM: | wireshark-3.0.11-1.mga7.src.rpm | CVE: | |
| Status comment: | |||
|
Description
David Walser
2020-07-02 20:54:46 CEST
Testing procedure: https://wiki.mageia.org/en/QA_procedure:Wireshark Keywords:
(none) =>
has_procedure mga7, x86_64
Added user to wireshark group and installed all the packages from release.
Tested wireshark by capturing a pcap file for the ethernet interface.
Updated wireshark - 10 packages and ran the test procedure.
$ wireshark -n testing.pcapng
That brought up the wireshark interface which showed a series of TCP ACKs and a few Standard query-responses and http transactions. Selected a GET, which displayed the packet in twinhex and ASCII. Recognized the references to the site just viewed, the EU exoplanet catalogue. Protocol information is listed in a separate panel.
That all looks fine.
Captured a few more packets and examined the capture file.
$ wireshark -n wiresharktest.pcap
All looks normal.
$ tshark -nr wiresharktest.pcap
[...]
677 138.129218 13.224.78.21 → 192.168.1.103 TLSv1.2 112 Application Data
678 138.129240 192.168.1.103 → 13.224.78.21 TCP 66 46444 → 443 [ACK] Seq=905 Ack=6076 Win=64128 Len=0 TSval=209081722 TSecr=274493503
679 138.129955 151.139.128.14 → 192.168.1.103 TCP 66 [TCP Keep-Alive ACK] 80 → 58812 [ACK] Seq=944 Ack=372 Win=30080 Len=0 TSval=3086094995 TSecr=1886741943
$ ll
-rw-r--r-- 1 lcl lcl 14316 Jul 2 23:17 wiresharktest50
-rw-r--r-- 1 lcl lcl 202121 Jul 2 23:09 wiresharktest.pcap
$ mergecap -v -w wiresharkmerged wiresharktest.pcap wiresharktest50
mergecap: wiresharktest.pcap is type Wireshark/tcpdump/... - pcap.
mergecap: wiresharktest50 is type Wireshark/... - pcapng.
mergecap: selected frame_type Ethernet (ether)
mergecap: ready to merge records
[...]
Record: 729
mergecap: merging complete
$ ll
-rw-r--r-- 1 lcl lcl 228328 Jul 2 23:19 wiresharkmerged
$ randpkt -b 500 -t dns wireshark_dns.pcap
$ ll wireshark*
-rw-r--r-- 1 lcl lcl 285299 Jul 2 23:23 wireshark_dns.pcap
Could not find dftest.
$ locate dftest
/usr/share/doc/wireshark/dftest.html
/usr/share/man/man1/dftest.1.xz
/usr/share/wireshark/dftest.html
Is this a regression?
$ capinfos wiresharktest50
File name: wiresharktest50
File type: Wireshark/... - pcapng
File encapsulation: Ethernet
File timestamp precision: microseconds (6)
Packet size limit: file hdr: (not set)
Number of packets: 50
[...]
Number of interfaces in file: 1
Interface #0 info:
Encapsulation = Ethernet (1 - ether)
Capture length = 262144
Time precision = microseconds (6)
Time ticks per second = 1000000
Number of stat entries = 0
Number of packets = 50
It all looks good except for the missing /bin/dftest.CC:
(none) =>
tarazed25 dftest.c is available at https://github.com/boundary/wireshark/blob/master/dftest.c It's not a regression. We last had dftest in Mageia 6. Looking at the build log, it looks like it builds it but doesn't install it. Bug with the new cmake-based build system. I could try compiling it locally if wireshark.pc covers all the bases. Nope. This is packager country. So, given that dtest has been pushed in the past without dtest and that current tests look OK for the rest of it, let's set OK on this one. Whiteboard:
(none) =>
MGA7-64-OK s/dtest/dftest/ Validating. Advisory in Comment 0. CC:
(none) =>
andrewsfarm, sysadmin-bugs
Nicolas Lécureuil
2020-07-07 12:43:30 CEST
CC:
(none) =>
mageia An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2020-0156.html Status:
NEW =>
RESOLVED |