Re: [Wireshark-dev] Future of Wireshark's Debian packaging scripts in the main repository

Hi Guy, Guy Harris ezt írta (időpont: 2023. dec. 21., Cs, 21:04): > > On Dec 21, 2023, at 6:51 AM, Bálint Réczey wrote: > > > I'm not sure why libvirt dissector users should be "their users". In my > > eyes they are very much our users as well si

Re: [Wireshark-dev] Future of Wireshark's Debian packaging scripts in the main repository

sector users should be "their users". In my eyes they are very much our users as well since they use Wireshark extended with the plugin and I'm happy that they get the best service. Cheers, Balint > > Am Mi., 20. Dez. 2023 um 19:57 Uhr schrieb Bálint Réczey < bal...@balintreczey.hu&

Re: [Wireshark-dev] Future of Wireshark's Debian packaging scripts in the main repository

Hi João, On 2023. Dec 21., Thu at 12:02, João Valverde wrote: > > On 20/12/23 23:20, Anders Broman wrote: > > Hi, > > To me it is a useful feature to be able to easily build .deb packages > > and make repos to easily update and maintain wireshark across servers. > > This is a feature I vote for

Re: [Wireshark-dev] Future of Wireshark's Debian packaging scripts in the main repository

o skip a good technical >> discussion. >> >> I'm ignoring your other points on purpose, there is only so much I can >> handle in one sitting. >> >> On 20/12/23 13:24, Bálint Réczey wrote: >> > Having separate packages follows Debian packaging best practices a

Re: [Wireshark-dev] Changes to the plugin registration API

y beneficial. I think we resolved the GPL question and there is no pressing need to check the plugins' license, it was just based on an unfortunate misunderstanding. Cheers, Balint > Just my 2 cents > > Roland > > Am Mo., 4. Dez. 2023 um 13:12 Uhr schrieb Bálint Réczey > :

Re: [Wireshark-dev] Future of Wireshark's Debian packaging scripts in the main repository

Hi, João Valverde ezt írta (időpont: 2023. nov. 27., H, 21:42): > > > > On 27/11/23 16:26, Jeff Morriss wrote: > > On Wed, Nov 22, 2023 at 11:54 AM João Valverde wrote: > > > > > > On 22/11/23 15:37, John Thacker wrote: > >> On Wed, Nov 22, 2023 at 9:40 AM João Valverde wrote: > >> >

Re: [Wireshark-dev] Changes to the plugin registration API

João Valverde ezt írta (időpont: 2023. dec. 4., H, 12:59): > > > > On 03/12/23 23:25, João Valverde wrote: > > Hi, > > > > There are some changes in progress to the plugin registration API that > > break compatibility and require manual intervention from plugin > > authors maintaining plugins

Re: [Wireshark-dev] Changes to the plugin registration API

On 2023. Dec 4., Mon at 10:02, João Valverde wrote: > Hi, > > The GPL never allowed for that, as far as I know. See: > > https://www.gnu.org/licenses/gpl-faq.html#IfLibraryIsGPL > > In this case Wireshark is a library for plug-ins. > > What you can do is not distribute the (private-use) plug-in,

[Wireshark-dev] Future of Wireshark's Debian packaging scripts in the main repository

Hi All, João shared his opinion about the project's commitment to maintain the packaging/debian/ in the project's repository: https://gitlab.com/wireshark/wireshark/-/commit/79da670bd1b4f91eebee5c96b19eaf1f33c94777#note_1656501952 I believe the current practice is reasonable and beneficial

Re: [Wireshark-dev] Future of Wireshark's shared library ABI stability

João Valverde ezt írta (időpont: 2022. jan. 21., P, 11:17): > > > > On 21/01/22 09:44, Bálint Réczey wrote: > > Hi João, > > > > João Valverde ezt írta (időpont: 2022. jan. 21., P, 1:14): > >> > >> > >> On 20/01/22 12:41, Bálint Réczey

Re: [Wireshark-dev] Future of Wireshark's shared library ABI stability

ted. Cheers, Balint > > kind regards > Roland > > Am Fr., 21. Jan. 2022 um 11:17 Uhr schrieb João Valverde : >> >> >> >> On 21/01/22 09:44, Bálint Réczey wrote: >> > Hi João, >> > >> > João Valverde ezt írta (időpont: 2022. jan. 21

Re: [Wireshark-dev] Future of Wireshark's shared library ABI stability

João Valverde ezt írta (időpont: 2022. jan. 21., P, 1:29): > > > > On 20/01/22 21:24, Bálint Réczey wrote: > > Hi Guy, > > > > Guy Harris ezt írta (időpont: 2022. jan. 20., Cs, > > 21:52): > >> On Jan 20, 2022, at 12:34 PM, Gerald Combs

Re: [Wireshark-dev] Future of Wireshark's shared library ABI stability

Hi João, João Valverde ezt írta (időpont: 2022. jan. 21., P, 1:14): > > > > On 20/01/22 12:41, Bálint Réczey wrote: > > Hi All, > > > > João shared his opinion about the project's commitment to maintain > > stable shared library ABI within stable branch

Re: [Wireshark-dev] Future of Wireshark's shared library ABI stability

Hi Guy, Guy Harris ezt írta (időpont: 2022. jan. 20., Cs, 21:52): > > On Jan 20, 2022, at 12:34 PM, Gerald Combs wrote: > > > Q: Should *wsutil* be part of that stable ABI? > > > > Debian, Ubuntu and (according to rpmfind.net) OpenSuSE and Mageia treat it > > as such. It would be helpful to

[Wireshark-dev] Future of Wireshark's shared library ABI stability

Hi All, João shared his opinion about the project's commitment to maintain stable shared library ABI within stable branches: https://gitlab.com/wireshark/wireshark/-/issues/17822 I believe the current practice is reasonable and beneficial enough for many parties to warrant the work, but I could

Re: [Wireshark-dev] Debianbuild fails on Ubuntu 18.04

Hi Anders, Anders Broman via Wireshark-dev ezt írta (időpont: 2021. okt. 20., Sze, 11:24): > > Hi, > > I can no longer create a debian package on Ubuntu 18.04... The build fails due to a debhelper bug. I've submitted the workaround at https://gitlab.com/wireshark/wireshark/-/merge_requests/4755

Re: [Wireshark-dev] G729

Hi Jaap, Thanks for the heads up!: https://salsa.debian.org/debian/wireshark/-/commit/4f3b519334121ee8115f255d21c22f305e233cc2 Cheers, Balint Jaap Keuter ezt írta (időpont: 2020. dec. 7., H, 12:04): > > FYI, it seems to have finally happened, bcg729 has landed in Debian testing. > > ---8<--- >

[Wireshark-dev] Git tagging scheme

Hi Gerald, I noticed that there is no wireshark-3.0.0 tag in the repository. Could you please create it? In the Debian package the debian/watch file monitors the wireshark-N.N.N tags for new releases. I found the establisted practice of tagging final releases as wireshark-.* and RC-s and similar

Re: [Wireshark-dev] Ubuntu PPAs

2017-03-14 14:28 GMT+01:00 Peter Wu <pe...@lekensteyn.nl>: > On Tue, Mar 14, 2017 at 12:29:24AM +0100, Bálint Réczey wrote: >> Hi, >> >> I have created a separate PPA for backported dependencies of Wireshark: >> https://launchpad.net/~wireshark-dev/+archive/ubunt

[Wireshark-dev] Ubuntu PPAs

Hi, I have created a separate PPA for backported dependencies of Wireshark: https://launchpad.net/~wireshark-dev/+archive/ubuntu/wireshark-deps This would help people running internal builds of Wireshark. (Hi Anders, sorry for the delay ;-)) I plan removing the dependencies from the

Re: [Wireshark-dev] Remove our bundled crypto library (in favor of Libgcrypt)?

Hi, 2017-02-11 22:44 GMT+01:00 Peter Wu : > On Sat, Feb 11, 2017 at 08:54:39PM +, João Valverde wrote: > [..] >> I think a small abstraction layer above the lower-level crypto routines, >> whatever those may be (libgcrypt, nettle, home-grown - yuck), would be a >> useful

Re: [Wireshark-dev] Remove our bundled crypto library (in favor of Libgcrypt)?

Hi All, 2017-02-09 11:34 GMT+01:00 Bálint Réczey <bal...@balintreczey.hu>: > Hi Guy, > > 2017-02-08 19:51 GMT+01:00 Guy Harris <g...@alum.mit.edu>: >> On Feb 8, 2017, at 5:40 AM, Peter Wu <pe...@lekensteyn.nl> wrote: >> >>> I did not expect Li

Re: [Wireshark-dev] Remove our bundled crypto library (in favor of Libgcrypt)?

Hi Guy, 2017-02-08 19:51 GMT+01:00 Guy Harris : > On Feb 8, 2017, at 5:40 AM, Peter Wu wrote: > >> I did not expect Libgcrypt to consume entropy when it is just doing >> decryption. > > I'm concerned with consuming CPU and wall-clock time - i.e., slowing

Re: [Wireshark-dev] Segfault when running older Wireshark with capture from CVE-2013-4075

2016-11-11 11:43 GMT+01:00 Guy Harris : > On Nov 11, 2016, at 1:59 AM, Anders Broman wrote: > >> https://wiki.wireshark.org/Development/LifeCycle >> >> Version Stable Release Date End of LifeNotes >> >> 1.8 June 21, 2012

Re: [Wireshark-dev] unable to compile wireshark-2.0.1 on Ubuntu 14.04

Hi, 2016-11-08 22:43 GMT+01:00 Vidya Dharmaraju : > Hi wireshark-dev, > > > > I am unable to compile wireshark 2 on Ubuntu 14.04 > > > > Need some quick help here – any clues, please share. > > > > Attached is the 1) config.log 2) Compile errors with make > > > > Steps

Re: [Wireshark-dev] checklicenses.py

