Remix.run Logo
▲ post-it 7 hours ago

Yes, but in the end that's not their fault, and in a sense it's good that this happened. It was well understood from the invention of security certificates that private keys might leak and certificates will need to be revoked. Systems that were not designed with this in mind should never have been deployed, and should now be decommissioned and replaced.

It might even be sensible to intentionally revoke a small number of certificates every month, to make sure nobody is complacent.

▲ryukoposting 6 hours ago | parent | next [-]

The number of awesome things we're going to get as a result of this is exciting to think about.

My wife bought this fuckass IoT air purifier that's constantly phoning home. I'm gonna figure out what it's telling the mothership.

▲trklausss 6 hours ago | parent | next [-]

Mmmh so you will be trying to supplant the destination server with your own, with this emudhra leaked cert, to see what's being sent? Or how are you planning to do that? Just curious :)

▲ryukoposting 5 hours ago | parent | next [-]

Use my pihole to make the domain resolve to some machine on my LAN, then use this glorious new mitmproxy feature:

https://www.mitmproxy.org/posts/releases/mitmproxy-12.3/

▲tga_d 5 hours ago | parent | prev [-]

Presumably just mitmproxy https://news.ycombinator.com/item?id=50189232 though this assumes the cert isn't pinned, which for IoT it may very well be (and probably should be).

▲paimapi 5 hours ago | parent | prev | next [-]

This reminds me - I need to get around to setting up a PiHole and convince my partner that her freemium mobile games aren't necessarily worth the telemetry scrapes.

▲DoctorOetker 5 hours ago | parent | next [-]

a high quality set of FOSS, community inspected "freemium clones" may do more for national security and individual privacy compared to yet another crypto library with zero novel mathematics just another reimplementation of specs...

▲post-it 3 hours ago | parent | prev | next [-]

My girlfriend deliberately watches the extra ads to get in-game rewards, so I can't even pihole the whole home network unless I exclude her phone. (I find that most of these games work fine if you block ads, but they also don't give you the rewards for watching an ad that never loaded.)

▲ryukoposting 5 hours ago | parent | prev [-]

I've had a PiHole running on a NUC for about 2.5 years. I adore it. It should be built into every consumer router.

My wife still plays her freemium games, the ads just don't load. She took out one of those games when we were sitting at the airport once. She was frustrated that her once-pleasant strategy game was suddenly crammed full of ads for boomer slot machine apps, and I had to explain that the app had probably always been that way.

▲paimapi 4 hours ago | parent [-]

That makes sense and seems like it might be a net positive. While she's waiting for her ad countdown, she can gaze into my eyes and realize how much she appreciates me lol

▲srveale 5 hours ago | parent | prev [-]

PPMs > threshold, health insurance revoked

▲throw0101c 6 hours ago | parent | prev | next [-]

> Yes, but in the end that's not their fault, and in a sense it's good that this happened.

I am reminded of the US DST changes back in the 2000s: there was all sorts of drama because a lot of software is written in the US, and there was much 'computerization' in the 1990s, but US coders had never personally experienced a DST rule change during that time period, so any change needed a reboot to pick up the new rules.

That drama led to (e.g.) periodic dynamic checking of /etc/localtime on various Unix-y system.

Sometimes you don't realize that things can be improved until you experience situations in which they currently suck.

▲WebDanube 6 hours ago | parent | next [-]

The leadership page is comedy gold ("Leadership That Inspires Trust"):

> He has wide experience spanning over 45 years in Banking, Financial Services and Technology Industry. His profound understanding of the digital security landscape has been instrumental in eMudhra's global expansion and innovation. ...

> A thought leader and author, Mr. Srinivasan penned "New Age Management Philosophy from Ancient Indian Wisdom," ...

> Under his visionary leadership, eMudhra has become a cornerstone in digital security, known for its pioneering solutions and steadfast adherence to global standards.

https://emudhra.com/en-us/leadership

---

The CEO guy had 45 years of experience and still managed to make a mistake that would get a high school student an 'F' on their hw assignment.

▲geodel 2 hours ago | parent | next [-]

You say comedy gold. However in Vishwaguru Indian universe they are much vaunted South Indian Brahmins who anyone in the world accept that they are the best in anything they do. Hence they are pure gold.

▲eviks 4 hours ago | parent | prev [-]

It takes much less than 45 years to forget almost everything that was taught at high school

▲kccqzy 6 hours ago | parent | prev [-]

Tell Congress to change the rules again soon, lest a new generation of programmers become complacent and hardcode transitions again. Many current junior programmers don’t remember the 2000s rule change.

I can even hear this conversation happening: what? I need to open this America/Los_Angeles file just to convert a timestamp? What pretentious overengineering! I want a single-file executable with zero dependencies. Let me hard code the rules.

▲mook 5 hours ago | parent | next [-]

There's a bunch of changes recently / coming up in Canada, so that might be good enough. I've started occasionally reading the tzdb mailing list archives for fun because of that.

▲throw0101c 6 hours ago | parent | prev [-]

> I want a single-file executable with zero dependencies.

Isn't this what Go programs are to a certain extent?

▲kccqzy 5 hours ago | parent [-]

Yes. Get ready for Go programs produced by inexperienced programmers to do DST conversion incorrectly after the next rule change.

(Actually Go allows you to embed the tz database instead of forcing you to hardcode, so I hope this issue won’t be very widespread.)

▲hobofan 6 hours ago | parent | prev | next [-]

Kind of what Let's encrypt did for automating certificate rotation.

Let's call it "Let's Decrypt!"

▲FLeXMurphy 5 hours ago | parent [-]

I like it already.

▲Zobat 6 hours ago | parent | prev | next [-]

Google has decided to stop trusting certificates with dual purpose (server and client) and managed to negotiate a decrease in the maximum (SSL/TLS) certificate lifetime because certificate revocation doesn't work.

We've had to rework part of our application and certificate use because of this.

▲thayne 5 hours ago | parent | prev | next [-]

Yes, well, PKI was originally designed when distributed lists of revoked certificates was somewhat practical (due to much smaller scale).

Now we are in a situation where we don't really have a practical and correct way to revoke certificates, but many, many things depend on pki.

▲hluska 6 hours ago | parent | prev | next [-]

> It might even be sensible to intentionally revoke a small number of certificates every month, to make sure nobody is complacent.

No, this is not even remotely sensible.

▲noitpmeder 6 hours ago | parent | next [-]

Failure paths that are not exercised with regularity will inevitably fail in surprising ways when actually needed.

▲solarkraft 6 hours ago | parent | prev | next [-]

Please elaborate. Conventional thinking goes that emergency plans must be exercised to make sure they’re actually effective.

▲sam1714 5 hours ago | parent [-]

The problem isn't revocation of end-user identity certificates. There's hundreds of millions of those floating around at any given point, so revocation happens very regularly. The issue is revocation of intermediates and roots, which involves invalidating tens of millions of certificates and often find themselves in embedded/non-web applications (financial, legal signatures, medical data exchange).

An analogy would be shutting down neighborhood streets versus shutting down major highways in a state for a hurricane evacuation. You can't test the latter at scale.

▲sophacles 6 hours ago | parent | prev [-]

It really is. It's basically chaos monkey for pki.

Code paths and procedures that aren't exercised regularly are broken.

Even better is having a way to reoke keys and big players occasionally include revoked keys in trust chains and blast a warning if the revoked key is considered valid.

▲shadowgovt 6 hours ago | parent | prev [-]

Honestly, that's not a bad idea at all. That's exactly the kind of thing that companies like Google do in disaster recovery testing.

If you don't know if you can hot-swap your certs, you probably can't.