Re: [Wireshark-dev] [Wireshark-commits] master 246fe2c: Fixup: tvb_* -> tvb_captured

2014-06-19 Thread Dario Lombardo
t;> URL: >> https://code.wireshark.org/review/gitweb?p=wireshark.git;a=commit;h=246fe2ca4c67d8c98caa84e2f57694f6322e2f96 >> Submitter: Anders Broman (a.broma...@gmail.com) >> Changed: branch: master >> Repository: wireshark >> >> Commits: >> >>

Re: [Wireshark-dev] [Wireshark-commits] master 14824e6: Revert "Fixup: tvb_* -> tvb_captured"

2014-06-20 Thread Dario Lombardo
On Thu, Jun 19, 2014 at 9:18 PM, Evan Huus wrote: > We were not bulk-converting them so that we could catch the ones that really > should have been tvb_reported_length and tvb_reported_length_remaining from > the beginning. If you look at the code in epan/tvbuff.h:228,237,244 you can find those d

Re: [Wireshark-dev] [Wireshark-commits] master 14824e6: Revert "Fixup: tvb_* -> tvb_captured"

2014-06-20 Thread Dario Lombardo
On Fri, Jun 20, 2014 at 4:33 PM, Jeff Morriss wrote: > IOW the reason these functions were renamed was because a large portion of > the time dissector-writers would use tvb_length() when they really should > have been using tvb_reported_length(). By renaming the functions and adding > a macro--wh

[Wireshark-dev] Deprecated APIs

2014-06-20 Thread Dario Lombardo
Hi list I'm having a look at obsolete APIs and I've got those lines from checkAPI.pl Warning: Found soft-deprecated APIs in packet-bacapp.c: ep_address_to_str Warning: Found soft-deprecated APIs in packet-umts_fp.c: se_new0 but I can't find how those func should be changed. Can anyone help me?

Re: [Wireshark-dev] Translation tools

2014-10-09 Thread Dario Lombardo
On Wed, Oct 8, 2014 at 9:06 PM, Alexis La Goutte wrote: > Hi, > > It is now possible to translate the Gui of Wireshark (with Qt) > > Actually, there is start of French translation, Polish (Thanks Michal) > and Japanese (Thanks martin & Megane) > How one can start a task like that? Is there any d

Re: [Wireshark-dev] Translation tools

2014-10-09 Thread Dario Lombardo
change was not ported to the "compiled" ones. Am I right? What should I do with those changes? Keep them or discard them? On Thu, Oct 9, 2014 at 4:22 PM, Alexis La Goutte wrote: > On Thu, Oct 9, 2014 at 4:02 PM, Dario Lombardo > wrote: > > > > > > On Wed,

Re: [Wireshark-dev] Translation tools

2014-10-10 Thread Dario Lombardo
Ok, thanks. I'm able to start the translation. I've translated a couple of entries, recompiled, changed the language, and everything is ok: my translated entries are now in wireshark. But if now I translate other entries, run lupdate and lrelease, then make, the ui is not recompiled again. It seems

[Wireshark-dev] QT with cmake

2014-10-21 Thread Dario Lombardo
Hi list I tried to compile the master of wireshark using cmake. mkdir build cd build cmake .. make In run/ I can find wireshark-gtk but not qt. Any specific command to pass to cmake to have it? I am able to obtain qt executable using autotools (meaning that my qt dev subsystem should be fine). T

Re: [Wireshark-dev] QT with cmake

2014-10-21 Thread Dario Lombardo
t; > On 21 October 2014 11:20, Dario Lombardo > wrote: > >> Hi list >> I tried to compile the master of wireshark using cmake. >> >> mkdir build >> cd build >> cmake .. >> make >> >> In run/ I can find wireshark-gtk but not qt. Any sp

Re: [Wireshark-dev] QT with cmake

2014-10-21 Thread Dario Lombardo
Well... after installing some other qt5 packages I get CMake Error at ui/qt/CMakeLists.txt:306 (QT5_ADD_TRANSLATION): Unknown CMake command "QT5_ADD_TRANSLATION". On Tue, Oct 21, 2014 at 11:49 AM, Peter Wu wrote: > On Tuesday 21 October 2014 11:20:54 Dario Lombardo wrote: &

Re: [Wireshark-dev] QT with cmake

2014-10-21 Thread Dario Lombardo
On Tue, Oct 21, 2014 at 1:20 PM, Peter Wu wrote: > > What distro are you using? For Debian/Ubuntu you need to install > qttools5-dev. > It is exactly what I'm using (ubuntu 14.04). I've installed qttools5-dev and compilation made few steps ahead, but then stopped with Scanning dependencies of

Re: [Wireshark-dev] QT with cmake

2014-10-21 Thread Dario Lombardo
On Tue, Oct 21, 2014 at 2:48 PM, Peter Wu wrote: > > Have you tried to clear your build dir? The QtGui/QAction file is located > in the > qt4 include directory, in qt5 it is located at QtWidgets/QAction. > > I've completely deleted the build dir and started over. Same output. [ 79%] Building CXX

[Wireshark-dev] QT with cmake

2014-10-21 Thread Dario Lombardo
Hi list I tried to compile the master of wireshark using cmake. mkdir build cd build cmake .. make In run/ I can find wireshark-gtk but not qt. Any specific command to pass to cmake to have it? I am able to obtain qt executable using autotools (meaning that my qt dev subsystem should be fine). T

Re: [Wireshark-dev] QT with cmake

2014-10-22 Thread Dario Lombardo
:13:01PM +0200, Dario Lombardo wrote: > > On Tue, Oct 21, 2014 at 2:48 PM, Peter Wu wrote: > > > > > > > > Have you tried to clear your build dir? The QtGui/QAction file is > located > > > in the > > > qt4 include directory, in qt5 it is located at

Re: [Wireshark-dev] Installing on Ubuntu 12.04.5

2014-10-23 Thread Dario Lombardo
You installed gtk3 that is the library pkg but not the -dev pkg that is what configure checks for. The key packet you're probably missing is - libgtk-3-dev as stated in the Robert's list. To be sure, look for "gtk" in your config.log. You will find configure:30681: gcc -o conftest -g -O2 -W

[Wireshark-dev] Compiling with ninja

2014-11-04 Thread Dario Lombardo
Hi list Some days ago I played a bit with ninja and I found useful info I'd like to share with you. Ninja is a compilation system similar to make. It's advantage is that it was built with parallelism in mind, to take advantage of multi-core CPUs. Wireshark uses cmake that has a generator for ninja,

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

2014-11-05 Thread Dario Lombardo
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 develop/test wireshark italian translation I switch to IT. I don't know if this scenario appli

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

2014-11-05 Thread Dario Lombardo
On Wed, Nov 5, 2014 at 10:52 AM, Bálint Réczey wrote: > Please run "LC_ALL=it_IT wireshark" instead of asking the project to > keep the language-switching feature. > Thanks for your suggestion. ___ Sent via:Wireshark-dev

Re: [Wireshark-dev] Capture from multiple remote machines

2014-11-19 Thread Dario Lombardo
On Wed, Nov 19, 2014 at 9:12 AM, Ozan T wrote: > Hi Patrick , > > Thank you, it works! > > Sorry, it is my mistake I thought rpcapd and "Remote Interfaces" wer just > for Windows machines. Here , I see it works well on Linux and BSD also. > > > Thanks again. > > > Ozan. > > Hi Ozan Can you share

[Wireshark-dev] nflog in qt and gtk

2014-12-18 Thread Dario Lombardo
Hi list! I tried to use nflog to capture packets with wireshark qt and gtk (master) and I got different results. First I run sudo iptables -A OUTPUT -j NFLOG sudo iptables -A INPUT -j NFLOG then I launched wireshark-gtk and choose nflog as capture interface. All worked. But when I launched wiresh

Re: [Wireshark-dev] nflog in qt and gtk

2014-12-19 Thread Dario Lombardo
On Thu, Dec 18, 2014 at 4:29 PM, Peter Wu wrote: > > > You should not run Wireshark with sudo, instead set the appropriate > privileges on the dumpcap binary as described at > http://wiki.wireshark.org/CaptureSetup/CapturePrivileges > > Generally speaking, you are right, and it's waht I do with my

Re: [Wireshark-dev] nflog in qt and gtk

2014-12-19 Thread Dario Lombardo
On Fri, Dec 19, 2014 at 11:44 AM, Peter Wu wrote: > > > If I need to perform a capture, i just overwrite dumpcap with: > ln -sfv /usr/bin/dumpcap /tmp/wsbuild/run/ > > It looks like you also avoid overwriting this file/symlink by disabling > dumpcap building: > > cmake -DBUILD_dumpcap=0 ... >

Re: [Wireshark-dev] nflog in qt and gtk

2014-12-19 Thread Dario Lombardo
On Fri, Dec 19, 2014 at 12:35 PM, Peter Wu wrote: > The Capture -> Options > dialog is another place where these stats are visible. > Is it visible during capture? ___ Sent via:Wireshark-dev mailing list Archives:ht

Re: [Wireshark-dev] nflog in qt and gtk

2014-12-23 Thread Dario Lombardo
> > > > Kill statistics before starting the capture? Sounds fine to me, though I > am not sure whether it has other side-effects. The Capture -> Options > dialog is another place where these stats are visible. > What about filing a bug? Do you think it would be useful? Or is there anyone taking ca

[Wireshark-dev] Patch being stuck

2015-01-08 Thread Dario Lombardo
Hi list I pushed a patch a couple of days ago https://code.wireshark.org/review/#/c/6350/ I think it's getting stuck for some reason (not even the petri dish buildbot has processed it). Other patches submitted later (eg. https://code.wireshark.org/review/6394 or https://code.wireshark.org/revie

Re: [Wireshark-dev] Patch being stuck

2015-01-08 Thread Dario Lombardo
On Thu, Jan 8, 2015 at 11:50 AM, Graham Bloice wrote: > > No blockage reason, just no-one on the core team has gotten around to > having a look at it yet. Submission to the Petri-Dish isn't (yet) > automatic, it requires a manual flag (from a core team member). > > Ok, that's the part I missed.

[Wireshark-dev] Question about stats_tree

2015-01-13 Thread Dario Lombardo
Hi list I was planning to have stats_tree for hpfeeds, but I have a problem and I need some suggestion from you. In hpfeeds the channel is a user-defined string that is not defined by the protocol, and that is used to share infos in a set of consumer/producer. For that I can't create a pivot table

[Wireshark-dev] JSON as mime type

2015-01-21 Thread Dario Lombardo
Hi list, Now that the json dissector has became heuristic, I was trying to make wireshark open a native json file, like it is able to do it with xml. What is necessary to make it work other than add a line like heur_dissector_add("wtap_file", dissect_json_heur, proto_json); in the json dissector

Re: [Wireshark-dev] nflog in qt and gtk

2015-01-23 Thread Dario Lombardo
Dario. On Tue, Dec 23, 2014 at 11:15 AM, Dario Lombardo < dario.lombardo...@gmail.com> wrote: > >> >> Kill statistics before starting the capture? Sounds fine to me, though I >> am not sure whether it has other side-effects. The Capture -> Options >> dial

Re: [Wireshark-dev] nflog in qt and gtk

2015-01-26 Thread Dario Lombardo
n up to 10 times. It works on my machine. I noticed that the first try fails, while the second succeds. You can find the change here https://code.wireshark.org/review/#/c/6796/ Comments welcome. Dario. On Fri, Jan 23, 2015 at 2:11 PM, Dario Lombardo wrote: > Hi Peter > I opened a bug on b

[Wireshark-dev] Undissected packet bytes

2015-02-03 Thread Dario Lombardo
Hi list I was wondering if there is a comfortable way to find out undissected bytes in packets. This would be useful to find incomplete dissectors. Any hint? Thanks! Dario. ___ Sent via:Wireshark-dev mailing list Archives:

Re: [Wireshark-dev] Undissected packet bytes

