Page MenuHome GnuPG
Create Task
Maniphest T5253

expiration changes during interactive expire date verification
Open, LowPublic
Actions

Description

Expiration date (displayed value) gets recalculated after awaiting user input/verification.
User has to react fast to set explicit expiration date (e.g. last second of specific day).

Compact example to reproduce:
gpg --edit-key -> expire -> 20201231T235959
Likely changes to 20210101T0000?? -> 2021-01-01 (on UTC)

see g10/keygen.c: problematic timestamp query in ask_expiredate()

Details

External Link
https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=blob;f=g10/keygen.c;h=01eec57acc4716e79911890713cab3235d2cdc15;hb=refs/heads/master#l2914

Related Objects

Event Timeline

becm created this task.Jan 19 2021, 8:25 PM
becm added a comment.Jan 19 2021, 8:31 PM

Similar to T5252, likely requiring the concept of some kind of "fixed reference date".

In this case below ask_expiredate(), in the ask_expire_interval/parse_expire_string call chain.

• werner triaged this task as Low priority.Jan 20 2021, 9:32 AM
• werner added a project: gnupg (gpg23).
• werner added a subscriber: • werner.

Thanks for the reports. IIRC, we had similar reports in the past either here or on a ML.

I assign a low priority because I can't see a common use case for up to a second creation/expiration times.

• werner added a project: gnupg24.Dec 13 2022, 11:21 AM