-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
WIP: Initial feature for OTP / authenticator passwords #5306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5306 +/- ##
==========================================
+ Coverage 93.88% 93.89% +0.01%
==========================================
Files 123 123
Lines 8972 9007 +35
==========================================
+ Hits 8423 8457 +34
- Misses 549 550 +1
Continue to review full report at Codecov.
|
3c16166
to
b395f15
Compare
Tokens should be secured at rest, check out 7.5 of the specification: https://www.ietf.org/rfc/rfc4226.txt. If the Depending on how you want the 2FA to be used, IE (only at login) you could use composite keys (Section 8), the user's password/pin is used to generate the token, meaning the database effectively only stores a seed. |
Ok, we could introduce a runtime encryption key for the tokens, different from the master key. Or just use the master key. What do you think? Sent with GitHawk |
Probably best to use a different key, as if you somehow gained access to a master key, you also gain the power to query the token.
—
…Sent from my iPhone
On 2 Feb 2019, at 14:49, Florent Vilmart ***@***.***> wrote:
Ok, we could introduce a runtime encryption key for the tokens, different from the master key. Or just use the master key. What do you think?
Sent with GitHawk
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Makes sense, we can add the option. I also will likely add an OTP adapter, so users will be able to transmit the OTP password by email or phone if they want to. Sent with GitHawk |
Good idea - I'm looking for an email based solution - (although I want a single auth, email only, passwordless solution) |
@awgeorge any interest in getting this across the finish line? If you can pick up where @flovilmart left off, I can get up to speed so I can review it with you. |
This is something I’m interested in - I’ll take a look and see what’s left to get this implantation merged.
—
…Sent from my iPhone
On 6 Apr 2019, at 17:28, Arthur Cinader ***@***.***> wrote:
@awgeorge any interest in getting this across the finish line? I can review and get up to speed if it is still something you'd like to see in the product?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
Not at this time, feel free to take it on. Thanks. |
Alright @awgeorge. Thanks for the update. |
Hey guys! is it finished yet? If anyone is interested we can do it together. |
No description provided.