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

Expose TOTP provisioning code for manual entry #6114

Closed
garyemiller opened this issue Jun 27, 2019 · 5 comments · Fixed by #6119
Closed

Expose TOTP provisioning code for manual entry #6114

garyemiller opened this issue Jun 27, 2019 · 5 comments · Fixed by #6119
Assignees
Labels
UX/UI design, user experience, user interface

Comments

@garyemiller
Copy link

I use the command line tool "oathtool" for my 2FA. But your 2FA enrollment page only shows a QR code. How do I get the key for oathtool use?

@nlhkabu nlhkabu changed the title How to get the 2FA key? Expose TOTP provisioning code for manual entry Jun 28, 2019
@nlhkabu nlhkabu added this to the OTF Security work milestone Jun 28, 2019
@nlhkabu nlhkabu added the UX/UI design, user experience, user interface label Jun 28, 2019
@nlhkabu
Copy link
Contributor

nlhkabu commented Jun 28, 2019

Hi @garyemiller thanks for opening this ticket.

Currently we don't expose this information in the user interface, but we can take a look into this.

@woodruffw I assume we can simply output this information on the provisioning page? If you want to make a PR adding this to the template, I can style it.

@woodruffw
Copy link
Member

woodruffw commented Jun 28, 2019

I assume we can simply output this information on the provisioning page? If you want to make a PR adding this to the template, I can style it.

Yep, should be as simple as that. I'll open a PR in a bit.

Edit: An idea: we might want to expose this as a clipboard action. @nlhkabu would that be possible?

@garyemiller
Copy link
Author

@woodruffw: without testing it, your pull request looks good to me.

Everybody note that github. this system we are on now, does expose the TOTP key. It also goes further and give the user 10 backup codes. Just be sure there is some recovery method that does not suck.

@di
Copy link
Member

di commented Jun 28, 2019

@garyemiller Please also note that Github is also a large for-profit company that is worth several billion dollars. PyPI is a entirely volunteer staffed project, with the exception of the occasional contractor hired by various grants we are awarded.

As such, I'd like to ask you to improve your tone on this issue tracker: everyone here is working very hard to provide something "that does not suck". We're aware that folks would like to have recovery codes (see #5800), however we don't have the funding to add this in the current scope of work, and haven't had a volunteer with the time to add the feature either.

@garyemiller
Copy link
Author

@di: Way ahead of you. That is why made it a "please note", not an issue or an RFE.

You also misunderstood my comment about "does not suck". I did not mean to imply anything about anybody or anyone's work to date. Chill.

I also work on many 100% volunteer FOSS projects and as such feel your pain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UX/UI design, user experience, user interface
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants