-
-
Notifications
You must be signed in to change notification settings - Fork 163
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
gpg: Sorry, no terminal at all requested - can't get input #18
Comments
I think you are using a key with passphrase, so GPG must get that from you. |
Also, in pass mode I suspect it hangs because it tries to read the passphrase from the terminal, which is not connected. And lastly, I have tested key with both passphrases and keys on smartcards with PINs to work on Linux (default gpg setup) and Windows (gpg4win) at least, so it is at least not generally broken... |
Unfortunately I can't test on OsX currently . . |
Most of these issues are fixed, all except for one. The freezing is caused by an upstream bug in pass when (in my case) using a GPG smart-card and not having it inserted. I have a pull request waiting to fix this https://github.com/zx2c4/password-store/pull/14 When the fix is merged and propagated to at-least the Linux distributions I use and Homebrew OSX, I'll close this issue. |
I still experience all of this issues. |
The second screenshot gives a hint. Could you help me debugging this by giving me some more information on your setup? Unfortunately the pass locking issue (third screenshot) is caused by pass itself, using my fork of pass solved that issue for me. https://github.com/annejan/password-store It looks to me like there is something "wrong" with the execution environment that causes GPG to not find your secret key. I will have a deeper look into this, since I now have a mac OS environment to test in again, any information on your setup you can give will help me fix this issue. I have just found out that on a test account I have created this happens when I start QtPass from the Applications thing which is apparently the way things work on a Mac. Starting QtPass from the Terminal ( open QtPass.app ) or from QtCreator and everything works normally, this makes debugging a bit awkward . . This is indeed a showstopper as "normal" Mac users would just drag and drop the application into the Applications thing. |
Apparently using /usr/local/MacGPG2/bin/gpg2 as the pass executable in the configuration menu works a lot better than the /usr/local/bin/gpg . . Or in the latest develop version https://github.com/IJHack/qtpass/tree/develop by removing the gpg executable from the configuration and restarting the application. Please try and test this build if you don't want to wait: https://annejan.com/media/qtpass.dmg |
Yes, the pass in the command line does work for me. When I execute this command 'open /Users/vladislavzaets/Downloads/qtpass-master-2/QtPass.app' it still doesn't work. I don't have such directory /usr/local/MacGPG2/ |
I am convinced it is a path issue in the QProcess, will have a deeper look tomorrow. I have uninstalled MacGPG2 and installed http://sourceforge.net/p/gpgosx/docu/Download/ For now I'm concluding that QtPass on Mac only works with the https://gpgtools.org/ version of GPG. |
Not working for me in both "native" and "pass" modes.
In "native git/gpg" I get this error – "gpg: Sorry, no terminal at all requested - can't get input". As I looked up in google I should remove "no-tty" string from gpg config file, but in my config there is no such string.

After installing gpg2 and pointing gpg exec to "/usr/local/bin/gpg2", I get this error:

In "pass" mode the window just freezes.

The text was updated successfully, but these errors were encountered: