Re: [secdir] SECDIR Review draft-koster-rep

Gary Illyes <garyillyes@google.com> Thu, 23 June 2022 07:55 UTC

Return-Path: <illyes@google.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28914C13182F for <secdir@ietfa.amsl.com>; Thu, 23 Jun 2022 00:55:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.109
X-Spam-Level:
X-Spam-Status: No, score=-17.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 Z7GyQ7XjgV9W for <secdir@ietfa.amsl.com>; Thu, 23 Jun 2022 00:55:33 -0700 (PDT)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 82FC4C14F748 for <secdir@ietf.org>; Thu, 23 Jun 2022 00:55:33 -0700 (PDT)
Received: by mail-lf1-x135.google.com with SMTP id g4so19546978lfv.9 for <secdir@ietf.org>; Thu, 23 Jun 2022 00:55:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=qyQ0OREN4CABKIDjdGhSpub44ZxIHsJ+BpfG/wbWcDg=; b=mkLnldYAzQxYxmJ7l1uJu3Q7agVJ/lEDTkwFJlz8XyPJrJ6YQYR6rPz5isuZxnBVTK vuTy6kP6bhRtpe5lcQvIHW+Vt3FER5u3o9Lr4+4CPiwjHTcvl1krp9EK3+e1QuJaePYF 10BcxBjQxPFODUHqevpFbLCpDMKpQZ1sGNIAL4YD4Bf/xyaeTOFrWC3855Zw1Mzr3pVH vcj3VtB8n/3K4QgB2nJzt2/76X/8QkG0oPEHbPlLOoOtQW6arlWEckd0hdu1wv0sZb9c JGQi8dLdeQJpYhgzOTPZk15+fpQyLzQSqtysUMFPVe10xL8+CJCscv5upBhYZelxiqZc 5srA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=qyQ0OREN4CABKIDjdGhSpub44ZxIHsJ+BpfG/wbWcDg=; b=sFUEBCr2Xe1YqDK36OU5FsQ7bLN7ixCV+lprO7PAeX4UdXQl0GaDhEshyqCoASAVGa JLsSYMHUKdDOwezpp/Rf7iFNDpAVCrlMzjUyd41bZ9saBQGDgSWVaN0Tk5cGzkLyHToH Cztr137s2GXWMfEHgR++sOQxodLA0ctFJX6QMm+DYDxRJG0878/HBK+TnnPYEH+fFn4N EgS9p50Sea5yGAObikexobAEuXoeGOpoyst6SwRAD5y4th1985IRTXT+xjYC5ql2tKJ/ ABfyQXgFJXNp0Rk9ZXGh7OeMOc8QBBmQhr1AiVmZAXBj01auqB4d7KwgQaUorp/wm2Wk 3v7A==
X-Gm-Message-State: AJIora+zpNzfCxN2A8p77MLVR0mbU7lERY0eKq5TyfyITKbJB1lpYXIk RHI3jlRGybyqDlRf50D21ocvsEe3anH49q2gR+vmSw==
X-Google-Smtp-Source: AGRyM1tWFA+BuXCj4Bf43LjTy3GnJqsZ/14B5eXCQITyzGsWXckmByDQ7mYUI8u2WE4pyJCHUaPkPYrkEExhtWifees=
X-Received: by 2002:a05:6512:260c:b0:47f:74f1:13b9 with SMTP id bt12-20020a056512260c00b0047f74f113b9mr4828692lfb.443.1655970931385; Thu, 23 Jun 2022 00:55:31 -0700 (PDT)
MIME-Version: 1.0
References: <CAFpG3gex3r1PH8xV7RTNESXbe+JyphzimrCggNH+X0KLPkaiCw@mail.gmail.com> <CADTQi=cd-EsOnpHMi7ZQ3YvGc4qOfgG=+cTsDziqEjETvg1DaQ@mail.gmail.com> <CAFpG3gfiZhjk43wrpUHo+jmDHN24bbx8RxKdBZ8eX7mapQm0Pw@mail.gmail.com>
In-Reply-To: <CAFpG3gfiZhjk43wrpUHo+jmDHN24bbx8RxKdBZ8eX7mapQm0Pw@mail.gmail.com>
From: Gary Illyes <garyillyes@google.com>
Date: Thu, 23 Jun 2022 09:55:19 +0200
Message-ID: <CADTQi=exp-NmAyNjfBL8fXfwCffXPUzL8bx9k_=mvXan_WAgig@mail.gmail.com>
To: tirumal reddy <kondtir@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-koster-rep.all@ietf.org, secdir@ietf.org
Content-Type: multipart/alternative; boundary="000000000000209c6105e218c787"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/J-OWB13fyJOBtHrqHzyjHQ5AWpY>
Subject: Re: [secdir] SECDIR Review draft-koster-rep
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jun 2022 07:55:34 -0000

On Thu, 23 Jun 2022 at 09:42, tirumal reddy <kondtir@gmail.com> wrote:

> On Wed, 22 Jun 2022 at 21:06, Gary Illyes <garyillyes@google.com> wrote:
>
>> Thanks Tiru!
>>
>> I updated our public repository with your suggestions and a diff of the
>> changes can be seen at
>> https://github.com/google/robotstxt/commit/a048272f9091570db556cf3656b6d33250797bba
>>
>> Specifically on point c) we added a new paragraph with a list of vectors
>> related to implementors based on a conversation we had with our security
>> team. On point a) and b) we restated that robots.txt is not a security
>> measure whatsoever and folks should employ a valid security measure such as
>> IP based ACL
>>
>
> Thanks Gary, changes look good to me. Are there better security measures
> to refer to than the IP based ACL (IP reputation is challenging with IPv6
> addresses and the IP address can possibly be spoofed) ?
>

Ah, fair. How about the authentication framework of the used protocol? i.e.
http auth for http, I think RFC 7235



> -Tiru
>
>
>>
>> On Mon, Jun 20, 2022 at 1:51 PM tirumal reddy <kondtir@gmail.com> wrote:
>>
>>> SECDIR Review draft-koster-rep
>>>
>>>
>>> Reviewer: Tirumaleswar Reddy
>>> Review result: Ready with Issues
>>>
>>>
>>>
>>> I have reviewed this document as part of the security directorate's
>>>
>>> ongoing effort to review all IETF documents being processed by the
>>>
>>> IESG..  Document editors and WG chairs should treat these comments
>>>
>>> just like any other last call comments.
>>>
>>>
>>>
>>> You may want to discuss the following security threats:
>>>
>>>
>>>
>>> a) Revealing disallowed URIs will make its paths easily discoverable.
>>> However, security by obscurity will not maintain or increase the security
>>> of the content provider (you can refer to
>>> https://datatracker.ietf.org/doc/html/rfc4949).
>>>
>>> b) A malicious crawler will not honor the disallow rules and can try to
>>> access the disallowed URIs, it should be mitigated by access control
>>> restrictions. Discuss any other count-measures used to block such malicious
>>> crawlers (like blocking the IP address).
>>>
>>> c) Attacks possible on crawlers because of a malicious robots.txt file.
>>>
>>>
>>> Cheers,
>>>
>>> -Tiru
>>>
>> --
Thanks,
Gary