Re: [Wireshark-dev] When to drop Qt 4 support and require Qt 5?

[Guy Harris]

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 off, and for now, I 
>>> would keep it that way.
>>> 
>>> 2.6 should be the final LTS for gtk and qt4.8
>> 
>> Speaking of dropping support for older Qt versions and the OSes that require 
>> them:
>> 
>> Qt 5.3.2 is the last version that supports macOS 10.6/Snow Leopard; do we 
>> want to drop support for Snow Leopard at some point?
> 
> This person:
> 
>   
> https://ask.wireshark.org/question/1760/crash-at-start-up-i-tried-all-versions-i-am-not-allowed-to-download-anything-other-than-wireshark-itself/
> 
> is still using Snow Leopard:
> 
>> Date/Time:   2018-02-21 08:32:09.445 -0500
>> OS Version:  Mac OS X 10.6.8 (10K549)

...and it's crashing due to what appears to be a low-level support library 
issue (as in "GCC support library") that has something to do with changes 
between 10.6 and 10.7.  I've put a long discussion in as the answer, and asked 
the person to file a bug.  I haven't figured out what needs to be done 
differently in the build procedure - or the procedure for building the support 
libraries on macOS - to fix it.

___
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

Re: [Wireshark-dev] error during DMG creation under macOS 10.13.2

[Guy Harris]

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.sh
> +++ b/packaging/macosx/osx-app.sh
> @@ -421,7 +421,7 @@ rpathify_file () {
>   #
>   # OK, what type of file is this?
>   #
> - filetype=$( otool -hv "$1" | sed -n '4p' | awk '{print $5}' ; exit 
> ${PIPESTATUS[0]} )
> + filetype=$( otool -hv "$1" | grep 'MH_MAGIC_64' | awk '{print $5}' ; 
> exit ${PIPESTATUS[0]} )
>   if [ $? -ne 0 ] ; then
>   echo "Unable to rpathify $1 in $( pwd ): file type failed."
>   exit 1

Checked in, but using MH_MAGIC rather than MH_MAGIC_64.
___
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

Re: [Wireshark-dev] When to drop Qt 4 support and require Qt 5?

[Guy Harris]

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 should be the final LTS for gtk and qt4.8
> 
> Speaking of dropping support for older Qt versions and the OSes that require 
> them:
> 
> Qt 5.3.2 is the last version that supports macOS 10.6/Snow Leopard; do we 
> want to drop support for Snow Leopard at some point?

This person:


https://ask.wireshark.org/question/1760/crash-at-start-up-i-tried-all-versions-i-am-not-allowed-to-download-anything-other-than-wireshark-itself/

is still using Snow Leopard:

> Date/Time:   2018-02-21 08:32:09.445 -0500
> OS Version:  Mac OS X 10.6.8 (10K549)
___
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

Re: [Wireshark-dev] Request for ECCN (Export Control Classification Number) for WireShark

[Anders Broman]

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 Classification 
Number) for WireShark

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
Asset Management Analyst | Koch Business Solutions, LP | (316)202-7548 | 
danielle.el...@kbslp.com

___
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

[Wireshark-dev] Dissector for decryted content

[Jose Selvi]

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 the decrypted content, but not mine.

Browsing forums, I found this:

https://osqa-ask.wireshark.org/questions/58217/how-do-i-dissect-decrypted-ssl-data-when-im-using-a-master-secret-log

However, I can't find similar options for ESP, so I guess it only works
for SSL.

Any hint will be more than welcomed.
Cheers.
___
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

Re: [Wireshark-dev] Windows builds seem to fail with some frequency even though the Linux builds don't!

[Richard Sharpe]

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 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 mean locally, or the Petri-dish or build slaves?
>>
>> Petri-dish
>>
>> For example, this one:
>>
>> https://buildbot.wireshark.org/petri-dish/builders/Windows%20Petri%20Dish%20x64/builds/2307
>>
>> I can't figure out what is wrong.
>>
>> There are a whole lot of docbook errors in there, but the Linux build
>> succeeded and I did not touch the docbook stuff, I believe:
>>
>
> There have been some infrastructure changes around the docbook generation
> recently, switching over to using asciidoctor that may have made things a
> little rocky.
>
> Clutching at a straw, as this change has been worked on for a while,
> assuming your changes are in a local git branch, have you tried rebasing the
> branch to master?

I typically pull in master fairly frequently, but let me try that.

-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)
___
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

Re: [Wireshark-dev] Windows builds seem to fail with some frequency even though the Linux builds don't!

[Graham Bloice]

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 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 mean locally, or the Petri-dish or build slaves?
>
> Petri-dish
>
> For example, this one:
> https://buildbot.wireshark.org/petri-dish/builders/
> Windows%20Petri%20Dish%20x64/builds/2307
>
> I can't figure out what is wrong.
>
> There are a whole lot of docbook errors in there, but the Linux build
> succeeded and I did not touch the docbook stuff, I believe:
>
>
There have been some infrastructure changes around the docbook generation
recently, switching over to using asciidoctor that may have made things a
little rocky.

