Ägypten: Problem with pinentry-qt

[Ingo Klöcker]

--Boundary-02=_0i5+9wDiSCe/fxD
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Description: signed data
Content-Disposition: inline

Hi,

after updating to the latest versions of the relevant libraries and=20
programs (from cvs as described on the Aegypten page) pinentry-qt=20
doesn't work anymore.

Here's an example session with pinentry-gtk:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
ingo@erwin:~> eval "$(gpg-agent --daemon --default-cache-ttl 3600)"
ingo@erwin:~> echo Test 1...2...3... | gpg --sign --armor

You need a passphrase to unlock the secret key for
user: "Ingo Kl=F6cker <ingo.kloecker@epost.de>"
1024-bit DSA key, ID 30E0B9D8, created 2000-10-16

gpg-agent[0x80629ec] -> OK Your orders please
gpg-agent[0x80629ec] <- OPTION display=3D:0
gpg-agent[0x80629ec] -> OK
gpg-agent[0x80629ec] <- OPTION ttyname=3D/dev/pts/1
gpg-agent[0x80629ec] -> OK
gpg-agent[0x80629ec] <- OPTION ttytype=3Dxterm
gpg-agent[0x80629ec] -> OK
gpg-agent[0x80629ec] <- OPTION lc-ctype=3Den_US
gpg-agent[0x80629ec] -> OK
gpg-agent[0x80629ec] <- OPTION lc-messages=3Den_US
gpg-agent[0x80629ec] -> OK
gpg-agent[0x80629ec] <- [ 47 45 54 5f 50 41 53 53 50 48 52 41 53 45 20=20
37 31 32 41 30 39 31 30 33 32 31 41 43 37 36 32 44 34 38 30 35 34 30 38=20
31 41 37 34 37 45 34 35 33 30 45 30 42 39 44 38 20 58 20 58 20 59 6f 75=20
2b 6e 65 65 64 2b 61 2b 70 61 73 73 70 68 72 61 73 65 2b 74 6f 2b 75 6e=20
6c 6f 63 6b 2b 74 68 65 2b 73 65 63 72 65 74 2b 6b 65 79 2b 66 6f 72 2b=20
75 73 65 72 3a 25 30 41 22 49 6e 67 6f 2b 4b 6c c3 b6 63 6b 65 72 2b 3c=20
69 6e 67 6f 2e 6b 6c 6f 65 63 6b 65 72 40 65 70 6f 73 74 2e 64 65 3e 22=20
25 30 41 31 30 32 34 2d 62 69 74 2b 44 53 41 2b 6b 65 79 2c 2b 49 44 2b=20
33 30 45 30 42 39 44 38 2c 2b 63 72 65 61 74 65 64 2b 32 30 30 30 2d 31=20
30 2d 31 36 25 30 41 ]
gpg-agent[18401]: DBG: connection to PIN entry established
  (the pinentry window asks me for the passphrase)
gpg-agent[0x80629ec] -> [Confidential data not shown]
gpg-agent[0x80629ec] <- [EOF]
=2D----BEGIN PGP MESSAGE-----
Version: GnuPG v1.2.1 (GNU/Linux)

owGbwMvMwCQoVVLnavBg5w3G0xJJDLa/JzSFpBaXKBjq6ekZAbExEHN12DOzgqQm
wNQKMlmxMSxYqJ68mGd9TPdem2a9/Ai/Vq2plusZFjzgDZ8a3CcSsPLlanH3hzum
VzuwNQEA
=3DXhPB
=2D----END PGP MESSAGE-----
ingo@erwin:~>
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Now the same with pinentry-qt:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
  (first let's kill the running gpg-agent)
ingo@erwin:~> killall gpg-agent
  (make gpg-agent use pinentry-qt instead of ~-gtk)
ingo@erwin:~> vi .gnupg/gpg-agent.conf
ingo@erwin:~> eval "$(gpg-agent --daemon --default-cache-ttl 3600)"
ingo@erwin:~> echo Test 1...2...3... | gpg --sign --armor

You need a passphrase to unlock the secret key for
user: "Ingo Kl=F6cker <ingo.kloecker@epost.de>"
1024-bit DSA key, ID 30E0B9D8, created 2000-10-16

gpg-agent[0x80629ec] -> OK Your orders please
gpg-agent[0x80629ec] <- OPTION display=3D:0
gpg-agent[0x80629ec] -> OK
gpg-agent[0x80629ec] <- OPTION ttyname=3D/dev/pts/1
gpg-agent[0x80629ec] -> OK
gpg-agent[0x80629ec] <- OPTION ttytype=3Dxterm
gpg-agent[0x80629ec] -> OK
gpg-agent[0x80629ec] <- OPTION lc-ctype=3Den_US
gpg-agent[0x80629ec] -> OK
gpg-agent[0x80629ec] <- OPTION lc-messages=3Den_US
gpg-agent[0x80629ec] -> OK
gpg-agent[0x80629ec] <- [ 47 45 54 5f 50 41 53 53 50 48 52 41 53 45 20=20
37 31 32 41 30 39 31 30 33 32 31 41 43 37 36 32 44 34 38 30 35 34 30 38=20
31 41 37 34 37 45 34 35 33 30 45 30 42 39 44 38 20 58 20 58 20 59 6f 75=20
2b 6e 65 65 64 2b 61 2b 70 61 73 73 70 68 72 61 73 65 2b 74 6f 2b 75 6e=20
6c 6f 63 6b 2b 74 68 65 2b 73 65 63 72 65 74 2b 6b 65 79 2b 66 6f 72 2b=20
75 73 65 72 3a 25 30 41 22 49 6e 67 6f 2b 4b 6c c3 b6 63 6b 65 72 2b 3c=20
69 6e 67 6f 2e 6b 6c 6f 65 63 6b 65 72 40 65 70 6f 73 74 2e 64 65 3e 22=20
25 30 41 31 30 32 34 2d 62 69 74 2b 44 53 41 2b 6b 65 79 2c 2b 49 44 2b=20
33 30 45 30 42 39 44 38 2c 2b 63 72 65 61 74 65 64 2b 32 30 30 30 2d 31=20
30 2d 31 36 25 30 41 ]
gpg-agent[18407]: can't connect server: ec=3D-1
gpg-agent[18407]: can't connect to the PIN entry module: ec=3D-1
gpg-agent[18407]: command get_passphrase failed: no pin entry
gpg-agent[0x80629ec] -> ERR 101 server fault
gpg: problem with the agent - disabling agent use
Enter passphrase: gpg-agent[0x80629ec] <- [EOF]
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

pinentry-qt can be started manually. But I get
ingo@erwin:~> pinentry-qt
Warning: using insecure memory!
OK Your orders please

I don't get this warning when I start pinentry-gtk manually. Could this=20
be the problem?

BTW, pinentry-gtk still doesn't show the DESC when it asks for my=20
passphrase. So the problem with non-ASCII characters in DESC is still=20
not fixed (cf. my message from Oct 3, 2002).

Regards,
Ingo


--Boundary-02=_0i5+9wDiSCe/fxD
Content-Type: application/pgp-signature
Content-Description: signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQA9+5i0GnR+RTDgudgRAqYNAJ9LoEdSfuYfsMz4c3W8ctTg+adR7wCeNj+P
Ymuimql7ix1SeIpnhIYW0fA=
=QnuU
-----END PGP SIGNATURE-----

--Boundary-02=_0i5+9wDiSCe/fxD--