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 cert
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 certificate contains
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 boi
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.
That is my other alternative. If there's a commercial one I can buy that can
have a common name without a . in it OR
You cannot self-sign a certificate without the private key file. The
private key file is the thing which allows the signature to be
created, the public key (in the certificate) is the thing which allows
the signature to be verified.
Commercial SSL certificates don't require *your* private key fil
