5 ms·
I'm paying for certificates about as much as for domain names, and it's a small fraction of what I'm paying for hosting. Win XP with non-IE browser supports SN
by pornel 12y ago
I'm paying for certificates about as much as for domain names, and it's a small fraction of what I'm paying for hosting.
Win XP with non-IE browser supports SNI.
- cm2187 12y agoThat's right. I remember that wikipedia was saying all browsers under XP but I just made a test and chrome is compatible. Still I suspect that most users who are still using XP either don't have a choice of browser (locked down corporate environment) or aren't sophisticated enough to worry about changing browser. And XP usage is still shockingly high. The cheapest wildcard certificate I can find is £99 per annum. No matter the security requirements I just do not believe it costs that much to run this service. I suspect that we have a bit of a cartel there.
- michaelt 12y agoThe cheapest wildcard certificate I can find is £99 per annum. Best I can find is [1] which is $61=£36/year, or [2] which is $42=£25/year but with lots of typos on their web page. [1] https://cheapsslsecurity.com/comodo/positivessl-wildcard.html https://cheapsslsecurity.com/comodo/positivessl-wildcard.htm... [2] https://www.ssl2buy.com/cheap-wildcard-ssl-certificates-ads https://www.ssl2buy.com/cheap-wildcard-ssl-certificates-ads
- gaadd33 12y agoAlphaSSL resellers tend to be even cheaper: http://www.garrisonhost.com/ssl-certificates/alphassl.html http://www.garrisonhost.com/ssl-certificates/alphassl.html $45/year (£26.42/year)
- rys 12y agohttps://www.startssl.com/ https://www.startssl.com/ $60 one off payment to be verified, then you can issue unlimited wildcard certs for any and all domains you control. i.e., the certs themselves are free, you just pay for verification.
- darklajid 12y agoI actually started that and stopped midway through. The process was absolutely hostile, the requirements insane and I haven't stripped like that, ever. Plus, it's plain BROKEN (Really? Like, requiring a utility bill for verification? What? Why?). Obviously I didn't finish it (I did send most of my documents but stopped at some point and told them that this is crazy, I don't care anymore), so my advice might be crap. But I would advice everyone to avoid. this. process.
- vacri 12y agoThe process is hostile and the UI confusing at times, but the requirements aren't insane. They're doing what they're supposed to do: verify you are who you say you are and that you're the owner of the domain. Just sending a mail to the webmaster is weak verification (and a SPOF, if nothing else).
- darklajid 12y agoI stand by my original argument. A sane version in this country is PostIdent. It's a way to verify a person & address using the post. Think postman arrives, asks you to pull out your ID and sign something, hits okay. Company knows that you are a real person with the specified name living at that place. They _might_ have access to the number on your national ID afterwards, but I'm not even sure about that one. Have you checked what kind of documents you're to send to a random foreign company for verification? On top of that, the process doesn't WORK internationally. I still don't understand what kind of utility bills you have in Israel (StartSSL) or the US (usually the source for.. things), but mine are different. Plus, what does a random letter in a random language prove? Sending in an ID is understandable - it's a state issued document and protected by law, forging one would be a Bad Idea. A "utility bill"... Well, as I said: Insane. And arbitrary. For the fun of it I looked up the mail exchange. Documents they asked for (* denoting that I sent them): - Mobile bill - Utility bill* (sent a cable provider's bill) - Passport & ID * (I think I provided my driving license as well) The first two documents are absolutely braindead requirements. They certainly don't have the expertise to know all utility providers/mobile network providers on a global level. So I could hand in ANYTHING and it would a) be probably legal (there's no law to prevent me from 'forging' a utility bill.tell ..) and impossible to prove. That is .. unless they call your utility/mobile provider to check the information, which wouldn't work in the first place (data protection laws) unless you IMPERSONATE the person you try to check. Which would be crazy on a different level. In the end they wanted to send me a registered letter by snail mail and I cancelled the whole ordeal. Doing that would've been an option of course, but not after they asked for random documents proving my address. EITHER send me a registered letter OR ask for crazy stuff that contains my name and address in the header. Plus, transparency. This whole process took a while and was a lot of "Now please send this", "We really need that", "Since you have no mobile bill to offer, we fall back to snail mails". I discovered this in painful mails, after handing over enough of my data to do mostly anything in my name. I fail to understand how this process could be acceptable and I certainly consider it broken, hostile and inefficient. (Handing in my utility bill was difficult as well - I blacked out all but the letter head, which caused them to complain again and again. Ignoring that the letter contained the SIP credentials for my landlines, what the..? I cannot _invent_ a reason for this requirement. My creativity is too limited, it seems)
- pornel 12y agoWhen you get a domain from gandi.net it's £11 (otherwise £31). You can get $9 certs from namecheap: https://www.namecheap.com/security/ssl-certificates/comodo.aspx https://www.namecheap.com/security/ssl-certificates/comodo.a...
- thesimon 12y agohttps://www.gogetssl.com/wildcard-ssl-certificates/comodo-positive-ssl-wildcard/ https://www.gogetssl.com/wildcard-ssl-certificates/comodo-po... 76 USD/year which is about 45GBP per annum.
- cnst 12y agoHow many domains you have? If you have 2 domains, and no subdomains, that might as well be the case. If you have more than a couple of domains, certificate costs can go up exponential -- it's 10$/year for a single domain cert, but 50$/domain/year for a multidomain one. I have maybe about a dozen or two of active domains; I cannot afford to have my domain costs go up exponentially all for some thin air.
- kijin 12y agoThe cost of SSL certificates scales linearly, not exponentially, with the number of domains. Just buy a certificate for each domain and don't bother with the "multidomain" or "wildcard" rackets. Oh, you need multiple IPv4 addresses for that? Just buy them, SSL is a valid jusstification for consuming IPv4 addresses. It's also a lot cheaper than multidomain certificates. Again, the cost increase is only O(N), not exponential. If it costs you more than $150/year to secure a dozen domains, each with its own IPv4 address, it's not because you're being ripped off, it's because you didn't do your homework. The very fact that some companies can still get away with selling $500 certificates in a purportedly free market implies that most people aren't doing their homeworks.
- cnst 12y agoIPv4 addresses are more like 2 EUR/IPv4/month now -- already more than twice more expensive than the domain names, plus, there is generally a limitation of, say, 8 or 16 addresses per non-enterprise hosting accounts. And these prices will only go up in the future! Plus, are you suggesting that I even get separate certificates (and IPs!) for subdomains? Because I don't actually have to pay anything for my own subdomains to anyone! (Other than the https certificate companies, apparently.) Plus, having to manually re-install all of these certificates every year? No, thanks! Fix it first! I don't have to re-install my STARTTLS in SMTP, noone gets any self-signed warnings, yet all my email is still immune from passive eavesdropping or any kind of passive tapping of the traffic.
- kijin 12y agoI was just trying to point out that the cost increases linearly and nowhere near $50/domain/yr. Besides, it was your choice to get a dozen different domains and create a bunch of subdomains on them, instead of, say, subdirectories. You should have been fully aware of the costs and limitations of existing protocols and market conditions when you did that. It's also entirely your choice whether or not to support non-SNI clients. Some of us stopped supporting IE8/XP a long time ago, some of us keep supporting it at a significant cost (often many thousands of dollars). Either way, it's your choice. Every choice has pros and cons to it. No use complaining about it because you happened to choose a less widely supported and more costly option. Hell, I'd love to get a thousand different domains and an entire /20 for personal use. Why should I pay $10K/yr for my preferences? If you don't want to pay for overpriced certificates on your gazillion subdomains, just don't. Consolidate your domains and subdomains, or at least consolidate the parts that need SSL. It's as simple as that. If nobody ever fell for the wildcard and/or multidomain certificate racket, CAs would have to price their products more competitively. Stop whining and start voting with your wallet, it's the only vote that matters.