On Thu, Jun 18, 2009 at 11:28:48AM -0400, Jim Adams wrote:
> The private key is probably encoded with a non-FIPS-compliant algorithm.
> Try encoding the private key with PKCS8.
No. See my previous post. In any case, the browser is generating the
container. The container can be re-encoded, to use stronger keys, and
the browser will probably be able to read it, even if it does not
generate the key that way. Of course the code doing the conversion
needs to be non-FIPS code, as it needs to access the non-FIPS cert.
--
Viktor.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager majord...@openssl.org
