Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754903AbbGGIII (ORCPT ); Tue, 7 Jul 2015 04:08:08 -0400 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:51843 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752407AbbGGIHy (ORCPT ); Tue, 7 Jul 2015 04:07:54 -0400 Message-Id: <1436256473.3809610.317083993.4E2A41A3@webmail.messagingengine.com> X-Sasl-Enc: 8vYiJsh0k8+SiMq16FVtMEliWyb5Yy0b0jKayi+6jxeM 1436256473 From: Hannes Frederic Sowa To: Matteo Croce , Valdis.Kletnieks@vt.edu Cc: Nicolas Dichtel , netdev@vger.kernel.org, linux-kernel@vger.kernel.org MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain X-Mailer: MessagingEngine.com Webmail Interface - ajax-bfc056ae Subject: Re: [PATCH v2] add stealth mode Date: Tue, 07 Jul 2015 10:07:53 +0200 In-Reply-To: References: <21611.1436179798@turing-police.cc.vt.edu> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1070 Lines: 26 On Mon, Jul 6, 2015, at 21:44, Matteo Croce wrote: > 2015-07-06 12:49 GMT+02:00 : > > 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? > > If you mean using a default DROP policy and allowing only the traffic > do you want, > then the use case is where the port can change at runtime and you may not > want > to update the firewall every time Can't you use socket match in netfilter to accomplish exactly that? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/