Clutching at a straw, as this change has been worked on for a while,
assuming your changes are in a local git branch, have you tried rebasing
the branch to master?



>   120>CUSTOMBUILD : compilation error : file
> http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl
> line 33 element include
> [C:\buildbot\builders\windows-x86-64-petri-dish\windows-x86-
> 64-petri-dish\build\cmbuild\docbook\developer_guide_html.vcxproj]
>  xsl:include : unable to load
> http://docbook.sourceforge.net/release/xsl/current/common/targets.xsl
>  http://docbook.sourceforge.net/release/xsl/current/html/
> autoidx.xsl:4:
> warning: failed to load external entity
> "http://docbook.sourceforge.net/release/xsl/current/common/entities.ent";
>  %common.entities;
>   ^
>  Entity: line 1:
>   %common.entities;
>^
>  http://docbook.sourceforge.net/release/xsl/current/html/
> autoidx.xsl:33:
> parser error : Entity 'primary' not defined
>   use="translate(substring(&primary;, 1,
> 1),&lowercase;,&uppercase;)"/>
> ^
>  http://docbook.sourceforge.net/release/xsl/current/html/
> autoidx.xsl:33:
> parser error : Entity 'lowercase' not defined
>   use="translate(substring(&primary;, 1,
> 1),&lowercase;,&uppercase;)"/>
>^
>  http://docbook.sourceforge.net/release/xsl/current/html/
> autoidx.xsl:33:
> parser error : Entity 'uppercase' not defined
>   use="translate(substring(&primary;, 1,
> 1),&lowercase;,&uppercase;)"/>
>
> ^
>  http://docbook.sourceforge.net/release/xsl/current/html/
> autoidx.xsl:37:
> parser error : Entity 'primary' not defined
>   use="&primary;"/>
> ^
>  http://docbook.sourceforge.net/release/xsl/current/html/
> autoidx.xsl:41:
> parser error : Entity 'primary' not defined
>   use="concat(&primary;, &sep;, &secondary;)"/>
>^
>  http://docbook.sourceforge.net/release/xsl/current/html/
> autoidx.xsl:41:
> parser error : Entity 'sep' not defined
>   use="concat(&primary;, &sep;, &secondary;)"/>
>   ^
>
>
> --
> Regards,
> Richard Sharpe
> (何以解憂？唯有杜康。--曹操)
>
> --
Graham Bloice
___
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

Re: [Wireshark-dev] error during DMG creation under macOS 10.13.2

