frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Show HN: Bowbuilds, a configurator and tuning toolkit for compound archers

https://bowbuilds.com
1•whereismyreleas•2m ago•0 comments

Could Lovable's automatic 10% pay raise be the cure for toxic cultures?

https://techcrunch.com/2026/05/07/could-lovables-automatic-10-pay-raise-be-the-cure-for-toxic-cul...
1•doener•3m ago•0 comments

The Matrix Conference

https://conference.matrix.org/
1•doener•4m ago•0 comments

Feeding the Machine

https://www.theverge.com/cs/features/831818/ai-mercor-handshake-scale-surge-staffing-companies
1•amai•5m ago•0 comments

UFO Files Released by U.S. Shed Light on What the Government Knows

https://www.nytimes.com/2026/05/08/us/politics/ufo-sightings-us-government.html
1•quapster•5m ago•0 comments

Tell HN: Prayer with AI models is suboptimal

1•3pt14159•6m ago•0 comments

Show HN: I built a translator for SPANGLISH and mixed-language text

https://spanglishtranslator.net
1•Odeh13•6m ago•0 comments

Flatcar Container Linux – container optimized, immutable fs, config provisioning

https://www.flatcar.org/
1•gessha•8m ago•0 comments

Gulp – We have been made aware of a potential incident and are shutting down all

https://old.reddit.com/r/letsencrypt/comments/1t7ifve/gulp_we_have_been_made_aware_of_a_potential/
1•newsoftheday•8m ago•0 comments

NTFS-recover – NTFS data recovery when the MFT is corrupted

https://github.com/mjgil/rust-ntfs-recover
1•mjgil•10m ago•0 comments

Open TCP Connection in the Browser

https://developer.puter.com/networking/
1•ent101•10m ago•0 comments

1 in 277 PubMed-indexed 2026 papers shows fabricated references, says analysis

https://retractionwatch.com/2026/05/07/one-in-277-pubmed-indexed-papers-in-2026-shows-fabricated-...
1•bookofjoe•12m ago•1 comments

ShowHN: Guantr - Type-Safe JavaScript/TS Authorization Library; Major v2 Release

https://github.com/Hrdtr/guantr
1•hrdtr•14m ago•0 comments

Show HN: Cyoda-go – application platform in Go without the Temporal/Kafka glue

https://github.com/Cyoda-platform/cyoda-go
1•physix•15m ago•0 comments

DHCoin

https://github.com/StoyanDenev/decentralized-message-queue/
1•expeler•16m ago•0 comments

Fabricated citations: an audit across 2·5M biomedical papers

https://www.thelancet.com/journals/lancet/article/PIIS0140-6736(26)00603-3/fulltext
3•ep_jhu•18m ago•0 comments

Fifteen Portugese police officers detained in torture investigation

https://www.bbc.com/news/articles/c0r2zq9wg9xo
2•lastdong•18m ago•0 comments

Engineering Intelligence from Autocomplete

https://www.szia.ai/post/engineer-intelligence-from-autocomplete
1•mszel•19m ago•0 comments

Certificate Issuance through Let's Encrypt unavailable

https://www.cloudflarestatus.com/incidents/z3vgxxfvt3yb
1•hosteur•20m ago•0 comments

Why technology made the world richer and rich countries feel poorer

https://aesium22.substack.com/p/the-two-speed-economy
2•-__hn__-•20m ago•0 comments

The American, Intense World of High-School Debate

https://www.newyorker.com/magazine/2026/05/11/the-very-american-very-intense-world-of-high-school...
1•limitedfrom•20m ago•0 comments

AI's Big Messaging Pivot

https://www.noahpinion.blog/p/ais-big-messaging-pivot
1•paulpauper•21m ago•0 comments

Could development economics be more useful?

https://www.noahpinion.blog/p/could-development-economics-be-more
1•paulpauper•22m ago•0 comments

A simple point about diversification

https://marginalrevolution.com/marginalrevolution/2026/05/a-simple-point-about-diversification.html
1•paulpauper•23m ago•0 comments

Dirty Frag: Universal Linux LPE

https://github.com/V4bel/dirtyfrag
3•unbeli•23m ago•0 comments

