Increase Public Key size to RSA4096 in certificate signing request

[Lenny_Juarbe]

Hello, 

I am trying to import CA signed certs for my OneView 4.00.9 appliances.  My CA admin was able to add the correct template with the following:

X509v3 Key Usage:

Digital Signature, NonRepudiation, Key Encipherment

X509v3 Extended Key Usage:

TLS Web ServerAuthentication, TLS Web Client Authentication

However, when submitting the request it complained about the Public Key size.  Apparently our policy is to use RSA 4096 bits. 

Question is how do you increase the Public Key size in the request to 4096?  

Any help is greatly appreciated.

[ChrisLynch]

Unfortunately, it is not possible to create a CSR with 4096 key length today.  With HPE OneView 4.10 and the appliance put into CNSA Mode (which can break communication with legacy and older systems that cannot support the stronger encryption and cyphers), the CSR would generate a 3072 bit length key.

[Lenny_Juarbe]

Thank you Chris for the reply.  

Just so I understand you correctly, with CNSA Mode the strongest encryption the appliance will generate is 3072 bits.  Is it then possible to generate a csr using openssl with the key size set to 4096 and import the cert?  In other words, does OneView accept/support certs with a 4096 bit Public key size generated by a csr outside of the appliance's own mechanism?

[ChrisLynch]

Unfortunately no.  HPE OneView must generate the CSR today.  We do not have a method to import both the private and publicly signed key to the appliance.

[Thomas24]

Are there any changes until today.

I saw the option over the GUI to use 3072bit but our company policiy only allows key kength of at least 4096

Is there a way to create manually and import Certificates using 4096bits now?

[TravellingKiwi]

Plus 1 on this... We are in pretty much the same boat. 

Has this been 'fixed' yet (OneView 5.3) - The docs would suggest it hasn't...

[DanCernese]

Not in HPE OneView 5.3 or 5.4 (next week).  It is in the backlog though.

[Daniel_Ufer]

I have version 6.20.00-0443754 and still the same problem. 2048 bit for default or 3072 bits for CNSA compatible certificates. Is there an option to create a 4096 bit key/request now?

Regards, Daniel

[ChrisLynch]

We have not had many customers request 4k cert key length, only to reduce it to 2k.  Is this a hard requirement for your organization?

[JT77_CB]

@ChrisLynch .

Hi Chris,

I'm infratructure engineer from Germany. My company will allow certificate templates with least RSA public keys 3072/4096bit after October 2022 depends to Federal Office for Information Security (BSI)  "BSI TR-02102-1: "Cryptographic Mechanisms: Recommendations and Key Lengths" Version: 2022-1 " by January 2022.  BSI recommened to use RSA keys hihger then 3000bit. I guess more german companies with HPE related hardware will get in this rsa key issue.

I'm running HPE Oneview 6.6 due still existing blade enclosures and BL460C Gen9.

So my question is is there a possibility to get CSR with 4096bit, also ILO 4+5 certificates which support 4096bit rsa public key?

Many Thanks Jens

[ChrisLynch]

We are working on a feature that will allow you to import the private and signed key via the REST API.  That means you can generate the CSR outside of OneView, submit to your issuing CA, then import both in PCKS#12 format.  I don't have an ETA that I can share publically.

[JT77_CB]

@ChrisLynch 

Thanks for response Chris.

Can I assume that also the ILO FW will contains the CSR request generate function with 4096bit?

[mc1903-2]

@JT77_CB  I've stumbled across your post trying to find a solution for creating an iLO 5 certificate with a RSA key size greater than 2048 bits.

As far as I can workout through research and testing with an iLO 5 running firmware version 2.78 (latest as of today) there is NO support for iLO certificates with an RSA key size greater than 2048 bits.

CSR generation via the iLO GUI or PowerShell does not ask for keysize input - it's fixed at 2048 bits.

The iLO GUI offers an "Import an SSL Certificate & Private Key" option, but when I manually created a CSR using OpenSSL with a RSA key size of 4096 bits, the import failed with the error "SSL certificate could not be imported since the input key is not supported with the configured iLO security state. Verify the input key is either 384-bit ECDSA key in CNSA security state or 2048-bit RSA key in other security states."

HPE is not alone in this respect. Over the past 10 years, I have found most server/storage vendors remain way behind the times when it comes to any certificate related operations within their products.

It simply has never been given it the importance it should have had from day #1 and that will never change now, as most sheeple are dumb & happy enough to live with self-generated/self-signed certs.

[rant] Nothing will change until vendors are forced (shamed?) to stop relying on self-signed certs in their products and users are forced to use a 'real' CA to provide signed certificates as a mandatory part of the initial service bring up process. [/rant]

M

[JT77_CB]

Knahh another server hardware vendor also from the States can handle RSA4096 Keys, company name have 4 letters ,begins with D and ends with L

But better a RSA2048 key certificate imported then selfsigned rubbish;)

[Jef_Paris]

Hello, any news on this ?  

Even Superm**** allow 4096 keys.