31 Jan
2017
31 Jan
'17
12:25 p.m.
At the moment it looks like the DKDM was issued against the signing veers
and not the decrypting certainty.
On Tue, Jan 31, 2017 at 3:03 AM Carsten Kurz via DCPomatic <
dcpomatic(a)carlh.net> wrote:
I remember that I had an issue after I had been
working with, and updating
DCP-o-matic for a long time on the same machine. I couldn't issue working
certificates for a DKDM.
'Recreate certificates and keys' solved that issue. Something in
preferences must have been mixed up over so many version updates.
However, I guess before doing that, exporting the current chain and saving
it under a name of the current date and DOM version before that may be a
good idea. Depends on what you had been working on before.
- Carsten
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
--
[image: SpectiCast] <http://www.specticast.com/> Tom Haines :: Executive
Director of Digital Cinema Services
210 W Rittenhouse Sq, Ste 400 | Philadelphia, PA 19103, USA
Office: 215-618-3874 | Mobile: 484-269-8227 | Skype: tom.haines41
Facebook <https://www.facebook.com/SpectiCastEntertainment> | Twitter
<https://twitter.com/Specticast> | Google+
<https://plus.google.com/u/0/b/104757180246475600072/104757180246475600072/posts>
| Instagram <http://instagram.com/specticast> | Tumblr
<http://specticast.tumblr.com/>