2015-02-04 Thread Dario Lombardo
is not currently available, but it would > >> probably be fairly useful and easy. You just need to iterate the proto > >> tree and keep track of which byte ranges are claimed/unclaimed. > >> proto_find_field_from_offset does something related to this (it is > >> u

Re: [Wireshark-dev] Undissected packet bytes

2015-02-04 Thread Dario Lombardo
and easy. You just need to iterate the proto > tree and keep track of which byte ranges are claimed/unclaimed. > proto_find_field_from_offset does something related to this (it is > used for matching bytes to fields in the UI) so it's probably a good > place to start. > > On Tue,

Re: [Wireshark-dev] Undissected packet bytes

2015-02-04 Thread Dario Lombardo
On Wed, Feb 4, 2015 at 3:52 PM, Evan Huus wrote: > > As a side note, I would expect that method to be *very* slow, since it > traverses the entire tree for every byte of the packet. Traversing the > tree once and maintaining a set of covered/uncovered ranges would be > much more efficient. > I c

Re: [Wireshark-dev] Undissected packet bytes

2015-02-04 Thread Dario Lombardo
On Wed, Feb 4, 2015 at 5:25 PM, Evan Huus wrote: > I think you will need to add a function very similar to > proto_find_field_from_offset that makes use of > proto_tree_traverse_pre_order and tracks which bytes have been "seen" > as the traversal proceeds. > And how the output could be shown to

Re: [Wireshark-dev] Undissected packet bytes

2015-02-05 Thread Dario Lombardo
On Wed, Feb 4, 2015 at 7:28 PM, Evan Huus wrote: > I suppose you could add a an expert info, but I think that might be > overkill, most users probably don't care that much. Expert infos could be added under conditional compilation. If enabled it would allow to filter packets that has expert inf

Re: [Wireshark-dev] Undissected packet bytes

2015-02-05 Thread Dario Lombardo
On Thu, Feb 5, 2015 at 1:19 PM, Evan Huus wrote: > I believe g_log and friends go to standard out, but maybe not on all > platforms. An expert info under conditional compilation would probably > be enough though, I hadn't thought of that. > Another question. I've found a promising point to put t

Re: [Wireshark-dev] Undissected packet bytes

2015-02-05 Thread Dario Lombardo
To test it, simply comment any proto_tree_add_item() from a dissector of your choice, and open a packet with wireshark or with tshark -V. Comments are welcome. Dario. On Thu, Feb 5, 2015 at 1:41 PM, Dario Lombardo wrote: > On Thu, Feb 5, 2015 at 1:19 PM, Evan Huus wrote: > >> I believe g

Re: [Wireshark-dev] Undissected packet bytes

2015-02-06 Thread Dario Lombardo
On Fri, Feb 6, 2015 at 7:52 AM, Michal Labedzki wrote: > One more hint: if push patch as draft then add reviewer, because draft > is invisible for anyone (expect author and reviewers) > > Alternative command(s) to send to gerrit: > git push origin HEAD:refs/drafts/master > git push origin HEAD:re

Re: [Wireshark-dev] False positive from the new "Look for incomplete dissectors" function.

2015-02-12 Thread Dario Lombardo
Hi Anders If you carefully have a look at the bytes, you can notice that the 2 bytes reported by the logs are claimed by the SIP dissector, but they're not decoded. Until SIP/2.0, bytes are decoded (address up to 0x0040+12). >From "Max-Forward" and beyond (address 0x0040+15) they are decoded. Addr

Re: [Wireshark-dev] False positive from the new "Look for incomplete dissectors" function.

2015-02-13 Thread Dario Lombardo
On Thu, Feb 12, 2015 at 6:18 PM, Anders Broman wrote: > I suspected as much, but I think all the sip lines skip the CRLF... > > > What about adding the skipped bytes as hidden, labeled as "unused bytes"? ___ Sent via:Wire

Re: [Wireshark-dev] False positive from the new "Look for incomplete dissectors" function.

2015-02-13 Thread Dario Lombardo
On Fri, Feb 13, 2015 at 10:14 AM, Anders Broman wrote: > First thought is, unnecessary processing to satisfy this new > functionality, which frankly I have my doubts about... > I have the same feeling. But I can't figure out something else so far. _

Re: [Wireshark-dev] False positive from the new "Look for incomplete dissectors" function.

2015-02-13 Thread Dario Lombardo
t; > *From:* wireshark-dev-boun...@wireshark.org [mailto: > wireshark-dev-boun...@wireshark.org] *On Behalf Of *Dario Lombardo > *Sent:* den 13 februari 2015 10:18 > *To:* Developer support list for Wireshark > *Subject:* Re: [Wireshark-dev] False positive from the new "

Re: [Wireshark-dev] False positive from the new "Look for incomplete dissectors" function.

2015-02-17 Thread Dario Lombardo
On Fri, Feb 13, 2015 at 5:15 PM, Jeff Morriss wrote: > I have to admit that I like being able to click on a byte and see what > field it maps to. From that perspective I like when padding is claimed by > the dissector which knew it was padding. And when CR+NL are claimed by the > item which the

[Wireshark-dev] Can't compile with cmake

2015-02-18 Thread Dario Lombardo
Today I can't compile wireshark using cmake. Using git bisect I've found out that this commit is responsible for that 7263af87c6b0019c1bfda0f66fdc991330941892 I'm looking forward in the code to find out what exactly broke the compilation. Dario. ___

Re: [Wireshark-dev] Can't compile with cmake

2015-02-18 Thread Dario Lombardo
lto: > wireshark-dev-boun...@wireshark.org] *On Behalf Of *Alexis La Goutte > *Sent:* den 18 februari 2015 14:27 > *To:* Developer support list for Wireshark > *Subject:* Re: [Wireshark-dev] Can't compile with cmake > > > > Hi Dario, > > What the warning ? > > >

