Bug #52: Expiration date is sometimes ignored - KDE Certification Authority Tool - Redmine

Actions

Copy link

Bug #52

closed

Expiration date is sometimes ignored

Added by Felix Tiede about 12 years ago. Updated about 12 years ago.

Status:

Closed

Priority:

Urgent

Assignee:

Felix Tiede

Target version:

0.1.9

Start date:

11/16/2013

Due date:

11/17/2013

% Done:

100%

Estimated time:

4:00 h

Spent time:

2:00 h

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.

Actions

Copy link

Updated by Felix Tiede about 12 years ago

% Done changed from 0 to 10

The date is correctly used if the validity timespan is still positive.
It does not work if the following conditions are met:

Start of validity (date and time) is in the future.
Time of expiration is before time of start of validity.
Date of expiration is set to the same date as start of validity.

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.

Actions

Copy link