View Bug Details

IDProjectCategoryView StatusLast Update
0001422DCP-o-matic[All Projects] Featurespublic2018-12-02 15:28
ReportercarlAssigned To 
PrioritynormalSeverityminorReproducibilityN/A
Status newResolutionopen 
Product Version 
Target Version2.13.xFixed in Version 
Summary0001422: Set the validity period of DCP-o-matic's certificates to start before "now" on creation
Description

Otherwise if DCP-o-matic is installed and then used straight away to create stuff, the validity times can be in the future to servers with badly-synced clocks.

TagsNo tags attached.
Estimated work requiredUnknown

Activities

Carsten

2018-12-02 14:22

manager   ~0002789

I would say this only concerns very rare circumstances where a new installation of DCP-o-matic is used immediately for the creation of encrypted content to be played out 'immediately'. Admittedly, it can happen. Some Dolby media blocks have clocks with unusually high drift rates, and if not corrected on a regular basis, can drift multiple days. And maybe this could also cause problems with the signing certificate if the server is picky.

I can see no reason why the certificate validity period couldn't be set to start a few days from the past.

  • Carsten

Carsten

2018-12-02 15:28

manager   ~0002790

Last edited: 2018-12-02 15:28

View 2 revisions

On a side note - our Sony was installed in March 2013. It was delivered from Japan sometime in February 2013. It was one of the very first units to be installed.

The media block certificate validity window is:

Tue, Dec 18, 2012 09:16 UTC — Thu, Dec 11, 2042 09:26 UTC

Bug History

Date Modified Username Field Change
2018-12-01 22:01 carl New Bug
2018-12-02 14:22 Carsten Note Added: 0002789
2018-12-02 15:28 Carsten Note Added: 0002790
2018-12-02 15:28 Carsten Note Edited: 0002790 View Revisions