News for hackers. Stuff that matters.
Re:Let's Encrypt is 10 years old now by dachris on Wednesday November 20, 2024 @02:55AM (#42191676)
There's still enough people out there who don't know better, manually (or auto-renew) purchasing new a certificate every year from their hosting provider like it's 2013.
Re:Let's Encrypt is 10 years old now by karel-3d on Wednesday November 20, 2024 @03:54AM (#42191976)
I have dealt with banking environment when they required SSL with at least 1-year validity on the callback API URL. Which excluded Let's Encrypt.

We were looking for a SSL provider that had > 1 year old certs AND supported ACME... for some reason we ended up with SSL.com that did support ACME for longer lasting certs; however, there was some minor incompatibilities in how kubernetes cert-manager implemented ACME and how SSL.com implemented ACME; we ended up debugging SSL.com ACME protocol implementation.

Fun. We should have just clicked once per 3 years, better than debugging third parties APIs.

No, I don't remember the details and they are all lost in my old work emails.

(Nowadays I think zerossl.com also supports ACME for >1 year certs? but they did not back then. edit: no they still don't, it's just SSL.com I think)

Re:Let's Encrypt is 10 years old now by JoshTriplett on Wednesday November 20, 2024 @04:12AM (#42192077)
> I have dealt with banking environment when they required SSL with at least 1-year validity on the callback API URL. Which excluded Let's Encrypt.

I wonder if this would be an opportunity for revenue for Let's Encrypt? "We do 90-day automated-renewal certificates for free for everyone. If you're in an unusual environment where you need certificates with longer validity, we offer paid services you can use."

Re:Let's Encrypt is 10 years old now by account42 on Wednesday November 20, 2024 @04:37AM (#42192215)
Probably better to keep LE / ISRG completely non-profit. Adding a profit motive has too big of a chance to end with actually security-relevant features being gated behind payment eventually.
Re:Let's Encrypt is 10 years old now by JoshTriplett on Wednesday November 20, 2024 @05:26AM (#42192523)
It's less about the profit motive, and more about removing the remaining incentives to stay outside the ACME ecosystem. The funding would be to provide additional infrastructure (e.g. revocation servers for longer-lasting certificates), and to fund new such efforts.
Re:Let's Encrypt is 10 years old now by account42 on Wednesday November 20, 2024 @05:36AM (#42192587)
But once there is an income stream from issuing certificates there is an incentive to increase it which will quickly find itself at odds with the primary missions of providing secure connections to as many people as possible. Making infrastructure depend on that income stream only increases that incentive. Perhaps you trust the ISRG to resist the temptaton but as far as I know they are run by humans.
Re:Let's Encrypt is 10 years old now by JoshTriplett on Wednesday November 20, 2024 @06:57AM (#42193063)
There are many, many opportunities in both the business and non-profit world to make more money by screwing your customers/users, and despite that, it does not always happen. Businesses and non-profits are built on the trust of users (or built in spite of the utter lack of it, e.g. Comcast). I don't think they should be afraid to provide things users need. It is, in fact, possible to choose and keep choosing to maintain the trust of your users.

I think there's still incentive alignment here. Getting people moved from the "purchase 1 year certificate" world (which is apparently still required in some financial contexts) into the ACME-based world provides a path for making a regulatory argument that it'd be easy for such entities to switch over to shorter-lived certificates because the ACME infrastructure is right there.

Re:Let's Encrypt is 10 years old now by karel-3d on Wednesday November 20, 2024 @05:23AM (#42192496)
If they want to do something commercial, they should go for the code signing certificates, that stuff is still a racket.
Re:Let's Encrypt is 10 years old now by Nekit1234007 on Wednesday November 20, 2024 @07:10AM (#42193166)
I'm pretty sure ISRG doesn't want to deal with payments any more than they do now (i.e. outside of donations and sponsorships)
Re:Let's Encrypt is 10 years old now by lol768 on Wednesday November 20, 2024 @04:21AM (#42192133)
> I have dealt with banking environment when they required SSL with at least 1-year validity on the callback API URL

Why are (some) banks always completely clueless about these things? Validating ownership of the domain more often (and with an entirely automated provisioning set-up that has no human weak links) can only be a good thing.

Perhaps the banking sector will finally enter the 21st century in another ten years?

Re:Let's Encrypt is 10 years old now by karel-3d on Wednesday November 20, 2024 @05:21AM (#42192487)
The banking sector usually goes with "checkbox security".

They have these really, really long lists what all needs to be secured and how. Some of it is reasonable, some of it is bonkers, there is way too much of that stuff, and it overall increases the price of any solution 10x at least.

But OTOH I can hardly blame them, failures can be catastrophic there, as they deal with real money directly and can be held liable for failures. So they don't really care about security, and more about covering their asses.

Re:Let's Encrypt is 10 years old now by dspillett on Wednesday November 20, 2024 @06:36AM (#42192910)
> some of it is bonkers

Some of it is truly bonkers and never was good practise, but much of the irritating stuff is simply out-of-date advice. The banks tend to be very slow to change unless something happens that affects (or directly threatens to affect) the bottom line, or puts them in the news unfavourably.

Of course some of it is bonkers, like HSBC and FirstDirect changing the auth for my personal accounts from “up to 9 case-sensitive alpha-numeric characters” (already considered bad practise for some years) to “6 digits”, and assuring me that this is just as secure as before…

Re:Let's Encrypt is 10 years old now by dizhn on Wednesday November 20, 2024 @06:47AM (#42192988)
That sounds like "we were truncating your id and pass before anyway".
Re:Let's Encrypt is 10 years old now by dspillett on Wednesday November 20, 2024 @07:25AM (#42193303)
I don't think so, because it would also imply they were also throwing away anything non-numeric, and I really hope nothing that stupid was going on. When the change happened everyone had to establish a new password.

I read it as “we have been asked to integrate an ancient system that we can't update (or more honestly in many cases: can't get the higher-ups to agree to pay to update), so are bringing out other systems down to the lowest common denominator”. That sort of thing happens too often when two organisations (or departments within one) that have different procedures, merge or otherwise start sharing resources they didn't previously.

Re:Let's Encrypt is 10 years old now by BrandoElFollito on Wednesday November 20, 2024 @04:02PM (#42198073)
I won't go into the idiocies banks implement. They usually have to because totally incompetent people tell them they have to.

One of the practices was pathetic to the point of being funny: you had to input specific characters of your password (2nd, 4th, 6th, etc - this was changing at each login) AND there was a short timeout. My children probably learned a few new words when I was logging in.

Re:Let's Encrypt is 10 years old now by jjeaff on Thursday November 21, 2024 @06:52AM (#42203392)
I suppose the purpose of that was to signal to hackers that they ARE in fact storing all passwords in plaintext?
Re:Let's Encrypt is 10 years old now by BrandoElFollito on Thursday November 21, 2024 @07:20AM (#42203599)
It is very likely, yes. After a year or so of this practice (people were writing down their password with digits under the letters to quickly match the request) the bank said that they now propose two "secure login forms" - the older one and a new, normal one.

Some time later they silently removed the first one.

Re:Let's Encrypt is 10 years old now by Apfel on Thursday November 21, 2024 @09:31AM (#42204638)
Tsb bank in the UK still do exactly this
Re:Let's Encrypt is 10 years old now by Veen on Wednesday November 20, 2024 @05:03AM (#42192383)
The problem is more likely one of regulation than technical knowledge. Banks hire very smart people who know that a lot of what they do is bullshit, but they're paid to comply with banking and security regulations that lag a long way behind technical advances. Banks are also inherently conservative in their technical choices, and for good reason.
Re:Let's Encrypt is 10 years old now by merb on Wednesday November 20, 2024 @03:40PM (#42197885)
Globalsign and digicert have acme support.
Re:Let's Encrypt is 10 years old now by karel-3d on Thursday November 21, 2024 @12:45AM (#42201487)
Hm, I have no idea why we didn't pick tgem back then. I see it now. Maybe it was too expensive? I don't remember the reasoning at this point
Re:Let's Encrypt is 10 years old now by mrtksn on Wednesday November 20, 2024 @03:04AM (#42191711)
AFAIK there's things like Extended Validation Certificate Verification that used to make the browser address bar look more trustworthy by making it green but I don't know if its still a thing. At least in Safari, I don't see a green padlock anywhere.
Re:Let's Encrypt is 10 years old now by Propelloni on Wednesday November 20, 2024 @03:40AM (#42191904)
They are still there, but most browsers don't do anything with it anymore since 2019, when Firefox and Chrome stopped caring.

There are some scenarios where you still have to employ EV certificates, e.g. code signing.

