[Wireshark-bugs] [Bug 13059] New: InterfaceTreeList: The column for the Extcap interface Options widget sometimes is not displayed

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13059 Bug ID: 13059 Summary: InterfaceTreeList: The column for the Extcap interface Options widget sometimes is not displayed Product: Wireshark Version: 2.3.x (Experimental)

[Wireshark-bugs] [Bug 13058] New: InterfaceTreeList - Can not successfully unhide all interfaces from Manage Interfaces dialog

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13058 Bug ID: 13058 Summary: InterfaceTreeList - Can not successfully unhide all interfaces from Manage Interfaces dialog Product: Wireshark Version: 2.3.x (Experimental)

[Wireshark-bugs] [Bug 13057] New: Buildbot crash output: fuzz-2016-10-27-31904.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13057 Bug ID: 13057 Summary: Buildbot crash output: fuzz-2016-10-27-31904.pcap Product: Wireshark Version: unspecified Hardware: x86-64 URL:

[Wireshark-bugs] [Bug 13050] [AMQP 1.0] Dissector fails to handle frames with length > 64Kb

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13050 --- Comment #3 from Michael Mann --- (In reply to chugzilla77 from comment #2) > Decoding the trace to PDML (using release code 2.2.1) produces a killer text > file that puts gedit and emacs to sleep. So is this a

[Wireshark-bugs] [Bug 13050] [AMQP 1.0] Dissector fails to handle frames with length > 64Kb

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13050 --- Comment #2 from chugzill...@gmail.com --- Created attachment 15016 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15016=edit AMQP 300kb+ frame that causes decoding errors The traffic is between hosts 10.18.97.70:36782 -

[Wireshark-bugs] [Bug 13056] New: Buildbot crash output: fuzz-2016-10-26-28356.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13056 Bug ID: 13056 Summary: Buildbot crash output: fuzz-2016-10-26-28356.pcap Product: Wireshark Version: unspecified Hardware: x86-64 URL:

[Wireshark-bugs] [Bug 13055] Allow decode as Modbus RTU over USB

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13055 --- Comment #1 from Gerrit Code Review --- Change 18468 merged by Michael Mann: packet-mbtcp: Allow decode as Modbus RTU over USB https://code.wireshark.org/review/18468 -- You are receiving this mail

[Wireshark-bugs] [Bug 13055] Allow decode as Modbus RTU over USB

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13055 Gerrit Code Review changed: What|Removed |Added Status|UNCONFIRMED

[Wireshark-bugs] [Bug 13055] New: Allow decode as Modbus RTU over USB

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13055 Bug ID: 13055 Summary: Allow decode as Modbus RTU over USB Product: Wireshark Version: Git Hardware: All OS: All Status: UNCONFIRMED Severity:

[Wireshark-bugs] [Bug 13054] New: Buildbot crash output: fuzz-2016-10-26-15841.pcap

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13054 Bug ID: 13054 Summary: Buildbot crash output: fuzz-2016-10-26-15841.pcap Product: Wireshark Version: unspecified Hardware: x86-64 URL:

[Wireshark-bugs] [Bug 13025] Relay Data option is not allowed in Bulk Leasequery reply

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13025 --- Comment #4 from Gerrit Code Review --- Change 18480 had a related patch set uploaded by Alexis La Goutte: DHCPv6: Remove check for Relay Data option about Bulk Leasequery reply

[Wireshark-bugs] [Bug 13052] SGASP malformed packet

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13052 --- Comment #6 from Nadia --- OK, I understood. But there is no test equipment and this is a real traffic. I have a question on following situation. In row 5 there also same messages and NAS container seem to

[Wireshark-bugs] [Bug 13052] SGASP malformed packet

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13052 --- Comment #5 from Anders Broman --- Junk as in not valid data, a NAS message container filled all with 0xff is not a valid SMS message. If you are using some test equipment to generate this signals it's

