-
-
Notifications
You must be signed in to change notification settings - Fork 654
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
IDEA: Lock Trezor to work only with a particular host #32
Comments
I dislike using of MAC addresses, which is basically a public information. If ever, I would consider providing some "key file" to Bridge, stored somewhere in the user profile. |
Another option is to use the keyfile in the bridge to encrypt the whole communication (v2 protocol) and ignore the communication with the wrong communication key. |
prusnak
added
core
Trezor Core firmware. Runs on Trezor Model T and T2B1.
feature
labels
Apr 16, 2019
prusnak
added
core
Trezor Core firmware. Runs on Trezor Model T and T2B1.
and removed
core
Trezor Core firmware. Runs on Trezor Model T and T2B1.
labels
Apr 17, 2019
tsusanka
added
feature
Product related issue visible for end user
and removed
W?
labels
Feb 19, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is possible to lock the device to communicate only with a particular host.
The implemenetation would look like this:
The text was updated successfully, but these errors were encountered: