On Feb 21, 2018, at 8:48 AM, Guy Harris wrote:
> On Jan 25, 2018, at 3:13 PM, Guy Harris wrote:
>
>> On Jan 25, 2018, at 2:15 PM, Roland Knall wrote:
>>
>>> But as far as versions go, it was agreed at SFEU17, that all dependencies
>>> for 2.4 must be set for 2.6 as well. 3.0 is when we cut o
On Feb 20, 2018, at 4:23 PM, Peter Meiser wrote:
> I finally found the root cause. It's not the error message which was shown.
> This totally misleaded me to look for the real root cause.
>
> The problem was the otool command which checks for the file type.
>
> --- a/packaging/macosx/osx-app.s
On Jan 25, 2018, at 3:13 PM, Guy Harris wrote:
> On Jan 25, 2018, at 2:15 PM, Roland Knall wrote:
>
>> But as far as versions go, it was agreed at SFEU17, that all dependencies
>> for 2.4 must be set for 2.6 as well. 3.0 is when we cut off, and for now, I
>> would keep it that way.
>>
>> 2.6
https://www.wireshark.org/export.html
Regards
Anders
From: Wireshark-dev [mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of
Ellis, Danielle R.
Sent: den 20 februari 2018 16:41
To: wireshark-dev@wireshark.org
Cc: Ellis, Danielle R.
Subject: [Wireshark-dev] Request for ECCN (Export Control
Hi there,
It's my first time developing a dissector, so apologize in advance if my
question is too obvious for you guys.
I'm trying to code a dissector (I'm using LUA) for a quick test. It
should match a piece of traffic inside a ESP tunnel. I have seen that
other dissectors are working inside th
On Wed, Feb 21, 2018 at 7:41 AM, Graham Bloice
wrote:
>
>
> On 21 February 2018 at 15:24, Richard Sharpe
> wrote:
>>
>> On Wed, Feb 21, 2018 at 2:55 AM, Graham Bloice
>> wrote:
>> >
>> >
>> > On 20 February 2018 at 18:01, Richard Sharpe
>> >
>> > wrote:
>> >>
>> >> Hi,
>> >>
>> >> I have notice
On 21 February 2018 at 15:24, Richard Sharpe
wrote:
> On Wed, Feb 21, 2018 at 2:55 AM, Graham Bloice
> wrote:
> >
> >
> > On 20 February 2018 at 18:01, Richard Sharpe <
> realrichardsha...@gmail.com>
> > wrote:
> >>
> >> Hi,
> >>
> >> I have noticed over the last few days that Windows builds are
Hi,
I finally found the root cause. It's not the error message which was shown.
This totally misleaded me to look for the real root cause.
The problem was the otool command which checks for the file type.
--- a/packaging/macosx/osx-app.sh
+++ b/packaging/macosx/osx-app.sh
@@ -421,7 +421,7 @@ rp
Good Day,
We are looking at potentially getting the WireShark software installed for our
company. We were needing your ECCN in order to check the compliance on
exporting. Can you please provide me with your ECCN (Export Controls
Classification Number) on WireShark?
Thank you,
Danielle Ellis
A
On Wed, Feb 21, 2018 at 2:55 AM, Graham Bloice
wrote:
>
>
> On 20 February 2018 at 18:01, Richard Sharpe
> wrote:
>>
>> Hi,
>>
>> I have noticed over the last few days that Windows builds are failing
>> quite a lot even though the Linux builds are not.
>>
>> Also, I cannot seem to find the reason
On 02/20/2018 10:39 PM, Richard Sharpe wrote:
On Tue, Feb 20, 2018 at 7:07 PM, Ed Beroset wrote:
On 01/31/2018 09:44 AM, Ed Beroset wrote:
I've submitted code to Wireshark in the past, but not since Gerrit. I
tried again yesterday to register and now I remember why it's been so long
-- I can
On 20 February 2018 at 18:01, Richard Sharpe
wrote:
> Hi,
>
> I have noticed over the last few days that Windows builds are failing
> quite a lot even though the Linux builds are not.
>
> Also, I cannot seem to find the reason for the build failures.
>
> Is it something I am doing?
>
>
Do you mea
12 matches
Mail list logo
