[Bug 1852696] Re: pinentry does not work for both desktop login and SSH login

Tue Nov 19 11:01:38 UTC 2024

Thank you for reporting this bug to Ubuntu.

Ubuntu 23.10 (mantic) reached end-of-life on July 11, 2024.
Ubuntu 23.04 (lunar) reached end-of-life on January 25, 2024.
Ubuntu 22.10 (kinetic) reached end-of-life on July 20, 2023.
Ubuntu 21.10 (impish) reached end-of-life on July 14, 2022.
Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.
Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 18.04 (bionic) reached end-of-standard-support on May 31, 2023.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.
Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.
Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009.
Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.
Ubuntu 6.10 (edgy) reached end-of-life on April 26, 2008.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it anymore. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.

** Changed in: pinentry (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pinentry in Ubuntu.
https://bugs.launchpad.net/bugs/1852696

Title:
  pinentry does not work for both desktop login and SSH login

Status in pinentry package in Ubuntu:
  Incomplete

Bug description:
  I'm working on a Ubuntu 18.04.3 LTS x86_64 machine (fully patched).
  The machine has a GNOME3 desktop. Sometimes I sit at the workstation,
  and other times I SSH into the workstation.

  When sitting at the workstation Git commit signing works. I use 'git
  commit -S ... -m ...', and things work as expected. I get a UI prompt
  for my GnuPG password and the work flows as usual.

  When I work remotely on the same workstation over SSH I have to forgo
  commit signing because:

     $ git commit -S log.h -m "Remove unneeded header"
     error: gpg failed to sign the data
     fatal: failed to write commit object

  I'm using a "standard" configuration for SSH, Git and GnuPG. I am not
  aware of any special configurations for this setup. However, the repo
  is located on my local LAN (and not GitHub, GitLab, etc):

     $ cat .git/config 
     [core]
         repositoryformatversion = 0
         filemode = true
         bare = false
         logallrefupdates = true
      [remote "origin"]
         url = ssh://git@callmaster:/var/callboot-src
         fetch = +refs/heads/*:refs/remotes/origin/*
     [branch "master"]
         remote = origin
         merge = refs/heads/master

  There is no specialized GnuPG conf file in $HOME/.gnupg:

     $ ls -A ~/.gnupg/
     3F537D88ADBC1677-private-key.asc  pubring.kbx
     private-keys-v1.d                 trustdb.gpg

  Here is pinentry on the machine:

     $ ls -Al /usr/bin/pinentry-*
     -rwxr-xr-x 1 root root 63992 Feb  5  2018 /usr/bin/pinentry-curses
     -rwxr-xr-x 1 root root 72184 Feb  5  2018 /usr/bin/pinentry-gnome3
     lrwxrwxrwx 1 root root    30 Sep  2 19:14 /usr/bin/pinentry-x11 -> /etc/alternatives/pinentry-x11

  And then:

     $ ls -Al /etc/alternatives/pinentry-*
     lrwxrwxrwx 1 root root 24 Sep  2 19:14 /etc/alternatives/pinentry-x11 -> /usr/bin/pinentry-gnome3
     lrwxrwxrwx 1 root root 40 Sep  2 19:14 /etc/alternatives/pinentry-x11.1.gz -> /usr/share/man/man1/pinentry-gnome3.1.gz

  My .bashrc includes:

     export GPG_TTY=$(tty)

  Search is finding a lot about Git signing failures, but not results
  for this particular situation. I have to turn the problem over to the
  maintainers since I can't figure it out.

  What users like me expect is, things just work regardless of how we
  are logged in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pinentry/+bug/1852696/+subscriptions