[Wireshark-bugs] [Bug 13052] SGASP malformed packet

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13052 --- Comment #4 from Nadia --- Comment on attachment 15014 --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15014 new trace there other trace that packet is not malformed. Sorry I am beginner in SGs

[Wireshark-bugs] [Bug 13052] SGASP malformed packet

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13052 Nadia changed: What|Removed |Added CC|

[Wireshark-bugs] [Bug 12814] Unable to save changes to coloring rules

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12814 Alexis La Goutte changed: What|Removed |Added Status|CONFIRMED

[Wireshark-bugs] [Bug 13052] SGASP malformed packet

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13052 Anders Broman changed: What|Removed |Added Component|Capture file support

[Wireshark-bugs] [Bug 13053] SGASP malformed packet

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13053 Pascal Quantin changed: What|Removed |Added Status|UNCONFIRMED

[Wireshark-bugs] [Bug 12814] Unable to save changes to coloring rules

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12814 giel.oberhols...@dimensiondata.com changed: What|Removed |Added Status|RESOLVED|CONFIRMED

[Wireshark-bugs] [Bug 13052] SGASP malformed packet

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13052 --- Comment #1 from Pascal Quantin --- *** Bug 13053 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.

[Wireshark-bugs] [Bug 13053] SGASP malformed packet

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13053 Nadia changed: What|Removed |Added CC|

[Wireshark-bugs] [Bug 13053] SGASP malformed packet

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13053 --- Comment #1 from Anders Broman --- We need a capture file to look at the problem. You can mark it as private if you want. -- You are receiving this mail because: You are watching all bug changes.

[Wireshark-bugs] [Bug 13053] New: SGASP malformed packet

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13053 Bug ID: 13053 Summary: SGASP malformed packet Product: Wireshark Version: 2.2.1 Hardware: All OS: All Status: UNCONFIRMED Severity: Normal

[Wireshark-bugs] [Bug 13052] New: SGASP malformed packet

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13052 Bug ID: 13052 Summary: SGASP malformed packet Product: Wireshark Version: 2.2.1 Hardware: All OS: All Status: UNCONFIRMED Severity: Normal

[Wireshark-bugs] [Bug 13012] sshdump does not save password

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012 --- Comment #15 from Graham Bloice --- That looks interesting, an ssh-agent replacement that proxies pageant. I'll have to test that to see if it can co-exist with the ssh-agent from Git that I normally have

[Wireshark-bugs] [Bug 13020] Column fields not displaying using -T {pdml, json, ek}

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13020 --- Comment #2 from Jaap Keuter --- (In reply to Guy Harris from comment #1) > It doesn't seem to work with -T pdml, either. Indeed, the question is 'How do you present packet summary info in a packet details

[Wireshark-bugs] [Bug 13012] sshdump does not save password

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012 --- Comment #14 from Dario Lombardo --- (In reply to Graham Bloice from comment #13) > > I have that on my long list of rainy day projects. > "Rainy day projects" ... I like it! For completeness, I found a code that

[Wireshark-bugs] [Bug 13012] sshdump does not save password

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012 Roland Knall changed: What|Removed |Added Status|CONFIRMED |RESOLVED

[Wireshark-bugs] [Bug 13012] sshdump does not save password

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012 --- Comment #13 from Graham Bloice --- Pageant support will require modifications to libssh, as it doesn't use a socket interface, instead it uses a shared memory mapped file for the data and Windows messages

[Wireshark-bugs] [Bug 13012] sshdump does not save password

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012 --- Comment #12 from Roland Knall --- (In reply to Dario Lombardo from comment #11) > (In reply to Roland Knall from comment #8) > > So I think, support for ssh-agent and pageant (putty's ssh agent) is the > > right way

[Wireshark-bugs] [Bug 13012] sshdump does not save password

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13012 --- Comment #11 from Dario Lombardo --- (In reply to Roland Knall from comment #8) > So I think, support for ssh-agent and pageant (putty's ssh agent) is the > right way forward. ssh-agent support is already in place.

