Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#46345 - [pinentry] pinentry-gtk2 crashes

Attached to Project: Arch Linux
Opened by Paul Davis (dangersalad) - Friday, 18 September 2015, 23:27 GMT
Last edited by Gaetan Bisson (vesath) - Saturday, 05 December 2015, 04:23 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Tobias Powalowski (tpowa)
Gaetan Bisson (vesath)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

pinentry-gtk2 started crashing for me on one of my systems starting in version `0.9.5-1`. I have been using the `0.9.1-1` release until recently when the ncurses 6 update forced me to use the newer version. `0.9.5-2` is working fine on another machine.

If the input reaches 16 characters, the pinentry window will exit immediatly with a message from systemd saying

Process <PID> (pinentry) of user <UID> dumped core.

and this from the gpg agent log

2015-09-18 19:23:19 gpg-agent[31413] DBG: error calling pinentry: End of file <GPG Agent>
2015-09-18 19:23:19 gpg-agent[31413] failed to unprotect the secret key: End of file
2015-09-18 19:23:19 gpg-agent[31413] failed to read the secret key
2015-09-18 19:23:19 gpg-agent[31413] ssh sign request failed: End of file <Pinentry>
2015-09-18 19:23:19 gpg-agent[31413] ssh request handler for sign_request (13) ready
2015-09-18 19:23:19 gpg-agent[31413] DBG: chan_7 -> RESTART
2015-09-18 19:23:19 gpg-agent[31413] DBG: chan_7 <- OK
2015-09-18 19:23:19 gpg-agent[31413] ssh handler 0x7fd09dc8d700 for fd 6 terminated

The same messages occur if I exit the dialog before the 16th character is input, as well as when enterin a PIN


Additional info:
* pinentry 0.9.5-2
* gnupg 2.1.8-2

Steps to reproduce:

Simply using pinentry-gtk2 causes the crash. Obviously there is some adverse reaction to something on my system, as a fresher install I have works fine. More help tracking down the actual issue is appreciated.
This task depends upon

Closed by  Gaetan Bisson (vesath)
Saturday, 05 December 2015, 04:23 GMT
Reason for closing:  Upstream
Comment by Gaetan Bisson (vesath) - Saturday, 19 September 2015, 01:58 GMT
Strange. I cannot reproduce this. Are you sure your system is up-to-date? Simply run `pacman -Syu`.

Otherwise, could you reproduce this when running pinentry manually? Just run `pinentry-gtk-2` and then, from within the prompt, `getpin`.

If that successfully reproduces the problem, you can run this with gdb and obtain a backtrace of the pinentry process.
Comment by Paul Davis (dangersalad) - Sunday, 20 September 2015, 19:28 GMT
I am sure everything is up to date, this has been an issue ever since 0.9.5 hit. Unfortunately, there is no crash when I run pinentry 0.9.5 directly, only when gpg-agent invokes it it seems.

gpg-agent is being run with

gpg-agent --daemon --enable-ssh-support --log-file %h/.gnupg/agent.log --debug-level 9 --debug-pinentry --debug 1024 --pinentry-program /usr/bin/pinentry-gtk-2

from a user systemd unit


here is some more info now that I have --debug-pinentry enabled



2015-09-20 15:26:13 gpg-agent[24224] starting a new PIN Entry
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 <- OK Pleased to meet you, process 24224
2015-09-20 15:26:13 gpg-agent[24224] DBG: connection to PIN entry established
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 -> OPTION grab
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 <- OK
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 -> OPTION allow-external-password-cache
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 <- OK
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 -> OPTION default-ok=_OK
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 <- OK
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 -> OPTION default-cancel=_Cancel
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 <- OK
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 -> OPTION default-yes=_Yes
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 <- ERR 83886254 Unknown option <Pinentry>
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 -> OPTION default-no=_No
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 <- ERR 83886254 Unknown option <Pinentry>
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 -> OPTION default-prompt=PIN:
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 <- OK
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 -> OPTION default-pwmngr=_Save in password manager
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 <- OK
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 -> OPTION default-cf-visi=Do you really want to make your passphrase visible on the screen?
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 <- ERR 83886254 Unknown option <Pinentry>
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 -> OPTION default-tt-visi=Make passphrase visible
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 <- ERR 83886254 Unknown option <Pinentry>
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 -> OPTION default-tt-hide=Hide passphrase
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 <- ERR 83886254 Unknown option <Pinentry>
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 -> OPTION touch-file=/home/paul/.gnupg/S.gpg-agent
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 <- OK
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 -> GETINFO pid
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 <- D 25374
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 <- OK
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 -> SETKEYINFO s/9EC46540E98AB25A6584D5CB7EFEFE1FF5BC2048
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 <- OK
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 -> SETDESC Please enter the passphrase for the ssh key%0A 50:cd:47:a0:de:8a:5f:34:87:84:52:ee:32:03:d1:58%0A (/home/paul/.ssh/id_rsa)
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 <- OK
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 -> SETPROMPT Passphrase:
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 <- OK
2015-09-20 15:26:13 gpg-agent[24224] DBG: chan_8 -> [[Confidential data not shown]]
2015-09-20 15:26:45 gpg-agent[24224] DBG: chan_8 <- [eof]
2015-09-20 15:26:45 gpg-agent[24224] DBG: error calling pinentry: End of file <GPG Agent>
2015-09-20 15:26:45 gpg-agent[24224] DBG: chan_8 -> BYE
2015-09-20 15:26:45 gpg-agent[24224] failed to unprotect the secret key: End of file
2015-09-20 15:26:45 gpg-agent[24224] failed to read the secret key
2015-09-20 15:26:45 gpg-agent[24224] ssh sign request failed: End of file <Pinentry>
2015-09-20 15:26:45 gpg-agent[24224] ssh request handler for sign_request (13) ready
2015-09-20 15:26:45 gpg-agent[24224] DBG: chan_7 -> RESTART
2015-09-20 15:26:45 gpg-agent[24224] DBG: chan_7 <- OK
2015-09-20 15:26:45 gpg-agent[24224] ssh handler 0x7fe3a021c700 for fd 6 terminated


Comment by Gaetan Bisson (vesath) - Sunday, 20 September 2015, 20:15 GMT
That's strange. Could you report this upstream to https://bugs.g10code.com/ ?

Your issue could be related to https://bugs.g10code.com/gnupg/issue2076 but I'd still recommend opening a new bug report with all the info above, just in case.
Comment by Paul Davis (dangersalad) - Wednesday, 23 September 2015, 14:16 GMT
REMOVED

Sorry, somehow I resent the POST requst for that comment from before
Comment by Paul Davis (dangersalad) - Wednesday, 23 September 2015, 14:29 GMT
According to this, it appears to be "fixed" in 0.9.6.

https://bugs.gentoo.org/show_bug.cgi?id=560158#c18

When that hits, we can see if it is still present.
Comment by Gaetan Bisson (vesath) - Saturday, 05 December 2015, 04:21 GMT
Could you please check whether pinentry-0.9.6-2 from [testing] still has your issue? If it does, please report it upstream.

Loading...