Is this the right way to generate a wildcard CSR?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
1
down vote

favorite












I generated my CSR on an Amazon Linux system using this command



openssl req -new -sha256 -key ~/mymaindomain.com.ssl/mymaindomain.com.key -out ~/mymaindomain.com.ssl/mymaindomain.com.csr


I verified what I had done using



[davea@host mymaindomain.com.ssl]$ openssl req -noout -text -in ~/mymaindomain.com.ssl/mymaindomain.com.csr
Certificate Request:
Data:
Version: 0 (0x0)
Subject: C=US, ST=NY, L=New York, O=Main Co, OU=SubCo, CN=mymaindomain.com
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)


Before I submit this to a CA, I was curious if this will match "www.mymaindomain.com" and "abc.mymaindomain.com." I wanted to create a CSR that would match the "*.mymaindomain.com" expression but not quite sure if I did it right.







share|improve this question




















  • When it asked you for the common name, did you list it as *.mydomain.com or just .mydomain.com? If you have the wildcard listed as the common name, it should work. Doesn't look like your common name has a wildcard.
    – saleetzo
    Mar 22 at 19:41











  • You didn't make it correctly, since there's no wildcard ( * ) appearing. Look with this example: openssl s_client -connect stackexchange.com:443 look at the CN . CN=*.stackexchange.com there's a * for wildcard. It wouldn't match stackexchange.com , but if you get the certificate and decode it with openssl x509 -noout -text you'll see all the SANs: DNS:*.stackexchange.com, DNS:stackoverflow.com, DNS:*.stackoverflow.com, [...] DNS:stackexchange.com . Now you know what to do. And yes adding SANs with openssl is a bit painful, but I'm sure there are already Q/A about this
    – A.B
    Mar 22 at 19:53











  • Thanks. No I didn't make it with "*.mymaindomain.com" ... it was just "mymaindomain.com". These comments give me exactly the answer I was looking for.
    – Dave
    Mar 22 at 20:13














up vote
1
down vote

favorite












I generated my CSR on an Amazon Linux system using this command



openssl req -new -sha256 -key ~/mymaindomain.com.ssl/mymaindomain.com.key -out ~/mymaindomain.com.ssl/mymaindomain.com.csr


I verified what I had done using



[davea@host mymaindomain.com.ssl]$ openssl req -noout -text -in ~/mymaindomain.com.ssl/mymaindomain.com.csr
Certificate Request:
Data:
Version: 0 (0x0)
Subject: C=US, ST=NY, L=New York, O=Main Co, OU=SubCo, CN=mymaindomain.com
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)


Before I submit this to a CA, I was curious if this will match "www.mymaindomain.com" and "abc.mymaindomain.com." I wanted to create a CSR that would match the "*.mymaindomain.com" expression but not quite sure if I did it right.







share|improve this question




















  • When it asked you for the common name, did you list it as *.mydomain.com or just .mydomain.com? If you have the wildcard listed as the common name, it should work. Doesn't look like your common name has a wildcard.
    – saleetzo
    Mar 22 at 19:41











  • You didn't make it correctly, since there's no wildcard ( * ) appearing. Look with this example: openssl s_client -connect stackexchange.com:443 look at the CN . CN=*.stackexchange.com there's a * for wildcard. It wouldn't match stackexchange.com , but if you get the certificate and decode it with openssl x509 -noout -text you'll see all the SANs: DNS:*.stackexchange.com, DNS:stackoverflow.com, DNS:*.stackoverflow.com, [...] DNS:stackexchange.com . Now you know what to do. And yes adding SANs with openssl is a bit painful, but I'm sure there are already Q/A about this
    – A.B
    Mar 22 at 19:53











  • Thanks. No I didn't make it with "*.mymaindomain.com" ... it was just "mymaindomain.com". These comments give me exactly the answer I was looking for.
    – Dave
    Mar 22 at 20:13












up vote
1
down vote

favorite









up vote
1
down vote

favorite











I generated my CSR on an Amazon Linux system using this command



openssl req -new -sha256 -key ~/mymaindomain.com.ssl/mymaindomain.com.key -out ~/mymaindomain.com.ssl/mymaindomain.com.csr


I verified what I had done using



[davea@host mymaindomain.com.ssl]$ openssl req -noout -text -in ~/mymaindomain.com.ssl/mymaindomain.com.csr
Certificate Request:
Data:
Version: 0 (0x0)
Subject: C=US, ST=NY, L=New York, O=Main Co, OU=SubCo, CN=mymaindomain.com
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)


Before I submit this to a CA, I was curious if this will match "www.mymaindomain.com" and "abc.mymaindomain.com." I wanted to create a CSR that would match the "*.mymaindomain.com" expression but not quite sure if I did it right.







share|improve this question












I generated my CSR on an Amazon Linux system using this command



openssl req -new -sha256 -key ~/mymaindomain.com.ssl/mymaindomain.com.key -out ~/mymaindomain.com.ssl/mymaindomain.com.csr


I verified what I had done using



