all 38 comments

sorted by: hot top controversial new old
[โ€“] 4 points 51 minutes ago

If anyone else here uses AdGuard, the latest version of their app rejects the affected certificates. ๐Ÿ‘

  • source
  • [โ€“] 2 points 2 hours ago (3 children)

    Shouldnt you also disable the "Comodo" ones?

  • source
  • hideshow 3 child comments
  • [โ€“] [S] 2 points 1 hour ago (2 children)
  • [โ€“] 6 points 1 hour ago* (last edited 1 hour ago) (1 child)

    they were/are a shittier-than-average CA that got famously hacked in 2011 and less famously other times; later they bizarrely tried to trademark the name "Lets Encrypt" (after the real Lets Encrypt already existed). Since 2022 they're called "Xcitium" and "Sectigo".

  • source
  • parent
  • hideshow 1 child comment
  • [โ€“] 78 points 5 hours ago (2 children)

    there's 4 of them, coincidence or conspiracy?

  • source
  • hideshow 2 child comments
  • [โ€“] 15 points 4 hours ago (3 children)

    I once tried to disable all but the ones I actually need. There are close to 200 CAs trusted by my devices and I only need to trust about 15 of them. But it's a colossal pain in the ass to figure out which CA an app needs, so I abandoned that experiment.

  • source
  • hideshow 3 child comments
  • [โ€“] [S] 5 points 4 hours ago (2 children)

    Yeah, I too had that ambition once, but I didn't even know where to begin, since I don't know how to find out which once my apps, websites and other services actually need. Other than investigating whole chains of collaboration between the various owners and devs of those services. Arduous much? ๐Ÿ˜…

  • source
  • parent
  • hideshow 2 child comments
  • [โ€“] 26 points 5 hours ago* (last edited 5 hours ago) (5 children)

    FYI, G3 is the only one listed with the issue, the others are fine AFAIK. But if you don't trust eMudhra at all after that, then that's fair.

    Edit: Actually it's the intermediate certs that are compromised, the roots are still fine, but many of them come from the G3 root cert (and Sectigo's AAA Certificate Services)

    Source: https://emudhra.we-have-a-problem.com/

  • source
  • hideshow 5 child comments
  • [โ€“] [S] 12 points 5 hours ago (3 children)

    Oh, thanks for that! ๐Ÿ˜Š I just heard that they quit the TLS business all together.

  • source
  • parent
  • hideshow 3 child comments
  • [โ€“] 6 points 5 hours ago (2 children)

    Yeah, my understanding was they're not issuing new certificates, but the current ones are still valid until they've expired.

  • source
  • parent
  • hideshow 2 child comments
  • [โ€“] 3 points 2 hours ago* (1 child)

    Recently learned that root CA don't actually expire. Yes, they have an expiration date, but nothing pays attention to it for a CA.

  • source
  • parent
  • hideshow 1 child comment
  • [โ€“] 4 points 1 hour ago

    Well you can't sign new certs (with the current date) with an expired root/intermediate cert, but the root/intermediate cert expiring doesn't strictly invalidate the already signed certs.

    But I was more talking about the end-user certificates in the previous comment.

  • source
  • parent
  • [โ€“] 14 points 5 hours ago (1 child)

    Thanks for reminding me to do that!

  • source
  • hideshow 1 child comment
  • [โ€“] [S] 9 points 5 hours ago

    No problem! But as I told another person, Iโ€™m only doing this because Iโ€™m not updating my phone anymore, because One UI 8 and above have disabled unlocking of the bootloader. If you're not rooted and you are still receiving updates from the vendor and Google, then I can't imagine this being useful.

  • source
  • parent
  • [โ€“] 4 points 4 hours ago (3 children)

    Why isn't this a change pushed by Google?

  • source
  • hideshow 3 child comments
  • [โ€“] 4 points 3 hours ago

    Because these are root certs which are still fine, it's the intermediate certs that are compromised.

    I still disabled eMudhra's emSign G3 anyway, but that's probably why Google hasn't disabled the ones shown.

  • source
  • parent
  • [โ€“] [S] 2 points 4 hours ago* (1 child)

    Is it not? I have no idea. My device isn't legitimate in their eyes. ๐Ÿ˜… (Rooted.)

  • source
  • parent
  • hideshow 1 child comment
  • [โ€“] 8 points 5 hours ago (13 children)
  • [โ€“] 13 points 5 hours ago (5 children)

    On Android:

    Security and privacy -> more security settings -> view certificates

    Or go to settings and serach of certificates in the search bar

  • source
  • parent
  • hideshow 5 child comments
  • [โ€“] 5 points 5 hours ago (3 children)

    Thanks! How was this not widely spread on day 1? Why wasn't it pushed as an ota update to deactivate them?

  • source
  • parent
  • hideshow 3 child comments
  • [โ€“] 7 points 5 hours ago (2 children)

    eMudhra invalidated their insecure certificates and released renewed ones as far as I know.

  • source
  • parent
  • hideshow 2 child comments
  • [โ€“] [S] 8 points 5 hours ago (6 children)

    Settings - Security and privacy - More security settings - View security certificates

    Mind you, I'm using an outdated Android 15 with a similarly outdated One UI 7. I hope that either AOSP or Samsung already have patched emudhra out of the latest releases? I'm only doing this because I'm not updating my phone anymore, because One UI 8 and above have disabled unlocking of the bootloader.

  • source
  • parent
  • hideshow 6 child comments
  • [โ€“] 11 points 4 hours ago (4 children)

    outdated Android 15 with a similarly outdated One UI 7

    ...outdated @ 15 w/ 7?

  • source
  • parent
  • hideshow 4 child comments
  • [โ€“] [S] 5 points 4 hours ago (3 children)

    Good God WHAT are you running ๐Ÿ˜‚๐Ÿ˜‚๐Ÿ˜‚

  • source
  • parent
  • hideshow 3 child comments
  • [โ€“] 10 points 4 hours ago (2 children)

    Uhhh, well on my most up to date device its at least a double digit android version.

  • source
  • parent
  • hideshow 2 child comments