From: sopium <sopium@mysterious.site>
To: "wireguard" <wireguard@lists.zx2c4.com>
Subject: Some questions about the protocol
Date: Wed, 15 Mar 2017 12:25:29 +0900 [thread overview]
Message-ID: <15acfffc263.e11103bb85901.2506936173902453879@mysterious.site> (raw)
In-Reply-To:
Hi,
These are some questions about some corner cases and details of
the protocol, that the paper does not seem to clearly specify:
* Do we send cookie reply messages in response to handshake
_response_ messages? My guess is YES? The figure in 5.4.1 only
shows the case that the responder chooses to reply with a
cookie message.
* Shall we start handshake in case the _previous_ session is not
alive, or too old? My guess is NO?
* When padding packets, how to avoid getting larger than MTU,
because we don't seem to know the MTU?
* When we receive a valid handshake init message, a secure
transport is session is created. Do we start sending with this
session immediately, in case there is still a valid previous
session? Because if the handshake response we send is lost, the
peer won't be able to decrypt our transport messages. The
problem should eventually go away, but the peer may experience
a brief blackout.
So, shall we wait until successfully receiving a transport
message with the new session, before start sending with
it? (When the previous session is still valid, of course.)
Regards,
Sopium
next reply other threads:[~2017-03-15 3:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 3:25 sopium [this message]
2017-03-15 5:52 ` sopium
2017-03-15 16:34 ` Jason A. Donenfeld
2017-03-20 5:06 ` sopium
2017-03-20 15:18 ` Jason A. Donenfeld
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=15acfffc263.e11103bb85901.2506936173902453879@mysterious.site \
--to=sopium@mysterious.site \
--cc=wireguard@lists.zx2c4.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).