Login
You're viewing the assemblag.es public feed.

Replies

  • __Miguel_nanianmichaels@tech.lgbt
    Oct 22, 2026, 2:11 PM

    @nCrazed @q3k Likely they were voluntold to either GTFO or be forcibly removed.

    Or they saw the rather clear writing on the wall that they'd be effectively cut off from root cert trust chains sooner rather than later and decided to just cut their losses before having their reputation dragged through the mud by having their certs forcibly removed from the trust chains.

    There have been complete root cert chains removed from trust chains much much less egregious issues, so IMO the writing was on the wall.

    Of course now the question is: were these the only certificates with laughably insecure private keys? Or are they trying to exit the space now before more of those situations being discovered?

    💬 0🔄 1⭐ 14
  • kasperdkasperd@westergaard.social
    Oct 23, 2026, 1:18 AM
    My recollection is that previous removals of root CAs have been due to attempts to cover up their screwups. In the current incident there has been a screwup but no cover up, so I am not entirely sure if it qualifies as worse.

    But it's bad enough that many have already chosen to remove the root CAs involved in the current incident. So it would be an uphill battle for them to regain trust. And their certificate business might not be big enough to take that battle.
    💬 0🔄 1⭐ 0
  • 💬 0🔄 0⭐ 0