On 08/05/2016 04:03 AM, Michael Mann wrote:
I thought I'd try to cut down on some of the "noise" created by
checklicenses.py and creating exceptions for files that obviously don't
need a license header (COPYING/AUTHORS files in plugins for example). I
thought it would simply be a matter of run
I confirm ;-) (too slow...)
But it is strange don't get the same warning between Ubuntu 14.04 and
16.04
Cheers
Le vendredi 5 août 2016, João Valverde a
écrit :
>
>
> On 08/05/2016 04:03 AM, Michael Mann wrote:
>
>> I thought I'd try to cut down on some of the "noise" created by
>> checklic
On 08/05/2016 08:56 AM, Alexis La Goutte wrote:
I confirm ;-) (too slow...)
But it is strange don't get the same warning between Ubuntu 14.04 and
16.04
I assume the licensecheck regexes changed. Michael may need to be
running 16.04 to test this with any accuracy.
While on the subject
On 5 August 2016 at 07:54, Paul Offord wrote:
> Hi,
>
>
>
> I have written a plugin dissector that uses some Qt5 functions. To build
> with Visual Studio 2013 I have to manually add some Qt5 libs via Project ->
> Properties -> Linker -> Input -> Additional Dependencies. This works OK
> but when
Paul, could you give an example, why you chose Qt libraries over Gtk? Was
it not possible, or is it a personal choice?
I do have plugins for WS, which use Qt, but not for dissectors, so I am
just curious, what was missing.
regards
Roland
On Fri, Aug 5, 2016 at 11:20 AM, Graham Bloice
wrote:
>
Thanks Graham.
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Graham Bloice
Sent: 05 August 2016 10:21
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Adding Qt5 libs via VS Additional Dependencies
On 5 August 2016 at 07
Hi Roland,
The dissector is called Syncro and it allows a remote process to access the WS
plugin_if extensions through a TCP connection. We wanted to be able to achieve
this without building a custom version of WS and so built it as a dissector.
We don’t use any of the GUI stuff from Qt, just
Hi,
As Graham I’m suspicious about GUI code in plugins. Code “enhancing” the GUI
should probably be placed in the respective GUI folder(Qt or GTK) and hook into
the menus.
I suppose that currently require you to build a custom Wireshark version. Can’t
your GUI code be made part of the standard v
On Aug 5, 2016, at 2:00 AM, João Valverde
wrote:
> On 08/05/2016 08:56 AM, Alexis La Goutte wrote:
>> I confirm ;-) (too slow...)
>>
>> But it is strange don't get the same warning between Ubuntu 14.04 and
>> 16.04
>
> I assume the licensecheck regexes changed. Michael may need to be runni
On 5 August 2016 at 10:45, Guy Harris wrote:
> On Aug 5, 2016, at 2:00 AM, João Valverde ulisboa.pt> wrote:
>
> > On 08/05/2016 08:56 AM, Alexis La Goutte wrote:
> >> I confirm ;-) (too slow...)
> >>
> >> But it is strange don't get the same warning between Ubuntu 14.04 and
> >> 16.04
> >
>
On 5 August 2016 at 10:52, Graham Bloice
wrote:
>
>
> On 5 August 2016 at 10:45, Guy Harris wrote:
>
>> On Aug 5, 2016, at 2:00 AM, João Valverde > .pt> wrote:
>>
>> > On 08/05/2016 08:56 AM, Alexis La Goutte wrote:
>> >> I confirm ;-) (too slow...)
>> >>
>> >> But it is strange don't get the sa
So, if I understand it correctly, it is a RPC interface? I still think,
implementing this as a dissector is a major overkill, and will also lead to
issues further down the line, if dissectory API changes or similar issues.
I'd implement such an interface via a simple plugin architecture, which
woul
On 08/05/2016 10:45 AM, Guy Harris wrote:
On Aug 5, 2016, at 2:00 AM, João Valverde
wrote:
On 08/05/2016 08:56 AM, Alexis La Goutte wrote:
I confirm ;-) (too slow...)
But it is strange don't get the same warning between Ubuntu 14.04 and
16.04
I assume the licensecheck regexes change
On Aug 5, 2016, at 2:52 AM, Graham Bloice wrote:
> I did look a bit for licensecheck and it appears to be a Perl script
> available as a Debian (and RPM) package devscripts as suggested by João, a
> package for Debian package maintainers. As such, it isn't available for
> Windows. The checkl
On 5 August 2016 at 11:21, Guy Harris wrote:
> On Aug 5, 2016, at 2:52 AM, Graham Bloice
> wrote:
>
> > I did look a bit for licensecheck and it appears to be a Perl script
> available as a Debian (and RPM) package devscripts as suggested by João, a
> package for Debian package maintainers. As
On 08/05/2016 11:21 AM, Guy Harris wrote:
On Aug 5, 2016, at 2:52 AM, Graham Bloice wrote:
I did look a bit for licensecheck and it appears to be a Perl script available
as a Debian (and RPM) package devscripts as suggested by João, a package for
Debian package maintainers. As such, it is
Hi Roland,
No, not really an RPC interface. Some very simple commands and events flow
back and forth, like this:
Command|GoToFrame|55
Response|MovedToFrame|55
Event|MovedToFrame|67
We needed it to be a dissector to enable us to detect when the user moves
within a trace so that we can generate
On Aug 5, 2016, at 3:36 AM, João Valverde
wrote:
> On 08/05/2016 11:21 AM, Guy Harris wrote:
>
>> Should we just grab some version that works and include it in the tools
>> directory, so that we don't get mysterious failures when updating the
>> version of Ubuntu on the buildbot and don't fai
On 08/05/2016 11:50 AM, Guy Harris wrote:
On Aug 5, 2016, at 3:36 AM, João Valverde
wrote:
On 08/05/2016 11:21 AM, Guy Harris wrote:
Should we just grab some version that works and include it in the tools
directory, so that we don't get mysterious failures when updating the version
of U
This is exactly what I do here with my plugin. Although without the TCP
part. The method to do it without using Qt in the dissector is to implement
a tap interface in the dissector, and register the plugin on that
interface. The plugin than can start the TCP server and monitors the tap
interface an
That sounds really interesting. Eliminating the Qt code is very attractive.
I’ll look into it.
Thanks and regards…Paul
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Roland Knall
Sent: 05 August 2016 11:57
To: Developer support list for Wir
Hi All,
I’m writing a new plugin dissector (nothing to do with my previous post). I
just have the basic functions at the moment of initialiser, handoff and
dissection – copied from the WS wiki. The build in VS fails with:
Error C1083: Cannot open include file: ‘moduleinfo.h’: No such file or
Hi Paul,
2016-08-05 14:02 GMT+02:00 Paul Offord :
> Hi All,
>
>
>
> I’m writing a new plugin dissector (nothing to do with my previous post).
> I just have the basic functions at the moment of initialiser, handoff and
> dissection – copied from the WS wiki. The build in VS fails with:
>
>
>
> Er
Hi Pascal,
Ha – I feel a bit stupid for not noticing that.
Thanks and regards…Paul
From: wireshark-dev-boun...@wireshark.org
[mailto:wireshark-dev-boun...@wireshark.org] On Behalf Of Pascal Quantin
Sent: 05 August 2016 13:06
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev]
I'm trying to compile wireshark on windows, but it fails. I have low skills
on windows, so maybe I'm missing something very basic.
Any hint? Thank you.
"c:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
"c:\Development\wsbuild64\docbook\release_notes_html.vcxproj.meta
On 5 August 2016 at 13:29, Dario Lombardo
wrote:
> I'm trying to compile wireshark on windows, but it fails. I have low
> skills on windows, so maybe I'm missing something very basic.
>
> Any hint? Thank you.
>
>
>"c:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
>"
Le 5 août 2016 14:34, "Graham Bloice" a
écrit :
>
> On 5 August 2016 at 13:29, Dario Lombardo
wrote:
>>
>> I'm trying to compile wireshark on windows, but it fails. I have low
skills on windows, so maybe I'm missing something very basic.
>>
>> Any hint? Thank you.
>>
>>
>>"c:\Development\
This is were we write documentation for, in this case doc/README.plugins. You
should have a look.
> On 05 Aug 2016, at 14:08, Paul Offord wrote:
>
> Hi Pascal,
>
> Ha – I feel a bit stupid for not noticing that.
>
> Thanks and regards…Paul
>
> From: wireshark-dev-boun...@wireshark.org
>
Actually I was missing one package. Then I cleaned repo up with git clean
-dfx. Now I still don't go to the end but with
Build FAILED.
"c:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
"c:\Development\wsbuild64\copy_qt_dlls.vcxproj.metaproj" (default
target) (14) ->
I have a TCP protocol that sends multiple PDUs. So far, my dissector seems to
handle the cases where one PDU is split across multiple frames, and when
multiple PDUs are dissected in one frame. Unfortunately, I'm having issues
where the TCP dissection stops if I have multiple PDUs that are spli
On 5 August 2016 at 14:22, Dario Lombardo
wrote:
> Actually I was missing one package. Then I cleaned repo up with git clean
> -dfx. Now I still don't go to the end but with
>
> Build FAILED.
>"c:\Development\wsbuild64\Wireshark.sln" (default target) (1) ->
>"c:\Development\wsbuil
On 5 August 2016 at 14:08, John Dill wrote:
> I have a TCP protocol that sends multiple PDUs. So far, my dissector
> seems to handle the cases where one PDU is split across multiple frames,
> and when multiple PDUs are dissected in one frame. Unfortunately, I'm
> having issues where the TCP dis
>
> What Qt version? I think I've seen that one before.
>>
>
>
5.3.2.
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/w
This may be related/similar to bug 6392
(https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6392).
I believe the capture in this bug has only a few "leftover" bytes (and I
thought the issue may be related to amount of fixed data needed by dissector).
However 38 bytes seems much larger than
On 5 August 2016 at 14:56, Dario Lombardo
wrote:
> What Qt version? I think I've seen that one before.
>>>
>>
>>
> 5.3.2.
>
On Windows we're using 5.6.1
--
Graham Bloice
___
Sent via:Wireshark-dev mailing list
Archiv
I updated qt to 5.6.1. After cmake, I get
-- The following OPTIONAL packages have not been found:
* CAP
* Gettext
* M
* PkgConfig
* Qt5Core
* Qt5LinguistTools
* Qt5Multimedia
* Qt5PrintSupport
* Qt5S
On 5 August 2016 at 17:01, Dario Lombardo
wrote:
> I updated qt to 5.6.1. After cmake, I get
>
> -- The following OPTIONAL packages have not been found:
> * CAP
> * Gettext
> * M
> * PkgConfig
> * Qt5Core
> * Qt5LinguistTools
>
On 5 August 2016 at 17:13, Graham Bloice
wrote:
> On 5 August 2016 at 17:01, Dario Lombardo
> wrote:
>
>> I updated qt to 5.6.1. After cmake, I get
>>
>> -- The following OPTIONAL packages have not been found:
>> * CAP
>> * Gettext
>> * M
>> * Pkg
>Message: 1
>Date: Fri, 5 Aug 2016 14:47:59 +0100
>From: Graham Bloice
>To: Developer support list for Wireshark
>Subject: Re: [Wireshark-dev] dissecting TCP packets with multiple PDUs
>
>>On 5 August 2016 at 14:08, John Dill wrote:
>>
>> I have a TCP protocol that sends multiple PDUs. So far,
On 08/05/2016 11:53 AM, João Valverde wrote:
On 08/05/2016 11:50 AM, Guy Harris wrote:
On Aug 5, 2016, at 3:36 AM, João Valverde
wrote:
On 08/05/2016 11:21 AM, Guy Harris wrote:
Should we just grab some version that works and include it in the
tools directory, so that we don't get myste
On Aug 5, 2016, at 12:17 PM, João Valverde
wrote:
> The Debian licensecheck.pl version prior to the Smedegaard take over was
> standalone. I think we should import that to tools.
We might still want to look over the list of files currently being complained
about (and make sure that the files
On Aug 5, 2016, at 2:31 PM, Guy Harris wrote:
> 'test/run_and_catch_crashes' has non-whitelisted license 'UNKNOWN'
> 'macosx-support-lib-patches/qt-fix-pc-files' has non-whitelisted
> license 'UNKNOWN'
> 'macosx-support-lib-patches/qt-fix-pc-file' has non-whitelisted license
>
42 matches
Mail list logo
