Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1251415 > unrolled thread

Bug#1108495: pinentry-tty: python3's gpg --decrypt gets no PIN dialog, no errors reported

Back to article view | Back to linux.debian.bugs.dist

Contents

  Bug#1108495: pinentry-tty: python3's gpg --decrypt gets no PIN dialog, no errors reported Boca Cavana <chaletrhodes@me.com> - 2025-06-29 19:50 +0200
    Bug#1108495: pinentry problem with Debian 12.11 Jeffrey Rhodes <chaletrhodes@me.com> - 2025-06-30 04:40 +0200
      Bug#1108495: pinentry problem with Debian 12.11 Andreas Metzler <ametzler@bebt.de> - 2025-07-07 16:30 +0200
    Bug#1108495: pinentry-tty: python3's gpg --decrypt gets no PIN dialog, no errors reported Andreas Metzler <ametzler@bebt.de> - 2025-07-07 16:30 +0200

#1251415 — Bug#1108495: pinentry-tty: python3's gpg --decrypt gets no PIN dialog, no errors reported

Package: pinentry-tty
Severity: important
X-Debbugs-Cc: chaletrhodes@me.com

Dear Maintainer,

   * What led up to the situation?
Python3 script's gpg code stopped prompting for Passphrase when 12.11 was used. 
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
Python3 code needs to discern when decryption is attempted for a message missing a key needed for decyption but that test failed one day.
   * What was the outcome of this action?
My code will overlook an infrequent encryption problem for the decryptor.
   * What outcome did you expect instead?
I expect my code to run like it did in Debian 10, 11 and 12 up to 12.11

-- System Information:
Debian Release: 12.11
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 6.1.0-37-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages pinentry-tty depends on:
ii  libassuan0     2.5.5-5
ii  libc6          2.36-9+deb12u10
ii  libgpg-error0  1.46-1

pinentry-tty recommends no packages.

Versions of packages pinentry-tty suggests:
pn  pinentry-doc  <none>

[toc] | [next] | [standalone]

#1251438 — Bug#1108495: pinentry problem with Debian 12.11

The pinentry bug is coincident with updating to or after a new install to 12.11. Prior to that a python3 script running in a Terminal could call os.system(‘gpg —decrypt file’) and a PIN pop-up window would request a Passphrase. Also, no decryption errors are reported, not even when the key needed for decryption is locally missing. 

[toc] | [prev] | [next] | [standalone]

#1252070 — Bug#1108495: pinentry problem with Debian 12.11

On 2025-06-30 Jeffrey Rhodes <chaletrhodes@me.com> wrote:
> The pinentry bug is coincident with updating to or after a new install
> to 12.11. Prior to that a python3 script running in a Terminal could
> call os.system(‘gpg —decrypt file’) and a PIN pop-up window would
> request a Passphrase. Also, no decryption errors are reported, not
> even when the key needed for decryption is locally missing. 


Works for me with both  pinentry-gtk2 and  pinentry-tty.

ametzler@argenau:~$ rm -rf /tmp/gpghome ; install -d -m0700 /tmp/gpghome ; gpg  --homedir /tmp/gpghome --batch --pinentry-mode loopback --passphrase 1234 --quick-generate-key blah@example.com
gpg: keybox '/tmp/gpghome/pubring.kbx' created
gpg: /tmp/gpghome/trustdb.gpg: trustdb created
gpg: directory '/tmp/gpghome/openpgp-revocs.d' created
gpg: revocation certificate stored as '/tmp/gpghome/openpgp-revocs.d/9C7D203179D87C924581E1968507ED6E2CB369C7.rev'
ametzler@argenau:~$ echo content > /tmp/input
ametzler@argenau:~$ gpg --homedir /tmp/gpghome --encrypt --recipient blah@example.com /tmp/input
gpg: checking the trustdb
gpg: marginals needed: 3  completes needed: 1  trust model: pgp
gpg: depth: 0  valid:   1  signed:   0  trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: next trustdb check due at 2028-07-06
ametzler@argenau:~$ /tmp/run-py.py
gpg: encrypted with cv25519 key, ID 02D8ABA3508D585F, created 2025-07-07
      "blah@example.com"
Please enter the passphrase to unlock the OpenPGP secret key:
"blah@example.com"
255-bit ECDH key, ID 02D8ABA3508D585F,
created 2025-07-07 (main key ID 8507ED6E2CB369C7).

Passphrase:
content
ametzler@argenau:~$ cat /tmp/run-py.py
#!/usr/bin/python3

import os

# ametzler@argenau:~$ rm -rf /tmp/gpghome ; install -d -m0700 /tmp/gpghome ; gpg --homedir /tmp/gpghome --batch --pinentry-mode loopback --passphrase 1234 --quick-generate-key blah@example.com
#  echo content > /tmp/input
# gpg --homedir /tmp/gpghome --encrypt --recipient blah@example.com /tmp/input

os.system("gpg --homedir /tmp/gpghome --decrypt  /tmp/input.gpg")

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

[toc] | [prev] | [next] | [standalone]

#1252071

On 2025-06-29 Boca Cavana <chaletrhodes@me.com> wrote:
> Package: pinentry-tty
> Severity: important
> X-Debbugs-Cc: chaletrhodes@me.com

> Dear Maintainer,

>    * What led up to the situation?
> Python3 script's gpg code stopped prompting for Passphrase when 12.11 was used. 
[...]

Hello,

could you please elaborate on that? What is "Python3 script's gpg code"
that's on version 12.11?

cu Andreas
-- 
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.bugs.dist

csiph-web