4 ms·
Nitpicky: You don't get a key somewhere. You make your own keypair, and send the public key off to be signed. It costs ~$100/year + you need an IP address, co
by klodolph 17y ago
Nitpicky: You don't get a key somewhere. You make your own keypair, and send the public key off to be signed. It costs ~$100/year + you need an IP address, compare that to what I pay for shared hosting ($75/year including domain) and you get your answer.
- lucumo 17y ago> Nitpicky: You don't get a key somewhere. You make your own keypair, and send the public key off to be signed. Precisely the type of details you'd had to figure out. For my current (very rudimentary) understanding of SSL that doesn't matter. Setting it up myself would mean I would have to know such things and more. As for costs: We have several IPs and our hosting costs are about 70 euros/month/server. Still, I wouldn't shell out the 100 bucks per year simply because it's lost money. It doesn't solve any of my problems and my users don't care, or at least seem to not care. I believe that to be the main reason. Users don't care. Tech people care, sometimes. Sometimes a site owner cares (banks etc.), but most of the time no one really cares too much about it. And when you think about it, if nobody cares, is it really a problem?