pimterry

I think there's a real argument for trying to push "user must be able to control their device's trust anchors" as the next right to repair battle.

If you don't, you can never tell what a device is sending/receiving, and devices have a hardcoded end-of-life date where they become useless. Would love to see groups starting to push in this direction.

I don't think that applies here. The trust store contains the _root_ certificate, not these intermediates.

The main eMudhra root cert backing these intermediates is "emSign ECC Root CA - G3", which was issued back in 2018 and was widely trusted for TLS way before these intermediates were created. The certs were also cross-signed by Sectigo using their "AAA Certificate Services" which was issued in 2004 (!!!) and was trusted in TLS stores until 2025 (after that it got removed/demoted to email signing only, depending on the store).

Everything which trust one of those roots will trust the intermediates (putting aside revocation, CT checks, lack of ECC support, etc) so the window is much much longer. The AAA does expire at the end of 2028 though!

> I find difficult to understand why intermediate certificates are present in trust stores.

They're not generally (there is a specific case of preloaded intermediates, but that's not the main problem here). The certs here aren't in any trust stores I'm aware of directly. The key change to mitigate this is indeed revocation, but that's hard, because many non-browser clients don't actually support revocation in any functional way.

Firefox has gone further though, and distrusted the corresponding root completely in their store. That's not strictly required if you support revocation for the intermediate, but their trust store is widely reused elsewhere and this guarantees the certs won't be trusted even without revocation support. And honestly everybody is now suspicious as hell of eMudhra, so they'd rather be over cautious.

Revolut Business is also down, which does business banking including payment terminals & online subscription processing, so this is going to disable quite a few businesses, in addition to normal consumer payment flows.

They've been expanding hard across Europe recently, this might dent people's confidence in these new fangled neobanks a bit...

From their last filings, they have 70+ million individual customers, 850k business customers. Highest in the UK: about 13 million, so nearly 20% of the population. Ouch.

Partly yes, but I also I think more than expected Node has been able to fix a lot of the warts itself within the existing model, which really undermines the niche further.

> I’m happy if this means Deno is able to get a second impulse

Bad news, sorry, the article says:

> We will support the Deno runtime for another year with monthly releases containing bug fixes and security updates. After that year we will end our development of the Deno runtime.

Sounds like Celld will live on within workerd, Deno is over.

This would be a neat API for a digital photo frame - just print photos to it and they appear on the screen.