Date: Mon, 19 Mar 2018 02:40:01 -0700
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+0166e4abadd46db6f6d47cfe71dd6536d6a9ba4641c0de9992cf0000000116c7477192a169ce0cb13645@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/377/374153046@github.com>
In-Reply-To: <quicwg/base-drafts/issues/377@github.com>
References: <quicwg/base-drafts/issues/377@github.com>
Subject: Re: [quicwg/base-drafts] ICMP and ICMPv6 (Type:
 DestinationUnreachable) (#377)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5aaf8571869f4_72c62add78750ec4188758";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/HMskx3fX7e4U-o8AQw3hny_m-fU>


----==_mimepart_5aaf8571869f4_72c62add78750ec4188758
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

In the case where you have an authenticated client, you are not necessarily vulnerable to vneg attacks because the client auth could be version specific. You could replace the version identifier with a nonce signed by the client and possibly some additional context to help identify the clients public key and identity - this is the tricky part.

-- 
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/377#issuecomment-374153046
----==_mimepart_5aaf8571869f4_72c62add78750ec4188758
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>In the case where you have an authenticated client, you are not necess=
arily vulnerable to vneg attacks because the client auth could be version=
 specific. You could replace the version identifier with a nonce signed b=
y the client and possibly some additional context to help identify the cl=
ients public key and identity - this is the tricky part.</p>

<p style=3D"font-size:small;-webkit-text-size-adjust:none;color:#666;">&m=
dash;<br />You are receiving this because you are subscribed to this thre=
ad.<br />Reply to this email directly, <a href=3D"https://github.com/quic=
wg/base-drafts/issues/377#issuecomment-374153046">view it on GitHub</a>, =
or <a href=3D"https://github.com/notifications/unsubscribe-auth/AWbkq08Js=
T5WfVyDgbAG7GIn8e33amI_ks5tf3zxgaJpZM4MXqun">mute the thread</a>.<img src=
=3D"https://github.com/notifications/beacon/AWbkq2tq_VflQB0ZIFeBze503P31A=
p_6ks5tf3zxgaJpZM4MXqun.gif" height=3D"1" width=3D"1" alt=3D"" /></p>
<div itemscope itemtype=3D"http://schema.org/EmailMessage">
<div itemprop=3D"action" itemscope itemtype=3D"http://schema.org/ViewActi=
on">
  <link itemprop=3D"url" href=3D"https://github.com/quicwg/base-drafts/is=
sues/377#issuecomment-374153046"></link>
  <meta itemprop=3D"name" content=3D"View Issue"></meta>
</div>
<meta itemprop=3D"description" content=3D"View this Issue on GitHub"></me=
ta>
</div>

<script type=3D"application/json" data-scope=3D"inboxmarkup">{"api_versio=
n":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name"=
:"GitHub"},"entity":{"external_key":"github/quicwg/base-drafts","title":"=
quicwg/base-drafts","subtitle":"GitHub repository","main_image_url":"http=
s://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6=
-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubuserconte=
nt.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","=
action":{"name":"Open in GitHub","url":"https://github.com/quicwg/base-dr=
afts"}},"updates":{"snippets":[{"icon":"PERSON","message":"@mikkelfj in #=
377: In the case where you have an authenticated client, you are not nece=
ssarily vulnerable to vneg attacks because the client auth could be versi=
on specific. You could replace the version identifier with a nonce signed=
 by the client and possibly some additional context to help identify the =
clients public key and identity - this is the tricky part."}],"action":{"=
name":"View Issue","url":"https://github.com/quicwg/base-drafts/issues/37=
7#issuecomment-374153046"}}}</script>=

----==_mimepart_5aaf8571869f4_72c62add78750ec4188758--