Added by Felix Tiede over 12 years ago. Updated over 12 years ago.
Description
At least when setting certificate expiration to the same date as validity start date the date gets ignored and seemingly random expiration dates are used.
For example a request is opened for signing and validity timestamp controls are filled as follows:
Not valid before: 09.05.2013 11:32:45 Expires: 09.06.2013 11:32:45
Changing Not valid before to 09.05.2013 11:45:00 and Expires to 09.05.2013 11:32:45 (changing date but leaving time as-is) renders this error.
Quick workaround is to change expiration time before changing expiration date. A bugfix will follow in release 0.1.9.
Applied in changeset kca|d473e21fe8d67a2d0281872f7a183b5a408d5583.