From:ger...@wireshark.org
<<< 501 ger...@wireshark.org... Refused
--- End Message ---
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)s
---
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
e tree?
> 2. Does this parse tree become that parse tree after this optimisation?
> 3. Does this parse tree become this BPF program after this translation?
That's independent of the representation; the same could be done for other
intermediate representations.
__
API supports an option set, so an alternative would be to pass
an option set to a new "compile this filter expression" API without having to
have a pcap_t to open and close.
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.t
a new pcap_dump_open() routine that takes a link-layer
> type and a snapshot length might be worth introducing, rendering
> pcap_open_dead() mostly, if not completely, redundant.
> ___
> tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
> To unsubscribe send an email to
se tree in the first pass risks adding a shiny new recursive
algorithm to upset fuzzers, although, if it makes certain things easier, if we
can limit the recursion depth to something such that a fuzzer would have to
*really* go crazy to provoke a stack overflow, that might be OK.)
___
mewhat of a greasy hack,
as far as I'm concerned. If all you're using libpcap for is to generate cBPF
code, a pcap_t seems to be extra baggage.
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to
tree looks like quite a demanding change.
--
Denis Ovsienko
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
first
> phase and, for each new link-layer/snapshot length pair in the file,
> would generate the appropriate code for the filter, caching the
> results.
A good plan.
___________
tcpdump-workers mailing list -- tcpdump-workers@lis
that file would be set
to the generated intermediate representation from the first phase and, for each
new link-layer/snapshot length pair in the file, would generate the appropriate
code for the filter, caching the results.
_______
tcpdump-workers mai
man Software Works|IoT architect [
] m...@sandelman.ca http://www.sandelman.ca/ | ruby on rails[
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
ew pcap_dump_open() routine that takes a link-layer type
and a snapshot length might be worth introducing, rendering pcap_open_dead()
mostly, if not completely, redundant.
_______
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe
hat the caller completely knows what they are doing. Then move
the definition of BPF_SPECIAL_VLAN_HANDLING from pcap-int.h to the public
header.
Anyone have a preference of which one I should go with, and/or have a
better suggestion?
Thanks,
Bill
__________
anted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany
man.ca http://www.sandelman.ca/| ruby on rails [
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
g...@greenie.muc.de
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
r doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany g...@greenie.muc.de
___
tcpdump-
Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany g...@greenie.muc.de
___________
tcpdump-workers
hat would allow people
running that release to use that flag in their scripts; if they do so,
splitting the IPv6 verbose output, as is done now with the IPv4 verbose output,
might break fewer scripts.
_______
tcpdump-workers mailing list --
documented.
>
> Perhaps we should implement that flag.
...and, if we do, and we split the lines in verbose mode for IPv6, the
-g/--ip-oneline flag would apply both to IPv4 and IPv6.
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpd
cpdump-group/tcpdump/issues/810
--
Denis Ovsienko
_______
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
umor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany g...@greenie.muc.de
_______
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsu
From:ger...@wireshark.org
<<< 501 ger...@wireshark.org... Refused
--- End Message ---
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)s
#x27;s was forked a while ago and they're maintaining it themselves; I think
they've picked up some changes from us.
DragonFly BSD is similar to FreeBSD's (not surprisingly, as DragonFly BSD was
originally a fork of FreeBSD). It's also in contrib/tcpdump.
_______
nse in making the latter two options more granular and/or arranging
the source such that assigning a specific dissector to a specific group
would be a matter of one #define. But this may be over-engineering.
--
Denis Ovsienko
_______________
tcpdump-workers ma
ything upstreamed to our repos.
Even if we -DDEBIAN, or -DEMBED or -DSMALL.
This would be a great new contributor effort.
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-work
---
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
ful material for this development.
--
Denis Ovsienko
--- End Message ---
_______
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistin
as the ASCII-centric nature
of the protocol messages and the potential for capturing timing
information more granularly.
Thank you once again for your valuable feedback.
Best regards,
Howard
On Sun, Jun 1, 2025 at 12:09 PM Denis Ovsienko via tcpdump-workers
wrote:
>
>
>
>
> -
this link-layer type, it would be easier to reason about it.
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
details:
https://github.com/hharte/oasis-utils/blob/main/wireshark/OASIS-send-recv-protocol.md
Thank you for your consideration.
-Howard
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers
--- Begin Message ---
The original message was received at Fri, 30 May 2025 19:19:00 +0200
from gsu.edu [5.81.79.253]
- The following addresses had permanent fatal errors -
--- End Message ---
___
tcpdump-workers mailing list -- tcpdump
computer safe.
Best wishes,
The lists.tcpdump.org support team.
--- End Message ---
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext
--- Begin Message ---
--- End Message ---
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
c061959
rust parser:
-
https://gitlab.com/kraxel/virt-firmware-rs/-/blob/main/varstore/src/pcap/parse.rs
take care,
Gerd
--- End Message ---
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-
kgsrc from 2024Q4 to 2025Q1 on
three NetBSD worker hosts), and
* various sysadmin chores (VM churn, OS and package updates).
----------
--
Denis Ovsienko
___
tcpdump-workers mailing li
--- Begin Message ---
The original message was received at Sat, 3 May 2025 09:19:00 -0700
from gsu.edu [6.197.124.38]
- The following addresses had permanent fatal errors -
tcpdump-workers@lists.tcpdump.org
- Transcript of the session follows -
... while talking to
most useful to lose the build option and to make all
> IPv6 syntax always available. (This would also eliminate a half of
>libpcap CI build matrix.)
libpcap pull request 1504 implements this, if anyone wishes to tell a
sound reason not to proceed, please do it now. Otherwise this change is
going
ill I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany g...@greenie.muc.de
_______
tcpdump-workers mailing list -- tcpd
hat fails, report
that flex doesn't work, tell the person trying to build libpcap that they need
to somehow arrange to have a flex that works, and fail.
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email
wrote:
>
> > Flex is not getting built. We have the binary checked in to our
> repository.
>
> What process produced that binary? Is it a binary you compiled, is it a
> copy of a binary from the OS, or is it from somewhere else?
>
__________
r ARM platform
>
> Well, likely the resulting flex test can't be run, since it's cross-compiled.
>
> I suggest *NOT* doing cross-compilation while you are working on new code.
+1
--- End Message ---
_______________
tcpdump-workers mailin
lse?
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>
> What does "which flex" print?
>
> > m4 exists and I have set M4PATH env variable as well; however, it seems
> to pick it up from where flex was built before.
>
> Why was flex built at all? Why not just rely on the system flex or the
> cross-build flex th
OS?
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
I did not run autoconf.
Only thing that I did was run the following
1) configure
2) make
Is it possible to set M4 using some other means?
On Mon, Apr 7, 2025 at 1:40 PM Denis Ovsienko via tcpdump-workers <
tcpdump-workers@lists.tcpdump.org> wrote:
>
>
>
> --
- End Message ---
_______
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
.out to see why it really failed; my guess is above.
> > Regardless, you will need to post more details about the failure.
>
> ...without the config.out file, we can't figure out what the problem is.
_______
tcpdump-workers mailing list -
ove.
> Regardless, you will need to post more details about the failure.
...without the config.out file, we can't figure out what the problem is.
_______________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe sen
for bison/m4. (I am not sure what is that tool for)
Read the config.out to see why it really failed; my guess is above.
Regardless, you will need to post more details about the failure.
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.o
n all sections of the pcapng file must have
>> the same link-layer header type and snapshot length, as the current API
>> reports a single link-layer header type and snapshot length for the entire
>> file;
>>
>> 3) block types other than packet blocks can't
ayer header type and snapshot length, as the current API reports
> a single link-layer header type and snapshot length for the entire file;
>
> 3) block types other than packet blocks can't be reported to the
> caller;
>
> 4) options such as comments can&#
s comments can't be reported to the caller.
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
s functionality available today or do we need to build it?
I can't recall if we can read pcapng.
_______
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_u
is functionality is available today or
> alternatively even wireshark would be ok to do this for me)
libpcap does support reading pcapng files, but does not yet support providing
comments to the program that reads them.
_______________
tcpdump-workers mailing lis
o build it?
>
> thanks in advance
>
_______________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
* developing code that is still work in progress or is waiting to be
merged,
* resolving/updating/opening a number of bug reports,
* various updates to the web site, and
* sysadmin chores (updates/reinstalls/troubleshooting).
--------
ement and user support,
* various minor fixes to code and documentation,
* preparing a few draft prototypes that yet remain to be completed,
* minor updates to the web site,
* manual testing on less common OSes as required, and
* sysadmin chores (mostly reconfigurations, upgrades and churn in the
vir
se it?
--
Francois-Xavier
--- End Message ---
_______
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
__
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
On Feb 12, 2025, at 1:54 PM, Francois-Xavier Le Bail via tcpdump-workers
wrote:
> They are also different:
>
> $ diff bpf_dump.c ../libpcap/bpf_dump.c
>
> 24,25c24
> < #include "netdissect-stdinc.h"
> <
> ---
--- Begin Message ---
On Wed, 12 Feb 2025 22:54:18 +0100
Francois-Xavier Le Bail wrote:
[...]
> They are also different:
Hopefully the difference is more meaningful now.
--
Denis Ovsienko
--- End Message ---
___
tcpdump-workers mailing l
--- Begin Message ---
On 09/02/2025 14:22, Denis Ovsienko via tcpdump-workers wrote:
> Hello all.
>
> tcpdump has been keeping a copy of bpf_dump.c from libpcap with the
> following description in INSTALL.md:
>
> "bpf_dump.c - BPF program printing routines, in case libp
udes a copy of bpf_dump.c too.
--
Denis Ovsienko
--- End Message ---
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
x in
case a filter uses the old-style VLAN keyword), but otherwise things
by default would work as before. Let's suppose the 1.11.x series
lasts a few years and provides a sufficient migration window even
after libpcap 2.0.0 has stabilised.
4. In the master branch the to-be-libpc
reciate it.
Regards, Oli
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
The original message was received at Sat, 30 Nov 2024 00:46:00 +0100
from wireshark.org [176.72.224.19]
- The following addresses had permanent fatal errors -
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To
reless, NoInject]
13.nflog (Linux netfilter log (NFLOG) interface) [NoInject]
14.nfqueue (Linux netfilter queue (NFQUEUE) interface) [NoInject]
One other disputable point is the choice of names for the flags -- I
suspect better naming is possible.
--
Denis Ovsienko
__
records. If the problem is
> limited to my address, I can subscribe from another one and you can just
> block my wireshark.org address if that's easier.
> _______
> tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
>
7;s easier.
_______
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
may have sent an infected document as an attachment, as indicated in
the message, but list processing has deleted the document.
--- End Message ---
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an e
On Nov 18, 2024, at 9:08 AM, Michael Richardson wrote:
> The message about the spam was in fact spam.
So what is the purpose of those types of spam? Testing a list's spam detectors?
___
tcpdump-workers mailing list -- tcpdump
this becomes an upstream (Kernel) request.
I think most platforms support capturing and injecting on all network
interfaces (as long as you have permission to open them).
_______________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
;{capturing,injecting} traffic
isn't supported on this device" error, and if they report *that*, at least it's
known what the problem is, shortening the Q&A session and getting an answer
more quickly.
> Does it make sense?
Sounds good to me.
false-positives, but there are some
reasonable howtos.
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
:
> PCAP_IF_NO_CAPTURE -- capture is guaranteed not to work
> PCAP_IF_NO_INJECT -- inject is guaranteed not to work
Yeah, that sounds reasonable for now.
_______________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To uns
t; Best wishes,
> The lists.tcpdump.org team.
>
> _______________
> tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
> To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.
your computer
safe.
Best wishes,
The lists.tcpdump.org team.
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name
t;
> 24 bits long, of course. Half the MAC address is OUI, not the entire
> address. Which may or may not make the mapping easier to implement,
> but that's not the point.
>
> --
> Denis Ovsienko
> ___________
> tcpdump-worker
set a "drop all packets" filter on the capture device, 2) possibly
> put the capture device in non-blocking mode (as there's no point in
> blocking, as no more packets will be seen), and 3) cause the packet
> processing loop in libpcap to quit as soon as it finds that there
&
t in blocking, as no more packets will
be seen), and 3) cause the packet processing loop in libpcap to quit as soon as
it finds that there are no more packets available to read. For programs using
pcap_loop(), that should be transparent; for programs using pcap_dispatch(),
they would have to treat
processing them, but it's not as if the
> capture mechanism will stop adding packets to the buffer, so that
> would behave as if tcpdump continued capturing.
>
> There is no current mechanism in libpcap by which tcpdump (or any
> other program using libpcap to capture networkin
libpcap to capture networking traffic, e.e. Wireshark) can indicate to
libpcap that it doesn't want any *more* packets from the network device, but
wants to be able to keep reading from the packets already *in* the buffer until
the last packet has been retrieved. That means tcpdump can't be told to do that
with any existing version of libpcap.
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
ing
> packet dissection text to be printed or the I/O buffer containing
> packets to be written to the file specified by -w, i.e. an *output*
> buffer for tcpdump?
Correct. I meant the input buffer, specified with the -B flag.
Regards,
Garri
_______
tcp
input* buffer for tcpdump, rather than,
for example, the standard I/O buffer containing packet dissection text to be
printed or the I/O buffer containing packets to be written to the file
specified by -w, i.e. an *output* buffer for tcpdump?
_______________
tcp
. Still, I wonder if this can be done by
tcpdump itself.
I was checking the behaviour using Linux kernel version 6.11.3 and
tcpdump/libpcap version 4.99.5/1.10.5.
Thank you.
Regards,
Garri
___
tcpdump-workers mailing list -- tcpdump-workers
On Jun 10, 2024, at 12:39 PM, Alberto Perez Bogantes via tcpdump-workers
wrote:
> We've been working on adding a new feature to tcpdump that will allow IP
> address anonymization ...
...
>
> I am sharing my GitHub project (https://github.com/aperezb21/tcpdump),
> which i
gards
Anders
_______
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
rds
Anders
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
c has been upgraded from
2024Q2 to 2024Q3, which among other things upgraded GCC from 13.3 to
14.2 and Clang from 17.0 to 18.1 on netbsd-aarch64.
Cheers.
1: https://www.digitalocean.com/open-source/credits-for-projects
--
Denis Ovsienko
_______
tcpdump-worke
nd that's "security" as in
"preventing people from capturing your traffic and reading it".
_______
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
s to dump things.
--
Michael Richardson. o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
_______
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tc
Michael, for the quick response. Is there a way to capture and
analyze *HTTPS* traffic since the data is encrypted?
Please guide me. Thanks in advance.
Best Regards,
Kaushal
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
window1> tcpdump -i lo -w myfile.pcap tcp port 80
_______________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
--- Begin Message ---
On Tue, 03 Sep 2024, Denis Ovsienko wrote:
> On Mon, 10 Jun 2024 14:39:01 -0500
> Alberto Perez Bogantes via tcpdump-workers
> wrote:
>
> > We believe that this functionality is well suited for tcpdump because
> > much of the logic used to print an I
PUT methods.
Please guide me. Thanks in advance.
Best Regards,
Kaushal
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s
er, not too bad.
_______
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
ime soon.
--
Denis Ovsienko
___________
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
and if so, why it was never reported?
> Please read some of the (many) attacks on eBPF to better understand
> the security landscape here. It’s a *very* hard problem to solve.
Finally, the most big (in effort) question: suppose we limited to
trusted root user etc. so it'
4 is not FreeBSD-only, you can see several non-FreeBSD mailing lists
here. It can be cross-platform and independent enough to be implemented
in e.g. network card or switch, for performance - having more registers
allows to achieve better results then eBPF for same goal.
--
WBR, @nuclight
___
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
1 - 100 of 9663 matches
Mail list logo
