Re: [v6ops] (IETF I-D): Implications of IPv6 Addressing on Security Operations (Fwd: New Version Notification for draft-gont-opsec-ipv6-addressing-00.txt)

Fernando Gont <fgont@si6networks.com> Wed, 15 February 2023 19:40 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECE15C14F720 for <v6ops@ietfa.amsl.com>; Wed, 15 Feb 2023 11:40:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HvZw4YTb7ntZ for <v6ops@ietfa.amsl.com>; Wed, 15 Feb 2023 11:40:23 -0800 (PST)
Received: from fgont.go6lab.si (fgont.go6lab.si [91.239.96.14]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA5FBC14F739 for <v6ops@ietf.org>; Wed, 15 Feb 2023 11:39:56 -0800 (PST)
Received: from [10.0.0.133] (unknown [186.19.8.47]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by fgont.go6lab.si (Postfix) with ESMTPSA id 255DE280818; Wed, 15 Feb 2023 16:39:51 -0300 (-03)
Message-ID: <a8f15953-99ac-f3c9-cce0-e4d5bcdb4658@si6networks.com>
Date: Wed, 15 Feb 2023 16:39:46 -0300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.1
Content-Language: en-US
To: Simon <linux@thehobsons.co.uk>, IPv6 Operations <v6ops@ietf.org>
References: <091075f1-033a-5577-60d9-3c6a009b3e21@si6networks.com> <55adf66d-23cb-0b2c-65d7-8f053a6f9298@si6networks.com> <A8F954DA-1F9C-4329-A454-E9D7D17689D1@thehobsons.co.uk>
From: Fernando Gont <fgont@si6networks.com>
In-Reply-To: <A8F954DA-1F9C-4329-A454-E9D7D17689D1@thehobsons.co.uk>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/GpMV8csBsQK-lbbwVuEE9yLeV80>
Subject: Re: [v6ops] (IETF I-D): Implications of IPv6 Addressing on Security Operations (Fwd: New Version Notification for draft-gont-opsec-ipv6-addressing-00.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2023 19:40:28 -0000

Hello, Simon,

Thanks for reaching out! In-line....

On 14/2/23 15:11, Simon wrote:
> 
> Interesting read. However, I think a few places are perhaps a little
> misleading.
> 
> One is discussing blocking a whole /64, and that it will probably
> block other (innocent) hosts on the same network. This isn’t really
> any different to the world of IPv4 where blocking a single address
> will most likely block all hosts in a network behind a NAPT gateway.
> To an extent, I can see that treating a /64 in much the same way as a
> /32 in the IPv4 world will become commonplace for the reasons you
> mention. I’ve definitely dealt with the situation where the email for
> a whole office keeps going down because one device was misconfigured
> and kept triggering fail2ban on our servers.

mm... what is misleading about this statement?  Or, in other words, how 
could you make e.g. fail2ban being off any use by blocking just /128s?

Are you arguing to only ban the /64 after a few blocks in that /64? Or 
something else?

Thanks!

Regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: F242 FF0E A804 AF81 EB10 2F07 7CA1 321D 663B B494