[Wireshark-bugs] [Bug 14357] Crash when opening Statistics -> I/O Graph

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14357 Jim Young changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED

[Wireshark-bugs] [Bug 14905] Crash opening a capture file or live capturing with either a regex display filter applied or with a coloring rule containing a regex

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14905 Jim Young changed: What|Removed |Added Status|INCOMPLETE |CONFIRMED CC|

[Wireshark-bugs] [Bug 13891] gui.ask_unsaved not functioning when starting new trace from Capture Options

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13891 --- Comment #3 from Laura --- It appears fixed. Ok to close. -- You are receiving this mail because: You are watching all bug changes.___ Sent via:

[Wireshark-bugs] [Bug 10428] tshark's -c flag no longer operates correctly

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10428 --- Comment #2 from Christopher Maynard --- An old bug, and still no solution, but here's a possible work-around that allows the original frame numbers to be displayed: tshark -r [file] -Y "tcp.stream eq 1" | head -n 3 (This of

[Wireshark-bugs] [Bug 14928] Unable to Store Regexp in a Display Macro

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14928 Christopher Maynard changed: What|Removed |Added Ever confirmed|0 |1 OS|macOS

[Wireshark-bugs] [Bug 14917] retapping packets leads to duplicates lines in VoIP call flow window

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14917 --- Comment #2 from Christopher Maynard --- Closing the VoIP Calls window, you also get a bunch of these warnings: 16:16:14.121 Warn remove_tap_listener(): no listener found with that tap data -- You are receiving this mail

[Wireshark-bugs] [Bug 13373] Coloring Rules does not work completely

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13373 Christopher Maynard changed: What|Removed |Added See Also||https://bugs.wireshark.org/

[Wireshark-bugs] [Bug 15034] Users get very little useful info when importing a coloring rules file uncovers rules that are wrong

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15034 Christopher Maynard changed: What|Removed |Added See Also||https://bugs.wireshark.org/

[Wireshark-bugs] [Bug 13373] Coloring Rules does not work completely

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13373 Christopher Maynard changed: What|Removed |Added See Also||https://bugs.wireshark.org/

[Wireshark-bugs] [Bug 14906] Handle errors in coloring rules better

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14906 Christopher Maynard changed: What|Removed |Added See Also||https://bugs.wireshark.org/

[Wireshark-bugs] [Bug 15034] Users get very little useful info when importing a coloring rules file uncovers rules that are wrong

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15034 Christopher Maynard changed: What|Removed |Added See Also||https://bugs.wireshark.org/

[Wireshark-bugs] [Bug 14906] Handle errors in coloring rules better

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14906 Christopher Maynard changed: What|Removed |Added See Also||https://bugs.wireshark.org/

[Wireshark-bugs] [Bug 14905] Crash opening a capture file or live capturing with either a regex display filter applied or with a coloring rule containing a regex

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14905 Christopher Maynard changed: What|Removed |Added Summary|Crash Opening Capture with |Crash opening a capture

[Wireshark-bugs] [Bug 14892] Expert Information dialog groups items incorrectly

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14892 Christopher Maynard changed: What|Removed |Added See Also||https://bugs.wireshark.org/

[Wireshark-bugs] [Bug 14892] Expert Information dialog groups items incorrectly

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14892 Christopher Maynard changed: What|Removed |Added Hardware|x86 |All

[Wireshark-bugs] [Bug 14425] Expert Information Summary for Bad Checksum is incorrect

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14425 Christopher Maynard changed: What|Removed |Added See Also||https://bugs.wireshark.org/

[Wireshark-bugs] [Bug 14891] "Capture to a permanent file" field repopulates after clearing

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14891 Christopher Maynard changed: What|Removed |Added Ever confirmed|0 |1

[Wireshark-bugs] [Bug 15472] Wireshark gets EINVAL on Windows when trying to write capture file

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15472 --- Comment #5 from Guy Harris --- (In reply to Guy Harris from comment #4) > Perhaps, on Windows, we need to look at _doserrno and try to detect errors > reading from or writing to a dead server. E.g., check for errors such as

[Wireshark-bugs] [Bug 14865] Qt wireshark crashed when I opened second IO Graph

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14865 --- Comment #1 from Christopher Maynard --- (In reply to Xiaochuan Sun from comment #0) > Qt wireshark crashed when I opened second IO Graph. There is no problem > when opening first IO graph. I can not reproduce this problem with

[Wireshark-bugs] [Bug 14784] Opening a capture file does not set the configured time display format

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14784 Christopher Maynard changed: What|Removed |Added Resolution|--- |WORKSFORME

