From: Tomas G. <to...@pr...> - 2008-10-06 13:01:35
|
We're releasing a couple of point releases just to keep the branches up to date as well. We still recommend EJBCA 3.7.1 for production. These are both minor releases aimed to fix a few issues found, most notable: - Upgrade fails to set internal state of CA expire time for externally signed CAs - Key length changes when editing CA in admin-GUI - LdapPublisher searches for old objects on certDN instead of Ldap DN If you have been affected by any of these issues, and want to keep running your older version, you can upgrade to these versions. For the key length change issue, there is also a CLI command that can be used to reset/change the value to your desired value. This can also be used to change algorithm or key length when renewing a CA. Regards, The EJBCA team Changes: 3.6.3, 2008-10-06 --- Bug * [ECA-952] - Entity Profile : the text "Use entity e-mail field" is not localizable * [ECA-954] - TestProtectedLog fails if ProtectedLogDevice is not enabled in configuration * [ECA-955] - PKCS11 support problem on OCSP responder * [ECA-957] - ocspclient.jar cannot handle answers with responderID of type Name. * [ECA-968] - Key length changes when editing CA in admin-GUI * [ECA-970] - LdapPublisher searches for old objects on certDN instead of Ldap DN 3.5.9, 2008-10-06 --- Improvement * [ECA-891] - Avoid unnecessary database searches during HealthCheck Bug * [ECA-886] - Upgrade fails to set internal state of CA expire time for externally signed CAs * [ECA-906] - EjbcaHealthCheck may use same session bean object for concurrent accesses * [ECA-968] - Key length changes when editing CA in admin-GUI |