Re: [Wireshark-dev] Can't compile with cmake

2015-02-18 Thread Dario Lombardo
https://code.wireshark.org/review/7235 (1 line ;)). On Wed, Feb 18, 2015 at 2:44 PM, Dario Lombardo wrote: > I've found out what is happened. A file (qcustomplot.cpp) was missing. I'm > pushing the patch. > > On Wed, Feb 18, 2015 at 2:30 PM, Anders Broman > wrote: >

Re: [Wireshark-dev] Google deprecating OpenID 2.0

2015-02-22 Thread Dario Lombardo
Shouldn't it be enough to log in into gerrit using google+ instead of google? The link Graham provided states that google+ implements the new version and supports google accounts (updated or not to g+). On Feb 22, 2015 6:10 PM, "Richard Sharpe" wrote: > On Sun, Feb 22, 2015 at 9:01 AM, Bill Meier

Re: [Wireshark-dev] Google deprecating OpenID 2.0

2015-02-23 Thread Dario Lombardo
Just had a try. Doesn't work for me too. On Mon, Feb 23, 2015 at 8:16 AM, Michal Labedzki wrote: > Did you try log with Google+? I do not have any idea what is username > for Google+ :) (or probably that does not work for me) > > On 23 February 2015 at 08:08, Dario

Re: [Wireshark-dev] Google deprecating OpenID 2.0

2015-02-23 Thread Dario Lombardo
On Mon, Feb 23, 2015 at 10:15 AM, Michal Labedzki wrote: > Ok. I had feedback about Google+. Username is that long number after > slash in URL when you are log in. Somehow it works... (created the > second account... [no Core permission there...]) > Can you provide more details? Which URL are yo

Re: [Wireshark-dev] Google deprecating OpenID 2.0

2015-02-23 Thread Dario Lombardo
ichal Labedzki wrote: > URL from address bar... Also there is no changes from my other > account, so I called it "the second". > > On 23 February 2015 at 10:22, Dario Lombardo > wrote: > > > > > > On Mon, Feb 23, 2015 at 10:15 AM, Michal Labedzki > >

[Wireshark-dev] ISIS ISO

2015-02-26 Thread Dario Lombardo
I've found an undecoded byte in the ISIS dissector. Before submitting a patch, I usually check with the reference standard (RFC, or others) the correctness of what I found. I found http://1.bp.blogspot.com/-9_nvv3M8ToU/T0-QsqCGc3I/AsI/YcBnXq2mkQI/s1600/pdu+format+ii.PNG Does anyone have a

[Wireshark-dev] Menagerie

2015-02-27 Thread Dario Lombardo
Browsing the buildbot site, I've read somewhere about menagerie. I suppose it is a large set of file that is used as regression test. Is it correct? Is it possible to download it? And to upload new samples to it? Thanks. Dario. ___

