IETF Logo Mail Archive

Re: [saag] results of IETF LC for draft-foudil-securitytxt-08 and next steps

Michael Richardson <mcr@sandelman.ca> Mon, 13 July 2020 01:05 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: saag@ietfa.amsl.com
Delivered-To: saag@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C25F3A00E4; Sun, 12 Jul 2020 18:05:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[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 n9LWn94M7FmI; Sun, 12 Jul 2020 18:05:02 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71D373A00D6; Sun, 12 Jul 2020 18:05:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 8FA3A389BC; Sun, 12 Jul 2020 21:02:02 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id LZTzKOv68Yfe; Sun, 12 Jul 2020 21:02:02 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id E57683898D; Sun, 12 Jul 2020 21:02:01 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 02ADB795; Sun, 12 Jul 2020 21:05:00 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Yakov Shafranovich <yakov@nightwatchcybersecurity.com>
cc: Benjamin Kaduk <kaduk@mit.edu>, draft-foudil-securitytxt@ietf.org, Security Area Advisory Group <saag@ietf.org>
In-Reply-To: <CAAyEnSPRKk-grcUfps7EUKmZjdQKu4bvFrrMn3uMEHAVY5ERmw@mail.gmail.com>
References: <20200630222455.GX58278@kduck.mit.edu> <12504.1593572624@localhost> <20200702034828.GB16335@kduck.mit.edu> <5953.1593706347@localhost> <20200702222032.GG16335@kduck.mit.edu> <29760.1593757978@localhost> <CAAyEnSPRKk-grcUfps7EUKmZjdQKu4bvFrrMn3uMEHAVY5ERmw@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sun, 12 Jul 2020 21:04:59 -0400
Message-ID: <19624.1594602299@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/saag/mAZgSOMeLT7Oh86nFZWvRGmKdcc>
Subject: Re: [saag] results of IETF LC for draft-foudil-securitytxt-08 and next steps
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/saag/>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jul 2020 01:05:04 -0000

Yakov Shafranovich <yakov@nightwatchcybersecurity.com> wrote:
    >> If a security.txt applies *only* to the web resource where you found it,
    >> then that means it doesn't generalize to the other instances of that device.
    >> That sounds dumb, and it is, but that's what I'm reading in section 3.1
    >>

    > The concern was that in a case where different parts of a website may
    > be owned by different customers, we didn't want customer A claiming
    > authority over customer B. This is well illustrated by Amazon's setup
    > for S3 where "domain.s3.amazonaws.com" is the same thing as
    > "s3.amazonaws.com/domain/".

I understand.
also cf: "geocities" :-)

    > With that being said, the intent is that the "Policy" directive can
    > point to an expanded policy document that would add more information
    > about scope. So in the case of the Teddy Cam, the "security.txt" file
    > would provide the absolute minimum but the policy directive can add
    > additional information.

okay, thank you, I'm happy with this.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email