Digg Is Back (Again)

3•basket278•25m ago•0 comments

NocTUI – Lightweight C Library for Building Terminal User Interfaces (TUIs)

https://github.com/UsboKirishima/noctui
2•333revenge•26m ago•0 comments

Real-Time Vibrotactile Stimulation and Inter-Brain Connectivity in Partner Dance

https://dl.acm.org/doi/10.1145/3731459.3773332
1•bookofjoe•26m ago•0 comments

Arena Physica

https://www.arenaphysica.com
1•skogstokig•27m ago•0 comments

Notes on Tanya M. Luhrmann's Book 'How God Becomes Real'

https://michaelnotebook.com/luhrmann/index.html
1•benbreen•28m ago•0 comments
Open in hackernews

Let’s Encrypt – Stopping Issuance for Potential Incident

https://letsencrypt.status.io/pages/incident/55957a99e800baa4470002da/69fe2d6698ca07050eb4b1b3
114•rbaudibert•1h ago

Comments

esseph•1h ago
Some other internet things going on to Discord, Cloudflare, and others.

Unsure if related in any way.

noplacelikehome•1h ago
Here's hoping it's not another security nightmare...
mcherm•57m ago
There is one little-discussed down side to ever shorter-lived certificates...
Analemma_•55m ago
Only if you’re reissuing right before expiration, which is a stupid thing to do. If you have a 47-day cert, best practice is to reissue on day 30, meaning LE would need to be down for more than two weeks before anything went wrong.

If this outage breaks your system, that’s entirely on you, not Let’s Encrypt.

rconti•53m ago
You're holding your 6-day cert wrong
cachius•49m ago
Thought that was the iPhone 6
bakies•48m ago
Chill, it's 2 hours. They recommend renewing at the first third of the 160 hrs.
gbear605•51m ago
Only as long as LE isn’t down for 17 days, then we’re in big trouble.
eqvinox•51m ago
Short-lived = 6 days. Even if you reissue after 2 or 3 days, that's… not a lot of breathing room.
bakies•47m ago
3-4 days is a ton of breathing room
striking•46m ago
You have to opt in, and they are honest about the tradeoffs when discussing them:

> Short-lived certificates are opt-in and we have no plan to make them the default at this time. Subscribers that have fully automated their renewal process should be able to switch to short-lived certificates easily if they wish, but we understand that not everyone is in that position and generally comfortable with this significantly shorter lifetime. We hope that over time everyone moves to automated solutions and we can demonstrate that short-lived certificates work well.

https://letsencrypt.org/2026/01/15/6day-and-ip-general-avail...

eqvinox•42m ago
That's not really an answer, especially with:

> We hope that over time everyone moves to automated solutions and we can demonstrate that short-lived certificates work well.

They're expressly trying to show that this is a viable approach. It's actually kinda good that this outage, whatever it is, is happening now, as it's giving them a chance to demonstrate (or not) that they can deliver.

nottorp•32m ago
> no plan to make them the default at this time

At this time! Boil the frog slowly...

jameshart•49m ago
Useful context: https://letsencrypt.org/2026/01/15/6day-and-ip-general-avail...
jldugger•43m ago
What people are responding to is a slippery slope. Before LE, most certs lasted years. LE started with 90 days, and now cuts to 45, but it's hard to see the logic that stops it from sliding to 15, or even 24 hours.
devrand•49m ago
If you're using ACME to handle certificate rotation, can't you just configure multiple providers?
dizhn•45m ago
Letsencrypt is not the only acme authority. ZeroSSL is the other popular one. There are others.
mark_round•57m ago
That's really not good. Fortunately I'm not using any short-lived certificates like the recently announced 6 day certs, so have some breathing room. Without further details, I'd imagine anyone with a short-lived cert is getting a bit sweaty right now.

Let's Encrypt has become one of those pieces of critical Internet infrastructure that just quietly hums away in the background, the fact that they've stopped ALL issuance is deeply concerning.

walrus01•53m ago
Considering the open source nature of Letsencrypt, I wonder what the barriers/costs would be (theoretically) to a wealthy benefactor who wanted to duplicate its server side infrastructure and a core staffing level of persons, and fund a "parallel" equally trusted, alternative entity with a solid governing board. Same general idea how Acton funded the Signal foundation.

Somewhere that none of the physical infrastructure/hosting environment overlapped with existing Letsencrypt stuff so that the failure of one entity would have zero blast radius affecting the other.

I know there's a long and complicated process to go through to become a trusted root CA and get your CA public cert auto-installed in every OS and browser trust store. Indeed in the early days of letsencrypt I recall their root CA certs were signed by other older root CAs.

dochtman•36m ago
A lot of Let’s Encrypt is not the software but a bunch of auditing and process that ensure compliance and make it legible to the required auditors.
walrus01•31m ago
I understand there's probably a big thorny problem of duplicating the corporate process/policies on the human level that ensure compliance, but is the back-end software pipelining stuff to CT logs not also something that can be replicated? Or is it not part of the server side stuff which has been open sourced?

https://letsencrypt.org/docs/ct-logs/

computer23•26m ago
Google has their own free ACME endpoint: https://pki.goog/
cachius•50m ago
Wonder what incident that even could have been.
Havoc•50m ago
>pieces of critical Internet infrastructure that just quietly hums away in the background,

And donation supported no less

jcims•44m ago
I just find it incredible that in 30+ years the industry hasn't adapted one bit to the brittle failure modes of certificates. I did some subcontract work with Verisign to deploy their CA infrastructure back in the early oughties and it felt like a solution was overdue way back then. I was at Google in the teensies when gmail broke due to expired SMTP certs. WAAAY overdue by then. Here we are, a decade later and it's still the same lol.
packetlost•41m ago
I mean, what's the alternative? I struggle to come up with a solution that doesn't boil down to the same primitive operations and trust model.
yjftsjthsd-h•41m ago
Other than automating renewal - which we have made huge strides on - what adaption would you want to see?
jaas•36m ago
Stopping all issuance is an pretty standard response if a CA thinks what they are issuing might be non-compliant in any way. It's an action we're required to take. It's not necessarily a sign of a more dramatic failure mode or key compromise. That said, the impact is the same for as long as the downtime lasts so it is unfortunate and we're sorry for the disruption.

I don't think the premise behind short lived (six day) certificates being viable is that CA issuance never goes down. Sure, the runway is shorter, but not that short. Most down time is a few hours or less, which is not a problem for six day certificates that should be renewed every three days.

Short lived certificates are optional though, so if it's not worth it to you there are longer lifetime options.

nottorp•34m ago
> like the recently announced 6 day certs

Just you wait for the 1 hour and 59 minutes certs! For security!

kalmarv•56m ago
Hopefully it's just a technical issue and not something like a key compromise. This could have disastrous effects considering how much of the web runs on LE certs these days.

Granted if it's configured properly everyone should have 30 days of leeway before having to issue new certs...

mark_round•55m ago
"We have been made aware of a potential incident and are shutting down all issuance" seems to lean towards the latter and not simply a technical issue :(
tptacek•49m ago
Josh Aas is on the thread. It's a compliance issue, they expect to be issuing shortly.
rvnx•43m ago
What if they get kicked out of trusted roots because non-compliant ?
nicolas_17•29m ago
That's why they take incidents like this seriously and stop issuance until it's fixed. They could get kicked out of trusted roots otherwise.
cedws•55m ago
Discord is out too right now, probably unrelated though.
aroman•51m ago
Just speculating, but I don't think it's unrelated. Discord heavily utilizes Cloudflare, and Cloudflare uses Let's Encrypt for a certificate issuance. If they happened to have a certificate signing dependency in some operational rollout today, I think it could explain it. Certainly the timing is very correlated.
cedws•41m ago
I guess we'll find out but it would be surprising if they use Let's Encrypt for their backend services. The front door is issued by Google Trust Services.
reaperducer•34m ago
Just speculating

Then why post? HN is for informed discussion, not every random thought in someone's head.

Certainly the timing is very correlated.

I had chocolate ice cream for breakfast. Certainly the timing is very corrolated [sic].

winstonwinston•17m ago
On my account they always serve Google issued certificates. There is also Let’s encrypt certificate but it is not used though. I guess that’s a fail-safe.
jstyles•54m ago
Hopefully just a minor mississuance incident and not something more serious.
bravetraveler•53m ago
It's certainly an incident when ceasing to issue certificates... after doing absolutely everything, including limiting lifetime, to encourage their frequent renewal
bstsb•51m ago
in other news, Digicert's Secure Site Pro certificates are down to only $5,880.00 yearly for one wildcard domain!
jaas•50m ago
This is a compliance incident, we should be issuing again shortly.

Update: Issuance is back up.

gabeio•49m ago
> This is a compliance incident

Uh. I don't know if I like the sound of that...

walrus01•41m ago
Indeed. "Compliance" can mean some internal audit/monitoring system has tripped and requires in depth investigation and preservation of logging, or it can mean "federal law enforcement with badges are right now standing in our datacenter and/or NOC serving a court order".
tptacek•40m ago
At times like this it's worth remembering that message boards strongly favor whatever narrative is going to be most fun and exciting to talk about.
walrus01•39m ago
I sincerely hope it's the most mundane and least spectacular explanation possible, just saying from my point above that compliance has a very wide range of possible meanings and interpretations (also depending on the background/career POV of the reader), until the incident is further explained..
jaas•33m ago
In that sense, prepare yourself to be bored.
michaelt•15m ago
I heard the CEO of Lets Encrypt, Warren Buffet, accidentally started a fire while charging his e-unicycle in the data centre and that knocked out the server that issues the certificates. They've got a backup, but it's in a safe only two people have keys to; one keyholder, Anne Hathaway, is at a parrot show in Singapore this week and her flight back is delayed due to fuel shortages. The other keyholder, Henry Kissinger, it turns out has been dead for 3 years.
eqvinox•36m ago
Federal law enforcement in your DC isn't something you'd call a "compliance" issue, that's not what that term means. Yes it's various derivatives of the English word "comply", but this is a field of well-defined verbiage, and that ain't it. Compliance means they failed (or are being questioned) about following particular practices that they have agreed to, nothing else really.

NB: "legal compliance" is another term. So is "{legal,lawful} enforcement"

john_strinlai•11m ago
"compliance incident" is the catchall for everything from a spelling error on a CPS (certification practice statement) or being one second late on revocation, all the way up to to key compromise.

it is almost always closer to the spelling mistake side than it is the key compromise side of the spectrum.

a peak at https://bugzilla.mozilla.org/buglist.cgi?product=CA%20Progra... will show that most compliance issues, to the general public, are quite mundane.

rbaudibert•48m ago
Thanks for the assurance, jaas! Keep up the good work
washingupliquid•42m ago
Real soon now?
theduderoger•17m ago
can you update the status page with this information?
x86a•50m ago
They had scheduled maintenance a few hours ago, https://letsencrypt.status.io/pages/maintenance/55957a99e800...
t1234s•49m ago
How much of the internet is going to fail because of this?
walrus01•35m ago
It's an interesting thought experiment to consider how much of 'the internet' would still find a way to communicate with each other and fix the problem if somebody waved a magic wand and all http and https servers and clients magically disappeared worldwide instantly.

For instance some of the folks who run core BGP at medium to large sized ISPs would revert back to a few legacy IRC channels and find each other to chat and figure out WTF is going on.

"the internet" would still exist, a subset of the application layer stuff that runs on top it wouldn't...

ben0x539•13m ago
I bet we'd see a bunch of unexpected breakage in presumed-to-be-lower-level-than-http[s] infrastructure so that eg. your legacy IRC server goes down because it's running on rented hardware and the hosting provider's operations rely on some internal http services.
nicolas_17•28m ago
None, unless someone is renewing their certificates only 2 hours before they expire, which is a dumb thing to do.
baigy•43m ago
dang I'll have to return to paid certs again?
DerekL•42m ago
The title is misspelled. It's “Let's Encrypt”, with an apostrophe.
croemer•36m ago
Issuance was stopped almost 2 hours ago: May 8, 2026 18:37 UTC.
hosteur•18m ago
Related Cloudflare issue: https://www.cloudflarestatus.com/incidents/z3vgxxfvt3yb