[davea@host mymaindomain.com.ssl]$ openssl req -noout -text -in ~/mymaindomain.com.ssl/mymaindomain.com.csr
Certificate Request:
Data:
Version: 0 (0x0)
Subject: C=US, ST=NY, L=New York, O=Main Co, OU=SubCo, CN=mymaindomain.com
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
Public-Key: (2048 bit)


Before I submit this to a CA, I was curious if this will match "www.mymaindomain.com" and "abc.mymaindomain.com." I wanted to create a CSR that would match the "*.mymaindomain.com" expression but not quite sure if I did it right.









share|improve this question











share|improve this question




share|improve this question










asked Mar 22 at 19:33









Dave

368827




368827











  • When it asked you for the common name, did you list it as *.mydomain.com or just .mydomain.com? If you have the wildcard listed as the common name, it should work. Doesn't look like your common name has a wildcard.
    – saleetzo
    Mar 22 at 19:41











  • You didn't make it correctly, since there's no wildcard ( * ) appearing. Look with this example: openssl s_client -connect stackexchange.com:443 look at the CN . CN=*.stackexchange.com there's a * for wildcard. It wouldn't match stackexchange.com , but if you get the certificate and decode it with openssl x509 -noout -text you'll see all the SANs: DNS:*.stackexchange.com, DNS:stackoverflow.com, DNS:*.stackoverflow.com, [...] DNS:stackexchange.com . Now you know what to do. And yes adding SANs with openssl is a bit painful, but I'm sure there are already Q/A about this
    – A.B
    Mar 22 at 19:53











  • Thanks. No I didn't make it with "*.mymaindomain.com" ... it was just "mymaindomain.com". These comments give me exactly the answer I was looking for.
    – Dave
    Mar 22 at 20:13
















  • When it asked you for the common name, did you list it as *.mydomain.com or just .mydomain.com? If you have the wildcard listed as the common name, it should work. Doesn't look like your common name has a wildcard.
    – saleetzo
    Mar 22 at 19:41











  • You didn't make it correctly, since there's no wildcard ( * ) appearing. Look with this example: openssl s_client -connect stackexchange.com:443 look at the CN . CN=*.stackexchange.com there's a * for wildcard. It wouldn't match stackexchange.com , but if you get the certificate and decode it with openssl x509 -noout -text you'll see all the SANs: DNS:*.stackexchange.com, DNS:stackoverflow.com, DNS:*.stackoverflow.com, [...] DNS:stackexchange.com . Now you know what to do. And yes adding SANs with openssl is a bit painful, but I'm sure there are already Q/A about this
    – A.B
    Mar 22 at 19:53











  • Thanks. No I didn't make it with "*.mymaindomain.com" ... it was just "mymaindomain.com". These comments give me exactly the answer I was looking for.
    – Dave
    Mar 22 at 20:13















When it asked you for the common name, did you list it as *.mydomain.com or just .mydomain.com? If you have the wildcard listed as the common name, it should work. Doesn't look like your common name has a wildcard.
– saleetzo
Mar 22 at 19:41





When it asked you for the common name, did you list it as *.mydomain.com or just .mydomain.com? If you have the wildcard listed as the common name, it should work. Doesn't look like your common name has a wildcard.
– saleetzo
Mar 22 at 19:41













You didn't make it correctly, since there's no wildcard ( * ) appearing. Look with this example: openssl s_client -connect stackexchange.com:443 look at the CN . CN=*.stackexchange.com there's a * for wildcard. It wouldn't match stackexchange.com , but if you get the certificate and decode it with openssl x509 -noout -text you'll see all the SANs: DNS:*.stackexchange.com, DNS:stackoverflow.com, DNS:*.stackoverflow.com, [...] DNS:stackexchange.com . Now you know what to do. And yes adding SANs with openssl is a bit painful, but I'm sure there are already Q/A about this
– A.B
Mar 22 at 19:53





You didn't make it correctly, since there's no wildcard ( * ) appearing. Look with this example: openssl s_client -connect stackexchange.com:443 look at the CN . CN=*.stackexchange.com there's a * for wildcard. It wouldn't match stackexchange.com , but if you get the certificate and decode it with openssl x509 -noout -text you'll see all the SANs: DNS:*.stackexchange.com, DNS:stackoverflow.com, DNS:*.stackoverflow.com, [...] DNS:stackexchange.com . Now you know what to do. And yes adding SANs with openssl is a bit painful, but I'm sure there are already Q/A about this
– A.B
Mar 22 at 19:53













Thanks. No I didn't make it with "*.mymaindomain.com" ... it was just "mymaindomain.com". These comments give me exactly the answer I was looking for.
– Dave
Mar 22 at 20:13




Thanks. No I didn't make it with "*.mymaindomain.com" ... it was just "mymaindomain.com". These comments give me exactly the answer I was looking for.
– Dave
Mar 22 at 20:13















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f432914%2fis-this-the-right-way-to-generate-a-wildcard-csr%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f432914%2fis-this-the-right-way-to-generate-a-wildcard-csr%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

How to check contact read email or not when send email to Individual?

Displaying single band from multi-band raster using QGIS

How many registers does an x86_64 CPU actually have?