Re: [Wireshark-users] [Wireshark-dev] The Wireshark wiki has a new home
On Aug 12, 2020, at 12:44 PM, Roland Knall wrote: > I agree that this is not ideal. I would opt for a second project. MoinMoin is > really not good anymore from an op-sec point of view ...and my MediaWiki-trained brain hurts every time I edit it. Markdown may also not be the same as MediaWiki markup, but I'm also using it for the GitHub-based libpcap and tcpdump projects' issue and pull request lists, so my brain may hurt less when using it. ___ Sent via:Wireshark-users mailing list Archives:https://www.wireshark.org/lists/wireshark-users Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe
[Wireshark-users] Wireshark 3.0.13 is now available
I'm proud to announce the release of Wireshark 3.0.13. What is Wireshark? Wireshark is the world’s most popular network protocol analyzer. It is used for troubleshooting, analysis, development and education. What’s New Bug Fixes The following vulnerabilities have been fixed: The following bugs have been fixed: • Dissector for ASTERIX Category 001 / 210 does not recognize bit 1 as extension. Bug 16662[1]. • "invalid timestamp" for Systemd Journal Export Block. Bug 16664[2]. • Short IMSIs (5 digits) lead to wrong decoding+warning. Bug 16676[3]. • Decoding of PFCP IE 'PFD Contents' results in "malformed packet". Bug 16704[4]. • RFH2 Header with 32 or less bytes of NameValue will not parse out that info. Bug 16733[5]. • CDP: Port ID TLV followed by Type 1009 TLV triggers [Malformed Packet]. Bug 16742[6]. • tshark crashed when processing opcda. Bug 16746[7]. • tshark with --export-dicom gives “Segmentation fault (core dumped)”. Bug 16748[8]. New and Updated Features There are no new features in this release. New Protocol Support There are no new protocols in this release. Updated Protocol Support ASTERIX, BSSAP, CDP, DCERPC SPOOLSS, DCOM, DVB-S2, E.212, GBCS, GSM RR, GSM SMS, IEEE 802.11, MQ, Nano, NIS+, PFCP, RTPS, systemd Journal, TDS, TN3270, and TN5250 New and Updated Capture File Support There is no new or updated capture file support in this release. New and Updated Capture Interfaces support pcapng Getting Wireshark Wireshark source code and installation packages are available from https://www.wireshark.org/download.html. Vendor-supplied Packages Most Linux and Unix vendors supply their own Wireshark packages. You can usually install or upgrade Wireshark using the package management system specific to that platform. A list of third-party packages can be found on the download page[9] on the Wireshark web site. File Locations Wireshark and TShark look in several different locations for preference files, plugins, SNMP MIBS, and RADIUS dictionaries. These locations vary from platform to platform. You can use About→Folders to find the default locations on your system. Getting Help The User’s Guide, manual pages and various other documentation can be found at https://www.wireshark.org/docs/ Community support is available on Wireshark’s Q site[10] and on the wireshark-users mailing list. Subscription information and archives for all of Wireshark’s mailing lists can be found on the web site[11]. Bugs and feature requests can be reported on the bug tracker[12]. Frequently Asked Questions A complete FAQ is available on the Wireshark web site[13]. Last updated 2020-08-12 17:56:01 UTC References 1. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16662 2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16664 3. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16676 4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16704 5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16733 6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16742 7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16746 8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16748 9. https://www.wireshark.org/download.html#thirdparty 10. https://ask.wireshark.org/ 11. https://www.wireshark.org/lists/ 12. https://bugs.wireshark.org/ 13. https://www.wireshark.org/faq.html Digests wireshark-3.0.13.tar.xz: 30928312 bytes SHA256(wireshark-3.0.13.tar.xz)=0463b0f424d0962933ae681b3d5580780906c02f08a3ab852b787999b2884c47 RIPEMD160(wireshark-3.0.13.tar.xz)=33653c23fc4ac5ce1d28e926d642a86237ed1573 SHA1(wireshark-3.0.13.tar.xz)=3f5a418cdd0f4ab6dd7b95d3ca8f1a0e85af9927 Wireshark-win64-3.0.13.exe: 59297592 bytes SHA256(Wireshark-win64-3.0.13.exe)=d9bf4bc656264d8b1e10a79c9d8d3edc112c218c39816e228bf3f882e5b5d32e RIPEMD160(Wireshark-win64-3.0.13.exe)=a5f0f0349001e46bd9b6bcc6fc1b91e785759517 SHA1(Wireshark-win64-3.0.13.exe)=9a473cd682547cd1d1860c6eb3dff00f4bbef769 Wireshark-win32-3.0.13.exe: 54085432 bytes SHA256(Wireshark-win32-3.0.13.exe)=1c61fe5ec90f20319d7b46e115c84d0a541a079ba8d1dae0303833f64a8da458 RIPEMD160(Wireshark-win32-3.0.13.exe)=d0a6cf8f5b933f78650de0da8ee3165f20c3afea SHA1(Wireshark-win32-3.0.13.exe)=625df6bd716a3a0c6ae26d3d872c00ccb3374ea2 Wireshark-win32-3.0.13.msi: 42082304 bytes SHA256(Wireshark-win32-3.0.13.msi)=11ea61c4ff1281b838de80309f82c38dc515216d245463b9d87b5857a50c0208 RIPEMD160(Wireshark-win32-3.0.13.msi)=1161abbf5ea69f64dc4c2e8a62098e80cb58 SHA1(Wireshark-win32-3.0.13.msi)=8ba6a500d0ec8ae6edc1fa02343a9bfa8a8b58d9 Wireshark-win64-3.0.13.msi: 47288320 bytes SHA256(Wireshark-win64-3.0.13.msi)=e411cbb6fe20432f8e686713fccb61f9e18ec7a1d2cce329dd8bcd916ba4ac21 RIPEMD160(Wireshark-win64-3.0.13.msi)=243659938004f15c16b830b3d2ff29f2490b1196
Re: [Wireshark-users] [Wireshark-dev] The Wireshark wiki has a new home
I agree that this is not ideal. I would opt for a second project. MoinMoin is really not good anymore from an op-sec point of view Cheers Roland > Am 12.08.2020 um 21:18 schrieb Gerald Combs : > > On 8/12/20 7:51 AM, Maynard, Chris via Wireshark-users wrote: >>> -Original Message- >>> From: Wireshark-dev On Behalf >>> Of Guy Harris >>> Sent: Tuesday, August 11, 2020 11:52 PM >>> To: Developer support list for Wireshark >>> Cc: Community support list for Wireshark >>> Subject: Re: [Wireshark-dev] The Wireshark wiki has a new home >>> On Aug 11, 2020, at 5:18 PM, Gerald Combs wrote: >>> As part of our larger GitLab migration effort I've migrated the Wireshark >>> wiki to its new home at https://gitlab.com/wireshark/wireshark/-/wikis/home There's still a fair amount of post-migration work to do (for instance the >>> "HowToEdit" is specific to our old wiki), but the new wiki should be faster >>> and >>> easier to edit, particularly if you're familiar with Markdown. >>> >>> So how do we edit a Wiki page? I'm logged into my gitlab.com account, but I >>> don't see, for example, an "Edit" button. >> >> Same. *Maybe* this is because Gerald is the only member of the project so >> far? >> https://gitlab.com/wireshark/wireshark/-/project_members > > Well, this stinks. I managed to overlook the fact that wiki editing requires > Developer permissions, which means that editing the wiki requires the same > rights as accepting merge requests and creating new branches: > > https://gitlab.com/help/user/permissions > > This is fine for core developers, but not so great for other people that > currently have editor permissions. Other people have the same problem, but I > don't see any indication that this will be fixed any time soon: > > https://gitlab.com/gitlab-org/gitlab/-/issues/25177 > https://gitlab.com/gitlab-org/gitlab/-/issues/27294 > https://gitlab.com/gitlab-org/gitlab/-/issues/15504 > > > We have a few options in the mean time: > > * Switch back to MoinMoin / wiki.wireshark.org and let it continue to bit-rot. > > * Switch back to MoinMoin, find some other wiki software, and migrate to it. > > * Create a separate, public wiki-only gitlab.com/wireshark/wireshark-wiki > project, and grant Developer permissions to anyone that wants to contribute. > > * Create a separate, possibly-private wiki-only > gitlab.com/wireshark/wireshark-wiki-backend project, grant Developer > permissions to anyone that wants to contribute, and mirror it to the main > project wiki. > > * Some other variation of the previous two items? > ___ > Sent via:Wireshark-dev mailing list > Archives:https://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-users mailing list Archives:https://www.wireshark.org/lists/wireshark-users Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe
[Wireshark-users] Wireshark 3.2.6 is now available
I'm proud to announce the release of Wireshark 3.2.6. What is Wireshark? Wireshark is the world’s most popular network protocol analyzer. It is used for troubleshooting, analysis, development and education. What’s New Bug Fixes The following vulnerabilities have been fixed: • wnpa-sec-2020-10[1] Kafka dissector crash. Bug 16672[2]. CVE-2020-17498[3]. The following bugs have been fixed: • Kafka dissector fails parsing FETCH responses. Bug 16623[4]. • Dissector for ASTERIX Category 001 / 210 does not recognize bit 1 as extension. Bug 16662[5]. • "invalid timestamp" for Systemd Journal Export Block. Bug 16664[6]. • Decoding Extended Emergency number list IE length. Bug 16668[7]. • Some macOS Bluetooth PacketLogger capture files aren’t recognized as PacketLogger files (regression, bisected). Bug 16670[8]. • Short IMSIs (5 digits) lead to wrong decoding+warning. Bug 16676[9]. • Decoding of PFCP IE 'PFD Contents' results in "malformed packet". Bug 16704[10]. • RFH2 Header with 32 or less bytes of NameValue will not parse out that info. Bug 16733[11]. • CDP: Port ID TLV followed by Type 1009 TLV triggers [Malformed Packet]. Bug 16742[12]. • tshark crashed when processing opcda. Bug 16746[13]. • tshark with --export-dicom gives “Segmentation fault (core dumped)”. Bug 16748[14]. New and Updated Features There are no new features in this release. New Protocol Support There are no new protocols in this release. Updated Protocol Support ASTERIX, BSSAP, CDP, CoAP, DCERPC SPOOLSS, DCOM, DICOM, DVB-S2, E.212, GBCS, GSM RR, GSM SMS, IEEE 802.11, Kafka, MQ, Nano, NAS 5GS, NIS+, NR RRC, PacketLogger, PFCP, RTPS, systemd Journal, TDS, TN3270, and TN5250 New and Updated Capture File Support PacketLogger and pcapng Getting Wireshark Wireshark source code and installation packages are available from https://www.wireshark.org/download.html. Vendor-supplied Packages Most Linux and Unix vendors supply their own Wireshark packages. You can usually install or upgrade Wireshark using the package management system specific to that platform. A list of third-party packages can be found on the download page[15] on the Wireshark web site. File Locations Wireshark and TShark look in several different locations for preference files, plugins, SNMP MIBS, and RADIUS dictionaries. These locations vary from platform to platform. You can use About→Folders to find the default locations on your system. Getting Help The User’s Guide, manual pages and various other documentation can be found at https://www.wireshark.org/docs/ Community support is available on Wireshark’s Q site[16] and on the wireshark-users mailing list. Subscription information and archives for all of Wireshark’s mailing lists can be found on the web site[17]. Bugs and feature requests can be reported on the bug tracker[18]. Frequently Asked Questions A complete FAQ is available on the Wireshark web site[19]. Last updated 2020-08-12 17:53:44 UTC References 1. https://www.wireshark.org/security/wnpa-sec-2020-10 2. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16672 3. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-17498 4. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16623 5. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16662 6. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16664 7. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16668 8. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16670 9. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16676 10. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16704 11. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16733 12. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16742 13. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16746 14. https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=16748 15. https://www.wireshark.org/download.html#thirdparty 16. https://ask.wireshark.org/ 17. https://www.wireshark.org/lists/ 18. https://bugs.wireshark.org/ 19. https://www.wireshark.org/faq.html Digests wireshark-3.2.6.tar.xz: 31635628 bytes SHA256(wireshark-3.2.6.tar.xz)=ebb1eebe39bcecee02195dc328dd25f6862fc9e9dea4c2e29eae50537d5eb4f2 RIPEMD160(wireshark-3.2.6.tar.xz)=09dcd3a088aa339e18871b053c9c8d8414b25a6a SHA1(wireshark-3.2.6.tar.xz)=e8f3e6cb9072670c8bdbbff7e5fe3ccd5203d35e Wireshark-win64-3.2.6.exe: 60127072 bytes SHA256(Wireshark-win64-3.2.6.exe)=9c211a6eda5f69b2c10dd1a794f8a438c1dafbe5da4879b807be496d8f29a6c4 RIPEMD160(Wireshark-win64-3.2.6.exe)=b7b61d4529ba496f51f3ac024d1e600d6067b5ca SHA1(Wireshark-win64-3.2.6.exe)=f511c383cd0fcd946e1e45ad302c0c6980631f60 Wireshark-win32-3.2.6.exe: 54946856 bytes
Re: [Wireshark-users] [Wireshark-dev] The Wireshark wiki has a new home
On 8/12/20 7:51 AM, Maynard, Chris via Wireshark-users wrote: >> -Original Message- >> From: Wireshark-dev On Behalf >> Of Guy Harris >> Sent: Tuesday, August 11, 2020 11:52 PM >> To: Developer support list for Wireshark >> Cc: Community support list for Wireshark >> Subject: Re: [Wireshark-dev] The Wireshark wiki has a new home >> >> On Aug 11, 2020, at 5:18 PM, Gerald Combs wrote: >> >>> As part of our larger GitLab migration effort I've migrated the Wireshark >> wiki to its new home at >>> >>> https://gitlab.com/wireshark/wireshark/-/wikis/home >>> >>> There's still a fair amount of post-migration work to do (for instance the >> "HowToEdit" is specific to our old wiki), but the new wiki should be faster >> and >> easier to edit, particularly if you're familiar with Markdown. >> >> So how do we edit a Wiki page? I'm logged into my gitlab.com account, but I >> don't see, for example, an "Edit" button. > > Same. *Maybe* this is because Gerald is the only member of the project so > far? > https://gitlab.com/wireshark/wireshark/-/project_members Well, this stinks. I managed to overlook the fact that wiki editing requires Developer permissions, which means that editing the wiki requires the same rights as accepting merge requests and creating new branches: https://gitlab.com/help/user/permissions This is fine for core developers, but not so great for other people that currently have editor permissions. Other people have the same problem, but I don't see any indication that this will be fixed any time soon: https://gitlab.com/gitlab-org/gitlab/-/issues/25177 https://gitlab.com/gitlab-org/gitlab/-/issues/27294 https://gitlab.com/gitlab-org/gitlab/-/issues/15504 We have a few options in the mean time: * Switch back to MoinMoin / wiki.wireshark.org and let it continue to bit-rot. * Switch back to MoinMoin, find some other wiki software, and migrate to it. * Create a separate, public wiki-only gitlab.com/wireshark/wireshark-wiki project, and grant Developer permissions to anyone that wants to contribute. * Create a separate, possibly-private wiki-only gitlab.com/wireshark/wireshark-wiki-backend project, grant Developer permissions to anyone that wants to contribute, and mirror it to the main project wiki. * Some other variation of the previous two items? ___ Sent via:Wireshark-users mailing list Archives:https://www.wireshark.org/lists/wireshark-users Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-users] [Wireshark-dev] The Wireshark wiki has a new home
> -Original Message- > From: Wireshark-dev On Behalf > Of Guy Harris > Sent: Tuesday, August 11, 2020 11:52 PM > To: Developer support list for Wireshark > Cc: Community support list for Wireshark > Subject: Re: [Wireshark-dev] The Wireshark wiki has a new home > > On Aug 11, 2020, at 5:18 PM, Gerald Combs wrote: > > > As part of our larger GitLab migration effort I've migrated the Wireshark > wiki to its new home at > > > > https://gitlab.com/wireshark/wireshark/-/wikis/home > > > > There's still a fair amount of post-migration work to do (for instance the > "HowToEdit" is specific to our old wiki), but the new wiki should be faster > and > easier to edit, particularly if you're familiar with Markdown. > > So how do we edit a Wiki page? I'm logged into my gitlab.com account, but I > don't see, for example, an "Edit" button. Same. *Maybe* this is because Gerald is the only member of the project so far? https://gitlab.com/wireshark/wireshark/-/project_members - Chris CONFIDENTIALITY NOTICE: This message is the property of International Game Technology PLC and/or its subsidiaries and may contain proprietary, confidential or trade secret information. This message is intended solely for the use of the addressee. If you are not the intended recipient and have received this message in error, please delete this message from your system. Any unauthorized reading, distribution, copying, or other use of this message or its attachments is strictly prohibited. ___ Sent via:Wireshark-users mailing list Archives:https://www.wireshark.org/lists/wireshark-users Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-requ...@wireshark.org?subject=unsubscribe
