Actions
Bug #26653
open
Improve the "reset status to be able to accept a different key" node feature
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
This button is very confusing in the node UI.
In order to make it more comprehensible for the users we should:
In order to make it more comprehensible for the users we should:
- hide the button as this is a very niche and "dangerous" operation
- display a popup to explain exactly what it does and what the user should do afterward, and ask for confirmation
- do not display the button for the root server
- display a "tag" or something in the node list for "reseted nodes"
Some documentation would also be nice. What does it do? Do I need to re-accept the node if its key has changed? If not, how is the trust handled?
Updated by Félix DALLIDET 15 days ago
- Category changed from Web - UI & UX to Security
Actions