[Peter Meiser]

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 @@ rpathify_file () {
#
# OK, what type of file is this?
#
-   filetype=$( otool -hv "$1" | sed -n '4p' | awk '{print $5}' ; exit 
${PIPESTATUS[0]} )
+   filetype=$( otool -hv "$1" | grep 'MH_MAGIC_64' | awk '{print $5}' ; 
exit ${PIPESTATUS[0]} )
if [ $? -ne 0 ] ; then
echo "Unable to rpathify $1 in $( pwd ): file type failed."
exit 1


After changing the command, the DMG package is created correctly.

Regards,
Peter

PS: Please add me to CC if you answer to me as I'm not subscribed to the 
mailing list.


Am 20.01.2018 um 08:31 schrieb Peter Meiser:
> Hi,
> 
> I try to compile Wireshark under macOS 10.13.2. I installed the needed 
> libraries and tools via brew (see the list and versions below).
> 
> "make" runs fine, "make dmg_package" shows the an error inbetween so that the 
> some libs the wrong rpath, e.g. libhogweed.4.dylib or ethercat.so.
> 
> Here's the error message:
> 
> error: 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool:
>  no LC_RPATH load command with path: /usr/local/Cellar/qt/5.10.0_1/lib found 
> in: Wireshark.app/Contents/MacOS/Wireshark (for architecture x86_64), 
> required for specified option "-delete_rpath 
> /usr/local/Cellar/qt/5.10.0_1/lib"
> 
> Could someone tell me how to fix this issue?
> 
> Thanks in advance.
> Best regards,
> Peter
> 
> 
> 
> macOS:build peter$ brew list --versions
> asciidoc 8.6.10_1
> boost 1.66.0
> c-ares 1.13.0
> cmake 3.10.1
> docbook 5.0
> geoip 1.6.11
> gettext 0.19.8.1
> glib 2.54.3
> gmp 6.1.2_1
> gnutls 3.5.16
> jansson 2.10
> jemalloc 5.0.1
> jpeg 9b
> libev 4.24
> libevent 2.1.8
> libffi 3.2.1
> libgcrypt 1.8.2
> libgpg-error 1.27
> libsmi 0.5.0
> libssh 0.7.5
> libssh2 1.8.0
> libtasn1 4.12
> libtiff 4.0.9_1
> libunistring 0.9.8
> lua@5.1 5.1.5_5
> lynx 2.8.8rel.2_1
> lz4 1.8.0
> nettle 3.4
> nghttp2 1.29.0
> openssl 1.0.2n
> p11-kit 0.23.9
> pcre 8.41
> pkg-config 0.29.2
> qt 5.10.0_1
> snappy 1.1.7_1
> spandsp 0.0.6_1
> 
___
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

[Wireshark-dev] Request for ECCN (Export Control Classification Number) for WireShark

[Ellis, Danielle R.]

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
Asset Management Analyst | Koch Business Solutions, LP | (316)202-7548 | 
danielle.el...@kbslp.com

___
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

Re: [Wireshark-dev] Windows builds seem to fail with some frequency even though the Linux builds don't!

[Richard Sharpe]

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 for the build failures.
>>
>> Is it something I am doing?
>>
>
> Do you mean locally, or the Petri-dish or build slaves?

Petri-dish

For example, this one:
https://buildbot.wireshark.org/petri-dish/builders/Windows%20Petri%20Dish%20x64/builds/2307

I can't figure out what is wrong.

There are a whole lot of docbook errors in there, but the Linux build
succeeded and I did not touch the docbook stuff, I believe:

  120>CUSTOMBUILD : compilation error : file
http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl
line 33 element include
[C:\buildbot\builders\windows-x86-64-petri-dish\windows-x86-64-petri-dish\build\cmbuild\docbook\developer_guide_html.vcxproj]
 xsl:include : unable to load
http://docbook.sourceforge.net/release/xsl/current/common/targets.xsl
 http://docbook.sourceforge.net/release/xsl/current/html/autoidx.xsl:4:
warning: failed to load external entity
"http://docbook.sourceforge.net/release/xsl/current/common/entities.ent";
 %common.entities;
  ^
 Entity: line 1:
  %common.entities;
   ^
 http://docbook.sourceforge.net/release/xsl/current/html/autoidx.xsl:33:
parser error : Entity 'primary' not defined
  use="translate(substring(&primary;, 1,
1),&lowercase;,&uppercase;)"/>
^
 http://docbook.sourceforge.net/release/xsl/current/html/autoidx.xsl:33:
parser error : Entity 'lowercase' not defined
  use="translate(substring(&primary;, 1,
1),&lowercase;,&uppercase;)"/>
   ^
 http://docbook.sourceforge.net/release/xsl/current/html/autoidx.xsl:33:
parser error : Entity 'uppercase' not defined
  use="translate(substring(&primary;, 1,
1),&lowercase;,&uppercase;)"/>

^
 http://docbook.sourceforge.net/release/xsl/current/html/autoidx.xsl:37:
parser error : Entity 'primary' not defined
  use="&primary;"/>
^
 http://docbook.sourceforge.net/release/xsl/current/html/autoidx.xsl:41:
parser error : Entity 'primary' not defined
  use="concat(&primary;, &sep;, &secondary;)"/>
   ^
 http://docbook.sourceforge.net/release/xsl/current/html/autoidx.xsl:41:
parser error : Entity 'sep' not defined
  use="concat(&primary;, &sep;, &secondary;)"/>
  ^


-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)
___
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

Re: [Wireshark-dev] gerrit registration problems

[Ed Beroset]

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't seem to register.  Is this the place to ask for help, or is there
a better way to do it?



I may or may not be registered and I may or may not have submitted a patch.
I followed the instructions here:
https://www.wireshark.org/docs/wsdg_html_chunked/ChSrcContribute.html

Git seems to have accepted the push, but I don't see any evidence that it
exists when I go to https://code.wireshark.org/review/#/dashboard/self

Any troubleshooting clues, or is it normal that a successful push has no
observable manifestation?


Is it this one?

https://code.wireshark.org/review/#/c/25956/


Yes!  It seems that I may have two registrations, but I only know one 
password.  Who has admin rights and can help me combine them?  Or is 
there some self-service thing I can do?


Ed
___
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

Re: [Wireshark-dev] Windows builds seem to fail with some frequency even though the Linux builds don't!

[Graham Bloice]

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 mean locally, or the Petri-dish or build slaves?

The build servers have been going well lately, so it would seem that it's
something in your environment.  You'll need to post the output of your
build, redirect to a file, e.g. msbuild ... 2>&1 > build.txt.  When
debugging build issues it helps to turn off parallel builds so drop the
"/m" from the command.



> --
> Regards,
> Richard Sharpe
> (何以解憂？唯有杜康。--曹操)
>


-- 
Graham Bloice
___
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