Should be fixed now, in master.
-hadriel
> On Jul 3, 2015, at 11:20 PM, Hadriel Kaplan wrote:
>
> Yeah, I figured it would break Lua when I saw his changes on gerrit this
> morning, but he was doing the changes in little pieces so I thought I’d wait
> until some of it got into master before d
Yeah, I figured it would break Lua when I saw his changes on gerrit this
morning, but he was doing the changes in little pieces so I thought I’d wait
until some of it got into master before doing the necessary changes to wslua.
-hadriel
> On Jul 3, 2015, at 9:57 PM, Evan Huus wrote:
>
> The
Hi list,
Given that current Wireshark can't make use of NPcap because of the DLL
search path problem mentioned in
https://www.wireshark.org/lists/wireshark-dev/201506/msg00030.html, I'd
like to make a patch for Wireshark. As it is a security consideration that
Wireshark don't want to search the DL
Thanks for info, Graham! It seems that WinPcap will view stability as the
primary goal. While as a Summer of Code project, NPcap will try to move as
fast as possible especially for these months. I am even planning to add
loopback packet capturing for NPcap and have made some progress these days,
an
The buildbot test suite is currently failing on the lua step, I
believe because Peter's recent init/cleanup split has changed the
number of times the init function is called, which is breaking
expectations in the lua bindings somewhere.
The fix may be as simple as changing the "expected number of
On Fri, Jul 3, 2015 at 11:53 AM, Helge wrote:
> Am Fri, 3 Jul 2015 11:26:08 +0200
> schrieb Pascal Quantin :
>
>> if could go into the master:
>> >
>> > 1) it is written in c++. Would it be acceptable?
>>
>> No for now we are not accepting any C++ dissector.
>>
>> > 2) it uses stl maps. Would it b
On 3 July 2015 at 17:29, Yang Luo wrote:
> Hi list,
>
> Since the last mail about how to make NPcap available for Wireshark, I
> have been waiting for WinPcap's official repo's news and I fortunately
> found this these days: https://github.com/wireshark/winpcap, is this the
> official WinPcap rep
Hi list,
Since the last mail about how to make NPcap available for Wireshark, I have
been waiting for WinPcap's official repo's news and I fortunately found
this these days: https://github.com/wireshark/winpcap, is this the official
WinPcap repo now? If yes, then what's the review policy? Like rec
Am Fri, 3 Jul 2015 11:26:08 +0200
schrieb Pascal Quantin :
> if could go into the master:
> >
> > 1) it is written in c++. Would it be acceptable?
>
> No for now we are not accepting any C++ dissector.
>
> > 2) it uses stl maps. Would it be acceptable or should it be
> > replaced by
> some "wmem
On Fri, Jul 3, 2015 at 12:49 AM, Dario Lombardo
wrote:
> 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
Hi Dario,
Le 3 juil. 2015 9:45 AM, "Dario Lombardo" a
écrit :
>
> Maybe some developer like to "develop in the wild"... that could mean
they can avoid some rules, push incomplete dissectors, or whatever else I
can't figure out. Rules for dissectors are very strict. I don't mean they
are useless,
Le 3 juil. 2015 10:29 AM, "Luis Espla" a écrit :
>
> Capture file attached and I'll go to open a bug in bugzilla
Thanks Luis, it confirms that this is a side effect of the change I was
talking about.
Pascal.
>
> On 2 July 2015 at 12:28, Pascal Quantin wrote:
>>
>> 2015-07-02 11:03 GMT+02:00 Lu
Capture file attached and I'll go to open a bug in bugzilla
On 2 July 2015 at 12:28, Pascal Quantin wrote:
> 2015-07-02 11:03 GMT+02:00 Luis Espla :
>
>> Hello,
>> Until now, I have used wireshark 1.99.5 and it can recognise http2
>> traffic, but now I have updated to 1.99.7 and I need to actív
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
Maybe some developer like to "develop in the wild"... that could mean they
can avoid some rules, push incomplete dissectors, or whatever else I can't
figure out. Rules for dissectors are very strict. I don't mean they are
useless, but they have been set to have a very robust code _inside_
wireshark
15 matches
Mail list logo
