So we are a minute off. The expiration timestamp is not stored in the key, instead the difference to the creation timestamp is give. This makes it a bit challenging to get it always right. Did you tried

Thanks

Nope, that is correct, the last update of the manual was

Oops, I am sorry for the confusion. This patch is the correct one. The patch originally attached contains also revert of the commit I've reported in the other bug report today.

@gniibe, will you be so kind and look into this?

It works for me(tm).

In T4933#134421, @werner wrote:

gpg -k --with-colons KEYID | awk -F: '$1=="pub" {print srtrftime ("%F %T", $7)}'

and that in ISO 8601 format

Right, we do have this option only in master (devel version).

I can't find such option.

How does it show when you specify --full-time-strings (in UTC by ISO time format)?
I wonder if it is valid as data, but there is a problem of showing key(s).

Attaching the actual program

Any progress on this one?

I debugged some more.

Yes, with current gnupg it works w/o problems. Well, unless systemd decided to remove the directory. There is a loginctl(1) way to avoid this.

Also I suppose the 2.1.20 version above is typo and 2.2.20 is actually meant.

Can you please clarify? Let's assume I am using current gnupg version (2.2.20) and /run/user/$UID exists. Everything should work seamlessly, should it?

You are still using the old way of having the sockets in ${GNUPGHOME:-~/.gnupg}. Since 2.2.13 we use

That would be awesome, thanks!

API-wise this would be possible because right now gpg errors out with

It is the pinentry-curses, which is needed to reproduce the problem.
Using tab and Return to navigate the dialog.
After pressing ok, the password question dialog reappears. I tried 20 times to press ok, every time the password question dialog reappeared.
If I press cancel, the process aborts. So I'm sure, I hit the right button.

I tested with this patch (which changes use of constant-time routine when it's secure memory):

Done for master

In D501#4558, @slandden wrote:

But I need it to shift H one to the left:
H1 = H << one;

And yes: If I install pinentry-gtk2 and follow the steps, it works as excepted.

Perhaps I explain the steps, I'm doing.
I'm on a minimal debian buster instance.

1. gpg2 --full-gen-key
2. Insert stuff.
3. See Dialog:

Real name: Test1 Tester
Email address: test1@example.com
Comment: no pw
You selected this USER-ID:

"Test1 Tester (no pw) <test1@example.com>"

remove <<64 | >> 64 which has poor codegen.

described in previous comment. Mostly cosmetic

Generally nice looking patch and great improvement for performance.

Ok. Renamed ist "ttytype_l" (l for local) and found the button to upload a file.
Hope it helps.

Using a double underscore in a symbol should be avoided because such symbols are reserved for system use.
(To include a diff inline, please intend it by two spaces so that it is not not considered as marked up text.)

Thanks. I tried to install the latest released version, 1.4.23, but I got the same error.

That is a very old version (2015); please retry using the latest released version 1.4.23 (from 2018).

Seems like this is applicable to other binaries as well:

I just tried and Pinentry ask me whether I really want to use an unprotected key. Take care that you hit the right button.