From: Fatih USTA <fatihusta86@gmail.com>
To: netfilter@vger.kernel.org
Subject: TCP 4 way handshake or TCP Split Handshake Attack
Date: Fri, 24 Jan 2020 17:26:33 +0300 [thread overview]
Message-ID: <33c1b81b-cb3d-e277-334f-5a8daaf8dd73@gmail.com> (raw)
Hello,
I am trying to protect my network from the tcp split handshake attack!
(4-way handshake rejection or 3-way handshake enforcement).
I tested the sample code. (link below) And passed the firewall(iptables).
I can't find any solution on the internet for Linux.
Any advice?
Link1:
https://tech.labs.oliverwyman.com/blog/2016/11/07/4-way-tcp-handshake-and-firewalls/
Link2: https://gist.github.com/anonymous/142ebe785dbb146dafaa7ff59d8a9da8
Link3: https://nmap.org/misc/split-handshake.pdf
Thank you.
next reply other threads:[~2020-01-24 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 14:26 Fatih USTA [this message]
2020-01-24 16:24 ` TCP 4 way handshake or TCP Split Handshake Attack Florian Westphal
2020-01-24 19:54 ` Fatih USTA
[not found] ` <CAN_K0LR36AZRc55aisesAU0xDrcEgw6e41zwzwHV=zSSOffVAQ@mail.gmail.com>
2020-01-24 23:48 ` Florian Westphal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33c1b81b-cb3d-e277-334f-5a8daaf8dd73@gmail.com \
--to=fatihusta86@gmail.com \
--cc=netfilter@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.