![]() ![]() We now feed OpenSSL the configuration and private key files and instruct it to output a new CSR. KeyUsage = digitalSignature, keyEncipherment, dataEnciphermentĠ.organizationName = ByteSizedAlex CorporationĬommonName = NODE1IPMI.ad. ĭistinguished_name = req_distinguished_name Be sure to use SHA256 as a minimum for the hashing algorithm. I’ll save this text file as ‘node1ipmi.cfg’. For this example I’m just going to re-use an existing template I have, modifying the common name. Now I have my private key it’s time to create my configuration file so I can then combine the two to generate my certificate signing request, also known as a CSR. Generating RSA private key, 2048 bit long modulus C:\OpenSSL\bin>openssl.exe genrsa 2048 > node1ipmi.key I will generate a private 2048 bit RSA key and redirect the output from OpenSSL to a file named ‘node1impi.key’, I strongly recommend you do not create a key size less than 2048 bits. It’s not the end of the world that they don’t but it would simplify things. ![]() The system requires we provide the new certificate and the private key, it would be nice if Supermicro provided a built-in certificate creation and signing request interface. Let’s get right to it – once logged on we can click the ‘Configuration’ button and then select the ‘SSL Certification’ option. Anyone I work with will tell you that I really do hate seeing certificate alerts! This is something I did at work some time ago and then handed over to our team junior to complete. Now that I’ve upgraded the firmware on both units I think it’s about time I sorted the certificates as well. I’ve been meaning to replace the SSL/TLS certificates on my Supermicro servers IPMI (Intelligent Provisioning Management Interface) consoles. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |