On Mon, 27 Feb 2023 03:31:27 +0100
Francois-Xavier Le Bail <devel.fx.leb...@orange.fr> wrote:

> There are already some doc/site with bad use of "tcp-psh" instead of
> "tcp-push" like: https://packetlife.net/media/library/12/tcpdump.pdf

The author has been notified about the error.

> https://github.com/the-tcpdump-group/tcpdump/issues/846

This indeed had happened.  Would it be correct to say only once in a
long time?

> https://github.com/tcpdump-examples/how-to-use-tcpdump

The fragment titled "Isolate TCP PSH flags." along with many others
is an old copy from https://danielmiessler.com/study/tcpdump/ and the
original document now says "tcp-push".

> https://blog.codefarm.me/2018/12/29/tcpdump-examples/

Another old copy from https://danielmiessler.com/study/tcpdump/.

> https://twitter.com/dc9221/status/1254154374143754241/photo/1

The above is a series of screenshots of
https://packetlife.net/media/library/12/tcpdump.pdf with the copyright
replaced with somebody else's.  See also

> https://github.com/marciopocebon/TCPDUMP-1

Another old copy from https://danielmiessler.com/study/tcpdump/.

> ...
> Thus, the problem already exists in reverse.

It has been this way for 32 years, so let's either fix this properly
with backward compatibility notes, or not at all.  And in any case,
with a clear understanding which is the right thing.

    Denis Ovsienko
tcpdump-workers mailing list -- tcpdump-workers@lists.tcpdump.org
To unsubscribe send an email to tcpdump-workers-le...@lists.tcpdump.org

Reply via email to