.
The commercial SSL certificates you buy don't require the private key file
to get a certificate back from them, so there should be a way to do this
right?
Thanks,
Chuck
--
View this message in context:
http://www.nabble.com/self-signed-cert-without-private-key-file-tp22609395p22609395.html
Sent from
.)
-Kyle H
--
View this message in context:
http://www.nabble.com/self-signed-cert-without-private-key-file-tp22609395p22621760.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
__
OpenSSL Project
carock wrote:
Can the same process be duplicated without going commercial? I need a
certificate that doesn't use a FQDN for the common name and I haven't found
a commercial one that allows that.
Set up your own CA, and issue your own certificates to your own
requirements. The problem then
the CSR from if you don't have a private key?
Regards,
Graham
--
--
View this message in context:
http://www.nabble.com/self-signed-cert-without-private-key-file-tp22609395p22624625.html
Sent from the OpenSSL - User mailing list archive at Nabble.com
carock wrote:
Unfortunately, I'm dealing with an HP Proliant server. Specifically the iLO
interface which is a backend management device embeded in the server.
This device has it's own SSL cert from the factory. With the latest rounds
of updates from Firefox, that browser now complains my
