Re: [quicwg/base-drafts] Why are stateless reset tokens 16 bytes long? (#2018)
ekr <notifications@github.com> Mon, 26 November 2018 13:21 UTC
Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FDB6130DEC for <quic-issues@ietfa.amsl.com>; Mon, 26 Nov 2018 05:21:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 kPxZJGM04cRL for <quic-issues@ietfa.amsl.com>; Mon, 26 Nov 2018 05:20:58 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D9E612D4ED for <quic-issues@ietf.org>; Mon, 26 Nov 2018 05:20:58 -0800 (PST)
Date: Mon, 26 Nov 2018 05:20:57 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1543238457; bh=6+6vQQ4iVXQZ5PAek7Ii4JzxZhbgtotElK46wIBGozI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=fdRdunkS9SVF5fLW9rnOvhz5irKW2WhHr2IMT/dDBnbLWd5jRUxL/M6hdza/vf/pS ZNU2+5vZXaSyyj/rn2RmvmkhXXYRJqAUQmyq6BO/MqaY9ZSOITyvp3yAiVvVOb9Jex P9UVByLqFcETtpWNwcVCYgIRKVpjjNTqH4gDIaUs=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab03b8380161a726057ec107384d147ac7e3047afa92cf000000011813b53992a169ce16c2396c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2018/441636308@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2018@github.com>
References: <quicwg/base-drafts/issues/2018@github.com>
Subject: Re: [quicwg/base-drafts] Why are stateless reset tokens 16 bytes long? (#2018)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bfbf3399579a_174c3fed294d45bc1749b5"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/e916fSZoOmLk3hFjUlpIh_FermY>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Nov 2018 13:21:00 -0000
Oh, yes, sorry. Long day and I was thinking retry token. On Sun, Nov 25, 2018 at 7:35 PM Martin Thomson <notifications@github.com> wrote: > Self-encryption isn't useful here. Self-encryption of a connection ID, > sure, but the producer and consumer of a stateless reset token is different. > > — > You are receiving this because you commented. > Reply to this email directly, view it on GitHub > <https://github.com/quicwg/base-drafts/issues/2018#issuecomment-441509663>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ABD1ofWDKDVXAo3LxuvusAVxuhL46Rjcks5uy2F7gaJpZM4YnRg3> > . > -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/quicwg/base-drafts/issues/2018#issuecomment-441636308
- [quicwg/base-drafts] Why are stateless reset toke… Marten Seemann
- Re: [quicwg/base-drafts] Why are stateless reset … MikkelFJ
- Re: [quicwg/base-drafts] Why are stateless reset … Kazuho Oku
- Re: [quicwg/base-drafts] Why are stateless reset … Marten Seemann
- Re: [quicwg/base-drafts] Why are stateless reset … Kazuho Oku
- Re: [quicwg/base-drafts] Why are stateless reset … Martin Thomson
- Re: [quicwg/base-drafts] Why are stateless reset … ekr
- Re: [quicwg/base-drafts] Why are stateless reset … Martin Thomson
- Re: [quicwg/base-drafts] Why are stateless reset … Kazuho Oku
- Re: [quicwg/base-drafts] Why are stateless reset … Martin Thomson
- Re: [quicwg/base-drafts] Why are stateless reset … Kazuho Oku
- Re: [quicwg/base-drafts] Why are stateless reset … ekr
- Re: [quicwg/base-drafts] Why are stateless reset … Dmitri Tikhonov
- Re: [quicwg/base-drafts] Why are stateless reset … Martin Thomson
- Re: [quicwg/base-drafts] Why are stateless reset … Martin Thomson