News for hackers. Stuff that matters.
Re:Defending Our Brand by CommanderData on Thursday June 23, 2016 @10:39AM (#11961198)
Learning this, I will not renew my certs with Comodo. This is childish behaviour on Comodos part.

If it helps I'll advise any companies I consult to do the same until this changes. Money is the only thing this company will understand.

Re:Defending Our Brand by distances on Thursday June 23, 2016 @10:41AM (#11961219)
I agree. I have an existing cert from Comodo for my personal site, as they were cheap and easy to get when I was looking for one. I will look for another provider when it's time to renew.
Re:Defending Our Brand by nik736 on Thursday June 23, 2016 @10:54AM (#11961356)
Why are you looking for another provider? Just use Lets Encrypt ;-)
Re:Defending Our Brand by vec on Thursday June 23, 2016 @11:50AM (#11961935)
Let's Encrypt doesn't offer EV certs. Which is reasonable; EV certs can't be automated (and they're a dumb idea anyway), but they're still necessary for some of my sites.
Re:Defending Our Brand by nailer on Thursday June 23, 2016 @12:22PM (#11962214)
> EV certs can't be automated

No entirely, but mostly: seeing as this is my job, I should have some idea. Currently writing a post about how we've used some psych techniques to automate the non-automatable parts which I'll post on HN.

> (and they're a dumb idea anyway)

EV matches identity to public keys. Nothing more, nothing less.

If you need EV, we (https://certsimple.com) specialise in making those background checks far less painless with a bunch of unique tech. This means you get your certificate faster and with a lot less effort on your behalf (and a lot more on ours) during the verification process: https://certsimple.com/about

If a DV cert is fine, go with Let's Encrypt (Hi Richard!), dnsimple (Hi Anthony!) or CloudFlare (Hi John and Filippo!) or Heroku.

Re:Defending Our Brand by Mtinie on Thursday June 23, 2016 @12:57PM (#11962502)
Anecdotally: I fully recommend CertSimple. We used them for an EV cert we needed and not only was it simple to set up the request, but the processing was quick, too!
Re:Defending Our Brand by nailer on Thursday June 23, 2016 @01:07PM (#11962604)
Thanks Ben :^)
Re:Defending Our Brand by sijoe on Friday June 24, 2016 @08:33AM (#11969246)
Quick plug for a company I've used: SSLmate (http://sslmate.com) makes cert purchase (for those whom need this) painless and fast. They use Comodo and Geotrust FWIW. I've had my own pain with Comodo through other resellers, and moved on to sslmate and godaddy. Recently moved my home blog (http://scalability.org) to LE. Work (http://scalableinformatics.com) is using godaddy for now, though thinking hard on using sslmate going forward for it (because ... godaddy).
Re:Defending Our Brand by jakobegger on Thursday June 23, 2016 @05:42PM (#11964508)
I can't find pricing on your website. There's a page called 'pricing' that says I can find pricing on the home page. When I click the link, I find a lot of marketing text, but no pricing.
Re:Defending Our Brand by nailer on Thursday June 23, 2016 @08:11PM (#11965264)
It's right underneath the 'Domain names' box, in to USD / GBP / EUR based on country (which is in turn based on your IP location).
Re:Defending Our Brand by jakobegger on Friday June 24, 2016 @01:07AM (#11966727)
Ok, now I discovered it. Had to put my phone in landscape mode (in portrait mode the website is totally different)

Pricing starts at 220€ per year, in case anyone is interested.

Re:Defending Our Brand by derefr on Thursday June 23, 2016 @01:32PM (#11962850)
(Not to sound like an advertisement, but) I got an email from StartCom the other day, saying that they're moving their StartSSL service to work on a similar policy to Let's Encrypt (which I hope means they're just running an ACME server)—but with the proviso that, since they do have the background-checking infrastructure required for EV "trust verification", they've combined the two.

If I recall, StartSSL sort of hoists their EV identity-verification out into its own step before you actually apply for certs. The identity-verification process costs money (and it can't not; it involves paying real people to do background checks), but any EV certs issued to a verified identity are free.

I think what this will mean is that, if you do an ACME request to StartSSL using an identity they've verified—and for a domain associated with that identity—then the cert in the response will automatically be an EV cert.

This is pretty huge, in that usually EV certs cost a large amount per issuance—whereas a pre-verified ACME-issued cert effectively has zero marginal cost to reissue. Previously, EV certs were usually used only for apex domains, with a secondary DV cert collecting the internal SANs together—because the DV cert had a low (now zero) reissuance cost, while the EV cert cost the full amount each time to get reissued. Now you can just use your EV cert for everything, and alter it as suits you: much simpler.

I hope other CAs adopt the same approach; it's a very good idea. (Pie-in-the-sky thought: maybe one day we'll have the equivalent of the semi-automated KYC service providers that have phone apps to scan drivers' licenses, but for corporations. Then issuing EV certs will just mean an API call.)

Re:Defending Our Brand by pfg on Thursday June 23, 2016 @02:03PM (#11963110)
Unfortunately, it doesn't look like they have plans to use ACME. They do have a public API (StartAPI) for issuance, which is better than nothing, but they definitely missed an opportunity with ACME, IMO. Mainly, being the first CA with OV/EV support that would also benefit from the existing ACME ecosystem (i.e. server auto-configuration).

StartEncrypt, the equivalent of an ACME client for their API, appears to be a closed-source binary blob with no documentation whatsoever (based on what's visible on their product landing page and what's inside the downloaded files).

Re:Defending Our Brand by djsumdog on Thursday June 23, 2016 @02:15PM (#11963176)
...oh but they do. If you're in education and are an InCommon member, you get unlimited EV certs. It's pretty nice as you can add read certs to literally every server in your system and not have to abuse a *. cert. Hell you can even add real certs to every AD machine; no more creating your own CA and installing it via a group policy.

That was back in 2012 when I worked for a University. Good luck getting those certs though. Their web service was so broken and if you ever asked for a 2nd cert it'd revoke the first one (which is great if you use them for e-mail encryption because now you can't read any of your old e-mails :-P .. that was more of an Outlook/GAL issue though).

I really hate that InCommon was using Comodo considering all the shit they've done (like issue Google and Facebook certs to the Iranian government).

Re:Defending Our Brand by JoshTriplett on Thursday June 23, 2016 @01:27PM (#11962795)
> EV certs can't be automated

Not entirely, but Let's Encrypt could partially automate the verification process (e.g. looking up business entities and contacting their registered agent with an authorization code), and then fully automate obtaining a certificate with those verified credentials.

Re:Defending Our Brand by jakobegger on Thursday June 23, 2016 @11:04AM (#11961475)
Lets encrypt certs are only valid for 3 months. In many situations the auto-renewal stuff is inconvenient. Then its easier to just buy a commercial cert that's valid for a few years.
Re:Defending Our Brand by _jomo on Thursday June 23, 2016 @11:09AM (#11961522)
I always use acme-tiny [0] to set up LE certs. You can follow their README to set up everything, including automatic reneweal cronjob in a couple minutes.

0: https://github.com/diafygi/acme-tiny#readme

Re:Defending Our Brand by bradleyjg on Thursday June 23, 2016 @12:17PM (#11962158)
That's not always an option. For example, when I was looking into it for google app engine, I came across these directions: http://blog.seafuj.com/lets-encrypt-on-google-app-engine and http://igorartamonov.com/2015/12/lets-encrypt-ssl-google-app...

That's not so bad if you have to do it once a year or better yet once every two years, but I'm not doing that every 3 months.

There's an issue open to allow for the process to be automated, hopefully by the next time I need to renew it'll be available. But as it stands today I went with a paid certificate.

Re:Defending Our Brand by newman314 on Thursday June 23, 2016 @01:13PM (#11962664)
+1

I was just looking at doing this last night for two sites and came to the conclusion that it was too painful.

Far too many products still require manual intervention which is a huge bummer. Synology, VMware, ddwrt etc.

OTOH, lego with Cloudflare DNS challenge proved to be very easy to use with a single command.

Re:Defending Our Brand by bouk on Thursday June 23, 2016 @12:59PM (#11962529)
I know this doesn't help you, but the best fix for this would be for App Engine to implement letsencrypt support directly, so they can automatically provision and renew certificates for anyone that uses app engine
Re:Defending Our Brand by Ajedi32 on Thursday June 23, 2016 @05:10PM (#11964330)
Re:Defending Our Brand by distances on Thursday June 23, 2016 @11:11AM (#11961548)
The Comodo cert was for 5 years at a total of $25 IIRC. I didn't consider that bad at all, especially as that was add-and-forget.

Of course that's still like a money printing machine, and wildcards and greenbars are much more. But the deal was pretty fine for my personal domain. To be frank, I would probably have renewed with them.

Re:Defending Our Brand by davidgerard on Thursday June 23, 2016 @12:34PM (#11962308)
The whole idea is to motivate you to automate the process as far as possible. This is basically a good idea. It's a faff for us at present 'cos we don't have direct access to our load balancers at this moment (just switched hosting), but we're working on that.
Re:Defending Our Brand by distances on Thursday June 23, 2016 @11:08AM (#11961511)
That counts as a provider too, and a likely one at that.
Re:Defending Our Brand by nikcub on Thursday June 23, 2016 @12:19PM (#11962189)
I've avoided the big issuers for a while now. Big plug for Digicert who are excellent - they're independent (so not conflicted), have great infrastructure (fastest on OSCP), super support and active in pushing standards such as CT, short-lived certs, and adopting .onion support after internal names were deprecated.

I use LetsEncrypt in most cases (and have companies I work with donate a portion of what they used to spend) and then DigiCert for EV SAN.

Re:Defending Our Brand by knet on Thursday June 23, 2016 @12:35PM (#11962320)
+1 for Digicert, awesome service. I'm definitely looking at letsencrypt for our next project.
Re:Defending Our Brand by mpclark on Thursday June 23, 2016 @10:47AM (#11961263)
Turns out I have a Comodo cert expiring soon. Let's see if they do the right thing before I do...
Re:Defending Our Brand by icebraining on Thursday June 23, 2016 @11:04AM (#11961474)
They already refused to back down, even after requests from Let's Encrypt lawyers. Backpedalling now in response to the PR crisis would not be enough, in my opinion. I'd only consider them again if they were to make a decent donation to Let's Encrypt.
Re:Defending Our Brand by lucb1e on Thursday June 23, 2016 @01:30PM (#11962826)
I had a Comodo cert expiring in a year or so, but still went with Let's Encrypt since I was setting it up for other domains.
Re:Defending Our Brand by mpclark on Friday June 24, 2016 @06:31PM (#11974001)
Well, colour me impressed. Looks like they have indeed done the right thing. Fair's fair, I'm going to go ahead and renew my Comodo cert.
Re:Defending Our Brand by waterphone on Thursday June 23, 2016 @08:01PM (#11965223)
I had one just about to expire, and this was my motivation to switch over to Let's Encrypt.
Re:Defending Our Brand by danra on Thursday June 23, 2016 @11:17AM (#11961611)
I've avoided buying a code signing certificate from Comodo just because of their reputation, even though they offered the cheapest price.

To me, this behavior reinforces that that was the right decision.

Re:Defending Our Brand by johansch on Thursday June 23, 2016 @12:31PM (#11962276)
It's quite a bit more than being childish. They're basically saying F U to the security community and to people who want a secure Internet.

How is this company still alive after their numerous security breaches/issue (https://en.wikipedia.org/wiki/Comodo_Group#Controversies) and then on top of those, this thing? They need to go out of business.

Re:Defending Our Brand by rhizome on Thursday June 23, 2016 @03:13PM (#11963638)
It's troubling that an ostensibly security-oriented company would seek to muddy the waters like this and reduce the reliability and integrity of the marketplace.
Re:Defending Our Brand by devy on Thursday June 23, 2016 @11:41AM (#11961850)
I am on LetsEncrypt's side to defend their branding. However, Comodo's intent is understandably clear: you take away my business by giving away free certs I screw you in your branding. (not that I agree with this tactic.)
Re:Defending Our Brand by Joeri on Thursday June 23, 2016 @12:55PM (#11962473)
It's a bit like a buggy whip manufacturer registering a trademark on the word 'ford' at the introduction of the model T. Understandable, but not permissible.
Re:Defending Our Brand by rhizome on Thursday June 23, 2016 @03:11PM (#11963622)
They're both bad faith registrations, "understandable" doesn't enter into it.
Re:Defending Our Brand by jonlucc on Thursday June 23, 2016 @11:01AM (#11961452)
Just curious, but do you think companies you consult care enough to switch? It's usually easier to just renew, and I wonder if consultants have the leverage to get customers to care.
Re:Defending Our Brand by JoshTriplett on Thursday June 23, 2016 @01:29PM (#11962811)
It'd be easy to make a case that Comodo is no longer trustworthy, pointing to several of their past actions, and recommending a switch to a safer provider. If the consultant does the work to make the switch happen, and the cost doesn't increase, I doubt the customer would object.
Re:Defending Our Brand by CommanderData on Thursday June 23, 2016 @07:15PM (#11965010)
They couldn't care if I mentioned it and I don't plan to. Renewals often involve just as much work as installing a new cert. This is more about personal recommendations, after I recommend its normally accepted without question.
Re:Defending Our Brand by eximius on Thursday June 23, 2016 @01:17PM (#11962708)
Is it easier? How automated can you make renewal with Comodo? Even big companies goof and have a few hours of downtime where their cert expired. With Let's Encrypt, you make it not a human's error anymore.
Re:Defending Our Brand by davidgerard on Thursday June 23, 2016 @12:37PM (#11962330)
We buy EV certs for those sites where the business unit and/or marketing demands it, but otherwise we just use Let's Encrypt. (Small publisher with some paid info sites.)
Re:Defending Our Brand by ultramancool on Thursday June 23, 2016 @10:57AM (#11961400)
Yeah, the only reason to use them was that they were cheap and now AlphaSSL's resellers are cheaper anyways, $40 wildcards are hard to argue with. Heck, I paid $100 for 3 years on renewal.
Re:Defending Our Brand by sandGorgon on Thursday June 23, 2016 @03:36PM (#11963771)
go with rapidssl - because we use docker and bake our certificates into our vms, we find it hard to use letsencrypt. but we have been very happy with rapidssl (even using it on our apis that serve legacy android devices)