ssl certificates

[PEO]

Hi,

 

Just doing some research In to creting my own web hosting buisness. I know its a big crazzy idea and there is lots of competition but I like a challenge.

 

any way I've got 3 diffrent open source control pannel software in mind

 

gplhost

web-cp

syscp

 

I'm a little lost on this ssl certificate thing. would I just need 1 for the hosting site, or 1 for my hosting site pluss additional ssl certificates for the clients sites?

 

can any one point me in the right direction?

 

cheers

[PEO]

bump

[localzuk]

Depends what you intend to offer for clients for secure sites. If you wish to allow them to have ssl certs with their domain (ie https://www.customerdomain.com) then you need one for each domain. If you are just going to allow access to a 'secure area' on your domain (such as https://secure.hostingco.com) with their domain being left standard then you'll only need one for your secure domain.

 

May I say that getting in to the hosting business is hard work - and would require a lot of customers to make enough profit - unless you offers something special.

[SYNACK]

Basically you would need one for your config site and others for each client site that requires ssl.

 

SSL authenticates the address so you would need at least one for every domain name that will handle secured SSL traffic. For example https://secure.buystuff.com would require a different cert than secure.rentstuff.com, if you are using subdomains you can secure everything unter that domain with a wild card cert which covers *.buy.com so secure.buy.com and http://www.buy.com could use the same cert but these are more expensive.

 

A bit corporate but this page may have some answers http://www.verisign.com/ssl/ssl-information-center/how-ssl-security-works/index.html

 

Edit: looks like I was beaten to it whilst typing

[PEO]

Basically you would need one for your config site and others for each client site that requires ssl.

 

SSL authenticates the address so you would need at least one for every domain name that will handle secured SSL traffic. For example https://secure.buystuff.com would require a different cert than secure.rentstuff.com, if you are using subdomains you can secure everything unter that domain with a wild card cert which covers *.buy.com so secure.buy.com and http://www.buy.com could use the same cert but these are more expensive.

 

A bit corporate but this page may have some answers http://www.verisign.com/ssl/ssl-information-center/how-ssl-security-works/index.html

 

Edit: looks like I was beaten to it whilst typing

 

 

aaa yeh wildcard ssl. yeh i was looking at this.

 

I know it will be solid, but i've never been put off by a challenge I will come up with something special.