oVirt Engine now uses the PKCS#12 format to store keys, replacing the previous Java Key Store format. The PKCS#12 format separates the engine as client key usage and engine as server key usage to support third party certificates for the web administration and user portals.
Author: Alon Bar-Lev <firstname.lastname@example.org>
Date: Sat Aug 4 21:27:00 2012 +0300
pki: use PKCS#12 format to store keys
Java supports standard cryptographic format PKCS#12, this format
bundles private key and certificate chain into one file with integrity
Using Java proprietary key store format force additional work if using
This change is a migration from JKS and duplicates into single PKCS#12
keystore for private key store. It does not handle the trust store which
is left as JKS for now.
Remove unnecessary scripts from CA implementations that do not support
Signed-off-by: Alon Bar-Lev <email@example.com>
This bug is currently attached to errata RHEA-2013:14491. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
Doc is provided at dependencies.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.