Hi folks,
I installed 4.2.2 on a Windows Server 2012 system and got the following
error:
"The procedure entry point SystemParametersInfoForDpi could not be located
in the dynamic link library ..."
[image: image.png]
Is there a work-around?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操
_subtree et al, which means that such
filtering will not always be possible.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wiresha
he change is
> merged, while other references such as "see #4512" will simply link to the
> issue.
Thanks. Looks like I chose the wrong way :-(
> On Tue, Oct 18, 2022 at 12:46 PM Richard Sharpe
> wrote:
>>
>> Hi folks.
>>
>> What do I put in a c
Hi folks.
What do I put in a commit message to indicate that it fixes an issue?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org
On Tue, Oct 18, 2022 at 9:39 AM Pascal Quantin wrote:
>
> Hi Richard,
>
> Le mar. 18 oct. 2022 à 18:30, Richard Sharpe a
> écrit :
>>
>> Hi folks,
>>
>> How do I squeeze more than 240 chars into a string field?
>
> You can't currently. As seen in
with 3.4.8?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options
,
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
On Wed, Oct 12, 2022 at 11:10 AM Richard Sharpe
wrote:
>
> Hi folks,
>
> As a result of a recent issue and MR I suggested the use of tshark to
> extract some info but it does not work.
>
> I suggested this:
> --
> ./run/tshark -r ~/SNR* -Y &quo
tshark is extracting is the scidx numbers but not the phi and psi
values following it.
Has anyone seen this issue before? I guess I will look into it soon
but was interested to know if anyone has seen it.
--
Regards,
Richard Sharpe
(何以解憂？唯
On Tue, Aug 23, 2022 at 6:56 AM João Valverde wrote:
>
> On 8/23/22 14:29, Richard Sharpe wrote:
> > On Tue, Aug 23, 2022 at 2:30 AM João Valverde wrote:
> >> On 8/22/22 14:42, Richard Sharpe wrote:
> >>> Hi folks,
> >>>
> >>> In try
On Tue, Aug 23, 2022 at 2:30 AM João Valverde wrote:
>
> On 8/22/22 14:42, Richard Sharpe wrote:
> > Hi folks,
> >
> > In trying to introduce my contexts approach for display filters to
> > handle embedded/recursive structures in 802.11 Information Elements
> &g
Hi folks,
Is there some way that gitlab can inform me of merge requests for the
802.11 dissector?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https
for the dfilter stuff? I have been
using dftest to test my changes but it would be good to see if I have
disturbed anything.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives
On Wed, Aug 17, 2022 at 6:31 AM Richard Sharpe
wrote:
>
> On Sun, Jul 31, 2022 at 3:36 AM João Valverde wrote:
> >
> > Maybe we could add wildcards?
> >
> > |diameter.*.Result-Code
> >
> > The star represents "any nesting level", not "
ted and the generator is not
> > respecting naming schemes but they face the same issue.
> >
> > Kind regards
> > Roland
> >
> > > Am 29.07.2022 um 18:28 schrieb Richard Sharpe
> > :
> > >
> > > Hi folks,
> &g
..@wireshark.org
> > > ?subject=unsubscribe
> > >
>
>
> --
> Tmore1
> ___
> Sent via:Wireshark-dev mailing list
> Archives:https://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://www.wiresh
ftp streams could be opened in the same ssh session, how do I tell the
> subdissector with which "conversation" it should work)?
Conversation info should probably be in the pinfo, but if not, pass in
enough info to find the conversation.
--
Regards,
Ri
figure out where it failed?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org
?
--
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
s occurred!
What is going on?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wir
and do reassembly there.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman
starting
sequence number) with the ending seq number or length and pointer to
the data and a more-data flag or something.
Then, when you have all the data you can index into the hash table by
starting sequence number starting at 1.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
__
ate the Wi-Fi 6 and Wi-Fi 7 and Wi-Fi 99 additions
into separate files, for the most part.
Perhaps we would need a mechanism for Wi-Fi X+1 to override some parts
of Wi-Fi X as well, but I have no idea how to handle that for the
moment.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。-
files?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options
On Fri, Oct 29, 2021 at 7:56 AM Richard Sharpe
wrote:
>
> Hi folks,
>
> In one project I have a bunch of custom dissectors in a 3.5.0 build.
>
> They are all defined in epan/dissectors/CMakeListsCustom.txt.
>
> When I run cmake it tells me it found the custom stuff.
run make rpm-package the custom dissectors are not
built and there are not .o files in the build directory for the custom
dissectors.
Where should I look to figure out what is going wrong?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者
> Regards
> Anders
>
> -Original Message-
> From: Wireshark-dev On Behalf Of
> Richard Sharpe
> Sent: den 24 oktober 2021 15:17
> To: Developer support list for Wireshark
> Subject: [Wireshark-dev] I have added another file to wireshark but keep
> getting un
to the files list in
epan/dissectors/CMakeLists.txt.
What else should I do?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark
On Tue, Aug 31, 2021 at 7:52 AM chuck c wrote:
>
> http://www.packettrain.net/2017/07/05/wireshark-hints-multi-column/
Well, sh*t, seems there is nothing new under the sun.
> On Tue, Aug 31, 2021 at 9:49 AM Richard Sharpe
> wrote:
>>
>> Hi folks,
>>
>>
,
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
subscribe: https://www.wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:
On Thu, May 27, 2021 at 10:16 AM Moshe Kaplan wrote:
>
> I believe Peter Wu created a script a while back to do that and published it
> here: https://github.com/Lekensteyn/wireshark-fuzztools
Thanks for that.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传
Hi folks,
It seems like the OSS-FUZZ tool is very useful in finding certain
types of problems, but it would be even more useful if it could
generate a pcap file of the packets it used to find a problem.
Does anyone know how hard it would be to modify to do that?
--
Regards,
Richard Sharpe
(何以解
dd_uint("ethertype", ETHERTYPE_IEEE_1905, ieee1905_handle);
eapol_handle = find_dissector("eapol");
}
You can ignore the eapol_handle stuff unless you also plan to use
EAPOL (ieee801.X) in your protocol.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
y, I guess.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailm
.
--
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
On Wed, Apr 21, 2021 at 10:47 AM Pascal Quantin wrote:
>
> Hi Richard,
>
> Le mer. 21 avr. 2021 à 19:43, Richard Sharpe a
> écrit :
>>
>> My latest MR failed with these errors:
>>
>> -
>> C:\builds\wireshark\wireshark\ep
: '=': conversion from 'double' to 'float', possible loss
of data [C:\builds\wireshark\wireshark\build\epan\dissectors\dissectors.vcxproj]
---
They are not in packet-ieee80211.c where my changes were.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者
On Sun, Apr 18, 2021 at 9:30 PM Guy Harris wrote:
>
> On Apr 18, 2021, at 2:33 PM, Richard Sharpe
> wrote:
>
> > I am thinking of writing a wtap module to read ComView WLAN Analyzer
> > and Decoder NCFS format files.
> >
> > They are a little li
Hi folks,
I just came across this validation check in the commview wiretap code:
if (... cv_hdr.year < 1970 || cv_hdr.year >= 2038 || ...)
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wir
or different WTAP type and
write a separate dissector for those headers.
Any thoughts?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org
east if the name is all ASCII printable characters and
> contains no spaces); if it doesn't, that's a sign that the build process
> isn't robust enough.
Indeed, I routinely build in directories like wireshark-build or
wireshark--build and I have never
on a Fedora 31
system.
Has anyone seen this before?
I am currently building 3.4.4 on Fedora to see if the problem is
across more than one build of 3.4.4,
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via
did not touch those files ... what is going on?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https
wlan.ftm.ista.availability_block_2 == 0x1ff37 or
whatever.
2. Insert the whole lot as an FT_BYTES field but then it seems like
the user will have to enter the whole value, up to 32 bytes if it is
that long.
3. ??? Is there a better way?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者
on. The workflow
is quite painful.
Is there a simpler way to do this?
If not, could we add a button for Next packet satisfying filter?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
On Tue, Mar 16, 2021 at 9:23 PM Richard Sharpe
wrote:
>
> Hi folks,
>
> I have been seeing some compiler errors on CentOS 8 like the following:
>
> ---
> /home/rsharpe/src/wireshark/epan/packet.c:142:25: error:
> cast between incompatible f
two arguments, while
g_free takes only one argument.
How do I avoid the warning/error?
Also, should we fix these things up?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
On Sun, Mar 14, 2021 at 4:43 PM Richard Sharpe
wrote:
>
> Hi folks,
>
> I am trying to sign into the gitlab UI and it just sits there saying
> it is checking my browser and telling me it may take up to 5 seconds
> but never gets there.
Seems to be a browser issue. I tried a
Hi folks,
I am trying to sign into the gitlab UI and it just sits there saying
it is checking my browser and telling me it may take up to 5 seconds
but never gets there.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者
n appropriate record header ...
On the other hand, I am unaware of any code that does that.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/list
ters?
Do you really need the parameter? If so, does adding _U_ after it not
fix the problem?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:h
On Mon, Feb 1, 2021 at 7:22 AM Pascal Quantin wrote:
>
> Hi Richard,
>
> Le lun. 1 févr. 2021 à 16:09, Richard Sharpe a
> écrit :
>>
>> Hi folks,
>>
>> In one of the builds for my merge request around Robust AV Streaming,
>> I got this:
>&g
(but perhaps the original code was wrong.)
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https
reak in between posts as usual).
Hi Joey,
Is there any code we can look at?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wire
On Sat, Jan 2, 2021 at 11:07 PM Pascal Quantin wrote:
>
> Hi Richard,
>
> Le dim. 3 janv. 2021 à 01:01, Richard Sharpe a
> écrit :
>>
>> Hi folks,
>>
>> I just tried to push some changes to my upstream repo prior to
>> creating a merge reque
branch is called ieee80211-PV1 ...
Is this something I can change in my fork or do I have to use
something like cherry-pick-.xxx?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing
Hi folks,
I came across this:
https://www.crowdsupply.com/traverse-technologies/ten64/updates/10g-options-and-performance
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
ation and my problem was elsewhere :-)
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.w
and
then keep dissecting.
How can I handle this?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https
both looking at the same capture, I think, when
he hit the problem.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Un
apply as a column?
It was the SMB2 Time from request field in responses.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wiresha
Mac OS X?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wire
tallation and
then re-adding it all worked correctly.
My colleague is using a Mac. Not sure if this is relevant.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:
,
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
es.
Welcome. There are many helpful people on the list.
It would be useful if you can point us to a protocol description
document but that can wait until help is needed. It may be that all
the online resources are sufficient, but if not, do not hesitate to
use this list to ask questions.
contribute to the "Add Git protocol support to Wireshark" project.
Perhaps Amanda could resend her introduction on the wireshark-dev
mailing list because this is the list for development type questions
and will get better responses for developer-type
.* files. There is also a
sample dissector in doc/packet-PROTOABBREV.c
However, it can all be a bit daunting for a beginner so I am willing
to help get things started.
I should also point out that there are many people on the
wireshark-developer mailing list who will be more than happy to help
I am more than happy to offer advice and ideas and look at code to get
new Wireshark developers going.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://w
rs, and I am sure many other developers are as well.
--
Regards
Richard Sharpe
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/opti
on the first monitor (and
other craziness can occur as well.)
Are these related at all? Do we plan to skip Qt 5.15?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives
Hi folks,
Has the switchover occurred?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https
tching
against some obscure protocol, or perhaps it should be:
wlan.tag.number == and found:wlan.tag.length >=
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:ht
lue is prone to false positives if any tagged field in the
frame has that number and any other tagged field in the frame has a
length ge the value.
How can I limit the length comparison to the tag found in the first comparison?
Do we even have that concept?
--
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
>
much data to disk is
> something I do with small portable servers (about the size of a small shoe
> box)
> with a FPGA based capture card.
NVMe can handle it ...
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
looked at System 76 and Librem but it does not seem they
are capable of handling the load.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org
On Sun, Jul 5, 2020 at 5:29 AM Richard Sharpe
wrote:
>
> On Sun, Jul 5, 2020 at 5:30 AM Jaap Keuter wrote:
> >
> > Hi Richard,
> >
> > Have you seen these entries from conflict check:
> >
> > ** (process:12824): WARNING **: 08:16:29.502: Field 'Stat
st is inconsistent with local MAC address
> policy)
>
> Do you know how to address this?
Probably.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:http
Hi folks,
I tried to submit a change for review but got:
remote: Unauthorized
fatal: Authentication failed for 'https://code.wireshark.org/review/wireshark/'
What is going on?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者
, the enc part is not being busted out for me.
Does anyone know how to do this?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists
On Thu, Jun 4, 2020 at 3:09 AM Peter Wu wrote:
>
> On Wed, Jun 03, 2020 at 11:17:01AM -0700, Richard Sharpe wrote:
> > Hi folks,
> >
> > Some protocols define status values etc in terms of 802.11.
> >
> > I am trying to get the latest changes for IEEE1905
and allow the linker to deal with it?
2. Provide a function that retrieves a pointer to it?
3. Some other mechanism?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives
On Sat, May 16, 2020 at 8:51 AM Pascal Quantin wrote:
>
> Hi Richard,
>
> Le sam. 16 mai 2020 à 17:34, Richard Sharpe a
> écrit :
>>
>> On Sat, May 16, 2020 at 6:00 AM João Valverde
>> wrote:
>> >
>> > Hi Richard,
>> >
>> >
On Sat, May 16, 2020 at 6:00 AM João Valverde
wrote:
>
> Hi Richard,
>
> On 15/05/20 23:46, Richard Sharpe wrote:
> > On Fri, May 15, 2020 at 3:33 PM Peter Wu wrote:
> >> The "asn1" target rebuilds all asn1 dissectors.
> >> Alterna
gt; cmake ..
> cmake --build . --target generate_dissector-pkcs1
>
> Or if you use ninja:
>
> mkdir build
> cd build
> cmake -GNinja ..
> ninja generate_dissector-pkcs1
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
On Fri, May 15, 2020 at 2:29 PM Richard Sharpe
wrote:
>
> On Fri, May 15, 2020 at 2:30 PM Peter Wu wrote:
> >
> > Hi Richard,
> >
> > On Fri, May 08, 2020 at 08:54:58AM -0700, Richard Sharpe wrote:
> > [..]
> > > It doesn't look like it was manuall
On Fri, May 15, 2020 at 2:30 PM Peter Wu wrote:
>
> Hi Richard,
>
> On Fri, May 08, 2020 at 08:54:58AM -0700, Richard Sharpe wrote:
> [..]
> > It doesn't look like it was manually modified. The last person who
> > touched that file was Peter Wu, it seems, so maybe
vation is not handled by the decryption
> engine so PTK remains unknown which makes decryption fail. And unfortunately
> directly entering PTK for decryption is not supported either.
It could be but it would take some work :-)
--
Regards,
Richard Sharpe
able.
>
> Is decryption of fast BSS transition data packets supported by Wireshark? If
> so, could you please suggest what we can do to investigate what is going on?
It is not currently supported. The WFA uses an external tool to
decrypt those packet
-
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wir
On Fri, May 8, 2020 at 8:43 AM Pascal Quantin wrote:
>
> Hi Richard,
It doesn't look like it was manually modified. The last person who
touched that file was Peter Wu, it seems, so maybe he can shed some
light on it.
> Le ven. 8 mai 2020 à 17:08, Richard Sharpe a
> écrit :
&g
,
BER_FLAGS_NOOWNTAG, dissect_pkcs1_Digest },
{ NULL, 0, 0, 0, NULL }
};
...
---
This seems like a problem ...
Perhaps I should file a bugzilla bug.
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者
On Thu, May 7, 2020 at 8:04 AM Pascal Quantin wrote:
>
> Hi Richard,
>
> Le jeu. 7 mai 2020 à 17:01, Richard Sharpe a
> écrit :
>>
>> Hi folks,
>>
>> I need a dissector for an EDCSA-Sig-Value, and it is nicely defined in
>>
it as an export to the pkcs1.cnf file by
adding it to the .EXPORTS section but perhaps I forgot to remove it
from the .NO_EMIT section ...
Is that all I need to do (and then re-run the command to generate the
new packet-pcks1.c file?)
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者
Hi folks,
I think I saw an email about things moving to github or gitlab and
wondered if they meant any changes to my workflow around submitting
changes?
If so, is there a link I can use to see what they are?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者
in pcapng file, if the link-layer type in an IDB is 0x, the IDB
> *MUST* contain a new option, containing the PEN and vendor-specific
> link-layer type.
>
> Given that it's for *two* capture file formats, these lists are probably
> better
Hi folks,
How do I get these into the collection?
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent via:Wireshark-dev mailing list
Archives:https://www.wireshark.org/lists/wireshark-dev
Unsubscribe
ed eap_type_vals.
3. Add the new entry or entries to that table.
4. Rebuild. Probably on Linux because building on Windows is hard.
5. Feed the capture into the new build.
6. Feel a burst of joy at making your first change to Wireshark.
7. Add any new attributes or whatever is needed to properly dissect th
his is of interest to
> include into the source base or not?
If someone would find it useful then you should submit it.
https://code.wireshark.org/review
--
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)(传说杜康是酒的发明者)
___
Sent
1 - 100 of 581 matches
Mail list logo
