[Wireshark-bugs] [Bug 13193] Support for DTLS-SRTP (used by WebRTC) with SIP signalling over Websockets

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13193

Jaap Keuter  changed:

   What|Removed |Added

 Status|UNCONFIRMED |IN_PROGRESS
 Ever confirmed|0   |1

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13044] Buildbot crash output: fuzz-2016-10-25-19751.pcap

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13044

--- Comment #14 from Guy Harris  ---
In dissect_cops_pdu() we do:

if (!pinfo->fd->flags.visited) {
cops_call = wmem_new(wmem_file_scope(), cops_call_t);
cops_call->op_code = op_code;
cops_call->solicited = is_solicited;
cops_call->req_num = pinfo->num;
cops_call->rsp_num = 0;
cops_call->req_time = pinfo->abs_ts;
g_ptr_array_add(pdus_array, cops_call);
}
else {
for (i=0; i < pdus_array->len; i++) {
cops_call = (cops_call_t*)g_ptr_array_index(pdus_array, i);
if ( cops_call->req_num == pinfo->num
  && cops_call->rsp_num != 0)  {
ti = proto_tree_add_uint_format(cops_tree,
hf_cops_response_in, tvb, 0, 0, cops_call->rsp_num,
  "Response to this request
is in frame %u", cops_call->rsp_num);
PROTO_ITEM_SET_GENERATED(ti);
}
}
}

cops_call is either allocated or fetched from an array; the only way one we
allocate would have solicited being uninitialized would be if is_solicited were
uninitialized.

However, it's always set before it's used.

So either there's something subtle going on here that I've missed, or this is a
false positive.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13044] Buildbot crash output: fuzz-2016-10-25-19751.pcap

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13044

--- Comment #13 from Guy Harris  ---
Line 1102 in packet-cops.c is the one that tests cops_call->solicited in

if (
( (cops_call->op_code == COPS_MSG_REQ) &&
(op_code == COPS_MSG_DEC && is_solicited) ) ||
( (cops_call->op_code == COPS_MSG_DEC) &&
( (op_code == COPS_MSG_RPT && is_solicited) ||
  (op_code == COPS_MSG_DRQ && is_solicited) ) ) ||
( (cops_call->op_code == COPS_MSG_SSQ) &&
( (op_code == COPS_MSG_RPT && is_solicited) ||
  (op_code == COPS_MSG_DRQ && is_solicited) ||
  (op_code == COPS_MSG_SSC) ) ) ||
( (cops_call->op_code == COPS_MSG_OPN) &&
(op_code == COPS_MSG_CAT ||
 op_code == COPS_MSG_CC) ) ||
( (cops_call->op_code == COPS_MSG_KA &&
!(cops_call->solicited)) &&
(op_code == COPS_MSG_KA && is_solicited) ) ) {
cops_call->rsp_num = pinfo->num;
break;

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13187] Buildbot crash output: fuzz-2016-11-30-31444.pcap

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13187

Michael Mann  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Michael Mann  ---


*** This bug has been marked as a duplicate of bug 13044 ***

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13044] Buildbot crash output: fuzz-2016-10-25-19751.pcap

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13044

--- Comment #12 from Michael Mann  ---
*** Bug 13187 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13049] Buildbot crash output: fuzz-2016-10-24-11612.pcap

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13049

--- Comment #29 from Michael Mann  ---
*** Bug 13186 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13186] Buildbot crash output: fuzz-2016-11-28-2043.pcap

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13186

Michael Mann  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |DUPLICATE

--- Comment #1 from Michael Mann  ---


*** This bug has been marked as a duplicate of bug 13049 ***

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13185] Wireshark doesn't decrypt 802.11 data packets

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13185

Michael Mann  changed:

   What|Removed |Added

 Status|INCOMPLETE  |RESOLVED
 Resolution|--- |NOTABUG

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13174] Export Objects dialog in GTK crashes due to wrong memory scope

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13174

--- Comment #6 from Michael Mann  ---
(In reply to Pascal Quantin from comment #5)
> SHould not another bug be opened for the Gt GUI instead?

Technically yes, but I was hoping someone familiar with the code could just
take a few minutes to check it (I think it just requires some basic Qt
knowledge that I don't have about whether the GUI objects take
control/responsibility of some of the memory assigned to them)

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13193] Support for DTLS-SRTP (used by WebRTC) with SIP signalling over Websockets

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13193

--- Comment #3 from Gerrit Code Review  ---
Change 18997 had a related patch set uploaded by Peter Wu:
SDP: add basic ICE candidate attribute dissection (RFC 5245)

https://code.wireshark.org/review/18997

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13193] Support for DTLS-SRTP (used by WebRTC) with SIP signalling over Websockets

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13193

--- Comment #2 from Gerrit Code Review  ---
Change 18996 had a related patch set uploaded by Peter Wu:
DTLS: add support for use_srtp extension (RFC 5764)

https://code.wireshark.org/review/18996

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13193] Support for DTLS-SRTP (used by WebRTC) with SIP signalling over Websockets

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13193

--- Comment #1 from Peter Wu  ---
Created attachment 15096
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15096&action=edit
TLS 1.2 and DTLS 1.0 master secrets (SSLKEYLOGFILE) for dtls-srtp-ws-sip.pcapng

For this test I used "DTMF demo" (from https://sip5060.net/test-calls/):
https://freephonebox.net/?dial=test.dtmf%40sip5060.net&video=false
which uses Asterisk 11.13.1.

Only the TCP stream for WSS/SIP and UDP (STUN, DTLS-SRTP/G.711, DNS) is
preserved to reduce capture size.

For Opus, there is also https://webrtc.freeswitch.org/

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13193] New: Support for DTLS-SRTP (used by WebRTC) with SIP signalling over Websockets

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13193

Bug ID: 13193
   Summary: Support for DTLS-SRTP (used by WebRTC) with SIP
signalling over Websockets
   Product: Wireshark
   Version: Git
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: Enhancement
  Priority: Low
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: pe...@lekensteyn.nl

Created attachment 15095
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15095&action=edit
Sample WSS/SIP + DTLS-SRTP/G.711 capture (Firefox 50, Asterisk 11.13.1)

Build Information:

--
WebRTC is a platform for web developer that want to implement realtime
multimedia applications. Its architecture is described at
https://webrtc.org/architecture/

This bug tracks the required changes to improve WebRTC support:
- SIP over Websockets (RFC 7118) (fixed today via bug 11420)
- STUN/ICE: need to extend SDP dissector to handle candidates
- DTLS-SRTP (RFC 5764): add use_srtp DTLS extension and add key extractor
- RTP: decryption support for SRTP is missing
- Support for playing the Opus audio codec (MTI per RFC 7874)
- ...

Refs:

Interactive Connectivity Establishment (ICE): A Protocol for Network Address
Translator (NAT) Traversal for Offer/Answer Protocols
https://tools.ietf.org/html/rfc5245

The Secure Real-time Transport Protocol (SRTP)
https://tools.ietf.org/html/rfc3711

Framework for Establishing a Secure Real-time Transport Protocol (SRTP)
Security Context Using Datagram Transport Layer Security (DTLS)
https://tools.ietf.org/html/rfc5763

Datagram Transport Layer Security (DTLS) Extension to Establish Keys
for the Secure Real-time Transport Protocol (SRTP)
https://tools.ietf.org/html/rfc5764

WebRTC Audio Codec and Processing Requirements
https://tools.ietf.org/html/rfc7874

RTP Payload Format for the Opus Speech and Audio Codec
https://tools.ietf.org/html/rfc7587

Multiplexing RTP Data and Control Packets on a Single Port
https://tools.ietf.org/html/rfc5761

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13191] Malformed Packet - SSL

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13191

Alexis La Goutte  changed:

   What|Removed |Added

 CC||alexis.lagou...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13178] HTML escaping of quotes in error message

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13178

--- Comment #6 from Gerrit Code Review  ---
Change 18992 had a related patch set uploaded by Gerald Combs:
Qt: Fix simple_dialog formatting.

https://code.wireshark.org/review/18992

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13178] HTML escaping of quotes in error message

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13178

Gerrit Code Review  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13178] HTML escaping of quotes in error message

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13178

