-
Notifications
You must be signed in to change notification settings - Fork 150
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
[Question] Should I not enter my pin via my pinentry-progam rather than my trezor? #325
Comments
Thanks for reporting this issue! Since Trezor model T supports on-device PIN entry, you shouldn't get notified to entry the PIN on your host machine. |
Sorry for the late response.
That's understood. However, I get on-device prompting more than once but this due my (mis-?) use of Emacs for which I'm still searching for a solution.
I presume Thanks for your time. |
In Trezor suite, you also have an option of entering password either on the device or on the machine... |
Do you? I can't seem to find such an option. |
You see this when you want to create a new wallet? I have the option to create a hidden wallet and if I do I presume I'll be presented with this GUI? |
This is a default screen when connecting a Trezor if you have a passphrase enabled. |
So I may be a unique case amongst your users. I'm using my trezor (model T) along with
pass
to manage my passwords. I also use Emacs to interact with my password-store. There is an Emacs major mode and other packages that facilitate this. As thetrezor-agent
documentation suggests I configurerun-agent.sh
to usepinentry-emacs
as my pinentry-program as follows:which brings up the question whether a
gpg-agent.conf
wherepinentry-program
would normally be defined applies totrezor-gpg-agent
?This resolves this NicolasPetton/pass#41 issue I was experiencing.
However, I still enter my PIN on the trezor itself. Is that expected if using a
pinentry-program
?That same issue describes the number of times I'm prompted by my trezor to decrypt the specific GPG password files. Is it normal to be prompted more than once when accessing a GPG file. Thanks for your time.
The text was updated successfully, but these errors were encountered: