As I came across the same problem I did some research and found the following:
Common name in the CSR code needs to be of a certain format. General requirements are latin alphanumeric characters and no special symbols like ! @ # $ % ^ ( ) ~ ? > < & / \ , . " ' _ More peculiarities are described here for your reference. IDN (International ...
If you have purchase a standard, single domain SSL certificate, then
it will be for one domain, so you can only use it for domainname.com
If you have purchased a wildcard or UCC certificate then it will allow
either unlimited subdomains (in the case of a wildcard) or mulitple
domains up to a certain number (in the case of ...
Per https://letsencrypt.org/docs/integration-guide/ :
Let’s Encrypt accepts RSA keys from 2048 to 4096 bits in length, and P-256 and P-384 ECDSA keys. That’s true for both account keys and certificate keys. You can’t reuse an account key as a certificate key.
So you can have EC-based certificates, but note that they will for now still be signed by a RSA-...
how can this work when it takes so long for the changes to propagate?
The propagation time (“up to 48 hours for the changes to be known world wide”) is a conservative estimate of the time that various DNS servers around the world may have records for your domain stored in their internal cache. However, when carrying out its DNS validation (as per the ACME ...
DirectAdmin 1.52.0 started supporting HTTPS for domain pointers. They say:
SSL certificates used in the VirtualHost/server will be the ones from the master domain the pointer is created under.
To avoid SSL Certificate errors, you'll need to ensure that the pointer is also in the master domains certificate.
LetsEncrypt can do this for you, just an extra ...
If you have explained your co-workers assertions correctly, he is incorrect.
CSR's do relate to a single set of certificates and do not affect your ability to create other certs with other CSR.
A CSR is a signing request, and they are not really time critical - indeed for the most part any date/validity period in a CSR is ignored. The important parts are ...
Only the EV = Extended Validation certificates give you the green bar.
It looks different, though, in each browser, these are just examples:
None of the OV / DV give it to you.
The OV certificates just contain company information in it, are worth in my opinion only to State authorities.
What they're really doing with this question is trying to decide which of several possible formats you want the certificate delivered in, without actually asking you.
Choose Apache -- even if you aren't using Apache -- because this should get you the certificate and chain files you need, in an easily usable format for anything in AWS.
This is the standard ...
It's a common mistake to think that when you create your own SSL certificate they are self-signed. You can also create your own CA, and sign your certificates with it (yeah, the CA certificate will be self signed too, but so are the "real" CA certificates - every certificate chain is started by the CA certificate, and CA is created from scratch). The main ...
It's important to understand that SSL certificates come in two "flavors":
Self-signed - In which case, you generate them entirely on your own with no additional cost.
CA-signed - In which case, a recognized certificate authority (Symantec, GeoTrust, GoDaddy, etc) signs the cert.
Is this a public facing website? If so, then I'd strongly suggest ...
EV/High Assurance SSL certs use unique object IDs that are inserted into the extended policy field of the SSL certificate. Most applications (browsers) that support EV-SSL have this OID and CA fingerprint hard coded into them. When they get a successful match, the browser then displays the extended data.
You don't mention your usage case, but if this is ...