Skip to content
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

Github 2FA #411

Open
My1 opened this issue May 27, 2016 · 0 comments
Open

Github 2FA #411

My1 opened this issue May 27, 2016 · 0 comments

Comments

@My1
Copy link

My1 commented May 27, 2016

well when trying to waltz a 2FA'd guthub account you get pretty much nothing.

now we have 2 options. either setup waltz as a 2FA device either by posing as U2F device or by re-setting up the 2FA Application so that waltz also can get the 2FA seed.
But in my opinion this option decreases security because everything is stored at the same place.

it may be true that waltz probably some kind of 2FA-based system but the problem is even if you make the way to the key 2FA, somebody could crack the database and especially in post-quantum where the effective security gets halved, which has QUITE an impact on the security of the database.
and then you essentially get a 2 sided 1 factor system because the same thing (the passowrd) is stored in 2 factors (1 your knowledge 2 the database) which makes the attack vector quite a bit wider.

Those people can turn off 2FA because that's NOT how you use it.

and then we have option 2: the one which sounds a lot better to me:
display the part of the page with the 2FA options (div id login) and ask for the code.

this would be the best answer in my opinion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant