Re: [Acme] acme-scoped-dns-challenges: account hash
Richard Körber <acme2@ml.shredzone.de> Sat, 16 March 2024 12:31 UTC
Return-Path: <acme2@ml.shredzone.de>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27BF9C14F609 for <acme@ietfa.amsl.com>; Sat, 16 Mar 2024 05:31:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=i7o.de
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 PiuPRKIg6jOq for <acme@ietfa.amsl.com>; Sat, 16 Mar 2024 05:31:34 -0700 (PDT)
Received: from i7o.de (i7o.de [95.216.117.94]) (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 5DA06C14F5EB for <acme@ietf.org>; Sat, 16 Mar 2024 05:31:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=i7o.de; s=dkim_1; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:From: References:To:Subject:MIME-Version:Date:Message-ID:Sender:Reply-To:Cc: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=ZZib5/GXRd2NrD9RpNReINVqH5D88qcU/ks0t/SKgtY=; b=DTjWlROfwOgdCm5Ct9SxeGA+lJ P7SRNyp41Bo3mAgf/o4Jg4fLKO8Yk3CyebKF3VZtVXjYWtgkYPtDuC9IMZbr1Hi2m9OvJywr0nxdb QEiM0sxAkzr/CDTA9dwJNENaaGgXIwMw+NkBQNS95219l3Kdfc8I2VPAzm4BE9VSCefA=;
Received: from p5ddd7d4a.dip0.t-ipconnect.de ([93.221.125.74] helo=[192.168.0.17]) by i7o.de with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.92.3) (envelope-from <acme2@ml.shredzone.de>) id 1rlTCD-0000O8-Ka for acme@ietf.org; Sat, 16 Mar 2024 13:31:29 +0100
Message-ID: <258ba3ba-2937-4c89-a97c-d319811325bb@ml.shredzone.de>
Date: Sat, 16 Mar 2024 13:31:29 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: IETF ACME <acme@ietf.org>
References: <7de8d083-2935-4e8a-932d-c834eb90be70@ml.shredzone.de> <7f8c034c-a222-441e-8b7d-b034b78d3535@gmail.com>
From: Richard Körber <acme2@ml.shredzone.de>
In-Reply-To: <7f8c034c-a222-441e-8b7d-b034b78d3535@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/I_tJ9zBxjBDb5Koz194Cs4ga4pg>
Subject: Re: [Acme] acme-scoped-dns-challenges: account hash
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 16 Mar 2024 12:31:39 -0000
Thank you! Yes, that fixed the problem. Looking at the specs again, I should have figured it out myself. Thanks, again! > it was "https://example.com/acme/acct/ExampleAccount" but looks like > autometic line change was in bad place > > 2024-03-16 오후 8:19에 Richard Körber 이(가) 쓴 글: >> Hello! >> >> In section 4 of draft-ietf-acme-scoped-dns-challenges-00, an example >> is given about how to calculate the hash of the account resource URL. >> >> The example gives this account URL: "https://example.com/acme/acct/" >> >> According to the example, the result of the >> "base32(SHA-256(<ACCOUNT_RESOURCE_URL>)[0:10])" operation is supposed >> to be "ujmmovf2vn55tgye". >> >> However, in my implementation I get the hash "jkk3cewh6vmq7rgf". >> >> I checked my code multiple times, but could not find an implementation >> error. >> >> Before I am going to waste more time with debugging, I'd like to ask >> if the example result in the specs is correct? >> >> Thank you! >> >> Best, >> Richard Koerber >> >> _______________________________________________ >> Acme mailing list >> Acme@ietf.org >> https://www.ietf.org/mailman/listinfo/acme > > _______________________________________________ > Acme mailing list > Acme@ietf.org > https://www.ietf.org/mailman/listinfo/acme
- [Acme] acme-scoped-dns-challenges: account hash Richard Körber
- Re: [Acme] acme-scoped-dns-challenges: account ha… Seo Suchan
- Re: [Acme] acme-scoped-dns-challenges: account ha… Richard Körber
- Re: [Acme] acme-scoped-dns-challenges: account ha… Amir Omidi