From: Ferris Ellis <ferris@ferrisellis.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Rolling keys without service interuption
Date: Sat, 2 Dec 2017 09:12:44 -0500 [thread overview]
Message-ID: <1CF77718-1E9B-4947-852F-930B6784F068@ferrisellis.com> (raw)
In-Reply-To: <CAHmME9q2h_QedDGfmbk-eaniAqB1DV7JUJZ0r36fYmM0Jr8Vow@mail.gmail.com>
Jason,
Awesome! That=E2=80=99s exactly what I needed :) I=E2=80=99ll try it out and=
post a follow up if I have any issues.
Cheers,
Ferris
> On Dec 2, 2017, at 8:31 AM, Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>=20
> Hi Ferris,
>=20
> Firstly, WireGuard already has forward secrecy, which means every new
> session (negotiated every 2 minutes) has fresh keys that are
> forgotten, so old recorded traffic cannot be compromised.
>=20
> It sounds like, however, you want to rotate the long term static
> "identity" keys. This is possible to do gracefully. If you change the
> private key of an interface, it won't actually be used until the next
> handshake occurs, which means you can rollover gracefully. Likewise
> you can add new peers (via public keys) dynamically at runtime. Moving
> a distinct allowed IP from one peer to another is an atomic operation
> as well.
>=20
> Hope this helps!
>=20
> Regards,
> Jason
prev parent reply other threads:[~2017-12-02 14:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 2:45 Ferris Ellis
2017-12-02 5:10 ` Aaron Jones
2017-12-02 13:31 ` Jason A. Donenfeld
2017-12-02 14:12 ` Ferris Ellis [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=1CF77718-1E9B-4947-852F-930B6784F068@ferrisellis.com \
--to=ferris@ferrisellis.com \
--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).