From: Derrick Lyndon Pallas <derrick@pallas.us>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Long outage when changing private key
Date: Thu, 24 Jan 2019 17:55:49 -0800 [thread overview]
Message-ID: <85e1199d-e81f-a2ad-d571-38b765f9c973@pallas.us> (raw)
In-Reply-To: <CAHmME9oSPTCvsnEy9nMfMtzWGVC9wWKwgpQbUCxKjA_2AvdtfQ@mail.gmail.com>
Thanks for taking a look, I should have spent 30 more minutes
investigating myself. Please see the patch set I just submitted.
Resetting the handshake timer is also necessary or else it takes until
the expiration of that timer to actually happen in my setup. It seemed
worth putting into a utility function in peers.c, rather than all in
netdev.c, so I did that. I checked the preshared key case and that seems
to work fine still. ~Derrick
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-01-25 1:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 21:22 Derrick Lyndon Pallas
2019-01-24 23:25 ` Derrick Lyndon Pallas
2019-01-24 23:59 ` Jason A. Donenfeld
2019-01-25 0:00 ` Jason A. Donenfeld
2019-01-25 1:55 ` Derrick Lyndon Pallas [this message]
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=85e1199d-e81f-a2ad-d571-38b765f9c973@pallas.us \
--to=derrick@pallas.us \
--cc=Jason@zx2c4.com \
--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).