-
Notifications
You must be signed in to change notification settings - Fork 10
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
Usage on a GUI-less server #90
Comments
For me it works in a non-X11 environment. I think what ultimately should be tried is something like:
which is pretty much what we use. My guess would be that this fails in the same way. If it doesn't that would be very interesting. In the past, I've had luck with:
in a slightly different scenario (when GPG was started on a different tty), so running that may be worth a shot (but judging from the logs you provided I am not sure that's the case here). Also, my notes suggest that:
helped me at some point with exactly this error message. That's more shots in the dark than anything else, though, or at least I don't see a clear connection in this case.
We more or less intentionally don't have that. pinentry should support all the scenarios we are interested in and should integrate nicely into the system, so I didn't see the need. |
Thank you for the check and thorough response! It looks clearer for me now. Closing, since it works on your side. |
Hi!
Is it possible to use
nitrocli
in a GUI-less /init 3
Linux environment? I tried to simulate it in an Ubuntu 19.04 Docker container, and got this error:Any ideas?
Pinentry
run separately works apparently. Getting status from the Storage device works as well.gpg-connect-agent
also seems to work.I tried to use
/usr/bin/pinentry-tty
(as here), but got other error:Perhaps, alternatively, is it possible to disable
gpg-connect-agent
usage, and makenitrocli
ask the PIN directly? E.g. via some kind of switch?Full install and execution log attached:
nitrocli.init3.log
Connected: support request.
The text was updated successfully, but these errors were encountered: