Re: Why exactly does pinentry fails with gpg-agent and ssh support?

On 2018-01-22 18:06, André Colomb wrote: >> the systemd user service takes care of automatically launching the >> gpg-agent when the user connects to it via the ssh-agent protocol, so >> this isn't required when using systemd. > > I can't see how it does that in my packaged Ubuntu version

Re: Why exactly does pinentry fails with gpg-agent and ssh support?

I'm glad to hear your comments guys. I've posted a bug report on ssh' bug tracker: https://bugzilla.mindrot.org/show_bug.cgi?id=2824 On Mon, Jan 22, 2018 at 08:43:41AM +0100, Werner Koch wrote: > On Sun, 21 Jan 2018 17:41, doron.be...@gmail.com said: > > > As far as I understand, because I use

Re: Why exactly does pinentry fails with gpg-agent and ssh support?

Hello Daniel, I'm on Ubuntu 17.10 with GnuPG 2.1.15, by the way. Daniel Kahn Gillmor wrote on 2018-01-22 12:53 (UTC+0100) > It may also depend on how the session itself is started. Maybe one of > you is starting the user session in non-graphical mode (either a vt >

Re: Why exactly does pinentry fails with gpg-agent and ssh support?

On Mon 2018-01-22 11:52:21 +0100, Peter Lebbing wrote: > It works for me out-of-the-box on Debian stretch/stable, supervised by > systemd... if I SSH before I do any GnuPG stuff, it correctly prompts me > in the (graphical) session that started the agent. So something must be > different in your

Re: Why exactly does pinentry fails with gpg-agent and ssh support?

On Mon 2018-01-22 08:43:41 +0100, Werner Koch wrote: > Another problem with ssh is that ssh can't start gpg-agent on the the > fly. Thus you need to make sure that gpg-agent has already been started > when you use ssh. A way to ensure this is to run > > gpg -K the systemd user service takes

Re: Why exactly does pinentry fails with gpg-agent and ssh support?

On 22/01/18 09:36, André Colomb wrote: > Strange thing is, I could use the GPG part of gpg-agent already before > issuing that command. Why does that behave differently? Because GnuPG *does* pass TTY and display to the agent. > Can something be done to the systemd user unit file so the process

Re: Why exactly does pinentry fails with gpg-agent and ssh support?

On 2018-01-22 08:43, Werner Koch wrote: >> As far as I understand, because I use `systemd`'s user service, whenever >> I want to unlock an authentication key I need to run the command >> `gpg-connect-agent updatestartuptty /bye`. > > Although I have no experience with the peculiarities of the

Re: Why exactly does pinentry fails with gpg-agent and ssh support?

On Sun, 21 Jan 2018 17:41, doron.be...@gmail.com said: > As far as I understand, because I use `systemd`'s user service, whenever > I want to unlock an authentication key I need to run the command > `gpg-connect-agent updatestartuptty /bye`. Although I have no experience with the peculiarities

Why exactly does pinentry fails with gpg-agent and ssh support?

Hello everyone, I've recently encountered the problem explained in item #3 here: https://www.gnupg.org/documentation/manuals/gnupg/Common-Problems.html and I would like to discuss it. I use the `systemd` user service provided with Arch Linux and it's `ExecStart` is: /usr/bin/gpg-agent