[pkg-gnupg-maint] Behavioral change for pinentry-qt 1.2.0-1
Daniel Kahn Gillmor
dkg at fifthhorseman.net
Tue May 24 05:56:46 BST 2022
On Thu 2022-05-19 10:05:10 +0200, Gard Spreemann wrote:
> Sorry, that was apparently wrong too. It's even more mysterious!
>
> gpg --sign file.txt
>
> triggers the *incorrect* behavior in 1.2.0-1 (correct in 1.1.0-4), but
>
> debsign foo.dsc
>
> triggers the *correct* behavior in both versions! I really have no idea
> what's going on here.
Reading /usr/bin/debsign it looks like it invokes gpg in a more
complicated way than you're trying thus far:
$signcommand --local-user "$signas" --clearsign \
--no-show-policy-url \
--armor --textmode --output "$ASCII_SIGNED_FILE" \
"$UNSIGNED_FILE" || \
it's also wrapped in some stty stuff that i don't understand, but
digging through the devscripts git history i see that it's probably from
#321684 in 2005 ("fix noecho behaviour for interrupted gpg call") and
#345636 in 2006 ("don't abort or complain if stty fails, as might happen
if run w/o a controlling terminal.")
Have you tried emulating the more complex invocation of gpg to see
whether it affects pinentry differently under sway?
--dkg
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnupg-maint/attachments/20220524/80651e04/attachment.sig>
More information about the pkg-gnupg-maint
mailing list