× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



I think the answer is:

openssl req -in my.csr -noout -pubkey

It generates a public key from the csr but then I get a formatting issue from the DCM issued CSR when evaluated for Letsencrypt. I know I have to issue the CSR from DCM in order to import the SSL cert later. Has anyone used the manual method for Letsencrypt? I have used the automated acme.sh script to get and validate a Letsencrypt certificate but since it is generated outside of DCM I can't use it with IBM's Apache (or, at least, haven't figured out how to....)

Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java
LinkedIn - www.linkedin.com/in/petehelgren
Twitter - Sys_i_Geek IBM_i_Geek

On 10/20/2016 9:40 PM, Pete Helgren wrote:
The first part, generating a CSR is easy. I can go to DCM and generate a CSR but the website that allows you to manually create a Letsencrypt SSL cert asks for a Public Key AND the CSR. So, where would I find/generate/export a public for the CSR? To get an idea of what I am dealing with, look here: https://gethttpsforfree.com/

The recommendation there is generate the key with openssl, which I have done in the past when I have generated a non-DCM CSR. But, when DCM is creating the CSR, where do I find the public private keys? I expect that they are stored somewhere, just like when I create certs/csr's using openssl. Just need to know the location.

Or, maybe this just isn't possible with DCM...?



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.