Page MenuHome GnuPG
Create Task
Maniphest T6806

Fix off by one day in the expiry date calculation
Closed, ResolvedPublic
Actions

Description

See T6736 for the problem. We should find a solid solution.

Related Objects
Search...

Event Timeline

• werner triaged this task as Normal priority.Nov 9 2023, 2:19 PM
• werner created this task.
• werner created this object with edit policy "Contributor (Project)".
• ikloecker added a comment.Nov 9 2023, 3:06 PM

See T6736#177624 for the possible cause of the off-by-one day problem.

• ebo added a comment.EditedJan 18 2024, 11:45 AM

works in Gpg4win-4.2.1-beta178
Note to self: need to check with "to the second" expiry time, in case this only occurs with summertime

• ebo closed this task as Resolved.Jan 29 2024, 1:27 PM
• ebo moved this task from Backlog to QA on the gnupg24 board.

Setting a date on the command line is in UTC, displayed in Kleopatra is the corresponding local date which might therefore be one day of. This is as intended and the same for dates before or after the Y2038 cut off.
-> Works with Gpg4win-4.3.0

In case somebody wonders about the ????-??-?? for expiry dates > 2038-01-19 on the command line on Windows: That will be fixed with T6508: Port GnuPG to 64-bit Windows

• werner moved this task from QA to 2.4.6 on the gnupg24 board.Jul 1 2024, 12:18 PM
• werner edited projects, added gnupg24 (2.4.6); removed gnupg24.