Originally created by @bjacke on GitHub (Feb 4, 2016).
when there is just one domain name configured for a certificate, the CSR shoud be done without altname extension. Currelty requesting a cert for
foo.example.com
will result in
X509v3 Subject Alternative Name:
DNS:foo.example.com
being added to the CSR and in the resulting certificate.
Originally created by @bjacke on GitHub (Feb 4, 2016).
when there is just one domain name configured for a certificate, the CSR shoud be done without altname extension. Currelty requesting a cert for
foo.example.com
will result in
X509v3 Subject Alternative Name:
DNS:foo.example.com
being added to the CSR and in the resulting certificate.
it's not exactly bad - it's just superfluous, makes the cert some bytes
larger for no reason. No big deal if you don't want to change this.
@bjacke commented on GitHub (Feb 5, 2016):
On 05.02.2016 15:59, Lukas Schauer wrote:
> Is that bad in any way?
it's not exactly bad - it's just superfluous, makes the cert some bytes
larger for no reason. No big deal if you don't want to change this.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @bjacke on GitHub (Feb 4, 2016).
when there is just one domain name configured for a certificate, the CSR shoud be done without altname extension. Currelty requesting a cert for
foo.example.com
will result in
X509v3 Subject Alternative Name:
DNS:foo.example.com
being added to the CSR and in the resulting certificate.
@lukas2511 commented on GitHub (Feb 5, 2016):
Is that bad in any way?
@bjacke commented on GitHub (Feb 5, 2016):
On 05.02.2016 15:59, Lukas Schauer wrote:
it's not exactly bad - it's just superfluous, makes the cert some bytes
larger for no reason. No big deal if you don't want to change this.