Hi, 2016-08-05 23:31 GMT+02:00 Guy Harris : ... > > 'debian/rules' has non-whitelisted license 'UNKNOWN' > 'debian/copyright' has non-whitelisted license 'LGPL (v2 or later) > GPL (v2 or later) LGPL (v2 or later)' > 'debian/compat' has non-whitelisted

[Wireshark-dev] Happy-shark or per-PDU regression tests

Hi, With Dario and Peter we created a small regression test suit aiming at checking the dissection engine with very targeted tests. It compares specific PDU's PDML representation against stored references. You can find it on GitHub: https://github.com/wireshark/happy-shark Feel free to add

Re: [Wireshark-dev] Debian builds in wireshark

2016-04-29 11:12 GMT+02:00 Bálint Réczey <bal...@balintreczey.hu>: > Hi Born, > > 2016-04-25 21:30 GMT+02:00 Born In <d3c1...@yahoo.com>: >> Thanks Balint, >> Do you know if dpkg-buildpackage also builds the asn.1 structures inside >> epan/dissectors/

Re: [Wireshark-dev] Debian builds in wireshark

ackage calls cmake then make, thus it does not regenerate the code for the ASN.1 based dissectors. I have prepared a patch to change that which I will submit when gerrit accepts new changes again. Cheers, Balint > > Regards. > > > > On Monday, April 25, 2016 2:06 PM, Bálint Réc

Re: [Wireshark-dev] Debian builds in wireshark

Hi Born, 2016-04-25 19:46 GMT+02:00 Born In : > When I try to build an installer package for Ubuntu (Debian), I am asked > (per the INSTALL doc in the root folder) to execute: "dpkg-buildpackage -us > -uc -rfakeroot" before I use configure/make etc. > However, after I checkout

Re: [Wireshark-dev] Wireshark 2.01 packages in Ubuntu ppa

Hi Peter, 2016-01-13 1:11 GMT+01:00 Peter Wu <pe...@lekensteyn.nl>: > On Sun, Jan 10, 2016 at 11:52:39AM +0100, Bálint Réczey wrote: >> Hi, >> >> 2016-01-09 16:40 GMT+01:00 Peter Wu <pe...@lekensteyn.nl>: >> > Hi Bernard, >> > >> > On

Re: [Wireshark-dev] Wireshark 2.01 packages in Ubuntu ppa

Hi, 2016-01-09 16:40 GMT+01:00 Peter Wu : > Hi Bernard, > > On Thu, Jan 07, 2016 at 12:31:12PM -0500, bernard ck Wong wrote: >> I have installed wireshark2.01 from the wireshark stable ppa on Wily (64 >> bit) and wireshark-gtk crashes immediately. The errors are in

Re: [Wireshark-dev] UI Proposal for better Analysis for Android devices

2015-12-31 0:10 GMT+01:00 Anders Broman : > > Den 30 dec 2015 17:01 skrev "Graham Bloice" : >> >> >> >> On 30 December 2015 at 10:52, VIKRAM VENKATESH HEGDE >> wrote: >>> >>> Hi, >>> >>> >>> >>> Sure, will submit the feature

Re: [Wireshark-dev] -fPIC on Ubuntu Wily

Hi All, I sadly became more and more convinced that starting the adoption of compiling with -fPIE was an overly optimistic move on my side. :-( It seems that there are too many integration corner cases to handle where -fPIE breaks and it may be a better idea to let the distribution-specific

Re: [Wireshark-dev] Moving codecs to libwireshark or libwsutil?

2015-12-02 21:25 GMT+01:00 Pascal Quantin : > > > 2015-11-30 20:15 GMT+01:00 Guy Harris : >> >> >> On Nov 30, 2015, at 11:07 AM, Pascal Quantin >> wrote: >> >> >> > Yes I should have been clearer in my initial description. >>

Re: [Wireshark-dev] wiretap - using as a library rather than coupled with Wireshark?

Hi Dario, You did not write the platforms you want to support, but in case it is just Ubuntu/Debian there are pre built wiretap headers and librerary for your consumption :-): https://packages.debian.org/unstable/libwiretap-dev It releasing the new software under GPL2+ we can integrate it to

Re: [Wireshark-dev] wiretap - using as a library rather than coupled with Wireshark?

2015-11-27 9:45 GMT+01:00 Bálint Réczey <bal...@balintreczey.hu>: > Hi Dario, > > You did not write the platforms you want to support, but in case it is just > Ubuntu/Debian there are pre built wiretap headers and librerary for your > consumption :-): > https://pack

Re: [Wireshark-dev] CMake: Disable building with QT ?

Hi, To enable completion you also need the bash-completion package installed and sourced in your bash session. Sometimes the bash-completion package is missing in VM-s to save space, but on default Ubuntu Desktop it is installed and enabled. Bash-completion performs the completion part and uses

Re: [Wireshark-dev] GCC GTK3 Wireshark build warnings ?

2015-11-11 22:10 GMT+04:00 Jeff Morriss : > On 11/11/15 12:28, Bill Meier wrote: >> >> When building GTK3 Wireshark on my Fedora system (after not having done >> so for a while), I'm getting many warnings similar to the following: >> >> >> CC

Re: [Wireshark-dev] Master-2.0 reminder and Buildbot updates

Hi Gerald, 2015-10-02 22:51 GMT+02:00 Gerald Combs : > As a quick reminder, the master-2.0 branch and builders will be created on > Monday. I've also made the following changes in our Buildbot environment: > > - Upgraded to Qt 5.3.2 on the Windows 64-bit, 32-bit, and Petri

[Wireshark-dev] Wireshark and hardening flags

Hi All, I have just created a review to add PIE when it is available to default flags: https://code.wireshark.org/review/#/c/10635 I think this matter is worth discussion here, too. Should we enable more compiler flags which make Wireshark more secure by default? I Debian I will enable all

Re: [Wireshark-dev] Planning the next major release

2015-06-06 11:23 GMT+02:00 Alexis La Goutte alexis.lagou...@gmail.com: Hi, On Fri, Jun 5, 2015 at 3:39 PM, Bálint Réczey bal...@balintreczey.hu wrote: Hi, 2015-06-04 23:58 GMT+02:00 Gerald Combs ger...@wireshark.org: We often make major releases in June, just before Sharkfest

Re: [Wireshark-dev] Planning the next major release

Hi, 2015-06-04 23:58 GMT+02:00 Gerald Combs ger...@wireshark.org: We often make major releases in June, just before Sharkfest. That probably won't happen this year. A major release now would mean either releasing 2.0 (featuring the Qt UI) without feature parity with the GTK+ UI, or releasing

Re: [Wireshark-dev] Error: implicit declaration of function ‘gdk_pixbuf_new_from_inline’

2015-05-20 13:43 GMT+02:00 Pascal Quantin pascal.quan...@gmail.com: 2015-05-20 13:34 GMT+02:00 Andrei Emeltchenko andrei.emeltchenko.n...@gmail.com: Hi, recently I hit following error when building wireshark on Ubuntu 15.04: ... AR libqtui.a make[2]: Leaving directory

Re: [Wireshark-dev] [Wireshark-commits] master e16500e: Fix check for NUL at the end of a string.

2015-05-13 0:26 GMT+02:00 Guy Harris g...@alum.mit.edu: On May 12, 2015, at 3:13 PM, Evan Huus eapa...@gmail.com wrote: Argh, one of these days I will learn to just put parentheses in rather than taking guesses at C operator precedence :( Yeah, the rule I've found works best for me is if

Re: [Wireshark-dev] build fails with switch --without-qt

Could you please try: git clean -dxf dpkg-buildpackage -us -uc -rfakeroot in the git directory? The deb packages are known to build fine: https://buildd.debian.org/status/package.php?p=wiresharksuite=unstable Cheers, Balint 2015-05-06 16:32 GMT+02:00 wulfman wulf...@wulfman.com: same error

Re: [Wireshark-dev] build fails with switch --without-qt

instance to build the package in a clean chroot: https://wiki.debian.org/sbuild Cheers, Balint On 5/6/2015 7:45 AM, Bálint Réczey wrote: Could you please try: git clean -dxf dpkg-buildpackage -us -uc -rfakeroot in the git directory? The deb packages are known to build fine: https

Re: [Wireshark-dev] Windows automated builds migrated to CMake

Great! Good job! Cheers, Balint 2015-04-16 10:19 GMT+02:00 Graham Bloice graham.blo...@trihedral.com: Woohoo. Change to delete *.nmake incoming :-) On 16 April 2015 at 04:06, Gerald Combs ger...@wireshark.org wrote: We reached a bit of a milestone today. The packages created by the

Re: [Wireshark-dev] Supported Python versions?

Hi Peter, 2015-03-24 18:17 GMT+01:00 Peter Wu pe...@lekensteyn.nl: On Sun, Mar 22, 2015 at 04:58:14PM +0100, Pascal Quantin wrote: 2015-03-22 16:48 GMT+01:00 Peter Wu pe...@lekensteyn.nl: Hi, Triggered by a build error due to html2text.py, I have recently started with adding Python 3

Re: [Wireshark-dev] dpkg-buildpackage -rfakeroot picking wrong version and dissectors

Hi Juanjo, 2015-03-25 15:26 GMT+01:00 Juan Jose Martin Carrascosa jua...@rti.com: Hi all, I am building a package for Ubuntu, and the debian packages I get as result are not picking the proper customized version (set in configure.ac), but what is worse, a custom dissector I wrote is not in

Re: [Wireshark-dev] Use Transifex for manage Translations

2015-03-03 11:58 GMT+01:00 Alexis La Goutte alexis.lagou...@gmail.com: On Tue, Feb 24, 2015 at 10:54 AM, Alexis La Goutte alexis.lagou...@gmail.com wrote: Hi, I have start to use Transifex web service to manage and follow Wireshark Translations. Transifex, it is a Gerrit of translation

Re: [Wireshark-dev] Can we put android phone device connected over USB to Win 7 PC in promiscous mode?

filesystems. If nothing else, scp would work. Cheers, Balint Is anyone aware of enumeration of WLAN interface from android phone as WiFi interface (WLAN adapter) on Win 7 or Linux hosts? On Tue, Feb 24, 2015 at 2:54 PM, Bálint Réczey bal...@balintreczey.hu wrote: Hi Michal, 2015-02-24

Re: [Wireshark-dev] Can we put android phone device connected over USB to Win 7 PC in promiscous mode?

2015-02-24 8:13 GMT+01:00 Shashikant Ajegaonkar ajegaon...@gmail.com: Hi All, Has anyone tried to put WiFi interface of Android device in promiscous mode? Is it possible to enumerate phone over adb interface as device wireless network interface in Win7 machine and configure it in promiscous

Re: [Wireshark-dev] American Fuzzy Lop - Menagerie Minimization

2015-01-25 15:41 GMT+01:00 Evan Huus eapa...@gmail.com: Gerald and I have (independently) started playing with the American Fuzzy Lop fuzzer recently [1] as a possibly more intelligent alternative or complement to our current fuzzing set-up. It includes a tool afl-cmin that uses its

Re: [Wireshark-dev] Issues packaging Wireshark in Ubuntu

Hi Juanjo, 2015-01-16 17:04 GMT+01:00 Juan Jose Martin Carrascosa jua...@rti.com: Hi all, I have a very quick question: am I supposed to create deb packages by doing make debian-package? The makefile doesn't recognize that option :( No, by running dpkg-buildpackage -rfakeroot. Cheers, Balint

Re: [Wireshark-dev] Questions about Submission of dissectors

Hi, 2015-01-10 13:08 GMT+01:00 Pascal Quantin pascal.quan...@gmail.com: Hi Christopher, 2015-01-09 21:51 GMT+01:00 Christopher Sheldahl christopher.sheld...@yahoo.com: My company has developed a number of dissectors for our own protocols, and we are interested in possibly having them

Re: [Wireshark-dev] [Wireshark-bugs] [Bug 10750] Use of GdkPixdata / gdk_pixbuf_new_from_inline deprecated in gdk-pixbuf 2.31.2

2015-01-07 20:08 GMT+01:00 Stephen Fisher sfis...@sdf.org: On Wed, Jan 07, 2015 at 07:51:33PM +0100, B?lint R?czey wrote: Removing usages of the deprecated functions is on my TODO list, but if I can't finish that in reasonable time keeping the reminder would help others to act. What about

Re: [Wireshark-dev] [Wireshark-bugs] [Bug 10750] Use of GdkPixdata / gdk_pixbuf_new_from_inline deprecated in gdk-pixbuf 2.31.2

Hi Stephen, 2015-01-07 19:31 GMT+01:00 Stephen Fisher sfis...@sdf.org: On Wed, Jan 07, 2015 at 06:21:06PM +, bugzilla-dae...@wireshark.org wrote: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=10750 --- Comment #7 from Balint Reczey bal...@balintreczey.hu --- (In reply to Stephen

Re: [Wireshark-dev] Update Windows Build Instructions

Hi Stephen, 2015-01-06 0:20 GMT+01:00 Stephen Fisher sfis...@sdf.org: On Mon, Jan 05, 2015 at 03:34:16PM -0500, Ed Beroset wrote: Having been around this particular block a couple of times, yes, CMake at times is a battle, but it's also better than the alternative of producing (and

Re: [Wireshark-dev] Generate AUTHORS file

2015-01-06 18:02 GMT+01:00 mman...@netscape.net: One thing I noticed when I reviewed one of the .mailman patches you've submitted was that some authors have multiple email addresses. Do we really want to include them all? I thought the current AUTHORS file typically only has one (hopefully

Re: [Wireshark-dev] CMake status

Hi, 2015-01-05 21:17 GMT+01:00 Gerald Combs ger...@wireshark.org: Our CMake environment has been coming along nicely. However, it's still missing several major build targets that are present in the Autotools and Nmake+QMake makefiles: dist. Balint created a script

Re: [Wireshark-dev] Ubuntu PPA for Wireshark stable branch

! Evan On Fri, Dec 12, 2014 at 4:53 PM, Bálint Réczey bal...@balintreczey.hu wrote: Hi All, I have created a PPA for the stable Wireshark branch point releases: https://launchpad.net/~wireshark-dev/+archive/ubuntu/stable The packages are back-ported from latest packaged version in Debian

[Wireshark-dev] Ubuntu PPA for Wireshark stable branch

Hi All, I have created a PPA for the stable Wireshark branch point releases: https://launchpad.net/~wireshark-dev/+archive/ubuntu/stable The packages are back-ported from latest packaged version in Debian unstable to prevent upgrade problems. Since in Debian we are in freeze phase I can't

Re: [Wireshark-dev] --without-gtk3 doesn't imply --with-qt

Hi Jeff, 2014-12-01 18:59 GMT+01:00 Jeff Morriss jeff.morriss...@gmail.com: On 11/29/14 05:44, Bálint Réczey wrote: Hi Jeff, 2014-11-26 19:26 GMT+01:00 Jeff Morriss jeff.morriss...@gmail.com: On 11/26/14 13:01, Stephen Fisher wrote: Is there any reason a user would have both GTK3

Re: [Wireshark-dev] CMake support out of source plugin compilation

2014-11-20 9:53 GMT+01:00 Maarten Bezemer maarten.beze...@gmail.com: On Thursday 13 November 2014 15:15:26 you wrote: On Thursday 13 November 2014 13:56:26 Graham Bloice wrote: While I'm all for making life easier for devs, if no-one else has identified this as a need, i.e. only you find it

Re: [Wireshark-dev] Backporting policy for protocols that are under construction

Hi, 2014-11-20 12:05 GMT+01:00 Alexis La Goutte alexis.lagou...@gmail.com: On Thu, Nov 20, 2014 at 5:03 AM, Evan Huus eapa...@gmail.com wrote: There is currently a change pending backport to the 1.12 branch (long since committed to master) that is a non-trivial dissector upgrade. Normally we

Re: [Wireshark-dev] Conflicts: field in commit messages

Hi, 2014-10-26 19:58 GMT+01:00 Bálint Réczey bal...@balintreczey.hu: 2014-10-08 11:41 GMT+02:00 Michal Labedzki michal.labed...@tieto.com: On 7 October 2014 19:29, Guy Harris g...@alum.mit.edu wrote: 2) somebody resolved the conflicts but forgot to edit the commit message. I think

Re: [Wireshark-dev] Wireshark 1.12.2 is now available

Hi Gerald, 2014-11-12 21:33 GMT+01:00 Gerald Combs ger...@wireshark.org: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm proud to announce the release of Wireshark 1.12.2. __ What is Wireshark? Wireshark is the world's

Re: [Wireshark-dev] On which platforms is there a need for Wireshark to have a Language preference?

Hi Dario, 2014-11-05 9:31 GMT+01:00 Dario Lombardo dario.lombardo...@gmail.com: Hi Guy The answer is yes. I live in italy, but I use linux in english. I switch to en or it for the specific purpose of the moment. With auto-detect I could't do that. For my daily use I switch to EN. To

Re: [Wireshark-dev] On which platforms is there a need for Wireshark to have a Language preference?

feature (or user experience) On 5 November 2014 10:52, Bálint Réczey bal...@balintreczey.hu wrote: Hi Dario, 2014-11-05 9:31 GMT+01:00 Dario Lombardo dario.lombardo...@gmail.com: Hi Guy The answer is yes. I live in italy, but I use linux in english. I switch to en

Re: [Wireshark-dev] Updating debian symbols?

Hi Anders, 2014-10-30 17:49 GMT+01:00 Anders Broman anders.bro...@ericsson.com: Hi, How to update the symbols file? The output of the dpkg-gensymbols command includes the patch which should be applied, Whenever a new symbol is exported/removed the symbols file must be updated. This reminds us

Re: [Wireshark-dev] Conflicts: field in commit messages

2014-10-08 11:41 GMT+02:00 Michal Labedzki michal.labed...@tieto.com: On 7 October 2014 19:29, Guy Harris g...@alum.mit.edu wrote: 2) somebody resolved the conflicts but forgot to edit the commit message. I think this is wrong meaning of this git feature. In my opinion Conflicts:

Re: [Wireshark-dev] 25 Warnings on Clang Scan Build

