223 points ahlCVA 2 hours ago 58 comments
tecleandor 2 hours ago | parent
DrammBA 2 hours ago | parent
xp84 2 hours ago | parent
r3trohack3r 1 hour ago | parent
At some point you’re forced to stack rank two or more of your values in a case where they’re mutually exclusive
tonymet 2 hours ago | parent
MajorTakeaway 1 hour ago | parent
thway15269037 33 minutes ago | parent
So, not trusting anything wireless is a thing for almost a decade.
Bratmon 1 hour ago | parent
shrubble 2 hours ago | parent
quotemstr 1 hour ago | parent
kevin_nisbet 1 hour ago | parent
the_snooze 1 hour ago | parent
seniorsassycat 2 hours ago | parent
himata4113 1 hour ago | parent
server: here are latest ads
btw, the ads are capable of code execution for whatever reason so now you have an RCE on your hands for your client
sippingabonedry 1 hour ago | parent
Anyone else bother to notice iOS still trusts 2 of the forged certs on the test site? I'd like to politely know what the fuck is going on because this is far from being "fixed".
xuki 1 hour ago | parent
snailmailman 1 hour ago | parent
TYPE_FASTER 53 minutes ago | parent
sippingabonedry 1 hour ago | parent
Edit: I'm not the only one with this issue:
https://www.reddit.com/r/iphone/comments/1xbvxgd/emudhra_cer...
My best guess is it's soft-failing on a failed OCSP lookup?
robrain 38 minutes ago | parent
I've just been rechecking everything and both iOS and MacOS browsers (Safari and Orion tested) now accept one (for MacOS, 27.0.1) or three (for iOS, 27.0.1) of them. I know the revocation is not an OS update, just including the version number for completeness.
EDIT: iPadOS with the same browsers continues to pass the tests.
Further EDIT: iPadOS now accepts one of them. This has to be a load issue on the "got a problem site", surely? Maybe a check for a certificate error message that never hits because a timeout beats it?
sippingabonedry 6 minutes ago | parent
No, because it lets you successfully navigate to the forged CA test site.
Try clicking the link containing the CA's name for any that fail the test.
kccqzy 8 minutes ago | parent
I don’t know if possible on iOS but I remember multiple incidents where people recommended turning off CRL and OCSP on macOS to speed things up. That even used to be a setting in the GUI. https://i0.wp.com/i.imgur.com/XVHWCNz.png
mintflow 1 hour ago | parent
xmcp123 1 hour ago | parent
Confiks 1 hour ago | parent
subscribed 1 hour ago | parent
brirec 6 minutes ago | parent
https://tech-insider.org/emudhra-ca-private-keys-compromised...
judge2020 31 minutes ago | parent
0xbadcafebee 1 hour ago | parent
deadbabe 1 hour ago | parent
Gigachad 1 hour ago | parent
jolmg 1 hour ago | parent
> On October 17, 2026, browser root programs received a report that the private keys of eight eMudhra intermediate certificates had been compromised. The private keys were 4, 56, 66, 115, 155, 156, 230, and 237. A P-384 elliptic-curve private key normally has about 384 bits of entropy, but these keys had between 3 and 8 bits.
lambda 1 hour ago | parent
CGamesPlay 58 minutes ago | parent
So from the perspective of hacking old IoT devices, if your device hasn't been updated since 2018, the AAA path should work; if since February 2025, either path works; if since October 2026, the emSign path.
codys 29 minutes ago | parent
mhils 9 minutes ago | parent
cherioo 51 minutes ago | parent
SAI_Peregrinus 34 minutes ago | parent
closetheloopdev 38 minutes ago | parent
I was mainly interested in testing which IoT devices are affected and protecting them, not trying to sniff their traffic since it's been a long day. My proxy thus just intercepted and forwarded the traffic upstream using a fresh TLS connection that does not use the compromised keys.