SSL Certificate

monkeyhead · Post by **monkeyhead** » Thu Oct 30, 2003 10:43 pm

ummm... dont know where to post.

So i got the server... we use for battlefield 1942. And well, its only got one IP. the company says we can have another, but we need to get a SSL Certificate... so i do some web searchin.... and i see these things for websites....

is this what i need? what the heck are they talkin about.

i know SSL makes stuff secure.... but umm... im totally lost....

Faust · Post by **Faust** » Thu Oct 30, 2003 10:45 pm

why don;t you just install another NIC?

monkeyhead · Post by **monkeyhead** » Fri Oct 31, 2003 9:39 pm

no no.... its not our machine....

we pay for it... and can remotely connect to it.....

they told us to get another IP we need this certificate

Stu · Post by **Stu** » Sun Nov 02, 2003 7:56 pm

Certificates aren't tied to IP addresses. So, as long as the server you are adding has the same domain name (same DNS name--for instance http://www.someurl.com), you only need one certificate. Therefore, if you keep the same domain name (you can do this with CNAME records in the DNS your site is managed by) all you need to do is copy the certificate over from the existing machine to the new one. There is one exception to this rule, if your site is virtually hosted, then your certificate will be issued by the ISP/Host using an IP address identifier.

However, unless you are going to be running a secure http server on this machine, I see no need for a certificate issued by a CA (Verisign, Thawte, etc.)--if you need one for SSH or something like that, a self-signed certificate (one you create yourself) is good enough.