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

LOCK setting for UPDATE AUTH transactions #114

Open
tbone-bts opened this issue Apr 22, 2019 · 1 comment
Open

LOCK setting for UPDATE AUTH transactions #114

tbone-bts opened this issue Apr 22, 2019 · 1 comment

Comments

@tbone-bts
Copy link

I think it would be a good security feature to have a LOCK setting (locked by default) which would need to be explicitly unlocked in order to have the ability to sign any UPDATE AUTH transactions.

While locked, if the user attempts to initiate an UPDATE AUTH action, they would get a message saying that action is locked and must be explicitly unlocked in settings before attempting again.

When unlocked, there should be a double confirmation along with highly visible warning something along the lines of "This is a dangerous action which could result in losing control of your account, etc etc".

After unlocking, it should automatically lock again after some period of time.

@sschiessl-bcp
Copy link
Collaborator

You mean like a sudo for critical operations

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

2 participants