Page MenuHome GnuPG

Kleopatra: Values for ValidityPeriodInDays ignored
Testing, HighPublic

Description

With the following registry settings:

I expect that the user can change the expiry date to 01.10.2024 but nothing else.
Trying to change the date to 30.09.2026 by changing the last digit in the "valid until" line results in:

But the expiry is then set to that date in 2026 anyway directly after clicking OK on the error notification. (Not additional OK in the creation window is needed.)

Regression.

Details

Version
gpg4win-Beta-50

Event Timeline

ebo triaged this task as High priority.Sep 30 2024, 3:18 PM
ebo created this task.
ikloecker moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.
ikloecker changed the task status from Open to Testing.Oct 1 2024, 1:38 PM

I expect that the user can change the expiry date to 01.10.2024 but nothing else.

For the displayed settings two expiration dates are allowed: 365 days from the current date and 366 days from the current date (min and max are both inclusive).

Backported for VSD 3.3 (backported manually because in master the code has been moved from kleopatra to libkleo)

ebo moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Oct 17 2024, 9:28 AM
ebo moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Nov 5 2024, 10:46 AM

Tested with Gpg4win-Beta-70: works for changing expiry date as well as key creation