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

recovery keys for OTP [feature] #2263

Closed
Leptopoda opened this issue Sep 2, 2018 · 4 comments
Closed

recovery keys for OTP [feature] #2263

Leptopoda opened this issue Sep 2, 2018 · 4 comments

Comments

@Leptopoda
Copy link

Expected Behavior

some services (e.g. GItHub) give you one time recovery/backup codes when 2FA/OTP is enabled

Current Behavior

Currently the only option is to write them into the "Notes" sector but because those are one time you have to edit the entry every time to delete the current one

Possible Solution

<-->

@droidmonkey
Copy link
Member

This is handled by #1167

@RAnders00
Copy link

RAnders00 commented Jul 6, 2024

Sorry for reviving this old ticket, but the related PR is not related to this feature request? It's about generating a QR code from the stored secret, this feature request is for adding first-class support for storing recovery tokens handed out by services without having to use the Notes field. Can we reopen this?

Note: KeePassOTP stores the recovery codes in the attribute KeePassOTP.RecoveryCodes, maybe we should support this attribute as well.

@droidmonkey
Copy link
Member

Why is that necessary? Notes is a great place to store them, or make your own attribute. This absolutely doesn't need a GUI feature.

@Leptopoda
Copy link
Author

You are completely right. My idea was an extra field for storing secrets that can be marked as already used.
This is indeed a very old issue so you might be better of opening a new one. (as this one didn't ever gain any traction).

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

3 participants