From: Nico Schottelius <nico.schottelius@ungleich.ch>
To: "Rémi Lapeyre" <remi.lapeyre@lenstra.fr>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Adding 2FA to WireGuard
Date: Fri, 13 Sep 2019 22:22:55 +0900 [thread overview]
Message-ID: <875zlw8h5c.fsf@line.ungleich.ch> (raw)
In-Reply-To: <CAFsReqTThNXkkPH+_YHOhC_DEbKwY5rPdmRDVJxLiTQbhfAbDA@mail.gmail.com>
Hey Rémi,
Rémi Lapeyre <remi.lapeyre@lenstra.fr> writes:
> Hi Nico, yes pyotp is the implementation I use on the server, but anything
> Compatible withrfc6238 should work.
That sounds about right!
>> We have written ungleich-otp [0] that extends the otp approach with
>> realms similar to kerberos.
>
> This looks interesting, I will move the code that validate the OTP in a
> separate class so that another validation backend like one based on this
> project can be used instead of reading the seeds from a SQLite file like
> I’m doing now.
>
> I did not see any kind of cool down in
> https://code.ungleich.ch/ungleich-public/ungleich-otp/blob/master/otpauth/serializer.py.
> Are you not worried that someone
> could try to brute-force the OTP validation?
That is a good point! We will certainly want to fix that, as the seed
entropy is not *that* big.
Best regards,
Nico
--
Your Swiss, Open Source and IPv6 Virtual Machine. Now on www.datacenterlight.ch.
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-09-13 13:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 21:01 Rémi Lapeyre
2019-09-13 12:49 ` Nico Schottelius
2019-09-13 13:17 ` Rémi Lapeyre
2019-09-13 13:22 ` Nico Schottelius [this message]
2019-09-15 16:46 ` Rene 'Renne' Bartsch, B.Sc. Informatics
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=875zlw8h5c.fsf@line.ungleich.ch \
--to=nico.schottelius@ungleich.ch \
--cc=remi.lapeyre@lenstra.fr \
--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).