2014-10-14 21:41 GMT+02:00 Alexis La Goutte alexis.lagou...@gmail.com: Hi, For the first time, you are under 25 warnings on Clang scan-build :-D ( https://www.wireshark.org/download/automated/analysis/ ) A quick review about last warnings : 3 coming from flex (Dead Assignement on

Re: [Wireshark-dev] Conflicts: field in commit messages

Hi Guy, 2014-10-07 19:29 GMT+02:00 Guy Harris g...@alum.mit.edu: On Oct 7, 2014, at 1:12 AM, Michal Labedzki michal.labed...@tieto.com wrote: You miss one thing - cherry-pick with conflicts is not the same that original commit. That's what with manual intervention is for, as per my earlier

[Wireshark-dev] Conflicts: field in commit messages

Hi All, I usually leave the Conflicts: ... in the commit message after resolving conflicts to document that the merge was not automatic. Should I continue doings so you prefer removing this from the commit message? Guy raised the issue in https://code.wireshark.org/review/#/c/4438 , but I think

[Wireshark-dev] Planet.wireshark.org?

Hi, We had some discussions about blogging more actively on https://blog.wireshark.org/, but I think there would be an other way of making the project more active on the press side. We have a nice community and we could provide and site for aggregating Wireshark-related news from individual

Re: [Wireshark-dev] [Wireshark-commits] master bcae048: Update to the latest version from the Samba Git repository.

Hi, 2014-09-26 21:12 GMT+02:00 Evan Huus eapa...@gmail.com: Since it looks like PIDL is also using git, how do people feel about using git submodules instead of maintaining our own copy of PIDL? I would avoid submodules because it adds a lot of complexity without providing little value. If we

Re: [Wireshark-dev] Systematic crash at startup when launching Wireshark GTK+ 1.99 x64 on Windows 8.1

Hi, 2014-09-16 8:24 GMT+02:00 Anders Broman a.broma...@gmail.com: Den 16 sep 2014 08:00 skrev Pascal Quantin pascal.quan...@gmail.com: Le 15 sept. 2014 23:13, Gerald Combs ger...@wireshark.org a écrit : On 9/15/14 10:51 AM, Gerald Combs wrote: On 9/15/14 10:02 AM, Pascal Quantin

Re: [Wireshark-dev] Qt License Change

Hi, 2014-08-20 18:36 GMT+02:00 ronnie sahlberg ronniesahlb...@gmail.com: I think the biggest gotcha with LGPLv3 is that it is no longer compatible with GPLv2 only code. Wireshark does not have any GPLv2only code right? If not, we should be ok. On Wed, Aug 20, 2014 at 9:31 AM, Evan Huus

Re: [Wireshark-dev] Buildbot Man Page Generation

Hi Evan, 2014-08-10 4:41 GMT+02:00 Evan Huus eapa...@gmail.com: http://buildbot.wireshark.org/trunk/builders/Clang%20Code%20Analysis/builds/2911/steps/check-abi/logs/stdio I took a quick look at the recent check-abi buildbot failure, which appears to be manpage related: wireshark.pod around

Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available

2014-07-31 10:32 GMT+02:00 Guy Harris g...@alum.mit.edu: On Jul 31, 2014, at 1:18 AM, Bálint Réczey bal...@balintreczey.hu wrote: Since the files stored in git are enough for building Wireshark on every platform we support So we shouldn't bother generating or shipping tarballs at all, just

Re: [Wireshark-dev] [Wireshark-announce] Wireshark 1.12.0rc3 is now available

2014-07-31 12:34 GMT+02:00 Peter Wu pe...@lekensteyn.nl: On Wednesday 30 July 2014 14:35:06 Gerald Combs wrote: After comparing the tarballs generated by make dist and git-export-release.sh I have to agree. Both have issues but the dist tarball will build according to our documentation on

Re: [Wireshark-dev] tvb allocator (was: Re: [Wireshark-commits] master b6d20a2: Optimize reseting epan_dissect_t when filtering.)

Hi Jakub, 2014-07-22 0:52 GMT+02:00 darkjames...@darkjames.pl: Hi, On Sat, Jul 12, 2014 at 02:27:06AM +0200, B??lint R??czey wrote: I plan using ASAN for all programs which would catch (among others) use-after-free and reading below or over the malloc()-ed memory area. Those can't be

Re: [Wireshark-dev] 1.12 release schedule

Hi Gerald, 2014-07-22 0:19 GMT+02:00 Gerald Combs ger...@wireshark.org: I plan to release 1.12.0rc3 tomorrow (the 22nd) followed by 1.12.0 on the 29th. If we need to hold off either release for any reason please let me know. Great! I would like to have the fix for 9891 included which I plan

Re: [Wireshark-dev] tvb allocator (was: Re: [Wireshark-commits] master b6d20a2: Optimize reseting epan_dissect_t when filtering.)

Hi All, Please provide the input data for letting others reproduce the results or perform the performance tests on pcap files already available to the public. I'm not a fan of implementing custom memory management methods because partly because I highly doubt we can beat jemalloc easily on

Re: [Wireshark-dev] tvb allocator (was: Re: [Wireshark-commits] master b6d20a2: Optimize reseting epan_dissect_t when filtering.)

Hi Evan, 2014-07-11 23:51 GMT+02:00 Evan Huus eapa...@gmail.com: On Fri, Jul 11, 2014 at 5:12 PM, Bálint Réczey bal...@balintreczey.hu wrote: Hi All, Please provide the input data for letting others reproduce the results or perform the performance tests on pcap files already available

Re: [Wireshark-dev] tvb allocator (was: Re: [Wireshark-commits] master b6d20a2: Optimize reseting epan_dissect_t when filtering.)

2014-07-12 0:07 GMT+02:00 Anders Broman a.broma...@gmail.com: Den 11 jul 2014 23:13 skrev Bálint Réczey bal...@balintreczey.hu: Hi All, Please provide the input data for letting others reproduce the results or perform the performance tests on pcap files already available to the public

Re: [Wireshark-dev] Fwd: Re: Storing Generated Code in Git [Was: master 9079e3a: Cheat and try to fix the generated file manually.]

2014-06-24 5:26 GMT+02:00 Joerg Mayer jma...@loplof.de: On Mon, Jun 23, 2014 at 09:17:32PM -0400, Evan Huus wrote: So perhaps what we should do is: not check generated code into Git; +1 put all generated code into the source tarballs. +2 How about releasing two

Re: [Wireshark-dev] [Wireshark-commits] master 9079e3a: Cheat and try to fix the generated file manually.

Hi, 2014-06-23 17:54 GMT+02:00 Evan Huus eapa...@gmail.com: I would *really* prefer we didn't do this. Me, too. Going this way makes maintaining Wireshark really hard. And for 1% speed increase in a very specific case? I generally don't agree with the approach and in this specific IMO the gains

Re: [Wireshark-dev] RTP Player

2014-06-20 7:38 GMT-07:00 Jeff Morriss jeff.morriss...@gmail.com: On 06/18/14 21:07, Evan Huus wrote: We have at least 30 bugs to do with RTP and the analysis/audio player: https://bugs.wireshark.org/bugzilla/buglist.cgi?quicksearch=rtp Do we have a plan for the Qt equivalent of this UI? Is

Re: [Wireshark-dev] RTP Player

2014-06-18 18:07 GMT-07:00 Evan Huus eapa...@gmail.com: We have at least 30 bugs to do with RTP and the analysis/audio player: https://bugs.wireshark.org/bugzilla/buglist.cgi?quicksearch=rtp Do we have a plan for the Qt equivalent of this UI? Is it worth doing, or should we hand it off to the

[Wireshark-dev] Are tfshark/filetap ready for 1.12?

Hi, I'm wondering if we should ship tfshark and the filetap libraries in 1.12. There is no man page or documentation for tfshark and they are both in very early phase of development. I'm not sure how they are useful for end users in their current form. The questions formed in me while trying to

Re: [Wireshark-dev] Reminder: 1.12 branch tomorrow

2014-06-05 13:29 GMT+07:00 Alexis La Goutte alexis.lagou...@gmail.com: On Tue, Jun 3, 2014 at 7:19 PM, Bálint Réczey bal...@balintreczey.hu wrote: Hi, 2014-05-23 6:33 GMT+07:00 Gerald Combs ger...@wireshark.org: Reminder: I'm going to create the master-1.12 branch along with the other

Re: [Wireshark-dev] Reminder: 1.12 branch tomorrow

Hi, 2014-05-23 6:33 GMT+07:00 Gerald Combs ger...@wireshark.org: Reminder: I'm going to create the master-1.12 branch along with the other changes listed below tomorrow. Original Message Subject: 1.12 branch + release schedule Date: Mon, 19 May 2014 14:46:42 -0700 From:

Re: [Wireshark-dev] Is it possible to update the version of gcrypt?

Hi, 2014-04-01 9:58 GMT+07:00 Gerald Combs ger...@wireshark.org: On 3/31/14, 6:35 PM, Pascal Quantin wrote: 2014-03-31 20:02 GMT+02:00 Gerald Combs ger...@wireshark.org mailto:ger...@wireshark.org: On 3/30/14 10:00 AM, Pascal Quantin wrote: 2014-01-08 0:25 GMT+01:00 Pascal Quantin

Re: [Wireshark-dev] Wireshark LTS branches

Hi, 2014-04-18 21:51 GMT+07:00 Jeff Morriss jeff.morriss...@gmail.com: On 04/17/14 23:11, Guy Harris wrote: On Apr 17, 2014, at 3:58 PM, Bálint Réczey bal...@balintreczey.hu wrote: Well, last time I brought this up the project decision was to allow minor improvements, too: http

Re: [Wireshark-dev] [Wireshark-core] Hash Tables and Algorithmic Complexity Attacks

05:36 To: Wireshark core developers Subject: Re: [Wireshark-core] Hash Tables and Algorithmic Complexity Attacks On Mon, Apr 21, 2014 at 6:28 PM, Balint Reczey rbal...@gmail.com wrote: On Apr 22, 2014 12:11 AM, Evan Huus eapa...@gmail.com wrote: On Mon, Apr 21, 2014 at 3:59 PM, Bálint Réczey

Re: [Wireshark-dev] Wireshark LTS branches

Hi Gerald, 2014-04-17 1:59 GMT+02:00 Gerald Combs ger...@wireshark.org: On 4/16/14 3:42 AM, Bálint Réczey wrote: Hi, Many of you probably know about the Wireshark package [1] in Debian which I started maintaining a few years ago. Like every other package in Debian, the version of Wireshark

Re: [Wireshark-dev] Wireshark LTS branches

2014-04-17 23:21 GMT+02:00 Evan Huus eapa...@gmail.com: On Thu, Apr 17, 2014 at 4:23 AM, Anders Broman anders.bro...@ericsson.com wrote: -Original Message- From: wireshark-dev-boun...@wireshark.org [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Bálint Réczey Sent: den

[Wireshark-dev] Wireshark LTS branches

Hi, Many of you probably know about the Wireshark package [1] in Debian which I started maintaining a few years ago. Like every other package in Debian, the version of Wireshark included in the major distribution release is getting security and stability updates through the lifetime [2] of the

  1   2   3   >