[Wireshark-bugs] [Bug 13048] sshdump does not allow empty capture filter

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13048 Dario Lombardo changed: What|Removed |Added Version|2.3.x (Experimental)|Git

[Wireshark-bugs] [Bug 13051] Extcap UI doesn't submit default values

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13051 --- Comment #6 from Dario Lombardo --- Yes. -- You are receiving this mail because: You are watching all bug changes. ___ Sent via:

[Wireshark-bugs] [Bug 13051] Extcap UI doesn't submit default values

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13051 --- Comment #5 from Roland Knall --- (In reply to Dario Lombardo from comment #4) > Uhmmm... I'd say the opposite. The ssh port can be omitted. sshdump will > alyaws choose a default port. If the filter is omitted it

[Wireshark-bugs] [Bug 13048] sshdump does not allow empty capture filter

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13048 --- Comment #4 from Dario Lombardo --- Yes, you're right. I have a bug about sshdump and UI interface that affects this bug too, so I'll work on both. -- You are receiving this mail because: You are watching all bug

[Wireshark-bugs] [Bug 13051] Extcap UI doesn't submit default values

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13051 --- Comment #4 from Dario Lombardo --- Uhmmm... I'd say the opposite. The ssh port can be omitted. sshdump will alyaws choose a default port. If the filter is omitted it means "don't use any filter", so the default value

[Wireshark-bugs] [Bug 13048] sshdump does not allow empty capture filter

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13048 --- Comment #3 from Stig Bjørlykke --- (In reply to Dario Lombardo from comment #2) > If I delete it an empty filter is submitted (correct). Have a look in sshdump.c run_ssh_command() at this code: 158

[Wireshark-bugs] [Bug 13051] Extcap UI doesn't submit default values

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13051 --- Comment #3 from Roland Knall --- (In reply to Dario Lombardo from comment #2) > How the utility is supposed to use empty values? > > Examples: > > The ssh port has _always_ a value. Not to specify it means to use

[Wireshark-bugs] [Bug 13051] Extcap UI doesn't submit default values

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13051 --- Comment #2 from Dario Lombardo --- How the utility is supposed to use empty values? Examples: The ssh port has _always_ a value. Not to specify it means to use the default. The filter can be empty, that means I

[Wireshark-bugs] [Bug 13051] Extcap UI doesn't submit default values

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13051 --- Comment #1 from Roland Knall --- This is actually done on purpose. Default values exist, because it is assumed, that the utility takes those values as default values if no other value is being provided. Why would

[Wireshark-bugs] [Bug 13051] Extcap UI doesn't submit default values

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13051 Dario Lombardo changed: What|Removed |Added CC|

[Wireshark-bugs] [Bug 13051] New: Extcap UI doesn't submit default values

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13051 Bug ID: 13051 Summary: Extcap UI doesn't submit default values Product: Wireshark Version: Git Hardware: All OS: All Status: UNCONFIRMED Severity:

[Wireshark-bugs] [Bug 13048] sshdump does not allow empty capture filter

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13048 --- Comment #2 from Dario Lombardo --- I can observe the opposite. The gui shows me the default filter. If I don't touch it I expect it is used while it is not (bug). If I change it, it is submitted and used (correct).

[Wireshark-bugs] [Bug 13048] sshdump does not allow empty capture filter

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13048 --- Comment #1 from Dario Lombardo --- I can't reproduce it. Can you tell me step-by-step what do you do? -- You are receiving this mail because: You are watching all bug changes.

[Wireshark-bugs] [Bug 13020] Column fields not displaying using -T {pdml, json, ek}

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13020 Guy Harris changed: What|Removed |Added Hardware|x86 |All

[Wireshark-bugs] [Bug 13020] Column fields not displaying using -T {pdml, json, ek}

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13020 Guy Harris changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED

[Wireshark-bugs] [Bug 13020] Column fields not displaying using -T json

https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13020 Jaap Keuter changed: What|Removed |Added Summary|Protocol Field Not |Column