Script execution failed: cancelled by user & decryption failed: No secret key #367
Labels
No labels
bug
Done
duplicate
enhancement
help wanted
incompatibility
invalid
need info
question
security
unconfirmed
upstream
user issue
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
PassFF/passff#367
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
General information. Describe your environment
Status line output:
[hh:mm:ss] show -> (0)show -> (2) gpg: cancelled by user gpg: decryption failed: No secret keyThose appear to be sane. The
passcommands work fine from a shell.[PassFF.content] Message Page.notify received in contentActual behaviour
Every time I try to fill some password, I get a window saying:
Expected behaviour
I expected a GPG prompt to enter my password.
Steps to reproduce the behaviour
I suspect an error between keyboard and floor but am unsure where to start to look at what I am doing wrong.
Hey kierun,
pass, does it prompt a pinentry in the terminal?If the answers to those questions are no then yes, could it be a pinentry issue?
See https://github.com/passff/passff#nothing-happens-when-i-click-on-a-password-and-select-an-action
No I am not. Just a result that something failed.
Yes, I am. Although it is the console version and not a GUI.
Thanks for the answers.
PassFF requires a GUI pinentry since the host app (
passff.py) runspassnon-interactively.You can either install a GUI pinentry (
pinentry-gtkorpinentry-qt), or still use the console version + gpg's cache.Tell me if it fixes your issue :)
I will add in the doc that the GUI pinentry is necessary.
Do you know a good website about CentOS packages? A CentOS/RHEL equivalent to https://www.debian.org/distrib/packages ?
My best catch is https://pkgs.org/
Oh I didn't know the
dnfpkg manager for CentOS :octocat:There is no
pinentry-gtkin the official repos butpinentry-qtis there. I am working from home for the next couple of days so cannot check it. I will update Thursday.'fraid not. There are a few around but I tend to use
dnf search Xto get whatever containing X to show.Yes, you can use it although it's experimental. I like living on the edge. ☺
I installed all the pinentries I could find. I have not restart my machine but that should not matter. I am still getting the same problem.
I wonder if this is because the first thing that the code looks for is
pinentrythus the console one…If I run
pass …in a console then the auto-fill works fine. I suspect pinentry caches the authentication for a little while so I can get around the issue but it's annoying. It works fine on my Fedora machine.You probably have to configure gpg2 to use a GUI pinentry. Or maybe you have to reload the gpg-agent. Restart if you can.
See https://wiki.archlinux.org/index.php/GnuPG#pinentry
Yes, gpg-agent do caches your passphrase for a while, the duration of retention is configurable.
This is indeed what gpg-agent looks for first.
If
/usr/bin/pinentryis a symlink on your system, you could also modify it, or configureupdate-alternativesto do it for you ;)And this was the solution! ☺
Many thanks indeed for taking the time and effort to help me debug this. It is much appreciated.
Nice, I'm glad the pinentry was the culprit ;)
I'm updating the README to explicitly document this dependency.
Thanks for using PassFF and supporting our work 👍
You are most welcome. Thank you again for your time and support