First GPG states that my passphrase is too simple then it won't accept it
GPG Kekchain
Hello.I created a public/private key today. When choosing a passphrase it said that it was too simple. I changed the passphrase to a sentence that adhered to alphanumeric. It still said that the passphrase was too simple. This time I kept the passphrase.
Now i am attempting to open a key and the gpg program will not accept my passphrase. I tried restarting the app. I restarted the computer. Still no luck. Basically, a website that I am trying to use sent me an encrypted document and in order to move forward I need to decrypt it. Because gpg will not accept my passphrase I m unable to do tat and move forward wit my accunt.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Steve on 07 Jun, 2017 09:22 PM
Hi Lee,
welcome to the GPGTools support platform. Sorry you are having problems using GPG Suite.
Could you try a few combinations of what you first entered and then the password with the full sentence you used. I would use several tries to see if you are able to recover the password. You could just encrypt some random text in TextEdit using GPGServices and then try to decrypt which will trigger pinentry asking for your password.
The following two Knowledge Base articles explain how GPGServices is used:
In case you are unable to recover, I would suggest to revoke the unusable key. This KB-article explains how to revoke a key.
Then create a new key.
Note, that you can use any password, the warnings can (but should not) be ignored.
All the best,
steve
Support Staff 2 Posted by Steve on 18 Aug, 2017 10:09 AM
Closing, since no further user feedback was received. Should your problem persist, feel free to re-open this discussion any time.
All the best, steve
Steve closed this discussion on 18 Aug, 2017 10:09 AM.