--- Comment #5 from Gerrit Code Review  ---
Change 18985 merged by Gerald Combs:
Qt: Fix simple_dialog formatting.

https://code.wireshark.org/review/18985

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13192] New: tshark doesn't respect protocols.display_hidden_proto_items setting

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13192

Bug ID: 13192
   Summary: tshark doesn't respect
protocols.display_hidden_proto_items setting
   Product: Wireshark
   Version: Git
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: Normal
  Priority: Low
 Component: TShark
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: jaap.keu...@xs4all.nl

Build Information:
TShark (Wireshark) 2.3.0 (v2.3.0rc0-1581-g7fe45cc)

Copyright 1998-2016 Gerald Combs  and contributors.
License GPLv2+: GNU GPL version 2 or later

This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with libpcap, with POSIX capabilities (Linux), with libnl 3,
with GLib 2.50.2, with zlib 1.2.8, with SMI 0.4.8, with c-ares 1.12.0, with Lua
5.2.4, with GnuTLS 3.5.6, with Gcrypt 1.7.3-beta, with MIT Kerberos, with
GeoIP,
without nghttp2, without LZ4, without Snappy.

Running on Linux 4.8.0-1-amd64, with Intel(R) Core(TM)2 Duo CPU E6850  @
3.00GHz, with 3955 MB of physical memory, with locale C, with libpcap version
1.8.1, with GnuTLS 3.5.6, with Gcrypt 1.7.3-beta, with zlib 1.2.8.

Built using gcc 6.2.0 20161109.
--
When running tshark, either with -V -o
protocols.display_hidden_proto_items:true or the respective setting in
~/.wireshark/preferences, doesn't show the hidden items.
Any TCP or UDP packet should show this.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13191] Malformed Packet - SSL

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13191

tzahpahima...@gmail.com changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13191] New: Malformed Packet - SSL

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13191

Bug ID: 13191
   Summary: Malformed Packet - SSL
   Product: Wireshark
   Version: unspecified
  Hardware: All
OS: All
Status: UNCONFIRMED
  Severity: Major
  Priority: Low
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: tzahpahima...@gmail.com

Created attachment 15094
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15094&action=edit
Pcap file showing malformed SSL analyzed

Build Information:
MITM setup (so repeating packets)
--
In a mitm setup, wireshark informs of an exception occuring in SSL malformed?
packet

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13174] Export Objects dialog in GTK crashes due to wrong memory scope

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13174

--- Comment #5 from Pascal Quantin  ---
SHould not another bug be opened for the Gt GUI instead?

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13174] Export Objects dialog in GTK crashes due to wrong memory scope

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13174

--- Comment #4 from Michael Mann  ---
(In reply to Pascal Quantin from comment #3)
> Michael, as your patch has been merged, is there more work needed for GTK UI?

The merged patch fixes 2.2 branch, https://code.wireshark.org/review/18927 will
fix the master branch.

But I was going to hold this bug open for confirmation that a memory leak
doesn't exist in the Qt GUI.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13189] Exception closing http exported objects window

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13189

--- Comment #2 from David  ---
Hi Pascal.

Thanks for the update, I was trying to find it in the database but I couldn't.
Good to know that is solved now :)

Thanks!!

David

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13174] Export Objects dialog in GTK crashes due to wrong memory scope

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13174

Pascal Quantin  changed:

   What|Removed |Added

 CC||pascal.quan...@gmail.com

--- Comment #3 from Pascal Quantin  ---
Michael, as your patch has been merged, is there more work needed for GTK UI?

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13174] Export Objects dialog in GTK crashes due to wrong memory scope

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13174

Pascal Quantin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13174] Export Objects dialog in GTK crashes due to wrong memory scope

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13174

Pascal Quantin  changed:

   What|Removed |Added

 CC||david.cristo...@gmail.com

--- Comment #2 from Pascal Quantin  ---
*** Bug 13189 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13189] Exception closing http exported objects window

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13189

Pascal Quantin  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||pascal.quan...@gmail.com
 Resolution|--- |DUPLICATE

--- Comment #1 from Pascal Quantin  ---


*** This bug has been marked as a duplicate of bug 13174 ***

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13190] Add timestamp option to extcap

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13190

Dario Lombardo  changed:

   What|Removed |Added

   Priority|Low |Medium
   Severity|Major   |Enhancement

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13190] Add timestamp option to extcap

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13190

--- Comment #1 from Peter Wu  ---
Copying comments from a related patch https://code.wireshark.org/review/18721 :

What about using timestamps with greater precision?

See https://doc.qt.io/qt-5/qdatetime.html#fromMSecsSinceEpoch
The timestamp seems to be implied to be UTC, is that desired?

Can we learn something from the nstime APIs for choosing an appropriate format?
Note that even if we decide to accept (say) a floating point number as
argument, the internal storage can be different (time_t, guint64, etc.).

(Another option is to store a string like RFC 3339-style "2006-08-14
02:34:56-06:00" or ISO 8601-style "2006-08-14T02:34:56-0600" which might be
prettier for humans. Leap seconds/hours could be problematic for this though.)

Simone, could you clarify your use case for ntop?

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 12787] Extcaps hang when launched from windows console

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=12787

Dario Lombardo  changed:

   What|Removed |Added

   Priority|Low |Medium
   Severity|Normal  |Enhancement

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13190] Add timestamp option to extcap

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13190

Dario Lombardo  changed:

   What|Removed |Added

 CC||maina...@ntop.org,
   ||pe...@lekensteyn.nl,
   ||rkn...@gmail.com

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13190] New: Add timestamp option to extcap

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13190

Bug ID: 13190
   Summary: Add timestamp option to extcap
   Product: Wireshark
   Version: Git
  Hardware: x86
OS: All
Status: UNCONFIRMED
  Severity: Major
  Priority: Low
 Component: Extras
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: lom...@gmail.com

Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
A new option type for timestamp is required to allow the user to pass
timestamps (taken from a calendar dialog) to extcaps.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13189] New: Exception closing http exported objects window

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13189

Bug ID: 13189
   Summary: Exception closing http exported objects window
   Product: Wireshark
   Version: 2.2.2
  Hardware: x86
OS: Windows NT
Status: UNCONFIRMED
  Severity: Major
  Priority: Low
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: david.cristo...@gmail.com

Build Information:
Version 2.2.2 (v2.2.2-0-g775fb08)

Copyright 1998-2016 Gerald Combs  and contributors.
License GPLv2+: GNU GPL version 2 or later

This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with GTK+ 2.24.23, with Cairo 1.12.16, with Pango 1.36.8,
with
WinPcap (4_1_3), with GLib 2.42.0, with zlib 1.2.8, with SMI 0.4.8, with c-ares
1.12.0, with Lua 5.2.4, with GnuTLS 3.2.15, with Gcrypt 1.6.2, with MIT
Kerberos, with GeoIP, with PortAudio V19-devel (built Nov 16 2016), with
AirPcap.

Running on 64-bit Windows 10, build 10240, with locale English_United
States.1252, with WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based
on libpcap version 1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with
Gcrypt 1.6.2, without AirPcap.
   Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz (with SSE4.2), with 8072MB of
physical memory.


Built using Microsoft Visual C++ 12.0 build 40629

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
I have a consistent issue when I close the window from the exported http
objects. 

Reproducible 100% in my computer (and other 2 virtual machines). Just File,
Export http objects, and then close that window.

Looking at the stack in WinBbg looks like a corruption releasing memory:

 # Child-SP Return   Call Site
 0 008e0521e588 7ffb26e8ac6e libwireshark!wmem_realloc+0x86f
 1 008e0521e590 7ffb26e8a9d9 libwireshark!wmem_realloc+0x5de
 2 008e0521e5c0 7ffb26e8a513 libwireshark!wmem_realloc+0x349
 3 008e0521e5f0 7ff727bf0401 libwireshark!wmem_free+0x63
 4 008e0521e630 63a45f3f Wireshark+0xb0401
 5 008e0521e660 63a565f3 libgobject_2_0_0!g_closure_invoke+0x12f
 6 008e0521e700 63a5d559
libgobject_2_0_0!g_signal_handler_disconnect+0x1e23
 7 008e0521e850 63a5d758
libgobject_2_0_0!g_signal_emit_valist+0xad9
 8 008e0521e9f0 6186d243 libgobject_2_0_0!g_signal_emit+0x18
 9 008e0521ea30 63a4bba5
libgtk_win32_2_0_0!gtk_notebook_set_action_widget+0x483
 a 008e0521ea60 7ff727b677da libgobject_2_0_0!g_object_run_dispose+0x35
 b 008e0521ea90 63a46169 Wireshark+0x277da


Last call to reallocate memory is this:
0:000> .frame /r 0x0; !mex.x
00 008e`0521e588 7ffb`26e8ac6e libwireshark!wmem_realloc+0x86f
rax=31223d6e6f697372 rbx= rcx=6576206c6d783f3c
rdx=008e0af7d890 rsi=008e12f1d8a0 rdi=008e0af7d8a0
rip=7ffb26e8aeff rsp=008e0521e588 rbp=
 r8=008e0701db80  r9=008e0af7d890 r10=008e0af7d890
r11=008e0701db80 r12=0001 r13=008e0521e880
r14=008e0521e7e0 r15=
iopl=0 nv up ei pl nz na po nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b efl=00010204
libwireshark!wmem_realloc+0x86f:
7ffb`26e8aeff 48894118mov qword ptr [rcx+18h],rax
ds:6576206c`6d783f54=

Looks like the memory is corrupt (I cannot go further on this, my knowledge is
limited)

Dump available here: 
https://citrite.sharefile.com/d-s8aff39f4c1547688

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13175] Runtime Error when try to merge .pcap files (Wireshark crashes)

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13175

--- Comment #21 from Pascal Quantin  ---
Nigel, did you have the opportunity to try the test release from comment #15? I
cannot be sure your issue is resolved unless you test it.

Thanks,
Pascal.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13188] bcp_bpdu size reports not header size, but all data underneath and its header size in UI

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13188

--- Comment #1 from Jaap Keuter  ---
If you can attach the actual capture instead of a partial screenshot, then
there's data to work with and verify a possible fix. Use TraceWrangler to
obfuscate the capture if you like.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11420] Wire Shark Not Capturing register, invite , 200 ok , bye etc which i can see in tcpdump

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11420

Gerrit Code Review  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11420] Wire Shark Not Capturing register, invite , 200 ok , bye etc which i can see in tcpdump

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11420

--- Comment #7 from Gerrit Code Review  ---
Change 18989 merged by Anders Broman:
sip: register with Websocket dissector (RFC 7118)

https://code.wireshark.org/review/18989

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13185] Wireshark doesn't decrypt 802.11 data packets

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13185

--- Comment #5 from mathiasb...@arcor.de ---
Hi,

you can close this ticket, i have checked this another time, the packets are
decrypted, but I was irritated that the EAPOL key wasn't decrypted. In the last
version I have see the ip-addresses.

SSID: WLAN_53B2CE
password: 

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 11420] Wire Shark Not Capturing register, invite , 200 ok , bye etc which i can see in tcpdump

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11420

--- Comment #6 from Gerrit Code Review  ---
Change 18989 had a related patch set uploaded by Peter Wu:
sip: register with Websocket dissector (RFC 7118)

https://code.wireshark.org/review/18989

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13188] New: bcp_bpdu size reports not header size, but all data underneath and its header size in UI

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13188

Bug ID: 13188
   Summary: bcp_bpdu size reports not header size, but all data
underneath and its header size in UI
   Product: Wireshark
   Version: 2.2.2
  Hardware: x86-64
OS: Windows 7
Status: UNCONFIRMED
  Severity: Minor
  Priority: Low
 Component: GTK+ UI
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: jo...@johandenoyer.fr

Created attachment 15093
  --> https://bugs.wireshark.org/bugzilla/attachment.cgi?id=15093&action=edit
capture

Build Information:
Copyright 1998-2016 Gerald Combs  and contributors.
License GPLv2+: GNU GPL version 2 or later

This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with Qt 5.6.1, with WinPcap (4_1_3), with GLib 2.42.0, with
zlib 1.2.8, with SMI 0.4.8, with c-ares 1.12.0, with Lua 5.2.4, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale
French_France.1252, with WinPcap version 4.1.3 (packet.dll version 0.10 r9),
based on libpcap version 1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15,
with Gcrypt 1.6.2, without AirPcap.
Intel(R) Core(TM) i5-4310U CPU @ 2.00GHz (with SSE4.2), with 8097MB of physical
memory.


Built using Microsoft Visual C++ 12.0 build 40629
--
When selecting the PPP Bridging Control Protocol Bridged PDU, it should show
only the header size. Here it returns the header size and the size of all data
underneath.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13187] New: Buildbot crash output: fuzz-2016-11-30-31444.pcap

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13187

Bug ID: 13187
   Summary: Buildbot crash output: fuzz-2016-11-30-31444.pcap
   Product: Wireshark
   Version: unspecified
  Hardware: x86-64
   URL: https://www.wireshark.org/download/automated/captures/
fuzz-2016-11-30-31444.pcap
OS: Ubuntu
Status: CONFIRMED
  Severity: Major
  Priority: High
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: buildbot-do-not-re...@wireshark.org

Problems have been found with the following capture file:

https://www.wireshark.org/download/automated/captures/fuzz-2016-11-30-31444.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/11275-cops-fuzz-test.pcap

Build host information:
Linux wsbb04 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename:xenial

Buildbot information:
BUILDBOT_REPOSITORY=ssh://wireshark-build...@code.wireshark.org:29418/wireshark
BUILDBOT_WORKERNAME=clang-code-analysis
BUILDBOT_BUILDNUMBER=3800
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-master/
BUILDBOT_BUILDERNAME=Clang Code Analysis
BUILDBOT_GOT_REVISION=7fe45cc0ec4e8bc1c3d5cd27c98feb8ecbb2b1b4

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit 7fe45cc0ec4e8bc1c3d5cd27c98feb8ecbb2b1b4
Author: Peter Wu 
Date:   Wed Nov 23 16:28:34 2016 +0100

Qt: fix GoToPacket when Voip Calls dialog is closed

After opening the Call Flows dialog from the Voip Calls dialog, followed
by closing the Voip Calls dialog, the Go To Packet functionality in the
Call Flows dialog is broken. That happens because the signal is not
proxied anymore.

Just remove all these indirections via signals and directly update the
selected packet.

Change-Id: I9c6d519dbe800e4dfdf0407d832f17819b344e46
Reviewed-on: https://code.wireshark.org/review/18933
Petri-Dish: Peter Wu 
Tested-by: Petri Dish Buildbot 
Reviewed-by: Gerald Combs 


==16247== Memcheck, a memory error detector
==16247== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==16247== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==16247== Command:
/home/wireshark/builders/wireshark-master-fuzz/clangcodeanalysis/install.plain/bin/tshark
-nr /fuzz/buildbot/clangcodeanalysis/valgrind-fuzz/fuzz-2016-11-30-31444.pcap
==16247== 
==16247== Conditional jump or move depends on uninitialised value(s)
==16247==at 0x6B9C8F4: dissect_cops_pdu (packet-cops.c:1102)
==16247==by 0x718E655: tcp_dissect_pdus (packet-tcp.c:3468)
==16247==by 0x6B9B2C1: dissect_cops (packet-cops.c:1134)
==16247==by 0x69ACDB5: call_dissector_through_handle (packet.c:650)
==16247==by 0x69ACDB5: call_dissector_work (packet.c:725)
==16247==by 0x69ACC7E: dissector_try_uint_new (packet.c:1290)
==16247==by 0x718EB6F: decode_tcp_ports (packet-tcp.c:5420)
==16247==by 0x718FE8F: process_tcp_payload (packet-tcp.c:5483)
==16247==by 0x718F3E8: desegment_tcp (packet-tcp.c:2990)
==16247==by 0x718F3E8: dissect_tcp_payload (packet-tcp.c:5550)
==16247==by 0x7193E57: dissect_tcp (packet-tcp.c:6434)
==16247==by 0x69ACDB5: call_dissector_through_handle (packet.c:650)
==16247==by 0x69ACDB5: call_dissector_work (packet.c:725)
==16247==by 0x69ACC7E: dissector_try_uint_new (packet.c:1290)
==16247==by 0x6DDD922: ip_try_dissect (packet-ip.c:1978)
==16247==by 0x6DDD922: dissect_ip_v4 (packet-ip.c:2441)
==16247== 
==16247== 
==16247== HEAP SUMMARY:
==16247== in use at exit: 6,085,520 bytes in 9,731 blocks
==16247==   total heap usage: 266,061 allocs, 256,330 frees, 37,344,896 bytes
allocated
==16247== 
==16247== LEAK SUMMARY:
==16247==definitely lost: 456 bytes in 90 blocks
==16247==indirectly lost: 384 bytes in 3 blocks
==16247==  possibly lost: 0 bytes in 0 blocks
==16247==still reachable: 6,084,680 bytes in 9,638 blocks
==16247== suppressed: 0 bytes in 0 blocks
==16247== Rerun with --leak-check=full to see details of leaked memory
==16247== 
==16247== For counts of detected and suppressed errors, rerun with: -v
==16247== Use --track-origins=yes to see where uninitialised values come from
==16247== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

[ no debug trace ]

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13186] New: Buildbot crash output: fuzz-2016-11-28-2043.pcap

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13186

Bug ID: 13186
   Summary: Buildbot crash output: fuzz-2016-11-28-2043.pcap
   Product: Wireshark
   Version: unspecified
  Hardware: x86-64
   URL: https://www.wireshark.org/download/automated/captures/
fuzz-2016-11-28-2043.pcap
OS: Ubuntu
Status: CONFIRMED
  Severity: Major
  Priority: High
 Component: Dissection engine (libwireshark)
  Assignee: bugzilla-ad...@wireshark.org
  Reporter: buildbot-do-not-re...@wireshark.org

Problems have been found with the following capture file:

https://www.wireshark.org/download/automated/captures/fuzz-2016-11-28-2043.pcap

stderr:
Input file: /home/wireshark/menagerie/menagerie/SMB-locking.pcapng.gz

Build host information:
Linux wsbb04 4.4.0-47-generic #68-Ubuntu SMP Wed Oct 26 19:39:52 UTC 2016
x86_64 x86_64 x86_64 GNU/Linux
Distributor ID:Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename:xenial

Buildbot information:
BUILDBOT_REPOSITORY=ssh://wireshark-build...@code.wireshark.org:29418/wireshark
BUILDBOT_WORKERNAME=fuzz-test
BUILDBOT_BUILDNUMBER=233
BUILDBOT_URL=http://buildbot.wireshark.org/wireshark-2.0/
BUILDBOT_BUILDERNAME=Fuzz Test
BUILDBOT_GOT_REVISION=0eed3601fd0cde339591f261c5691d657074630c

Return value:  0

Dissector bug:  0

Valgrind error count:  1



Git commit
commit 0eed3601fd0cde339591f261c5691d657074630c
Author: Gerald Combs 
Date:   Sun Nov 27 08:33:42 2016 -0800

[Automatic update for 2016-11-27]

Update manuf, services enterprise-numbers, translations, and other items.

Change-Id: Iec2b567d085a733aab43fc54bc54785315a76faa
Reviewed-on: https://code.wireshark.org/review/18966
Reviewed-by: Gerald Combs 


Command and args: ./tools/valgrind-wireshark.sh 

==15082== Memcheck, a memory error detector
==15082== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==15082== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==15082== Command:
/home/wireshark/builders/wireshark-2.0-fuzz/fuzztest/install/bin/tshark -nr
/fuzz/buildbot/fuzztest/valgrind-fuzz-2.0/fuzz-2016-11-28-2043.pcap
==15082== 
==15082== 
==15082== HEAP SUMMARY:
==15082== in use at exit: 1,098,121 bytes in 32,298 blocks
==15082==   total heap usage: 7,508,261 allocs, 7,475,963 frees, 400,580,810
bytes allocated
==15082== 
==15082== LEAK SUMMARY:
==15082==definitely lost: 36,892 bytes in 2,249 blocks
==15082==indirectly lost: 65,552 bytes in 1,867 blocks
==15082==  possibly lost: 0 bytes in 0 blocks
==15082==still reachable: 995,677 bytes in 28,182 blocks
==15082== suppressed: 0 bytes in 0 blocks
==15082== Rerun with --leak-check=full to see details of leaked memory
==15082== 
==15082== For counts of detected and suppressed errors, rerun with: -v
==15082== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 1 from 1)

[ no debug trace ]

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13182] Differentiate in pcapng info if dumpcap was launched manually or through Wireshark GUI

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13182

Guy Harris  changed:

   What|Removed |Added

  Component|Dissection engine   |Extras
   |(libwireshark)  |
   Hardware|x86 |All
 OS|macOS 10.12 |All
   Severity|Normal  |Enhancement

--- Comment #2 from Guy Harris  ---
(In reply to Alexis La Goutte from comment #1)
> No because it is always captured by dumpcap (and no Wireshark !)

But we could have Wireshark (and TShark) run dumpcap with a command-line option
indicating what program ran dumpcap, and dumpcap could use that in the SHB or
IDB.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13183] Qt: drag & drop of one column header in PacketList moves other columns

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13183

Jim Young  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 CC||jyo...@gsu.edu
Summary|On macOS, drag & drop of|Qt: drag & drop of one
   |Length column moves both|column header in PacketList
   |Protocol & Length cols  |moves other columns
 Ever confirmed|0   |1
 OS|macOS 10.12 |All

--- Comment #2 from Jim Young  ---
PacketList columns can be reordered using drag-and-drop using two different
methods:

1 - drag-and-drop a column header directly on the PacketList

2 - drag-and-drop a column entry in the "Column Preferences" dialog. 

This bug concern the first method.  Dragging a column header left or right will
sometimes result in other columns to unexpectedly move.

This PacketList column header drag and drop issue can be easily replicated
using latest master on Linux, Windows and macOS/OS X.

Start with a default gui.column.format preference entry:


> # Packet list column format
> # Each pair of strings consists of a column title and its format
> #gui.column.format: 
> # "No.", "%m",
> # "Time", "%t",
> # "Source", "%s",
> # "Destination", "%d",
> # "Protocol", "%p",
> # "Length", "%L",
> # "Info", "%i"


After following Thomas's example of simply dragging the "Length" column (which
is initially the 6th column) to the left and dropping it on top of the "Time"
column, the display will be updated to show the "Protocol" column as the 3rd
column and the "Length" column to be the 4th column.

After the drag-and-drop event the "gui.column.format" entry within the current
profile's preferences file will be immediately updated but will only show that
the "Length" column was moved:


> # Packet list column format
> # Each pair of strings consists of a column title and its format
> gui.column.format: 
>   "No.", "%m",
>   "Time", "%t",
>   "Length", "%L",
>   "Source", "%s",
>   "Destination", "%d",
>   "Protocol", "%p",
>   "Info", "%i"


The state of this updated "gui.column.format;" preference is reflected by the
order of the columns shown in the PacketList header's right-mouse click context
menu and also from within the "Column Preferences" dialog.  But the
PacketList's actual column order is different.

At this point if Wireshark is simply shutdown and restarted and a the trace
reopened, the PacketList columns will display in the desired configured order,
in this case with "Length" as the 3rd column and "Protocol" as the 6th column.

One can sometimes get the intended PacketList column order using several
PacketList drag-and-drops but when Wireshark is shutdown and restarted the
column order might NOT be what was last seen.

Workaound:  Use the drag-and-drop feature from within the "Column Preferences"
dialog to change the PacketList column order.

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13182] Differentiate in pcapng info if dumpcap was launched manually or through Wireshark GUI

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13182

Alexis La Goutte  changed:

   What|Removed |Added

 CC||alexis.lagou...@gmail.com

--- Comment #1 from Alexis La Goutte  ---
No because it is always captured by dumpcap (and no Wireshark !)

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe

[Wireshark-bugs] [Bug 13185] Wireshark doesn't decrypt 802.11 data packets

2016-11-30 Thread bugzilla-daemon
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13185

--- Comment #4 from Alexis La Goutte  ---
and the key ?

-- 
You are receiving this mail because:
You are watching all bug changes.
___
Sent via:Wireshark-bugs mailing list 
Archives:https://www.wireshark.org/lists/wireshark-bugs
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-bugs
 mailto:wireshark-bugs-requ...@wireshark.org?subject=unsubscribe