Skip to content
This repository has been archived by the owner on Jun 5, 2019. It is now read-only.

Invalid Pin when using encfs_aes_getpass.py #15

Closed
ddworken opened this issue Sep 6, 2014 · 4 comments
Closed

Invalid Pin when using encfs_aes_getpass.py #15

ddworken opened this issue Sep 6, 2014 · 4 comments

Comments

@ddworken
Copy link
Contributor

ddworken commented Sep 6, 2014

When I try to run encfs_aes_getpass.py, I get past it asking for a label for the new drive, and prompting the trezor device for entropy. It then asks me to "Please enter old PIN: " while the Trezor screen says "Please enter current PIN:". It is here that I am confused about how to enter my pin. If my password is 1234 and the trezor is displaying:

2 8 3
5 4 6
7 9 1

Which of these options would I enter?

  1. 9135
  2. 2835

I have tried both of the above methods, and both give me an Invalid PIN exception.

@prusnak
Copy link
Member

prusnak commented Sep 6, 2014

Mapping is the same as layout on numeric keyboard, that is :

7 8 9 
4 5 6
1 2 3

For your case the correct option is: 3795

@ddworken ddworken closed this as completed Sep 6, 2014
@tphyahoo
Copy link

From a usability perspective, this is really confusing.

Would you consider outputting the numeric keyboard layout to help the user, when in text mode?

So to be pedantically concrete, when you run helloworld.py the message would be something like

"Passphrase required:
(numeric keypad default layout is:
789
456
123)"

I think this would help usability a lot.

(so maybe reopen?)

@prusnak
Copy link
Member

prusnak commented Aug 18, 2015

Feel free to suggest a change via a pull request.

@prusnak
Copy link
Member

prusnak commented Aug 21, 2015

Implemented in b2bc509

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants