-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
Feature request: possibility to revoke/burn a secret #170
Comments
Well, just call the URL you got and retrieve it, it's immediately deleted from the server and therefore gone. (Deleting the secret as soon as it's retrieved once is a core feature of OTS.) |
I agree, still I think it would more user friendly to be able to revoke a secret via a UI button, without having to view it. |
Closing, as this feature is only a nice to have, |
Then why are you closing it, if you want to have it? |
Hi Luzifer, I've had a few moments when I needed that button. |
I agree, that was my sentiment originally as well, just did not want to waste valuable development time on a trivial feature. |
Signed-off-by: Knut Ahlers <knut@ahlers.me>
@mshedsilegx @HappyMan4 Please have a look at the attached PR (including screenshots) for the implementation draft of this feature. |
That looks excellent, thank you for doing this. |
I would be helpful to be able to burn or revoke a secret immediately in case of error or mistake, to invalidate it right away.
Similar to the below.
If the secret is passphrase protected, the correct passphrase would need to be entered to revoke/burn the secret.
The text was updated successfully, but these errors were encountered: