Re: [Uta] Google TLSRPTs
Viktor Dukhovni <ietf-dane@dukhovni.org> Fri, 26 April 2019 20:36 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 B1F201205E7 for <uta@ietfa.amsl.com>; Fri, 26 Apr 2019 13:36:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 kvuyOAyDwNHR for <uta@ietfa.amsl.com>; Fri, 26 Apr 2019 13:36:42 -0700 (PDT)
Received: from straasha.imrryr.org (straasha.imrryr.org [100.2.39.101]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16AEF1205D7 for <uta@ietf.org>; Fri, 26 Apr 2019 13:36:42 -0700 (PDT)
Received: from [192.168.1.161] (unknown [192.168.1.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by straasha.imrryr.org (Postfix) with ESMTPSA id EE1942B0100 for <uta@ietf.org>; Fri, 26 Apr 2019 16:36:40 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
From: Viktor Dukhovni <ietf-dane@dukhovni.org>
In-Reply-To: <924e6bc3-e656-729f-bfe0-1621b3ba599d@spamtrap.tnetconsulting.net>
Date: Fri, 26 Apr 2019 16:36:40 -0400
Content-Transfer-Encoding: quoted-printable
Reply-To: uta@ietf.org
Message-Id: <A782FAE6-AB9D-4654-8E3E-B1820EF7E74C@dukhovni.org>
References: <924e6bc3-e656-729f-bfe0-1621b3ba599d@spamtrap.tnetconsulting.net>
To: uta@ietf.org
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/uta/vNaVNVdeSwYmN4P_tlfdnEW96TY>
Subject: Re: [Uta] Google TLSRPTs
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: Fri, 26 Apr 2019 20:36:44 -0000
> On Apr 26, 2019, at 1:39 PM, Grant Taylor <gtaylor=40tnetconsulting.net@dmarc.ietf.org> wrote: > > Is anyone else seeing policy type of "no-policy-found" in the TLSRPTs that they are receiving from Google? > > I'm seeing said policy with a "total-successful-session-count" of exactly one each day in addition to the other policies. > > For a week now, I've had one or more successful counts on my "sts" policy and exactly one hit on a "no-policy-found", every day. > > I was curious if anyone had any thoughts before I go tilt at the Google windmill. If I were to hazard an inspired guess, this would for the delivery of the previous day's tlsrpt. Report delivery deliberately avoids enforcing TLS policy. -- Viktor.
- [Uta] Google TLSRPTs Grant Taylor
- Re: [Uta] Google TLSRPTs Viktor Dukhovni
- Re: [Uta] Google TLSRPTs Grant Taylor