Addressing the bug described in #27. Turns out that gpg expects the password given to it to be uri encoded. Which pinentry-rofi did not but do now.
This will however break users that used special characters in their password generated by pinentry-rofi-2.2.0 or older. I added a note in the readme about it and a recommendation on how to migrate.
Addressing the bug described in #27. Turns out that gpg expects the password given to it to be uri encoded. Which pinentry-rofi did not but do now.
This will however break users that used special characters in their password generated by
pinentry-rofi-2.2.0
or older. I added a note in the readme about it and a recommendation on how to migrate.