When I upgrade to a new version how can I make sure that the DKDMs from the earlier version keep working?
In the newer version it asks for a .dom extension file to import the KDM Encryption certificates. However, in the earlier versions i do not have an option to export the certificates in such a format.
Kindly guide.
Upgrading from 2.11.34 to 2.16.30
-
- Site Admin
- Posts: 2548
- Joined: Thu Nov 14, 2013 2:53 pm
Re: Upgrading from 2.11.34 to 2.16.30
It might "just work"™. But I would strongly advise backing up your configuration before doing the update.
Details of config file locations are here.
Details of config file locations are here.
-
- Posts: 133
- Joined: Wed Oct 04, 2017 4:49 am
Re: Upgrading from 2.11.34 to 2.16.30
I exported the decrypting (and signing) root, intermediate, leaf and leaf private keys from my 2.11.34 installation into 2.17 but at the startup of DOM i get an error which suggest the following
What shall i do in this case? I want to be able to use the DKDM from previous installation.
What shall i do in this case? I want to be able to use the DKDM from previous installation.
You do not have the required permissions to view the files attached to this post.
-
- Posts: 2804
- Joined: Tue Apr 15, 2014 9:11 pm
- Location: Germany
Re: Upgrading from 2.11.34 to 2.16.30
This will usually not create issues, as it only deals with the signing, not encryption. As you have backed up your settings, you should go ahead and recreate the signing chain. Going from 2.11.x to 2.16.x is a huge step, admittedly.
- Carsten
- Carsten