[Wireshark-bugs] [Bug 15472] Wireshark gets EINVAL on Windows when trying to write capture file

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15472 --- Comment #4 from Guy Harris --- Perhaps, on Windows, we need to look at _doserrno and try to detect errors reading from or writing to a dead server. -- You are receiving this mail because: You are watching all bug

[Wireshark-bugs] [Bug 14693] Re-implement the "MAP-Button" in the Endpoint dialog atop the new MaxMind database

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14693 Christopher Maynard changed: What|Removed |Added CC||le...@netcowboy.dk ---

[Wireshark-bugs] [Bug 14773] Maxmind geoip lookup not working

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14773 Christopher Maynard changed: What|Removed |Added Status|CONFIRMED |RESOLVED

[Wireshark-bugs] [Bug 14101] PacketGetStats error 995 on Bluetooth device

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14101 --- Comment #12 from LorenAmelang --- (In reply to Christopher Maynard from comment #11) > For me, it would seem to make more sense to close this bug as NOTOURBUG and > then for someone to open an issue with nmap for any behavioral

[Wireshark-bugs] [Bug 14772] IO Graph and Y Field Analysis is not working correctly

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14772 --- Comment #1 from Christopher Maynard --- (In reply to Henrik Wahsner from comment #0) > Expectation is that you enter a new line and the result is immediately shown > when you enable this line. This was the case in earlier versions may

[Wireshark-bugs] [Bug 15472] Wireshark gets EINVAL on Windows when trying to write capture file

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15472 --- Comment #3 from Guy Harris --- That particular dialog's message comes from dumpcap, where it's generated if either pcapng_write_block(), pcapng_write_enhanced_packet_block(), libpcap_write_packet(), or capture_loop_close_output()

[Wireshark-bugs] [Bug 15472] Wireshark gets EINVAL on Windows when trying to write capture file

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15472 --- Comment #2 from Christopher Maynard --- Since the capture files are being read from and written to a network share, did anything happen to the share, such as the connection to it being lost? Perhaps the solution is simply to save

[Wireshark-bugs] [Bug 15472] Wireshark gets EINVAL on Windows when trying to write capture file

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15472 Guy Harris changed: What|Removed |Added Summary|Wireshark unable to write |Wireshark gets EINVAL on

[Wireshark-bugs] [Bug 15472] Wireshark gets EINVAL on Windows when trying to write capture file

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15472 --- Comment #1 from Guy Harris --- It also gets EINVAL on a later read, apparently. -- You are receiving this mail because: You are watching all bug changes.___

[Wireshark-bugs] [Bug 12584] Saving PDML packet dissection crashes wireshark

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12584 Christopher Maynard changed: What|Removed |Added Severity|Minor |Major --- Comment #5 from

[Wireshark-bugs] [Bug 13513] Thread 0 crashes with SIGSEGV due to bad access when opening pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13513 Christopher Maynard changed: What|Removed |Added Status|INCOMPLETE |RESOLVED

[Wireshark-bugs] [Bug 15472] New: Wireshark unable to write capture file

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15472 Bug ID: 15472 Summary: Wireshark unable to write capture file Product: Wireshark Version: 2.6.6 Hardware: x86 OS: Windows 10 Status: UNCONFIRMED

[Wireshark-bugs] [Bug 14101] PacketGetStats error 995 on Bluetooth device

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14101 --- Comment #11 from Christopher Maynard --- (In reply to LorenAmelang from comment #10) > Happened to notice this today: > https://github.com/nmap/nmap/issues/757 > "It means that you didn't uninstall WinPcap 4.1.3 thoroughly last time.

[Wireshark-bugs] [Bug 13857] Resolved Addresses have more than what is in trace file

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13857 utente.ex...@tiscali.it changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever

[Wireshark-bugs] [Bug 12475] Qt: After modifying coloring rules, the coloring rule applied to the first packet reflects the coloring rules previously in effect.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12475 utente.ex...@tiscali.it changed: What|Removed |Added Ever confirmed|0 |1

[Wireshark-bugs] [Bug 15471] Coloring rule modifications does not apply to the first captured packet

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15471 Christopher Maynard changed: What|Removed |Added Resolution|--- |DUPLICATE

[Wireshark-bugs] [Bug 12475] Qt: After modifying coloring rules, the coloring rule applied to the first packet reflects the coloring rules previously in effect.

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12475 Christopher Maynard changed: What|Removed |Added CC||utente.ex...@tiscali.it

[Wireshark-bugs] [Bug 13857] Resolved Addresses have more than what is in trace file

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13857 utente.ex...@tiscali.it changed: What|Removed |Added CC||utente.ex...@tiscali.it