Re:Let's Encrypt is 10 years old now by mrweasel on Wednesday November 20, 2024 @03:21AM (#42191791)
I remember our boss really wanted that green bar, so we got an extend validation certificate. What we had failed to realise is that they would only be issued to the actual legal name of your company, but not any other names you may be operating under. We had a B2C webshop, where we wanted the ev-cert, but because the B2C side of the business wasn't it's own legal entity, the cert we go issued was for our B2B name, which none of our customer customers knew and it looked like a scam.

The only good thing dealing with certificate resellers at the time was that they where really flexible in a lot of ways. We got our EV cert refunded, or "store credit" and used the money to buy normal certificates.

Re:Let's Encrypt is 10 years old now by bux93 on Wednesday November 20, 2024 @03:34AM (#42191856)
Chrome 77 removed the prominent green EV badge. "A series of academic research in the 2000s studied the EV UI in lab and survey settings, and found that the EV UI was not protecting against phishing attacks as intended. The Chrome Security UX team recently published a study that updated these findings with a large-scale field experiment, as well as a series of survey experiments." [1]

Extended Validation can still play a role in a corporate's IT control framework; the extended validation is essentially a check-of-paperwork that then doesn't need to be performed by your own auditor. Some EV certificates also come with some (probably completely useless) liability insurance.

[1] https://chromium.googlesource.com/chromium/src/%2B/HEAD/docs...

Re:Let's Encrypt is 10 years old now by duskwuff on Wednesday November 20, 2024 @03:55AM (#42191981)
> Some EV certificates also come with some (probably completely useless) liability insurance.

Warranties / insurance on SSL certificates typically only pay out if a certificate is issued improperly, often in conjunction with other conditions like a financial loss directly resulting from the misissuance. Realistically, any screwup serious enough to result in that warranty paying out would also result in the CA being abruptly removed from browser root certificate programs.

Re:Let's Encrypt is 10 years old now by uid65534 on Wednesday November 20, 2024 @02:57PM (#42197508)
Ah yes, I too remember when COMODO was ripped out of browsers in 2011 when it came to light they gave sign-anything rights to a bunch of resellers, one of whom was hacked. And then again in 2016.

And another fun one unrelated to signing was when they tried to trademark "Let's Encrypt" in 2015.