Re: [Wireshark-dev] Menagerie

2015-02-27 Thread Dario Lombardo
On Fri, Feb 27, 2015 at 1:55 PM, Evan Huus wrote: > > I'm not sure if there is a more convenient way to download the entire > menagerie available to the general public. Who can know that? Gerald maybe? It would be very useful when conducting large scale tests to have access to a local copy of t

Re: [Wireshark-dev] Menagerie

2015-02-27 Thread Dario Lombardo
t; > > > P.S. This is a snapshot of the menagerie as of today, of course. > > > > On Fri, Feb 27, 2015 at 8:00 AM, Dario Lombardo > > wrote: > >> On Fri, Feb 27, 2015 at 1:55 PM, Evan Huus wrote: > >>> > >>> > >>> I'm not su

Re: [Wireshark-dev] Menagerie

2015-02-27 Thread Dario Lombardo
need > to open a hole in my firewall or something. I'm at work now anyways, > so I'll look at it again tonight unless somebody beats me to it. > > Evan > > On Fri, Feb 27, 2015 at 9:07 AM, Dario Lombardo > wrote: > > Should be supported by your torrent clien

Re: [Wireshark-dev] Menagerie

2015-02-27 Thread Dario Lombardo
On Fri, Feb 27, 2015 at 3:19 PM, Ed Beroset wrote: > > From the originally sent torrent, it seems to be 1.88G. I'm interested in > this too and could seed pretty much perpetually once we get it started. > I would rather prefer a rsync-compatible interface. The scenario I'm figuring out is that

Re: [Wireshark-dev] Menagerie

