>Apple was notified of the eMudhra incident on 17th October. As of 28th October, the developer tools Apple ships with macOS, including git, curl and python3, still trust the compromised certificates.>Worse, macOS 27.2, released on 26th October, did not fix the issue and undid the workaround that users had applied by hand, leaving them vulnerable again.https://emudhra.we-have-a-problem.com/apple.html
saar certificate is not comprised
>emudhra.we-have-a-problem
>>1101871434
>>110187156dont post this secret you bloody
>>110187156BLOODY NO! BENCHOD YOU!
>>110186934Isn't the problem that apple hasn't bothered to update the OS cert store so any program that uses it still trusts them?
>>110186934
>>110186934linuxchads stay winning
>>110186934nothingburger
APPLEL
>>110187479yes. they put out some fucking retarded press release basically saying "fix it yourself nerd. lol!"https://support.apple.com/en-us/149555it's insane how incompetent this company is. who the fuck buys this shit?
if you have used MacOS in the past week, ALL of your internet was 100% MITM'd! EVERY website you went to that had "HTTPS" was forged. LOL! All your "encrypted" data is now being preserved in plaintext until They are ready to weaponized that data against You. WOW.
>>110188635and let's be real, at least M$ basically tells you: use our Cert Store or Schannel or fuck off. not this wishy-washy lukewarm dog ass where they ship OpenSSL friendly PEM shit + whatever nonfree faggot TLS stack no one knows about.
>>110186934I only use Firefox. Not my problem.
>>110188685> they are ready to weaponizedThe brownest hands imaginable typed this. You guys can't help but out yourselves with your retarded spelling and comprehension of English, you bloody benchod
>>110186934SAAR certificate not compromised bloody basterd you make India lose izzat
>>110186934Ramdeep read about private keys being 384 bits random numbers, so he wrote a script that picks a number between 0 and 384.
>>110187156blody basterd
>>110189596kek
>>110187156BASTERD I FUCK YUOR IZZAT
>>110186934https://support.apple.com/en-us/149555
>>110186934iTODDLERS BTFO
>should we tell /g/eets that OCSP stapling rendered the attack vector useless from the start, for any serious traffic, or not yet?
