9 ms·
And meanwhile, Let's Encrypt is on track to offer wildcards at the start of next year (https://letsencrypt.org/2017/07/06/wildcard-certificates-coming-jan-2018.
by JoshTriplett 9y ago
And meanwhile, Let's Encrypt is on track to offer wildcards at the start of next year (https://letsencrypt.org/2017/07/06/wildcard-certificates-coming-jan-2018.html https://letsencrypt.org/2017/07/06/wildcard-certificates-com...), so one of the last reasons to need a non-LE cert is going away.
I used StartCom for years, but LE made it completely obsolete for me. And StartCom seems to have been willing to throw it all away with the WoSign acquisition.
- justinclift 9y agoLets Encrypt seems like a good solution for the https cert side of things. Wish there was an equivalent thing for signing executables. eg for the binaries of our software releases. We'd been using StartCom signing certs (for Win binaries) up until this clusterfk. ;)
- ktta 9y agoThere's always GPG signing.
- justinclift 9y agoTechnically correct, but it solves a different problem. The StartCom signing cert is a solution solving the "big scary warning" problem on Windows for untrusted binaries. GPG signing is suitable for a different group of users. :)
- tonyedgecombe 9y agoDoesn't solve the Windows scary warnings issue.
- khedoros1 9y agoDoes that provide the same integration into Windows that Authenticode does? Plus timestamp, dualsign, and cross-sign?
- deleted 9y ago[deleted]
- ktta 9y ago>Does that provide the same integration into Windows that Authenticode does? Nope
- tonyedgecombe 9y agoIf you are looking for an alternative I've been using KSoftware for years, they are cheap and good.
- justinclift 9y agoWhen I looked into this originally, before choosing StartCom, the KSoftware process was really non-optimal. Just to get a signing certificate I'd need to get my personal id docs signed by a public notary, get those docs to the KSoftware people, and THEN they'd be ok to issue the cert. Whilst not impossible, that's like the process was back in the Stone Age ;) for getting normal https website certs. Obviously went with the StartCom approach instead, which may need to be looked at again if we need to sign packages in the near future. :/
- imron 9y agoI second this recommendation. I've been using them for years too.
- adzm 9y agoSeriously, this has been a problem for the longest time. At one point you could get free ones for open source projects I think, from comodo perhaps? But no longer the case, which is tremendously frustrating.
- dom0 9y agoCERTUM provides AuthentiCode-compliant certificates from about 30 euros (for open-source usage).
- justinclift 9y agoInteresting. I looked at the Certum website a while ago, before choosing StartCom. The page on the Certum website about certs-for-open-source-signing didn't mention AuthentiCode at all. The AuthentiCode compliant certs seem like a different product. If their certs for Open Source projects really are Authenticode compliant, I'd expect that to be front and center on the page about it. It's the one main feature of importance. :)
- yuhong 9y agoStartCom is even part of the KMCS cross-cert list.
- devy 9y agoThere are still a few other reasons of using non-LE certs: extended validation TLS certs (the ones with greenbar + company/entity name), SAN TLS certs, etc.
- pfg 9y agoLet's Encrypt has supported SAN certificates with up to 100 hostnames ever since they launched.
- devy 9y agoYou are right on the SAN cert, my bad.
- byuu 9y agoFor me the last big one is longer-lasting certificates. I'd like a three-year cert like letsencrypt.org uses for their site, instead of the 90-day ones they offer. I much prefer the CA industry practice of, put a meta tag on your frontpage, or add a string to a DNS TXT record, and then download a certificate, then you're done for three years. I understand their security claims (which apparently don't apply to letsencrypt.org), but all CAs offer 2-3 year certs, so it's a feature they have that LE lacks. certbot raises complexities if you're using a managed hosting solution that doesn't have shell access, or the owner of your machine doesn't want you running code on their box, or you have a weird custom web server setup or something. But all the same, I'm not sure that avoiding certbot is worth continuing to pay $40 a year for my wildcard certificate from AlphaSSL. I may switch when mine expires. What I'm even more hopeful for is that prices of wildcard certs from other vendors will drop now that there's a free alternative. I'm super excited that LE are finally offering these for free!
- devy 9y agoI agree that free LE certs disrupt the TLS certificate market pricing and a lot of CAs are probably going to be out of business for that matter.
- 9y ago