Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.networking > #3409 > unrolled thread
| Started by | "papakota" <abrodski@hotmail.com> |
|---|---|
| First post | 2015-07-02 12:14 +0300 |
| Last post | 2015-07-03 15:07 +0300 |
| Articles | 7 — 2 participants |
Back to article view | Back to comp.os.linux.networking
Need advice on transfering SSL-enabled site from hosting to a localhost "papakota" <abrodski@hotmail.com> - 2015-07-02 12:14 +0300
Re: Need advice on transfering SSL-enabled site from hosting to a localhost "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2015-07-02 23:52 -0400
Re: Need advice on transfering SSL-enabled site from hosting to a localhost "papakota" <abrodski@hotmail.com> - 2015-07-03 15:06 +0300
Re: Need advice on transfering SSL-enabled site from hosting to a localhost "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2015-07-03 16:21 -0400
Re: Need advice on transfering SSL-enabled site from hosting to a localhost "papakota" <abrodski@hotmail.com> - 2015-07-03 15:06 +0300
Re: Need advice on transfering SSL-enabled site from hosting to a localhost "papakota" <abrodski@hotmail.com> - 2015-07-03 15:06 +0300
Re: Need advice on transfering SSL-enabled site from hosting to a localhost "papakota" <abrodski@hotmail.com> - 2015-07-03 15:07 +0300
| From | "papakota" <abrodski@hotmail.com> |
|---|---|
| Date | 2015-07-02 12:14 +0300 |
| Subject | Need advice on transfering SSL-enabled site from hosting to a localhost |
| Message-ID | <mn2vfl$uuh$1@adenine.netfront.net> |
Hello! I have a web site that has HTTPS. Right now I DO NOT have SSL certificate installed on hosting. They charge extra for that. I want to transfer my site to a localhost and then to install SSL on Apache myself. So I wonder whether I should pay them and have them SSL certificate installed on a hosting server and after that to copy to site to a localhost OR to leave it alone as it is now and just install SSL on Apache from scratch myself. I ALREADY have SSL certificate installed as it was PRIOR to my termination of my previous hosting account (when that archive ZIP file was originally created). It's already there files-wise, just not installed yet on my new (current) hosting server. And though I don't feel like wasting $25 for their job to install SSL's (I've got 2, but they charge for a bulk of an extra 10+1 free that comes with the hosting plan = 11 SSL's alltogether), money is not a critical point here. What is critical is the EASY path for me to get the job done. I'm not a big expert when it comes to system administration and Apache. And I'm a complete novice in Linux (I use W7/Ubuntu 14.04 Desktop edition dual-boot box). --- Это сообщение проверено на вирусы антивирусом Avast. https://www.avast.com/antivirus --- news://freenews.netfront.net/ - complaints: news@netfront.net ---
[toc] | [next] | [standalone]
| From | "David W. Hodgins" <dwhodgins@nomail.afraid.org> |
|---|---|
| Date | 2015-07-02 23:52 -0400 |
| Message-ID | <op.x06ic9bua3w0dxdave@hodgins.homeip.net> |
| In reply to | #3409 |
On Thu, 02 Jul 2015 05:14:18 -0400, papakota <abrodski@hotmail.com> wrote: > I have a web site that has HTTPS. Right now I DO NOT have SSL certificate > installed on hosting. They charge extra for that. I want to transfer my site > to a localhost and then to install SSL on Apache myself. So I wonder whether > I should pay them and have them SSL certificate installed on a hosting > server and after that to copy to site to a localhost OR to leave it alone as > it is now and just install SSL on Apache from scratch myself. > I ALREADY have SSL certificate installed as it was PRIOR to my termination > of my previous hosting account (when that archive ZIP file was originally A certificate is only good for the domain and hostnames it's been set up for. While you could generate your own certificate, no browser would trust it without the user approving it. A certificate generated for one domain or host can not be used on another host, without the users getting the warning that the hostname does not match the certificate name. Regards, Dave Hodgins -- Change nomail.afraid.org to ody.ca to reply by email. (nomail.afraid.org has been set up specifically for use in usenet. Feel free to use it yourself.)
[toc] | [prev] | [next] | [standalone]
| From | "papakota" <abrodski@hotmail.com> |
|---|---|
| Date | 2015-07-03 15:06 +0300 |
| Message-ID | <mn5tre$nsa$1@adenine.netfront.net> |
| In reply to | #3410 |
Thanks a lot for your reply! I think I might haven't made myself clear enough. The domain the cert is for remains THE SAME -- regardless whether it's installed in a hosting environment or on my local machine at home. As per hostnames, here I don't know what you meant exactly. I think that when a CA issues a certificate, you can install it on ANY server (at least, Apache, for sure). The cert is not tied to a specific box, right? Maximum, I might have to re-issue CSR or whatever it's called, I don't remember exactly all the procedures, but it's not that difficult anyhow. As per self-signed certificates that you mentioned -- I know what you're saying in that regard. It does look scary in a browser, unless you know 100% what it's about (like if it belongs to you). DEFINITELY I won't even think to show that Freddy Krueger thing to my potential clients! No way, God forbid! "David W. Hodgins" сообщил(а) в новостях следующее:op.x06ic9bua3w0dxdave@hodgins.homeip.net... On Thu, 02 Jul 2015 05:14:18 -0400, papakota <abrodski@hotmail.com> wrote: > I have a web site that has HTTPS. Right now I DO NOT have SSL certificate > installed on hosting. They charge extra for that. I want to transfer my > site > to a localhost and then to install SSL on Apache myself. So I wonder > whether > I should pay them and have them SSL certificate installed on a hosting > server and after that to copy to site to a localhost OR to leave it alone > as > it is now and just install SSL on Apache from scratch myself. > I ALREADY have SSL certificate installed as it was PRIOR to my termination > of my previous hosting account (when that archive ZIP file was originally A certificate is only good for the domain and hostnames it's been set up for. While you could generate your own certificate, no browser would trust it without the user approving it. A certificate generated for one domain or host can not be used on another host, without the users getting the warning that the hostname does not match the certificate name. Regards, Dave Hodgins -- Change nomail.afraid.org to ody.ca to reply by email. (nomail.afraid.org has been set up specifically for use in usenet. Feel free to use it yourself.) --- Это сообщение проверено на вирусы антивирусом Avast. https://www.avast.com/antivirus --- news://freenews.netfront.net/ - complaints: news@netfront.net ---
[toc] | [prev] | [next] | [standalone]
| From | "David W. Hodgins" <dwhodgins@nomail.afraid.org> |
|---|---|
| Date | 2015-07-03 16:21 -0400 |
| Message-ID | <op.x07r57v1a3w0dxdave@hodgins.homeip.net> |
| In reply to | #3411 |
On Fri, 03 Jul 2015 08:06:02 -0400, papakota <abrodski@hotmail.com> wrote: > I think I might haven't made myself clear enough. The domain the cert is for > remains THE SAME -- regardless whether it's installed in a hosting > environment or on my local machine at home. As per hostnames, here I don't > know what you meant exactly. I think that when a CA issues a certificate, > you can install it on ANY server (at least, Apache, for sure). The cert is > not tied to a specific box, right? Correct, as long as you have control over the dns records for the domain name. Regards, Dave Hodgins -- Change nomail.afraid.org to ody.ca to reply by email. (nomail.afraid.org has been set up specifically for use in usenet. Feel free to use it yourself.)
[toc] | [prev] | [next] | [standalone]
| From | "papakota" <abrodski@hotmail.com> |
|---|---|
| Date | 2015-07-03 15:06 +0300 |
| Message-ID | <mn5trn$nsd$1@adenine.netfront.net> |
| In reply to | #3410 |
Thanks a lot for your reply! I think I might haven't made myself clear enough. The domain the cert is for remains THE SAME -- regardless whether it's installed in a hosting environment or on my local machine at home. As per hostnames, here I don't know what you meant exactly. I think that when a CA issues a certificate, you can install it on ANY server (at least, Apache, for sure). The cert is not tied to a specific box, right? Maximum, I might have to re-issue CSR or whatever it's called, I don't remember exactly all the procedures, but it's not that difficult anyhow. As per self-signed certificates that you mentioned -- I know what you're saying in that regard. It does look scary in a browser, unless you know 100% what it's about (like if it belongs to you). DEFINITELY I won't even think to show that Freddy Krueger thing to my potential clients! No way, God forbid! "David W. Hodgins" сообщил(а) в новостях следующее:op.x06ic9bua3w0dxdave@hodgins.homeip.net... On Thu, 02 Jul 2015 05:14:18 -0400, papakota <abrodski@hotmail.com> wrote: > I have a web site that has HTTPS. Right now I DO NOT have SSL certificate > installed on hosting. They charge extra for that. I want to transfer my > site > to a localhost and then to install SSL on Apache myself. So I wonder > whether > I should pay them and have them SSL certificate installed on a hosting > server and after that to copy to site to a localhost OR to leave it alone > as > it is now and just install SSL on Apache from scratch myself. > I ALREADY have SSL certificate installed as it was PRIOR to my termination > of my previous hosting account (when that archive ZIP file was originally A certificate is only good for the domain and hostnames it's been set up for. While you could generate your own certificate, no browser would trust it without the user approving it. A certificate generated for one domain or host can not be used on another host, without the users getting the warning that the hostname does not match the certificate name. Regards, Dave Hodgins -- Change nomail.afraid.org to ody.ca to reply by email. (nomail.afraid.org has been set up specifically for use in usenet. Feel free to use it yourself.) --- Это сообщение проверено на вирусы антивирусом Avast. https://www.avast.com/antivirus --- news://freenews.netfront.net/ - complaints: news@netfront.net ---
[toc] | [prev] | [next] | [standalone]
| From | "papakota" <abrodski@hotmail.com> |
|---|---|
| Date | 2015-07-03 15:06 +0300 |
| Message-ID | <mn5tt0$nsl$1@adenine.netfront.net> |
| In reply to | #3410 |
Thanks a lot for your reply! I think I might haven't made myself clear enough. The domain the cert is for remains THE SAME -- regardless whether it's installed in a hosting environment or on my local machine at home. As per hostnames, here I don't know what you meant exactly. I think that when a CA issues a certificate, you can install it on ANY server (at least, Apache, for sure). The cert is not tied to a specific box, right? Maximum, I might have to re-issue CSR or whatever it's called, I don't remember exactly all the procedures, but it's not that difficult anyhow. As per self-signed certificates that you mentioned -- I know what you're saying in that regard. It does look scary in a browser, unless you know 100% what it's about (like if it belongs to you). DEFINITELY I won't even think to show that Freddy Krueger thing to my potential clients! No way, God forbid! "David W. Hodgins" сообщил(а) в новостях следующее:op.x06ic9bua3w0dxdave@hodgins.homeip.net... On Thu, 02 Jul 2015 05:14:18 -0400, papakota <abrodski@hotmail.com> wrote: > I have a web site that has HTTPS. Right now I DO NOT have SSL certificate > installed on hosting. They charge extra for that. I want to transfer my > site > to a localhost and then to install SSL on Apache myself. So I wonder > whether > I should pay them and have them SSL certificate installed on a hosting > server and after that to copy to site to a localhost OR to leave it alone > as > it is now and just install SSL on Apache from scratch myself. > I ALREADY have SSL certificate installed as it was PRIOR to my termination > of my previous hosting account (when that archive ZIP file was originally A certificate is only good for the domain and hostnames it's been set up for. While you could generate your own certificate, no browser would trust it without the user approving it. A certificate generated for one domain or host can not be used on another host, without the users getting the warning that the hostname does not match the certificate name. Regards, Dave Hodgins -- Change nomail.afraid.org to ody.ca to reply by email. (nomail.afraid.org has been set up specifically for use in usenet. Feel free to use it yourself.) --- Это сообщение проверено на вирусы антивирусом Avast. https://www.avast.com/antivirus --- news://freenews.netfront.net/ - complaints: news@netfront.net ---
[toc] | [prev] | [next] | [standalone]
| From | "papakota" <abrodski@hotmail.com> |
|---|---|
| Date | 2015-07-03 15:07 +0300 |
| Message-ID | <mn5u01$nt6$1@adenine.netfront.net> |
| In reply to | #3409 |
Thanks a lot for your reply! I think I might haven't made myself clear enough. The domain the cert is for remains THE SAME -- regardless whether it's installed in a hosting environment or on my local machine at home. As per hostnames, here I don't know what you meant exactly. I think that when a CA issues a certificate, you can install it on ANY server (at least, Apache, for sure). The cert is not tied to a specific box, right? Maximum, I might have to re-issue CSR or whatever it's called, I don't remember exactly all the procedures, but it's not that difficult anyhow. As per self-signed certificates that you mentioned -- I know what you're saying in that regard. It does look scary in a browser, unless you know 100% what it's about (like if it belongs to you). DEFINITELY I won't even think to show that Freddy Krueger thing to my potential clients! No way, God forbid! "papakota" сообщил(а) в новостях следующее:mn2vfl$uuh$1@adenine.netfront.net... Hello! I have a web site that has HTTPS. Right now I DO NOT have SSL certificate installed on hosting. They charge extra for that. I want to transfer my site to a localhost and then to install SSL on Apache myself. So I wonder whether I should pay them and have them SSL certificate installed on a hosting server and after that to copy to site to a localhost OR to leave it alone as it is now and just install SSL on Apache from scratch myself. I ALREADY have SSL certificate installed as it was PRIOR to my termination of my previous hosting account (when that archive ZIP file was originally created). It's already there files-wise, just not installed yet on my new (current) hosting server. And though I don't feel like wasting $25 for their job to install SSL's (I've got 2, but they charge for a bulk of an extra 10+1 free that comes with the hosting plan = 11 SSL's alltogether), money is not a critical point here. What is critical is the EASY path for me to get the job done. I'm not a big expert when it comes to system administration and Apache. And I'm a complete novice in Linux (I use W7/Ubuntu 14.04 Desktop edition dual-boot box). --- Это сообщение проверено на вирусы антивирусом Avast. https://www.avast.com/antivirus --- news://freenews.netfront.net/ - complaints: news@netfront.net --- --- Это сообщение проверено на вирусы антивирусом Avast. https://www.avast.com/antivirus --- news://freenews.netfront.net/ - complaints: news@netfront.net ---
[toc] | [prev] | [standalone]
Back to top | Article view | comp.os.linux.networking
csiph-web