[Wireshark-bugs] [Bug 15471] New: Coloring rule modifications does not apply to the first captured packet

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15471 Bug ID: 15471 Summary: Coloring rule modifications does not apply to the first captured packet Product: Wireshark Version: 2.6.6 Hardware: x86-64

[Wireshark-bugs] [Bug 13881] Add (IETF) QUIC Dissector

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13881 --- Comment #208 from Gerrit Code Review --- Change 31817 merged by Peter Wu: QUIC: put coalesced packets in separate trees https://code.wireshark.org/review/31817 -- You are receiving this mail because: You are watching all bug

[Wireshark-bugs] [Bug 15466] Column width and hidden issues when switching profiles

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15466 --- Comment #6 from Gerrit Code Review --- Change 31833 merged by Stig Bjørlykke: Qt: Restore column width and visibility when switching profiles https://code.wireshark.org/review/31833 -- You are receiving this mail because: You are

[Wireshark-bugs] [Bug 15466] Column width and hidden issues when switching profiles

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15466 --- Comment #4 from Gerrit Code Review --- Change 31832 merged by Stig Bjørlykke: Qt: Restore column width and visibility when switching profiles https://code.wireshark.org/review/31832 -- You are receiving this mail because: You are

[Wireshark-bugs] [Bug 15466] Column width and hidden issues when switching profiles

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15466 --- Comment #5 from Gerrit Code Review --- Change 31833 had a related patch set uploaded by Stig Bjørlykke: Qt: Restore column width and visibility when switching profiles https://code.wireshark.org/review/31833 -- You are receiving

[Wireshark-bugs] [Bug 15466] Column width and hidden issues when switching profiles

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15466 --- Comment #3 from Gerrit Code Review --- Change 31832 had a related patch set uploaded by Stig Bjørlykke: Qt: Restore column width and visibility when switching profiles https://code.wireshark.org/review/31832 -- You are receiving

[Wireshark-bugs] [Bug 15466] Column width and hidden issues when switching profiles

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15466 --- Comment #2 from Gerrit Code Review --- Change 31812 merged by Stig Bjørlykke: Qt: Restore column width and visibility when switching profiles https://code.wireshark.org/review/31812 -- You are receiving this mail because: You are

[Wireshark-bugs] [Bug 15463] Wireshark heap out-of-bounds read in infer_pkt_encap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15463 --- Comment #13 from Gerrit Code Review --- Change 31829 merged by Guy Harris: Also check whether we have nothing but DLCI bytes. https://code.wireshark.org/review/31829 -- You are receiving this mail because: You are watching all bug

[Wireshark-bugs] [Bug 15463] Wireshark heap out-of-bounds read in infer_pkt_encap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15463 --- Comment #15 from Gerrit Code Review --- Change 31830 merged by Guy Harris: Also check whether we have nothing but DLCI bytes. https://code.wireshark.org/review/31830 -- You are receiving this mail because: You are watching all bug

[Wireshark-bugs] [Bug 15463] Wireshark heap out-of-bounds read in infer_pkt_encap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15463 --- Comment #14 from Gerrit Code Review --- Change 31830 had a related patch set uploaded by Guy Harris: Also check whether we have nothing but DLCI bytes. https://code.wireshark.org/review/31830 -- You are receiving this mail because:

[Wireshark-bugs] [Bug 15463] Wireshark heap out-of-bounds read in infer_pkt_encap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15463 --- Comment #12 from Gerrit Code Review --- Change 31829 had a related patch set uploaded by Guy Harris: Also check whether we have nothing but DLCI bytes. https://code.wireshark.org/review/31829 -- You are receiving this mail because:

[Wireshark-bugs] [Bug 15463] Wireshark heap out-of-bounds read in infer_pkt_encap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15463 --- Comment #11 from Gerrit Code Review --- Change 31828 merged by Guy Harris: Also check whether we have nothing but DLCI bytes. https://code.wireshark.org/review/31828 -- You are receiving this mail because: You are watching all bug

[Wireshark-bugs] [Bug 15463] Wireshark heap out-of-bounds read in infer_pkt_encap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15463 --- Comment #10 from Gerrit Code Review --- Change 31828 had a related patch set uploaded by Guy Harris: Also check whether we have nothing but DLCI bytes. https://code.wireshark.org/review/31828 -- You are receiving this mail because:

[Wireshark-bugs] [Bug 15463] Wireshark heap out-of-bounds read in infer_pkt_encap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15463 --- Comment #9 from Mateusz Jurczyk --- If I'm not mistaken changes 31824/31825/31826 still allow for a one-byte overread. If i points to the last byte of the buffer (i == len - 1) after the loop, then the == 0x03 comparison will be