News for hackers. Stuff that matters.
Re:Creating a rogue CA certificate with MD5 hash collisions by fhars on Tuesday December 30, 2008 @04:55PM (#414727)
A sweeping revocation wouldn't work, as you can only revoke certifcates that have not been tampered with. You must issue a SHA-1 certificate to everyone and then change every piece of software that uses certificates not to trust certificates with an MD5 hash in the trust chain. If someone else has successfully performed this attack, he might posses a CA certificate that is valid until 2038 and you have no way to know about it until he uses it against you.
Re:Creating a rogue CA certificate with MD5 hash collisions by nailer on Tuesday December 30, 2008 @06:25PM (#414834)
I'd suggest browsers, via an update, stop accepting certificates using known vulnerable hashing routines.