2015-02-27 Thread Dario Lombardo
On Fri, Feb 27, 2015 at 3:36 PM, Evan Huus wrote: > I have rsync set up via ssh to the host server, but I'm pretty sure we > can't just give everyone ssh access :) > > Yes of course :). Maybe a public interface like http (or even rsync should be unautenticated, but I have no personal experience u

[Wireshark-dev] Undissected reserved fields

2015-02-27 Thread Dario Lombardo
I'm playing with the "undissected bytes" functionality of wireshark, patching some dissectors that clearly lack some fields. But now I've found some of them that fall in a "grey area" and I'd lilke to discuss with other devels the best way to go on. I've found that many dissectors lack decoding of

Re: [Wireshark-dev] Menagerie

2015-03-02 Thread Dario Lombardo
Evan, I'm not still able to download the torrent. Anyone tried and succeded? Can't the daily menagerie be exposed via a more convenient interface like http? I don't think the generated traffic would flood the server, especially if the files are compressed in a tar.bz2 or a zip.

Re: [Wireshark-dev] Menagerie

2015-03-02 Thread Dario Lombardo
On Mon, Mar 2, 2015 at 2:16 PM, Evan Huus wrote: > > The fastest way to get a decent menagerie right now might be to write a > script that scrapes all public bugzilla attachments... That's where the > majority of our menagerie comes from anyways. > I downloaded samples from wireshark's wiki, and

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

2015-03-05 Thread Dario Lombardo
How does the transfer into gerrit works? Is there a dummy account that commits and merges automatically? What about credits for contributions? Are they trasferred in some way from tx to git? Dario. ___ Sent via:Wireshark-de

[Wireshark-dev] Packet editor

2015-03-05 Thread Dario Lombardo
Guys, do you know wireedit? https://wireedit.com/ I looks like pretty close to how I would have figured out the "packet editor" feature in wireshark. Unfortunately it is not open source nor natively for linux (w32 bin with wine 8-|), so my testing stopped at their how-to video. Is there anyone ac

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

2015-03-20 Thread Dario Lombardo
On Fri, Mar 20, 2015 at 1:46 AM, Gerald Combs wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I'm proud to announce the release of Wireshark 1.99.5. > Hi Gerald Just out of curiosity... why 2 releases so close? Dario. _

Re: [Wireshark-dev] Wireshark code review

2015-03-25 Thread Dario Lombardo
Since you now have 2 changes submitted, you should abandon one of them (do it from the web interface), then follow Alexis' suggestion about sqashing and amending, then push the final revision into the survived change (do it using the correct change-id, read it from the web interface again). I don'

Re: [Wireshark-dev] Wireshark code review

2015-03-25 Thread Dario Lombardo
On Wed, Mar 25, 2015 at 10:03 AM, Alexis La Goutte < alexis.lagou...@gmail.com> wrote: > > > From local branch ? or remote branch ? (master / master-1.12...) > >> >> >From local. ___ Sent via:Wireshark-dev mailing list Ar

Re: [Wireshark-dev] Gerrit upgrade tomorrow

2015-05-08 Thread Dario Lombardo
Hi Gerald Do we still need to re-bind the google account to the actual gerrit profile or will be automatically done based on the email address? Thanks Dario. On Fri, May 8, 2015 at 12:12 AM, Gerald Combs wrote: > Gerrit 2.10.4 has been released, which includes improved support for OAuth: > > > h

Re: [Wireshark-dev] Gerrit upgrade tomorrow

2015-05-12 Thread Dario Lombardo
On Sat, May 9, 2015 at 1:34 PM, Graham Bloice wrote: > > Seems to work for me, without needing to relink my old Google identity. > > Works for me, as well. ___ Sent via:Wireshark-dev mailing list Archives:https://www

Re: [Wireshark-dev] Wrong URL at https://www.wireshark.org/docs/wsug_html_chunked/ChIntroHelp.html#ChIntroQA

2015-07-02 Thread Dario Lombardo
In wireshark's bugzilla you can file a bug, for website also. https://bugs.wireshark.org/bugzilla/enter_bug.cgi On Thu, Jul 2, 2015 at 12:30 AM, Rouslan Ryabykh wrote: > Hello. Didn't find enough time to know where to send an appropriate > address to send the info, so let it be here. > There is

[Wireshark-dev] hadoop dissector

2015-07-02 Thread Dario Lombardo
Hi list I opened a hadoop 2.6 capture file with the current master and I found that the hadoop dissector fails in opening the file (wrong dissection). This is probably related to the changes in the wire protocol that have not been reflected into the current dissector. So I decided to start understa

Re: [Wireshark-dev] hadoop dissector

2015-07-03 Thread Dario Lombardo
al author(s). Gerrit (and just Buzilla before that) > isn't THAT hard to navigate. Are we missing something? Are our code > standards too strict? > > > > > -Original Message- > From: Dario Lombardo > To: Developer support list for Wireshark > Sent: Thu, J

Re: [Wireshark-dev] How do I submit changes to gerrit again?

2015-07-03 Thread Dario Lombardo
Hi Richard If you commit with SSH, you can upload your public key in gerrit (upper right corner -> settings -> SSH public keys). If you commit with HTTP, you should use the password gerrit provides you (upper right cornet -> settings -> HTTP password). Dario. On Fri, Jul 3, 2015 at 5:57 AM, Richar

[Wireshark-dev] Crash during fuzzing

2015-08-10 Thread Dario Lombardo
Hi list II was fuzzing a protocol, and I experienced a crash. The fuzz-test.sh gave me this output $ ../tools/fuzz-test.sh -b run ../data/hpfeed_all_packets_sample.pcap [...] Starting pass 130: ../data/hpfeeds_all_packets_sample.pcap: (-nVxr) (-nr) OK Starting pass 131: ../data/hpfeeds_al

Re: [Wireshark-dev] Crash during fuzzing

2015-08-10 Thread Dario Lombardo
n Mon, Aug 10, 2015 at 3:52 PM, Dario Lombardo > wrote: > > Hi list > > II was fuzzing a protocol, and I experienced a crash. The fuzz-test.sh > gave > > me this output > > > > $ ../tools/fuzz-test.sh -b run ../data/hpfeed_all_packets_sample.pcap > > [...

Re: [Wireshark-dev] Crash during fuzzing

2015-08-10 Thread Dario Lombardo
On Mon, Aug 10, 2015 at 10:39 PM, Pascal Quantin wrote: > Hi Dario, > > Le 10 août 2015 10:27 PM, "Dario Lombardo" > a écrit : > > > > No crash still happening... > > > > $ ../tools/test-captures.sh -b run > ../data/hpfeeds

<    1   2   3   4   5