From: Matteo Croce <matteo@openwrt.org>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>,
Nicolas Dichtel <nicolas.dichtel@6wind.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] add stealth mode
Date: Tue, 7 Jul 2015 17:24:07 +0200 [thread overview]
Message-ID: <CAFnufp292vwyoSJKK6smF55cFerxbCC_5pg_9NbRsvnRC7VH6A@mail.gmail.com> (raw)
In-Reply-To: <559B7943.3070807@ladisch.de>
2015-07-07 9:01 GMT+02:00 Clemens Ladisch <clemens@ladisch.de>:
> Valdis.Kletnieks@vt.edu wrote:
>> On Thu, 02 Jul 2015 10:56:01 +0200, Matteo Croce said:
>>> Add option to disable any reply not related to a listening socket
>>
>> 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?)
>
> Even worse: if you want to pretend that the entire machine is "not there",
> you must make the router in front on you reply with an ICMP "destination
> unreachable" message.
You can't do sometimes, like in DSL lines where the router in front of
you is an ISP owned DSLAM
--
Matteo Croce
OpenWrt Developer
prev parent reply other threads:[~2015-07-07 15:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-02 8:56 [PATCH v2] add stealth mode Matteo Croce
2015-07-06 10:49 ` Valdis.Kletnieks
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 [this message]
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=CAFnufp292vwyoSJKK6smF55cFerxbCC_5pg_9NbRsvnRC7VH6A@mail.gmail.com \
--to=matteo@openwrt.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=clemens@ladisch.de \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).