Terminal use case for gpg-agent and gpg-agent for ssh-agent feature
Open, NormalPublic

Description

Situation is Debian systemd socket activation, and login to terminal (not using Desktop Graphical environment) and use gpg-agent as ssh-agent.

In the socket activation configuration, a user requires UPDATESTARTUPTTY to let gpg-agent knows about his TTY.
(This should be well explained in a document.)

  • If it doesn't have GPG_TTY, pinentry will hang (this should be detected?)
  • Once pinentry hangs, gpg-agent remains there, and next requests keep hanging

After login, a user needs to do:

gpg-connect-agent UPDATESTARTUPTTY /bye
gniibe created this task.Aug 21 2018, 5:48 AM
werner added a subscriber: werner.

gpg-agent has a pinentry caling timeout - doesn't that trigger?
In any case we agreed that Debian takes care of systemd support because that is not an upstream supported configuration.

gniibe updated the task description. (Show Details)Aug 22 2018, 9:56 AM
gniibe claimed this task.Aug 22 2018, 9:59 AM
gniibe triaged this task as Normal priority.

This entry was created based on the conversation at #gnupg channel.
I can't reproduce keep hanging.
I confirmed that pinentry vanished (perhaps, because of timeout).

gniibe updated the task description. (Show Details)Aug 22 2018, 10:00 AM
gniibe updated the task description. (Show Details)Aug 22 2018, 10:03 AM
gniibe updated the task description. (Show Details)