IETF Logo Mail Archive

HSTS Fingerprinting.

Mike West <mkwst@google.com> Wed, 18 September 2019 01:13 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1F5612007A for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 17 Sep 2019 18:13:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.406
X-Spam-Level:
X-Spam-Status: No, score=-10.406 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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, HTML_OBFUSCATE_10_20=0.093, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z0_ITxko4WTy for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 17 Sep 2019 18:13:13 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [IPv6:2603:400a:ffff:804:801e:34:0:38]) (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 78DA912006F for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 17 Sep 2019 18:13:13 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1iAOUl-0004WB-03 for ietf-http-wg-dist@listhub.w3.org; Wed, 18 Sep 2019 01:10:59 +0000
Resent-Date: Wed, 18 Sep 2019 01:10:58 +0000
Resent-Message-Id: <E1iAOUl-0004WB-03@frink.w3.org>
Received: from titan.w3.org ([2603:400a:ffff:804:801e:34:0:4c]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <mkwst@google.com>) id 1iAOUg-0004V3-NW for ietf-http-wg@listhub.w3.org; Wed, 18 Sep 2019 01:10:54 +0000
Received: from mail-lj1-x22d.google.com ([2a00:1450:4864:20::22d]) by titan.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <mkwst@google.com>) id 1iAOUf-0003sa-8t for ietf-http-wg@w3.org; Wed, 18 Sep 2019 01:10:54 +0000
Received: by mail-lj1-x22d.google.com with SMTP id 7so5424654ljw.7 for <ietf-http-wg@w3.org>; Tue, 17 Sep 2019 18:10:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=xD+wz6ACd8dXxZrpXx625RUzibLP0uqTwg5JYPB2Cv8=; b=tVIO9ehhmlBduDOkaIvZIiN5CwclnsiCYc+NLNHiaHUGV3ozYi9aGgF0DF4yuwxM85 BfoB71BtnGG2bj9sEV3vMImzVzuYNzekqUoOwEMW4GRuFLZ+RIUrQBrsmkB2K4KNaq/V 2rCt+W321S+CHlFEmn02oagrJYh9KZxl4B1trMThvU+S9RU+lhAzS2R6qY+uRlKYXsn9 k/HCAdKsnA3QLzHymIcJCd5v4RZCjVv8uOhnJkV5fbOjnVWfYYhZNax4Lon8Z1B1BIaC AejJRIXXGJFLRNHIfMD/V6V1GVJd9ZDVy/4TqXFAjYFAxj6iST1rFLQLyug4QfzJjT03 7G8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=xD+wz6ACd8dXxZrpXx625RUzibLP0uqTwg5JYPB2Cv8=; b=j/v0nOo1x3BzjZmj7MlDOGwf3SkJCz/hRr2VbUUxU5drom9IRxxFTOHmU4Rsn8cg5p yvuuRsPXeNSCswilDeK+u/sXmhsOcGG2B0kitoGAiYHNo3z0bSGgByulZQSk/5oAdZdf thQ3s6NIS+dwfzXX3x1ivZs2nMBlfKNqB+b4wfZUlnunJXCiy9RnVLcV/JoJJycaEBRg /il4rgWcMSPQBix2Udu6jizUvLGHlOvV3Ke13fHj71xSmyW0qRCWeYAS317yP8ENV+46 Wzf1Uu1difvKZPqtB7hRN9jlhYw5EUgefST1r2lZxw2XbRvMvJVuo1LNbbuNGUJWIc80 4DtQ==
X-Gm-Message-State: APjAAAXyBVZsVZoqDm1bstEHaIdW07EQaAzcAu3QeRdWKKNpCSH28CW/ UZrvRxpUPN3SNccLAjve6MxK0N1QIvSgaRcQshf0EbexZjmsADeZ
X-Google-Smtp-Source: APXvYqzX9SXzEiwapKPFYrlcFjY+tP4w+/NfOkO1vyIgd5n5xsH/HlGugUHaOtb67W+K+oqk9UIoTvJk1aGZtkhfkkY=
X-Received: by 2002:a2e:8054:: with SMTP id p20mr626527ljg.36.1568769030955; Tue, 17 Sep 2019 18:10:30 -0700 (PDT)
MIME-Version: 1.0
From: Mike West <mkwst@google.com>
Date: Wed, 18 Sep 2019 10:10:18 +0900
Message-ID: <CAKXHy=eh2JzMdKUFFKataSfomfQUcNc4kVhiRbjevQogEspvYA@mail.gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
Cc: Mark Nottingham <mnot@mnot.net>, John Wilander <wilander@apple.com>, Jeff Hodges <jdhodges@google.com>
Content-Type: multipart/alternative; boundary="000000000000d39e040592c980b2"
Received-SPF: pass client-ip=2a00:1450:4864:20::22d; envelope-from=mkwst@google.com; helo=mail-lj1-x22d.google.com
X-W3C-Hub-Spam-Status: No, score=-22.3
X-W3C-Hub-Spam-Report: AWL=2.203, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, HTML_OBFUSCATE_10_20=0.093, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1iAOUf-0003sa-8t 05b0d43fe256ddd4311e87c319ad70e0
X-Original-To: ietf-http-wg@w3.org
Subject: HSTS Fingerprinting.
Archived-At: <https://www.w3.org/mid/CAKXHy=eh2JzMdKUFFKataSfomfQUcNc4kVhiRbjevQogEspvYA@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37021
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

A year or two ago, +John Wilander <wilander@apple.com> and others at Apple
proposed some changes to HSTS in
https://webkit.org/blog/8146/protecting-against-hsts-abuse/ that went some
way towards mitigating the abuses documented in Section 14.9 of RFC6797
<https://tools.ietf.org/html/rfc6797#section-14.9>. Given some shifts in
the way we're thinking about some other concepts, I've written up a short
proposal at https://github.com/mikewest/strict-navigation-security that
builds upon and simplifies Apple's proposal. We discussed it briefly at
yesterday's webappsec meeting
<https://github.com/w3c/webappsec/blob/master/meetings/2019/2019-09-TPAC-minutes.md#hsts-fingerprinting>,
and there seems to be interest in doing something in this space.

+Mark Nottingham <mnot@mnot.net> and +Jeff Hodges
<jdhodges@google.com> suggested
that I loop this group into that conversation, as the original websec group
has disbanded. Is it a topic this group would like to pick up? If not,
would y'all be comfortable with us defining some web browser behavior/Fetch
integration in webappsec that constrains the existing RFC?

Thanks!

-mike

v2.23.0 | Report a Bug | By Email