IETF Logo Mail Archive

Re: Standard URL safe digest form and hash algorithm list

Lucas Pardue <lucaspardue.24.7@gmail.com> Fri, 29 April 2022 07:02 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 46AF6C159822 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 29 Apr 2022 00:02:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.751
X-Spam-Level:
X-Spam-Status: No, score=-2.751 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 9PdwO6D0NinB for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 29 Apr 2022 00:01:57 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7F56C157B5E for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 29 Apr 2022 00:01:57 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1nkKbO-0006FM-1p for ietf-http-wg-dist@listhub.w3.org; Fri, 29 Apr 2022 06:59:42 +0000
Resent-Date: Fri, 29 Apr 2022 06:59:42 +0000
Resent-Message-Id: <E1nkKbO-0006FM-1p@lyra.w3.org>
Received: from titan.w3.org ([128.30.52.76]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <lucaspardue.24.7@gmail.com>) id 1nkKbN-0006ES-0k for ietf-http-wg@listhub.w3.org; Fri, 29 Apr 2022 06:59:41 +0000
Received: from mail-qv1-xf2f.google.com ([2607:f8b0:4864:20::f2f]) by titan.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <lucaspardue.24.7@gmail.com>) id 1nkKbL-0007hz-Oa for ietf-http-wg@w3.org; Fri, 29 Apr 2022 06:59:40 +0000
Received: by mail-qv1-xf2f.google.com with SMTP id a5so4807815qvx.1 for <ietf-http-wg@w3.org>; Thu, 28 Apr 2022 23:59:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=uloHqu3VeS29C+6vSBXYcKs9gc3KwMgnPkhrQOKEcI4=; b=ZbKLlMtRrmlV9LtH+zQ7lt18mdSOm4ldia+rlQPCR62NaU+dByr5eVr3AjuO4hOMjS /w/MzEFG81oJb8TAD3qHrZ0es/K7PqgywvuvC94tTsVI2IdBxekX2loiFuy4oLqXhy2Z 1hYCNiCzyr0F0G9BBYw/moXwf+29mB0BuK4PFz/CQSF9LXeFksE49rT3xIwxWY901x0U KduGLW8+9cZ6vgTKthGx0Q9XEsNKZoApsB+gyCJl2B0BBl3vdn5pv7tgVVrL3MtfoLwU 5hA5FgTeYNAft443WTceTmiqr//gyrt3KPu22yJWe0N+KcY0KwfBRy93f88HBV0Lfm64 zmEA==
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=uloHqu3VeS29C+6vSBXYcKs9gc3KwMgnPkhrQOKEcI4=; b=UVD4RNrgXk3Y5n8S5Txx1iLRXZBAIg8jxCPHavnWwKS0RkdgHeaVtwa36TTyYrzR3g ooaVCAbLBlXlzGEJ6ioK61rIaEY08/dUdJF48G8yl7wH/o6JWEJkEfGsDKgxjsJoO6St xHPK77QnNh+qAVosX5JtZ9LOpiIEy5CNvO3E4xsf9wzXoRKznm/haGUh5WTkWV9UYG+6 iaecIrq0Nnk3UAD2bNPjY0TAsSql2DTP/xjLS3f0w4uVDU7WHRvRZBpcYOE65qOXfNTb 0lsz6njfKWpW7WijCdNFliCl6GNYceaicESX/Bz8l1JuU2fLdTr8mNaLDpt93kQm6sEk fkfg==
X-Gm-Message-State: AOAM530U7HIEVNycxzgIN6tDx/i9hV3kuip+ZTi/oBpyUQgU2sJIt2pQ gMah+hlJBbtyLr4xtCTCWFEIL5rwgkuDxko7Ais=
X-Google-Smtp-Source: ABdhPJw50KCYQUcoxdnmLN6+ieVuGPUOqrBpw4w5AvihWcuQK04MXL6CgUIWwUz/2dNiiqSpjQ8gE2eb5/+DVg4X/pQ=
X-Received: by 2002:a05:6214:d04:b0:454:674b:a4e4 with SMTP id 4-20020a0562140d0400b00454674ba4e4mr24385210qvh.4.1651215568972; Thu, 28 Apr 2022 23:59:28 -0700 (PDT)
MIME-Version: 1.0
References: <e878f0c7-26d0-163b-def4-7b51c3e031c0@profian.com> <CAMRHeuzfTOEX_f70MogQXp+=BMRDLTgbmrvyv9Xs7m+5jcSqiw@mail.gmail.com>
In-Reply-To: <CAMRHeuzfTOEX_f70MogQXp+=BMRDLTgbmrvyv9Xs7m+5jcSqiw@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Fri, 29 Apr 2022 07:59:19 +0100
Message-ID: <CALGR9oaHCHgQms8xkT1BM5+hQ13_b+w0igBp6Sfo4LxoSM+9wQ@mail.gmail.com>
To: Roberto Polli <roberto@teamdigitale.governo.it>
Cc: Roman Volosatovs <roman@profian.com>, HTTP Working Group <ietf-http-wg@w3.org>, nathaniel@profian.com
Content-Type: multipart/alternative; boundary="0000000000006fb0ef05ddc595f4"
Received-SPF: pass client-ip=2607:f8b0:4864:20::f2f; envelope-from=lucaspardue.24.7@gmail.com; helo=mail-qv1-xf2f.google.com
X-W3C-Hub-DKIM-Status: validation passed: (address=lucaspardue.24.7@gmail.com domain=gmail.com), signature is good
X-W3C-Hub-Spam-Status: No, score=-4.8
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: titan.w3.org 1nkKbL-0007hz-Oa 514cecbde3bf582be02356b07d39d890
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Standard URL safe digest form and hash algorithm list
Archived-At: <https://www.w3.org/mid/CALGR9oaHCHgQms8xkT1BM5+hQ13_b+w0igBp6Sfo4LxoSM+9wQ@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/40014
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>

Hey,

On Fri, 29 Apr 2022, 07:44 Roberto Polli, <roberto@teamdigitale.governo.it>
wrote:

> Hi Roman,
>
> Can you please file a github issue requesting the registration of two more
> digest algorithms?
>
> About the encoding, we decided to delegate it to SF. I don't remember why
> it was decided to use but instead of b64url though...
>
> Isn't decode/encode a viable solution?
>

I don't really see the issue here. The computed digest bytestring is the
same regardless of the serialization format for sending it over the wire.
The problem seems to be with trying to send the Structured Fields Byte
Sequence type in a URL. There's doesn't seem any need to do that, instead
you can just send the base64 encoding of the computed digest without the
colons.

Cheers
Lucas

v2.23.0 | Report a Bug | By Email