From: Valdis.Kletnieks@vt.edu
To: Matteo Croce <matteo@openwrt.org>
Cc: nicolas.dichtel@6wind.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] add stealth mode
Date: Mon, 06 Jul 2015 06:49:58 -0400 [thread overview]
Message-ID: <21611.1436179798@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Thu, 02 Jul 2015 10:56:01 +0200." <CAFnufp059tojfKYBye4eayOCvNNkAE9w_s_6E-PiG-EYp9K0Gg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
On Thu, 02 Jul 2015 10:56:01 +0200, Matteo Croce said:
> Add option to disable any reply not related to a listening socket,
> like RST/ACK for TCP and ICMP Port-Unreachable for UDP.
> Also disables ICMP replies to echo request and timestamp.
> The stealth mode can be enabled selectively for a single interface.
A few notes.....
1) Do you have an actual use case where an iptables '-j DROP' isn't usable?
2) You *do* realize that this isn't anywhere near sufficient in order
to actually make your machine "invisible", right? (Hint: What *other*
packets can be sent to a machine to provoke a response?)
3) At least my copy had massive whitespace damage, where all the tab characters
appear to have evaporated....
[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]
next prev parent reply other threads:[~2015-07-06 10:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 8:56 Matteo Croce
2015-07-06 10:49 ` Valdis.Kletnieks [this message]
2015-07-06 19:44 ` Matteo Croce
2015-07-07 2:34 ` David Miller
2015-07-07 8:07 ` Hannes Frederic Sowa
2015-07-07 15:27 ` Matteo Croce
2015-07-08 8:02 ` Hannes Frederic Sowa
2015-07-08 13:32 ` Austin S Hemmelgarn
2015-07-12 23:13 ` Matteo Croce
2015-07-13 13:03 ` Austin S Hemmelgarn
2015-07-14 14:51 ` Matteo Croce
2015-07-07 7:01 ` Clemens Ladisch
2015-07-07 15:24 ` Matteo Croce
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=21611.1436179798@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=matteo@openwrt.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®