-
-
Notifications
You must be signed in to change notification settings - Fork 669
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
wording for "Safety checks" feature #1133
Comments
Another idea for the possible settings. It would be nice to have an "enable temporarily" option. This would enable unsafe prompts until the next reboot, i.e. it wouldn't be written to storage. The typical use-case for this would be when a user has BTC sent to a LTC address and just needs to do a one-off fix. So it decreases the number of steps that the support team needs to instruct the user to do. |
Let's agree on this. I like both comments how about we have three stages then: strict, prompt and temporary.
Wording suggestions: strict:
prompt:
temp:
The third might be too long and I don't like "uncommon" very much. Ideas? |
Unusual? Also not sure about "reboot", might sound like you have to reboot your computer:) Not sure if "unplugging your Trezor" fits on the screen. |
I would try to be more succinct: |
I like @andrewkozlik's suggestions, let's go that way! @mmilata feel free to do this one as well, I think @matejcik does not have any work done here yet. |
👍 For future reference there's some discusion regarding the temporary-prompt option in #1240 (comment). |
I think we can close this one? |
the wording was changed in #1240 it seems |
in #1126 we introduced "Unsafe prompts" setting. This is confusing because of double-negatives: "enabling unsafe prompts" is the weaker setting and "disabling" is stronger.
We came up with an idea to rename this to "safety checks", with configurable levels, the default being "strict".
For trezorctl, we should change:
trezorctl set unsafe-prompts off
totrezorctl set safety-checks strict
trezorctl set unsafe-prompts on
totrezorctl set safety-checks prompt
For protobuf the following field should be changed:
to:
This way binary compatibility holds, because
bool
is basically an enum withFALSE = 0, TRUE = 1
Open question: how to reword the on-device screens?
current, for lowering strictness:
for raising:
The text was updated successfully, but these errors were encountered: