https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16771
Bug ID: 16771
Summary: dicom object extraction: discrepancy between tshark
and wireshark
Product: Wireshark
Version: 3.2.3
Hardware: x86
OS: Windows
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9069
--- Comment #4 from Gerrit Code Review ---
Change 38076 merged by Anders Broman:
packet_xml: detect and handle UTF-16 BOM
https://code.wireshark.org/review/38076
--
You are receiving this mail because:
You are watching all bug
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16772
Bug ID: 16772
Summary: EPL: timestamp format in error code list
Product: Wireshark
Version: unspecified
Hardware: All
OS: All
Status: UNCONFIRMED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16772
christian.kr...@br-automation.com changed:
What|Removed |Added
Ever confirmed|0 |1
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=9069
David Perry changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16772
--- Comment #1 from Gerrit Code Review ---
Change 38142 had a related patch set uploaded by Christian Krump:
EPL: modified timestamp format of errorcodelist
https://code.wireshark.org/review/38142
--
You are receiving this mail
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16760
--- Comment #2 from Anders Broman ---
The strategy of abusing the people who offer their spare time to work on this
project seems a bit contra productive if you want them to fix something in the
code in my humble opinion.
--
You are
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16772
--- Comment #2 from Gerrit Code Review ---
Change 38142 merged by Anders Broman:
EPL: modified timestamp format of errorcodelist
https://code.wireshark.org/review/38142
--
You are receiving this mail because:
You are watching all bug
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16773
--- Comment #2 from Amit ---
(In reply to Anders Broman from comment #1)
> That is an ancient version of Wireshark I think it will work on a more
> recent version. Can you try?
Wireshark v3.2.3 release notes are dated April-2020. That
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16773
--- Comment #3 from Amit ---
(In reply to Amit from comment #2)
> (In reply to Anders Broman from comment #1)
> > That is an ancient version of Wireshark I think it will work on a more
> > recent version. Can you try?
>
> Wireshark
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16773
Bug ID: 16773
Summary: tshark filtering with SCTP segmentation not working
Product: Wireshark
Version: 3.2.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16773
Amit changed:
What|Removed |Added
Priority|Low |High
--
You are receiving this mail
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16773
--- Comment #1 from Anders Broman ---
That is an ancient version of Wireshark I think it will work on a more recent
version. Can you try?
--
You are receiving this mail because:
You are watching all bug
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16773
--- Comment #4 from Amit ---
(In reply to Anders Broman from comment #1)
> That is an ancient version of Wireshark I think it will work on a more
> recent version. Can you try?
I double checked this. I mentioned the wrong tshark version
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16772
christian.kr...@br-automation.com changed:
What|Removed |Added
Status|IN_PROGRESS |RESOLVED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13207
--- Comment #31 from Jaap Keuter ---
Hi Richard, I assume this is still pending...?
--
You are receiving this mail because:
You are watching all bug changes.___
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13769
--- Comment #14 from Jaap Keuter ---
Again, what are we doing with this bug? Close this and open new issues later?
--
You are receiving this mail because:
You are watching all bug
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13540
--- Comment #17 from Christopher Maynard ---
(In reply to Jaap Keuter from comment #16)
> Pending the remaining issue of positioning the added column, is there the
> intention of implementing this or should this bug be closed since the
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16771
--- Comment #2 from Chuck Craft ---
pcap here:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16748
And resulting file names for tshark --export-objects:
tshark 3.0.12
-
3_0_12/000453-1-C-STORE-RQ-DATA.dcm
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13540
--- Comment #16 from Jaap Keuter ---
Pending the remaining issue of positioning the added column, is there the
intention of implementing this or should this bug be closed since the main
issues are resolved?
--
You are receiving this
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13585
Jaap Keuter changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13906
Jaap Keuter changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14609
--- Comment #9 from Jaap Keuter ---
Jim, what's your current take on this issue? Is it still present, or can this
no longer be reproduced with current versions of Wireshark?
--
You are receiving this mail because:
You are watching all
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13207
--- Comment #32 from Richard Sharpe ---
(In reply to Jaap Keuter from comment #31)
> Hi Richard, I assume this is still pending...?
I will try to add what I have this weekend.
--
You are receiving this mail because:
You are watching
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14433
--- Comment #6 from Jaap Keuter ---
Peter, what is the status here? Can we close this, or is there still more work?
--
You are receiving this mail because:
You are watching all bug
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14659
--- Comment #15 from Jaap Keuter ---
With the original issue resolved, can we close this bug and move the field
renaming question to a new issue?
--
You are receiving this mail because:
You are watching all bug
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15010
--- Comment #15 from Guy Harris ---
(In reply to Jaap Keuter from comment #14)
> Guy, is there more to be done than waiting/hoping for the Npcap issues to be
> fixed?
Nope. Those may be hard to fix - and it's not clear whether Microsoft
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15010
--- Comment #16 from Jaap Keuter ---
Then we might close this as notourbug.
--
You are receiving this mail because:
You are watching all bug changes.___
Sent via:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13122
Jaap Keuter changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13766
Jaap Keuter changed:
What|Removed |Added
Status|IN_PROGRESS |RESOLVED
Resolution|---
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14621
--- Comment #16 from Jaap Keuter ---
What's the status of this bug? The last comment on the commit was:
Paul Zander May 9, 2018
Patch Set 6:
I will make it configurable.
The default
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15010
--- Comment #14 from Jaap Keuter ---
Guy, is there more to be done than waiting/hoping for the Npcap issues to be
fixed?
--
You are receiving this mail because:
You are watching all bug
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16771
Chuck Craft changed:
What|Removed |Added
CC||bubbas...@gmail.com
--- Comment #1
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=14141
Jaap Keuter changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=15010
Guy Harris changed:
What|Removed |Added
Resolution|--- |NOTOURBUG
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13213
Jaap Keuter changed:
What|Removed |Added
Resolution|--- |FIXED
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16672
Gerald Combs changed:
What|Removed |Added
See Also||http://cve.mitre.org/cgi-bi
37 matches
Mail list logo