[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Full-disclosure] OpenID/Debian PRNG/DNS Cache poisoning advisory
- To: dave.korn@xxxxxxxxxx, ekr@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [Full-disclosure] OpenID/Debian PRNG/DNS Cache poisoning advisory
- From: pgut001@xxxxxxxxxxxxxxxxx (Peter Gutmann)
- Date: Sat, 09 Aug 2008 05:49:42 +1200
Eric Rescorla <ekr@xxxxxxxxxxxxxxxxxxxx> writes:
>It's easy to compute all the public keys that will be generated
>by the broken PRNG. The clients could embed that list and refuse
>to accept any certificate containing one of them. So, this
>is distinct from CRLs in that it doesn't require knowing
>which servers have which cert...
You'd also end up with a rather large list for the client to carry around,
which would be especially problematic for lightweight clients. You'd need to
represent it as something like a Bloom filter to avoid this (given that most
users will just click OK on invalid certs, the small false positive rate
shouldn't have much effect either :-).
Peter.
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/