From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: 2-factor auth options
Date: Fri, 22 Sep 2017 00:52:43 +0200 [thread overview]
Message-ID: <CAHmME9qPeMve8rRUNCsMpwHxgbXwomj2TCC_5CFKQoA+q0c3eQ@mail.gmail.com> (raw)
In-Reply-To: <20170921192148.GB2587@gmail.com>
Hi Konstantin,
The easiest way would be to add OTP to the part of your infra that
does the key exchange. That is, if you have some kind of HTTPS
REST-based API or an SSH-based API, you can have the server not accept
a new public key until the OTP challenge is satisfied.
Alternatively, you could do OTP in-band, in order to authorize that
public key for a certain window of time before inactivity. In this
scheme, you'd disallow access to the network segment based on firewall
rules until a certain in-band challenge is made -- perhaps by
contacting a certain sandboxed server and answering an OTP challenge
there
(At some point it is planned for WireGuard to have an API for sending
control messages directly to a public key, not via an IP address,
which will provide another option for in-band challenges (in addition
to dynamic configuration of IPs), but it's not immediately obvious
that this actually simplifies things, which is why I haven't yet
implemented the plan.)
What kind of infrastructure are you imagining? Is this for kernel.org?
Jason
next prev parent reply other threads:[~2017-09-21 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 19:21 Konstantin Ryabitsev
2017-09-21 22:18 ` David Woodhouse
2017-09-21 22:52 ` Jason A. Donenfeld [this message]
2017-09-22 14:45 ` Konstantin Ryabitsev
2017-09-22 23:19 ` Jason A. Donenfeld
2017-09-22 14:39 ` Joe Doss
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=CAHmME9qPeMve8rRUNCsMpwHxgbXwomj2TCC_5CFKQoA+q0c3eQ@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=konstantin@linuxfoundation.org \
--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).