From: Matthias Urlichs <matthias@urlichs.de>
To: wireguard@lists.zx2c4.com
Subject: Re: Future changes in crypto algorithms
Date: Fri, 22 Jun 2018 06:44:34 +0200 [thread overview]
Message-ID: <04238df1-db3d-66b3-32ca-c2ca7cb655ec@urlichs.de> (raw)
In-Reply-To: <CAEP1ZN=6aqe3B1sJNhDfB5c86emK+Gk2YJ9d-GaVVYuRzeXYGA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
On 18.06.2018 14:08, Vivien Malerba wrote:
> However, for any organization which will use WireGuard, even if admins
> are very effective at applying updates, updating all the endpoint
> systems simultaneously is not realistic. At the same time, it may be
> the case that the organization can't afford the downtime, in which
> case using WireGuard will simply not be an option, which is too bad.
Fixing any crypto weakness will require kernel updates and configuration
changes. A very easy config change, compared to all the other work you'd
have to do if a flaw is discovered that forces a different crypto
algorithm, is "use a second WG instance with a different UDP port".
A script that monitors connections to the new WG instance and
auto-disables the associated peer keys in the old instance is easy
enough to write.
Problem solved, no downgrade attack possible.
--
-- Matthias Urlichs
[-- Attachment #2: Type: text/html, Size: 1485 bytes --]
prev parent reply other threads:[~2018-06-22 4:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-18 12:08 Future changes in crypto algorithms Vivien Malerba
2018-06-21 22:58 ` Phil Hofer
2018-06-22 4:44 ` Matthias Urlichs [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=04238df1-db3d-66b3-32ca-c2ca7cb655ec@urlichs.de \
--to=matthias@urlichs.de \
--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).