Re: [Uta] Smallest practical MTA-STS maximum policy age?

Viktor Dukhovni <ietf-dane@dukhovni.org> Sat, 23 May 2020 19:27 UTC

Return-Path: <ietf-dane@dukhovni.org>
X-Original-To: uta@ietfa.amsl.com
Delivered-To: uta@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A2513A0DFE for <uta@ietfa.amsl.com>; Sat, 23 May 2020 12:27:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eBziGAr4_2hb for <uta@ietfa.amsl.com>; Sat, 23 May 2020 12:27:37 -0700 (PDT)
Received: from straasha.imrryr.org (straasha.imrryr.org [100.2.39.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B43AB3A0DFC for <uta@ietf.org>; Sat, 23 May 2020 12:27:37 -0700 (PDT)
Received: by straasha.imrryr.org (Postfix, from userid 1001) id 5052C2BCFD; Sat, 23 May 2020 15:27:36 -0400 (EDT)
Date: Sat, 23 May 2020 15:27:36 -0400
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
To: uta@ietf.org
Message-ID: <20200523192736.GB89731@straasha.imrryr.org>
Reply-To: uta@ietf.org
References: <CANHgQ8H-xTuwMO8g9rZMTN2peb7=0x-1d7ZGzjoYeYskDQ=-+A@mail.gmail.com> <8850ef7e-1c97-a6a8-b801-5ffa247af0b9@andreasschulze.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <8850ef7e-1c97-a6a8-b801-5ffa247af0b9@andreasschulze.de>
User-Agent: Mutt/1.12.2 (2019-09-21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/QsDRZt1hqMH7gYTmWqryGC4MWcU>
Subject: Re: [Uta] Smallest practical MTA-STS maximum policy age?
X-BeenThere: uta@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: UTA working group mailing list <uta.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/uta>, <mailto:uta-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/uta/>
List-Post: <mailto:uta@ietf.org>
List-Help: <mailto:uta-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/uta>, <mailto:uta-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 May 2020 19:27:40 -0000

On Sat, May 23, 2020 at 09:07:06PM +0200, A. Schulze wrote:

> I asked a similar question last year:
> https://mailarchive.ietf.org/arch/msg/uta/bnUjy9jxM_Va-lDXVtbB32zIkYI/
> Currently I use ~ 3 days as "max-age" and receive reports from google
> that don't let me think they have any problem with my setting.

Keep in mind that I expect implementations of MTA-STS to not refresh
refresh policy caches pre-expiration in the *absence of traffic to the
destination domain.  So if any domain hosts users who in aggregate
correspond with you less often than every 3 days, MTA-STS is completely
ineffective at protecting that traffic against MiTM downgrades.

Thus, my take is that MTA-STS policies with a max_age less than ~30 days
are potentially ineffective, and perhaps not worth the bother.

--
    Viktor.