IETF Logo Mail Archive

Re: [art] One more thing about draft-foudil-securitytxt

Benjamin Kaduk <kaduk@mit.edu> Thu, 14 May 2020 03:48 UTC

Return-Path: <kaduk@mit.edu>
X-Original-To: art@ietfa.amsl.com
Delivered-To: art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 968AB3A0837 for <art@ietfa.amsl.com>; Wed, 13 May 2020 20:48:51 -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 Fqvok1SuvV5I for <art@ietfa.amsl.com>; Wed, 13 May 2020 20:48:50 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 199D13A065A for <art@ietf.org>; Wed, 13 May 2020 20:48:49 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 04E3mhjw016400 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 13 May 2020 23:48:45 -0400
Date: Wed, 13 May 2020 20:48:42 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Mark Nottingham <mnot@mnot.net>
Cc: Ed Overflow <contact@edoverflow.com>, yakov+ietf@nightwatchcybersecurity.com, Kathleen.Moriarty.ietf@gmail.com, ART Area <art@ietf.org>
Message-ID: <20200514034842.GS27494@kduck.mit.edu>
References: <480748CD-7043-43AC-8EBC-BF6E3F17CEA1@mnot.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <480748CD-7043-43AC-8EBC-BF6E3F17CEA1@mnot.net>
User-Agent: Mutt/1.12.1 (2019-06-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/art/WCp2uwbYYIo7XmJ5a41DPSUnAxY>
Subject: Re: [art] One more thing about draft-foudil-securitytxt
X-BeenThere: art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Applications and Real-Time Area Discussion <art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/art>, <mailto:art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/art/>
List-Post: <mailto:art@ietf.org>
List-Help: <mailto:art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/art>, <mailto:art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 May 2020 03:48:52 -0000

Hi Mark,

On Thu, May 14, 2020 at 01:28:01PM +1000, Mark Nottingham wrote:
> It looks like it's becoming common practice for security.txt files to put *other* things in the /.well-known namespace.
> 
> For example:
> 
> "Signature: https://www.patreon.com/.well-known/security.txt.sig" on www.patreon.com
> "Signature: https://www.patreon.com/.well-known/security.txt.sig" on 1password.com
> 
> It might be good to mention that URLs in security.txt fields should not be in .well-known space unless registered for that purpose.

I've been going through and tabulating the last-call comments today, so
I'll be sure to add that to my summary writeup.

Thanks,

Ben

v2.23.0 | Report a Bug | By Email