skeeto (Chris Wellons)
User

Projects

User does not belong to any projects.

Today

  • Clear sailing ahead.

Tomorrow

  • Clear sailing ahead.

Tuesday

  • Clear sailing ahead.

User Details

User Since
Mar 27 2017, 4:48 PM (128 w, 5 d)
Availability
Available

Recent Activity

Wed, Aug 21

skeeto added a comment to T4677: Failure using pinentry-tty or pinentry-curses when GnuPG's standard input is a file.

@dkg, I changed the title and adjusted the description to more accurately describe the situation.

Wed, Aug 21, 2:24 AM · gnupg (gpg22), Info Needed, Bug Report
skeeto renamed T4677: Failure using pinentry-tty or pinentry-curses when GnuPG's standard input is a file from GnuPG unable to use imported protected subkeys to Failure using pinentry-tty or pinentry-curses when GnuPG's standard input is a file.
Wed, Aug 21, 2:22 AM · gnupg (gpg22), Info Needed, Bug Report

Aug 13 2019

skeeto added a comment to T4677: Failure using pinentry-tty or pinentry-curses when GnuPG's standard input is a file.

Those changes make the script work for me, specifically passing the input as an argument and not through standard input. Digging more, it looks like the underlying issue is related to using pinentry-tty (my case) or pinentry-curses when passing the OpenPGP input via standard input. This causes pinentry to give up before prompting. For pinentry-tty it fails with "ERR 83886340 Invalid IPC response" and pinentty-curses fails with "ERR 83918950 Inappropriate ioctl for device".

Aug 13 2019, 5:18 AM · gnupg (gpg22), Info Needed, Bug Report

Aug 12 2019

skeeto created T4677: Failure using pinentry-tty or pinentry-curses when GnuPG's standard input is a file.
Aug 12 2019, 6:16 PM · gnupg (gpg22), Info Needed, Bug Report
skeeto added a comment to T4676: libgcrypt S2K (algo 3) doesn't match OpenPGP.

Considering that early interop testing, you're probably right that this is a bug in the spec, not GnuPG. Otherwise this would have been pretty obvious long ago. The wording in RFC4880bis hasn't been corrected to match practice, so I should probably report this issue there.

Aug 12 2019, 3:03 PM · Documentation, OpenPGP
skeeto created T4676: libgcrypt S2K (algo 3) doesn't match OpenPGP.
Aug 12 2019, 1:25 AM · Documentation, OpenPGP

Aug 5 2019

skeeto added a comment to T4669: Key expiration time sometimes improperly interpreted as a signed 32-bit value.

Re-examining this now, I'm noticing the problem is not at all that it's being treated as signed, but that GnuPG is internally using a 32-bit unsigned integer for the time even though the key expiration scheme allows for expiration dates beyond 2106. Seeing dates in the past threw me off, and when I had originally tried using a zero creation time to test a broader range I ran into T4670.

Aug 5 2019, 12:54 PM · OpenPGP, gnupg, Bug Report
skeeto added a comment to T4669: Key expiration time sometimes improperly interpreted as a signed 32-bit value.

I'm using Debian 10 "Buster" on x86-64, but for this ticket I used my own build of GnuPG so that I could demonstrate with the latest version. The system's GnuPG 2.2.12 has the same behaviors I showed here.

Aug 5 2019, 12:43 PM · OpenPGP, gnupg, Bug Report
skeeto created T4670: Key expiration time ignored for zero creation date keys.
Aug 5 2019, 1:18 AM · gnupg (gpg22), Bug Report
skeeto created T4669: Key expiration time sometimes improperly interpreted as a signed 32-bit value.
Aug 5 2019, 12:45 AM · OpenPGP, gnupg, Bug Report

Dec 30 2014

skeeto added projects to T1800: Allow s2k options for gpg --export-secret-key: gnupg, Bug Report.
Dec 30 2014, 4:47 PM · Feature Request, gnupg
skeeto set Version to 2.1.1 on T1800: Allow s2k options for gpg --export-secret-key.
Dec 30 2014, 4:47 PM · Feature Request, gnupg