From: Ferris Ellis <ferris@ferrisellis.com>
To: wireguard@lists.zx2c4.com
Subject: Rolling keys without service interuption
Date: Fri, 1 Dec 2017 21:45:04 -0500 [thread overview]
Message-ID: <2185653B-D592-4179-96D6-2CFC16F3E0B1@ferrisellis.com> (raw)
I was wondering if WireGuard supported dynamically updating / rolling keys f=
or connections? In many operations security models credentials are short liv=
ed and rotated regularly so that the consequences of any compromise can be m=
inimized. One problem, however, with this is that rolling credentials often c=
auses a service interrupt for the connection being rolling. Does WireGuard h=
ave a way to do this currently?
I wanted to ask the mailing list about this both for my own knowledge and fo=
r public documentation. Though, I presume the answer is no as WireGuard uses=
the keys as identity primitives for connections (which I think is the most h=
onest means of relating identity to authorization) and thus =E2=80=9Crolling=
=E2=80=9D them makes no sense.
Cheers,
Ferris
next reply other threads:[~2017-12-02 2:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 2:45 Ferris Ellis [this message]
2017-12-02 5:10 ` Aaron Jones
2017-12-02 13:31 ` Jason A. Donenfeld
2017-12-02 14:12 ` Ferris Ellis
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=2185653B-D592-4179-96D6-2CFC16F3E0B1@ferrisellis.com \
--to=ferris@ferrisellis.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).