Re: Migrating Bouncy Castle keypairs to FIPS 140-2 compliant key store BCFKS

You can convert between keystore formats using the Java keytool.

Regards,

David

On 16/9/19 12:24 pm, Prateek Kumar wrote:
>
> --------------------------------------------------------------
>
> From: Prateek Kumar <Prateek.Kumar-WGr35GCoQU9Wk0Htik3J/[email protected]>
>
> To: [email protected] <mailto:[email protected]>
>
> Subject: Migrating Bouncy Castle keypairs to FIPS 140-2 compliant key
> store BCFKS
>
>  
>
> Hi,
>
>  
>
> Could anyone please advise on this requirement for our Java-webapp.
>
>  
>
> We have created keypairs (RSA and DH) using the non-FIPS Bouncy Castle
> provider in a .bks keystores, and now we are trying to replace the
> provider with the FIPS 140-2 compliant BC FIPS
> at https://downloads.bouncycastle.org/fips-java/bc-fips-1.0.2.jar
>
>  
>
> For an existing deployment containing these keypairs in .bks (which
> already exist) is there any way to:
>
>  
>
> * Migrate them into .bcfks keystores which is the compliant keystore
> (and any code samples to do so).
>
>  
>
> * "Convert" these keypairs (with same algorithms/mode/padding/keysizes
> as the ones chosen at creation time were already compliant, but
> created using standard Bouncy Castle jars) into versions that would be
> FIPS compliant, or as if they'd been created with the BC FIPS version.
> I don't know if this is possible and in documentation
> at https://downloads.bouncycastle.org/fips-java/BC-FJA-UserGuide-1.0.2.pdf (Page
> 66 Appendix E), all I'm seeing is converting between JCE keypairs to
> low-level FIPS key-primitives.
>
>  
>
> Thanks,
>
> Prateek Kumar
>
> --------------------------------------------------------------
>
>  
>
>
> ---------------------------------------------------------------------
> STATEMENT OF CONFIDENTIALITY
>
> The information contained in this electronic message and any
> attachments to this message are intended for the exclusive use of the
> addressee(s) and may contain confidential or privileged information.
> No representation is made on its accuracy or completeness of the
> information contained in this electronic message. Certain assumptions
> may have been made in the preparation of this material as at this
> date, and are subject to change without notice. If you are not the
> intended recipient, you are hereby notified that any dissemination,
> distribution or copying of this e-mail and any attachment(s) is
> strictly prohibited. Please reply to the sender at NextLabs Inc and
> destroy all copies of this message and any attachments from your
> system.
> ======================================================================