But yes, it is not a common issue and effort would be better focused on improving site security in other ways. (unlike the rest of my comment, this line isn't sarcasm.)

Re:Let's Encrypt is 10 years old now by Systemmanic on Wednesday November 20, 2024 @03:16AM (#42191763)
Re:Let's Encrypt is 10 years old now by _betty_ on Wednesday November 20, 2024 @04:02AM (#42192021)
they were also pretty bad for performance due to the extra lookup (and reduction in caching)
Re:Let's Encrypt is 10 years old now by account42 on Wednesday November 20, 2024 @04:31AM (#42192187)
What extra lookup. AFAIU they are just like normal certificates but with a "customer paid extra" flag.
Re:Let's Encrypt is 10 years old now by _betty_ on Wednesday November 20, 2024 @04:39AM (#42192233)
Re:Let's Encrypt is 10 years old now by _betty_ on Wednesday November 20, 2024 @04:37AM (#42192216)
they normally require a revocation lookup on the spot, and iirc there was differences in if they could or how stapling worked.
Re:Let's Encrypt is 10 years old now by account42 on Wednesday November 20, 2024 @05:38AM (#42192599)
Interesting. Sounds like a cost that is entirely reasonable for use cases like online banking though.
Re:Let's Encrypt is 10 years old now by sureIy on Wednesday November 20, 2024 @03:16AM (#42191765)
Yeah that also stopped being a thing. I'm really happy how Chrome and then other browsers gradually shifted the blame to insecure websites rather than highlighting "secure" ones.

You'll still find people online clamoring EV certificates are worth anything more than $0 but you can ignore them just as well.

Re:Let's Encrypt is 10 years old now by tannhaeuser on Wednesday November 20, 2024 @04:55AM (#42192314)
Huh? EV certificates are actually certifying you're the (juristical) person you're claiming to be based on ID and trade register checks, unlike Let's Encrypt certificates which only certify you're in possession of a domain. Isn't using EV certificates legally required for e-commerce web sites at least in parts of the world, and also obligatory for rolling out as MasterCard/Visa merchant by their anti-fraud requirements along with vulnerability checks and CI/site update processes being in place?
Re:Let's Encrypt is 10 years old now by khuey on Wednesday November 20, 2024 @05:17AM (#42192466)
> Isn't using EV certificates legally required for e-commerce web sites at least in parts of the world

Not in any jurisdiction I'm aware of, though it's a big world so it wouldn't shock me if some small corner of it has bad laws.

> and also obligatory for rolling out as MasterCard/Visa merchant by their anti-fraud requirements

PCI DSS does not require EV certificates.

Re:Let's Encrypt is 10 years old now by technion on Wednesday November 20, 2024 @03:36AM (#42191872)
I deal with multiple enterprise applications where idea of scripting a renewal involves playing with scripting headless Chrome.

I'm really not a fan of it but I'm happier paying for a one year cert than doing that

Re:Let's Encrypt is 10 years old now by yurishimo on Wednesday November 20, 2024 @03:48AM (#42191950)
Sorry if this is a dumb question, but why? If I'm not mistaken, Let's Encrypt supports validation via DNS now so you don't even need to have a working webserver to issue a certificate. Automating a script to perform a renewal should be much simpler than headless Chrome!

If your DNS provider doesn't have an API, that seems like a separate issue but one that is well worth your organization's time if you're working in the enterprise!

Re:Let's Encrypt is 10 years old now by blipvert on Wednesday November 20, 2024 @04:12AM (#42192076)
You can set up the _acme-challenge (or whatever it is)as a CNAME to point to a domain which does support an API for automating the renewal

(looking in to setting this up for a bunch of domains at work)

Re:Let's Encrypt is 10 years old now by patrakov on Wednesday November 20, 2024 @03:56AM (#42191989)
I guess it is not about renewal but about certificate deployment.
Re:Let's Encrypt is 10 years old now by technion on Wednesday November 20, 2024 @05:42AM (#42192621)
Obtaining a certificate via dns doesn't help you install it via a Web interface that takes 20+ clicks and a 15 minute reboot to apply .
Re:Let's Encrypt is 10 years old now by pastage on Wednesday November 20, 2024 @06:25AM (#42192850)
And open a ticket on a suppliers website, click through four pages with free text input, then send certificate via email.

Lets not talk about key delivery. We will get back the admin cost and of all that in a year if we tunnel them through one of our LBs.

Re:Let's Encrypt is 10 years old now by irjustin on Wednesday November 20, 2024 @03:23AM (#42191800)
Related point - we interface with Singapore gov services (MYINFO).

They don't recognize LE nor AWS's certs. Only the big paid ones. Such an annoying process too - to pay, to obtain and update the certs.

Re:Let's Encrypt is 10 years old now by tialaramex on Wednesday November 20, 2024 @03:33AM (#42191851)
I guess the good thing there is that it's absolutely transparent that this is just a way to make you pay somebody else. Like the Jones Act (Merchant Marine Act, but everybody just calls it the Jones Act). The US government doesn't get a slice if you want to buy ships to move stuff from one part of the US to another, but it does require that you buy the ships from an American shipyard, and so those yards needn't be internationally competitive because the US government has their back.

Nobody is like "Oh, the Jones Act ensures high quality ships" because it doesn't, the Jones Act just ensures that you're going to use those US shipyards, no matter what.

Re:Let's Encrypt is 10 years old now by vmit on Wednesday November 20, 2024 @04:52AM (#42192299)
Myinfo did away with certificate requirement altogether! Yay! (hello from Singapore)
Re:Let's Encrypt is 10 years old now by ta1243 on Wednesday November 20, 2024 @03:28AM (#42191829)
Our company bans the use of letsencrypt because of the legal terms. Nobody at the CxO level will sign off on it, so we end up paying whatever to globalsign.
Re:Let's Encrypt is 10 years old now by seszett on Wednesday November 20, 2024 @03:40AM (#42191898)
What legal terms do they find objectionable?

What about ZeroSSL, which is basically interchangeable with Let's Encrypt?

Re:Let's Encrypt is 10 years old now by yread on Wednesday November 20, 2024 @03:23AM (#42191799)
Unfortunately, the code signing certificates work pretty much the same way
Re:Let's Encrypt is 10 years old now by wink on Wednesday November 20, 2024 @05:41AM (#42192618)
Doesn't necessarily have anything to do with knowing, some environments are just not worth automating or support it so badly that even paying twice or more would still be nothing compared to the annoyance. It's been getting better over the years though.