wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: Trevor Perrin <trevp@trevp.net>
To: Karolin Varner <karo@cupdev.net>
Cc: wireguard@lists.zx2c4.com, noise <noise@moderncrypto.org>, labo@labo.rs
Subject: Re: another thread on montonic counter alternatives
Date: Mon, 9 Aug 2021 17:09:58 -0700	[thread overview]
Message-ID: <CAGZ8ZG1wU=A4Yu0v7938pRL2d1p+Gj_Mh8+9=sdA-ScHZiYVTQ@mail.gmail.com> (raw)
In-Reply-To: <6cd87006-902a-3411-4928-67ec5d1f77e2@cupdev.net>

On Sun, Aug 8, 2021 at 5:04 PM Karolin Varner <karo@cupdev.net> wrote:
>
> 2) Fall back to an interactive handshake using cookies. Define a protocol version two, mandate that in V2 the cookie must be mixed into the handshake hash. Assign a cookie in case of timestamp failure.

That could be deployed in a backwards-compatible way, I think?  If the
client's V1 handshake is rejected due to an old timestamp, the client
is given the cookie which enables it to do the V2 handshake?


> Jason pointed out, that it would be preferable to use a Noise-XK handshake which is a standard fully-interactive handshake but 1.5-RTT. I was assuming 1-RTT-ness was a necessity.
> Of course, coming up with a new handshake is…generally foolish and even though both my proposal technially fit into the noise-IK pattern, noise-XK certainly is more trustworthy.

I thought the goal of IK here was: server only stores state if client
is authenticated.  And the goal of timestamp was: replayed messages
can't invalidate an existing session state.

If those are still the requirements I'm not sure that XK meets them.
XK has better identity hiding (only reveals the client's identity
after forward-secrecy is negotiated), but that trades off against the
requirement that unauthenticated clients can't cause servers to store
state.  (Unless you put the state in a cookie, I suppose - which you
also suggested...)

Trevor

  reply	other threads:[~2021-08-10  0:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-08 22:33 Jason A. Donenfeld
2021-08-08 23:18 ` Karolin Varner
2021-08-10  0:09   ` Trevor Perrin [this message]
2021-08-10  7:53     ` Karolin Varner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAGZ8ZG1wU=A4Yu0v7938pRL2d1p+Gj_Mh8+9=sdA-ScHZiYVTQ@mail.gmail.com' \
    --to=trevp@trevp.net \
    --cc=karo@cupdev.net \
    --cc=labo@labo.rs \
    --cc=noise@moderncrypto.org \
    --cc=wireguard@lists.zx2c4.com \
    --subject='Re: another thread on montonic counter alternatives' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).