Let's Encrypt and EV certificates on the same domainCan TLS Compression be enabled on 3rd party CDN sites...
A Missing Symbol for This Logo
Clues on how to solve these types of problems within 2-3 minutes for competitive exams
Why zero tolerance on nudity in space?
GRASS not working with QGIS 3.6
How much mayhem could I cause as a fish?
Potential client has a problematic employee I can't work with
What would you call a real market that is close to perfect competition?
How to deal with possible delayed baggage?
Why does magnet wire need to be insulated?
What is a good reason for every spaceship to carry a weapon on board?
Does diversity provide anything that meritocracy does not?
Why is Agricola named as such?
Airplane generations - how does it work?
Why did Luke use his left hand to shoot?
Why do neural networks need so many training examples to perform?
Why is it that Bernie Sanders is always called a "socialist"?
What happens when a creature with flying blocks my non-flying attacker?
Should I reinstall Linux when changing the laptop's CPU?
Is the child responsible for the Parent PLUS Loan when the parent has passed away?
Is using an 'empty' metaphor considered bad style?
Eww, those bytes are gross
What is the difference between rolling more dice versus fewer dice?
What is the difference between "...", '...', $'...', and $"..." quotes?
Saint abbreviation
Let's Encrypt and EV certificates on the same domain
Can TLS Compression be enabled on 3rd party CDN sites that have no authentication?Security of SSL certificates bought via resellersCertificate ValidationHow to get a certificate from Let's Encrypt for the server which doesn't allows file creationWhy are Let's Encrypt certificates accepted by default by browsers?What if I want a certificate, but DON'T want my domain in a Certificate Transparency log?Why can't Let's Encrypt support wildcard certificates?SSL cert securing an on-premises web service where the domain is hosted externallyMust one have SSL certificates for each domain, to use HTTPS?what is the maximum life-time for Let's Encrypt certificates
I have an e-commerce site (example.com) and want to install an Extended Validation TLS certificate.
But I use a cookieless static content (static.example.com) for images of the website.
To be "Google Shopping friendly" and for secure e-commerce reasons, can I use Let's Encrypt or other domain-validated TLS certificates for static.example.com and EV certificates for example.com?
I have gone through this kind of question online but those were was similar to my situation.
tls letsencrypt
edited 25 mins ago
Luc
23.2k644101
asked 8 hours ago
overeroverer
111
New contributor
overer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I have an e-commerce site (example.com) and want to install an Extended Validation TLS certificate.
But I use a cookieless static content (static.example.com) for images of the website.
To be "Google Shopping friendly" and for secure e-commerce reasons, can I use Let's Encrypt or other domain-validated TLS certificates for static.example.com and EV certificates for example.com?
I have gone through this kind of question online but those were was similar to my situation.
tls letsencrypt
edited 25 mins ago
Luc
23.2k644101
asked 8 hours ago
overeroverer
111
New contributor
overer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
I have an e-commerce site (example.com) and want to install an Extended Validation TLS certificate.
But I use a cookieless static content (static.example.com) for images of the website.
To be "Google Shopping friendly" and for secure e-commerce reasons, can I use Let's Encrypt or other domain-validated TLS certificates for static.example.com and EV certificates for example.com?
I have gone through this kind of question online but those were was similar to my situation.
tls letsencrypt
edited 25 mins ago
Luc
23.2k644101
asked 8 hours ago
overeroverer
111
New contributor
overer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I have an e-commerce site (example.com) and want to install an Extended Validation TLS certificate.
But I use a cookieless static content (static.example.com) for images of the website.
To be "Google Shopping friendly" and for secure e-commerce reasons, can I use Let's Encrypt or other domain-validated TLS certificates for static.example.com and EV certificates for example.com?
I have gone through this kind of question online but those were was similar to my situation.
tls letsencrypt
tls letsencrypt
edited 25 mins ago
Luc
23.2k644101
asked 8 hours ago
overeroverer
111
New contributor
overer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 25 mins ago
Luc
23.2k644101
asked 8 hours ago
overeroverer
111
New contributor
overer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 25 mins ago
Luc
23.2k644101
edited 25 mins ago
Luc
23.2k644101
edited 25 mins ago
Luc
23.2k644101
23.2k644101
asked 8 hours ago
overeroverer
111
New contributor
overer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 8 hours ago
overeroverer
111
asked 8 hours ago
overeroverer
111
111
New contributor
overer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
overer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
overer is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
It is possible to have multiple certificates from different vendors for different parts of the domain and even have overlapping certificates., i.e. multiple certificates which could be used to authenticate the same domain.
Browsers actually only care that a specific certificate is valid for the specific domain it is used on and don't care if the same certificate could also be used for other domains. They also only care that all content is served over HTTPS (i.e. no mixed content) but don't care if some content is served with a EV certificate while other content is served with DV certificate only.
Apart from that, I recommend to read Extended Validation Certificates are Dead to get a better opinion if EV certificates are worth their money at all.
answered 6 hours ago
Steffen UllrichSteffen Ullrich
117k13203271
Very good link to Troy Hunt's article, worth the read.
– WoJ
3 hours ago
Overlapping certificates can actually be a problem for this particular case. If OP passess the key for static.example.com to a CDN but maintain example.com in their own control, then the CDN operator and an attacker who breached CDN operator's security will be able to snoop/impersonate example.com. Note that to actually prevent breaches of trust like this completely, you'll also need to use subresource integrity to prevent your CDN from modifying and injecting scripts into your pages.
– Lie Ryan
2 hours ago
Troy Hunt's extended blog post on EV certificates. A bit less of examples would have been more than enough. Still, it's so entertaining that it's hard to stop reading it.
– Esa Jokinen
2 mins ago
add a comment |
Yes you can, with some caveats.
Normally, letsencrypt certificate are valid for a single FQDN. So you can create an domain-identified only (DV) certificate for static.example.com and an EV-identified certificate for your root domain.
Note be careful that another consideration applies when using wildcard certificate and some multi domain certificate. Some CAs (including LetsEncrypt) may issue a wildcard/multi domain certificate that will also be valid for your root domain because the certificates the issue always contain SAN (subject alternative name) that includes your root domain even if you don't explicitly list your root domain when requesting the certificate. Check the SAN field of the certificate to be sure that your certificate are covering exactly what you expected and no more.
A couple security notes though, be careful of server settings that may apply to all subdomains, like certain Cookies and HSTS config.
answered 7 hours ago
Lie RyanLie Ryan
23.4k34977
2
Multidomain and wildcard are quite different things; LE does the first semiautomatically but not the second. Even if an LE cert does mistakenly include the bare domain, it's perfectly valid to not use that cert for that domain, as long as you can configure your webserver(s?) to do so.
– dave_thompson_085
6 hours ago
add a comment |
There are tree options for this situation:
- Go with wildcard ssl certificate to secure your root and its sub domains.
- If want EV SSL for root domain example.com and also want to secure sub domain static.example.com then go for Symantec EV SSL which now gives facility to secure multi domain with it. (Usually remains high in the price).
- If want EV SSL for root domain example.com and also want to secure sub domain static.example.com then other affordable option is EV Multi Domain SSL.
answered 1 hour ago
DanaDana
12
Your answer is a little short: you mention a few options as bullet points, but not what pros and cons are for each option. The answer also contains some typos. It's a good start for a useful answer, but to get more upvotes, you might want to expand the answer.
– Luc
20 mins ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "162"
};
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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
overer is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsecurity.stackexchange.com%2fquestions%2f204359%2flets-encrypt-and-ev-certificates-on-the-same-domain%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
It is possible to have multiple certificates from different vendors for different parts of the domain and even have overlapping certificates., i.e. multiple certificates which could be used to authenticate the same domain.
Browsers actually only care that a specific certificate is valid for the specific domain it is used on and don't care if the same certificate could also be used for other domains. They also only care that all content is served over HTTPS (i.e. no mixed content) but don't care if some content is served with a EV certificate while other content is served with DV certificate only.
Apart from that, I recommend to read Extended Validation Certificates are Dead to get a better opinion if EV certificates are worth their money at all.
answered 6 hours ago
Steffen UllrichSteffen Ullrich
117k13203271
Very good link to Troy Hunt's article, worth the read.
– WoJ
3 hours ago
Overlapping certificates can actually be a problem for this particular case. If OP passess the key for static.example.com to a CDN but maintain example.com in their own control, then the CDN operator and an attacker who breached CDN operator's security will be able to snoop/impersonate example.com. Note that to actually prevent breaches of trust like this completely, you'll also need to use subresource integrity to prevent your CDN from modifying and injecting scripts into your pages.
– Lie Ryan
2 hours ago
Troy Hunt's extended blog post on EV certificates. A bit less of examples would have been more than enough. Still, it's so entertaining that it's hard to stop reading it.
– Esa Jokinen
2 mins ago
add a comment |
It is possible to have multiple certificates from different vendors for different parts of the domain and even have overlapping certificates., i.e. multiple certificates which could be used to authenticate the same domain.
Browsers actually only care that a specific certificate is valid for the specific domain it is used on and don't care if the same certificate could also be used for other domains. They also only care that all content is served over HTTPS (i.e. no mixed content) but don't care if some content is served with a EV certificate while other content is served with DV certificate only.
Apart from that, I recommend to read Extended Validation Certificates are Dead to get a better opinion if EV certificates are worth their money at all.
answered 6 hours ago
Steffen UllrichSteffen Ullrich
117k13203271
Very good link to Troy Hunt's article, worth the read.
– WoJ
3 hours ago
Overlapping certificates can actually be a problem for this particular case. If OP passess the key for static.example.com to a CDN but maintain example.com in their own control, then the CDN operator and an attacker who breached CDN operator's security will be able to snoop/impersonate example.com. Note that to actually prevent breaches of trust like this completely, you'll also need to use subresource integrity to prevent your CDN from modifying and injecting scripts into your pages.
– Lie Ryan
2 hours ago
Troy Hunt's extended blog post on EV certificates. A bit less of examples would have been more than enough. Still, it's so entertaining that it's hard to stop reading it.
– Esa Jokinen
2 mins ago
add a comment |
It is possible to have multiple certificates from different vendors for different parts of the domain and even have overlapping certificates., i.e. multiple certificates which could be used to authenticate the same domain.
Browsers actually only care that a specific certificate is valid for the specific domain it is used on and don't care if the same certificate could also be used for other domains. They also only care that all content is served over HTTPS (i.e. no mixed content) but don't care if some content is served with a EV certificate while other content is served with DV certificate only.
Apart from that, I recommend to read Extended Validation Certificates are Dead to get a better opinion if EV certificates are worth their money at all.
answered 6 hours ago
Steffen UllrichSteffen Ullrich
117k13203271
It is possible to have multiple certificates from different vendors for different parts of the domain and even have overlapping certificates., i.e. multiple certificates which could be used to authenticate the same domain.
Browsers actually only care that a specific certificate is valid for the specific domain it is used on and don't care if the same certificate could also be used for other domains. They also only care that all content is served over HTTPS (i.e. no mixed content) but don't care if some content is served with a EV certificate while other content is served with DV certificate only.
Apart from that, I recommend to read Extended Validation Certificates are Dead to get a better opinion if EV certificates are worth their money at all.
answered 6 hours ago
Steffen UllrichSteffen Ullrich
117k13203271
answered 6 hours ago
Steffen UllrichSteffen Ullrich
117k13203271
answered 6 hours ago
Steffen UllrichSteffen Ullrich
117k13203271
answered 6 hours ago
Steffen UllrichSteffen Ullrich
117k13203271
117k13203271
Very good link to Troy Hunt's article, worth the read.
– WoJ
3 hours ago
Overlapping certificates can actually be a problem for this particular case. If OP passess the key for static.example.com to a CDN but maintain example.com in their own control, then the CDN operator and an attacker who breached CDN operator's security will be able to snoop/impersonate example.com. Note that to actually prevent breaches of trust like this completely, you'll also need to use subresource integrity to prevent your CDN from modifying and injecting scripts into your pages.
– Lie Ryan
2 hours ago
Troy Hunt's extended blog post on EV certificates. A bit less of examples would have been more than enough. Still, it's so entertaining that it's hard to stop reading it.
– Esa Jokinen
2 mins ago
add a comment |
Very good link to Troy Hunt's article, worth the read.
– WoJ
3 hours ago
Overlapping certificates can actually be a problem for this particular case. If OP passess the key for static.example.com to a CDN but maintain example.com in their own control, then the CDN operator and an attacker who breached CDN operator's security will be able to snoop/impersonate example.com. Note that to actually prevent breaches of trust like this completely, you'll also need to use subresource integrity to prevent your CDN from modifying and injecting scripts into your pages.
– Lie Ryan
2 hours ago
Troy Hunt's extended blog post on EV certificates. A bit less of examples would have been more than enough. Still, it's so entertaining that it's hard to stop reading it.
– Esa Jokinen
2 mins ago
Very good link to Troy Hunt's article, worth the read.
– WoJ
3 hours ago
Very good link to Troy Hunt's article, worth the read.
– WoJ
3 hours ago
Overlapping certificates can actually be a problem for this particular case. If OP passess the key for static.example.com to a CDN but maintain example.com in their own control, then the CDN operator and an attacker who breached CDN operator's security will be able to snoop/impersonate example.com. Note that to actually prevent breaches of trust like this completely, you'll also need to use subresource integrity to prevent your CDN from modifying and injecting scripts into your pages.
– Lie Ryan
2 hours ago
Overlapping certificates can actually be a problem for this particular case. If OP passess the key for static.example.com to a CDN but maintain example.com in their own control, then the CDN operator and an attacker who breached CDN operator's security will be able to snoop/impersonate example.com. Note that to actually prevent breaches of trust like this completely, you'll also need to use subresource integrity to prevent your CDN from modifying and injecting scripts into your pages.
– Lie Ryan
2 hours ago
Troy Hunt's extended blog post on EV certificates. A bit less of examples would have been more than enough. Still, it's so entertaining that it's hard to stop reading it.
– Esa Jokinen
2 mins ago
Troy Hunt's extended blog post on EV certificates. A bit less of examples would have been more than enough. Still, it's so entertaining that it's hard to stop reading it.
– Esa Jokinen
2 mins ago
add a comment |
Yes you can, with some caveats.
Normally, letsencrypt certificate are valid for a single FQDN. So you can create an domain-identified only (DV) certificate for static.example.com and an EV-identified certificate for your root domain.
Note be careful that another consideration applies when using wildcard certificate and some multi domain certificate. Some CAs (including LetsEncrypt) may issue a wildcard/multi domain certificate that will also be valid for your root domain because the certificates the issue always contain SAN (subject alternative name) that includes your root domain even if you don't explicitly list your root domain when requesting the certificate. Check the SAN field of the certificate to be sure that your certificate are covering exactly what you expected and no more.
A couple security notes though, be careful of server settings that may apply to all subdomains, like certain Cookies and HSTS config.
answered 7 hours ago
Lie RyanLie Ryan
23.4k34977
2
Multidomain and wildcard are quite different things; LE does the first semiautomatically but not the second. Even if an LE cert does mistakenly include the bare domain, it's perfectly valid to not use that cert for that domain, as long as you can configure your webserver(s?) to do so.
– dave_thompson_085
6 hours ago
add a comment |
Yes you can, with some caveats.
Normally, letsencrypt certificate are valid for a single FQDN. So you can create an domain-identified only (DV) certificate for static.example.com and an EV-identified certificate for your root domain.
Note be careful that another consideration applies when using wildcard certificate and some multi domain certificate. Some CAs (including LetsEncrypt) may issue a wildcard/multi domain certificate that will also be valid for your root domain because the certificates the issue always contain SAN (subject alternative name) that includes your root domain even if you don't explicitly list your root domain when requesting the certificate. Check the SAN field of the certificate to be sure that your certificate are covering exactly what you expected and no more.
A couple security notes though, be careful of server settings that may apply to all subdomains, like certain Cookies and HSTS config.
answered 7 hours ago
Lie RyanLie Ryan
23.4k34977
2
Multidomain and wildcard are quite different things; LE does the first semiautomatically but not the second. Even if an LE cert does mistakenly include the bare domain, it's perfectly valid to not use that cert for that domain, as long as you can configure your webserver(s?) to do so.
– dave_thompson_085
6 hours ago
add a comment |
Yes you can, with some caveats.
Normally, letsencrypt certificate are valid for a single FQDN. So you can create an domain-identified only (DV) certificate for static.example.com and an EV-identified certificate for your root domain.
Note be careful that another consideration applies when using wildcard certificate and some multi domain certificate. Some CAs (including LetsEncrypt) may issue a wildcard/multi domain certificate that will also be valid for your root domain because the certificates the issue always contain SAN (subject alternative name) that includes your root domain even if you don't explicitly list your root domain when requesting the certificate. Check the SAN field of the certificate to be sure that your certificate are covering exactly what you expected and no more.
A couple security notes though, be careful of server settings that may apply to all subdomains, like certain Cookies and HSTS config.
answered 7 hours ago
Lie RyanLie Ryan
23.4k34977
Yes you can, with some caveats.
Normally, letsencrypt certificate are valid for a single FQDN. So you can create an domain-identified only (DV) certificate for static.example.com and an EV-identified certificate for your root domain.
Note be careful that another consideration applies when using wildcard certificate and some multi domain certificate. Some CAs (including LetsEncrypt) may issue a wildcard/multi domain certificate that will also be valid for your root domain because the certificates the issue always contain SAN (subject alternative name) that includes your root domain even if you don't explicitly list your root domain when requesting the certificate. Check the SAN field of the certificate to be sure that your certificate are covering exactly what you expected and no more.
A couple security notes though, be careful of server settings that may apply to all subdomains, like certain Cookies and HSTS config.
answered 7 hours ago
Lie RyanLie Ryan
23.4k34977
answered 7 hours ago
Lie RyanLie Ryan
23.4k34977
answered 7 hours ago
Lie RyanLie Ryan
23.4k34977
answered 7 hours ago
Lie RyanLie Ryan
23.4k34977
23.4k34977
2
Multidomain and wildcard are quite different things; LE does the first semiautomatically but not the second. Even if an LE cert does mistakenly include the bare domain, it's perfectly valid to not use that cert for that domain, as long as you can configure your webserver(s?) to do so.
– dave_thompson_085
6 hours ago
add a comment |
2
Multidomain and wildcard are quite different things; LE does the first semiautomatically but not the second. Even if an LE cert does mistakenly include the bare domain, it's perfectly valid to not use that cert for that domain, as long as you can configure your webserver(s?) to do so.
– dave_thompson_085
6 hours ago
2
2
Multidomain and wildcard are quite different things; LE does the first semiautomatically but not the second. Even if an LE cert does mistakenly include the bare domain, it's perfectly valid to not use that cert for that domain, as long as you can configure your webserver(s?) to do so.
– dave_thompson_085
6 hours ago
Multidomain and wildcard are quite different things; LE does the first semiautomatically but not the second. Even if an LE cert does mistakenly include the bare domain, it's perfectly valid to not use that cert for that domain, as long as you can configure your webserver(s?) to do so.
– dave_thompson_085
6 hours ago
add a comment |
There are tree options for this situation:
- Go with wildcard ssl certificate to secure your root and its sub domains.
- If want EV SSL for root domain example.com and also want to secure sub domain static.example.com then go for Symantec EV SSL which now gives facility to secure multi domain with it. (Usually remains high in the price).
- If want EV SSL for root domain example.com and also want to secure sub domain static.example.com then other affordable option is EV Multi Domain SSL.
answered 1 hour ago
DanaDana
12
Your answer is a little short: you mention a few options as bullet points, but not what pros and cons are for each option. The answer also contains some typos. It's a good start for a useful answer, but to get more upvotes, you might want to expand the answer.
– Luc
20 mins ago
add a comment |
There are tree options for this situation:
- Go with wildcard ssl certificate to secure your root and its sub domains.
- If want EV SSL for root domain example.com and also want to secure sub domain static.example.com then go for Symantec EV SSL which now gives facility to secure multi domain with it. (Usually remains high in the price).
- If want EV SSL for root domain example.com and also want to secure sub domain static.example.com then other affordable option is EV Multi Domain SSL.
answered 1 hour ago
DanaDana
12
Your answer is a little short: you mention a few options as bullet points, but not what pros and cons are for each option. The answer also contains some typos. It's a good start for a useful answer, but to get more upvotes, you might want to expand the answer.
– Luc
20 mins ago
add a comment |
There are tree options for this situation:
- Go with wildcard ssl certificate to secure your root and its sub domains.
- If want EV SSL for root domain example.com and also want to secure sub domain static.example.com then go for Symantec EV SSL which now gives facility to secure multi domain with it. (Usually remains high in the price).
- If want EV SSL for root domain example.com and also want to secure sub domain static.example.com then other affordable option is EV Multi Domain SSL.
answered 1 hour ago
DanaDana
12
There are tree options for this situation:
- Go with wildcard ssl certificate to secure your root and its sub domains.
- If want EV SSL for root domain example.com and also want to secure sub domain static.example.com then go for Symantec EV SSL which now gives facility to secure multi domain with it. (Usually remains high in the price).
- If want EV SSL for root domain example.com and also want to secure sub domain static.example.com then other affordable option is EV Multi Domain SSL.
answered 1 hour ago
DanaDana
12
answered 1 hour ago
DanaDana
12
answered 1 hour ago
DanaDana
12
answered 1 hour ago
DanaDana
12
12
Your answer is a little short: you mention a few options as bullet points, but not what pros and cons are for each option. The answer also contains some typos. It's a good start for a useful answer, but to get more upvotes, you might want to expand the answer.
– Luc
20 mins ago
add a comment |
Your answer is a little short: you mention a few options as bullet points, but not what pros and cons are for each option. The answer also contains some typos. It's a good start for a useful answer, but to get more upvotes, you might want to expand the answer.
– Luc
20 mins ago
Your answer is a little short: you mention a few options as bullet points, but not what pros and cons are for each option. The answer also contains some typos. It's a good start for a useful answer, but to get more upvotes, you might want to expand the answer.
– Luc
20 mins ago
Your answer is a little short: you mention a few options as bullet points, but not what pros and cons are for each option. The answer also contains some typos. It's a good start for a useful answer, but to get more upvotes, you might want to expand the answer.
– Luc
20 mins ago
add a comment |
overer is a new contributor. Be nice, and check out our Code of Conduct.
overer is a new contributor. Be nice, and check out our Code of Conduct.
overer is a new contributor. Be nice, and check out our Code of Conduct.
overer is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Information Security Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsecurity.stackexchange.com%2fquestions%2f204359%2flets-encrypt-and-ev-certificates-on-the-same-domain%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
