10 ms·
Its not a mistake or a vulnerability either. Incorrect cache hits are fine, as long as there is some checking following the cache hit hash(A) == hash(B) &
by RubyPinch 10y ago
Its not a mistake or a vulnerability either.
Incorrect cache hits are fine, as long as there is some checking following the cache hit
hash(A) == hash(B) && A == B
> I wasn't aware they were checking the commonName sent with SNI.
If I'm not mistaken, it does sound like they were doing some checking after they pulled the generated cert from cache, but it obviously wasn't enough checking
- kuschku 10y ago> Incorrect cache hits are fine, as long as there is some checking following the cache hit Exactly. That’s why hashmaps don’t have objects in each bucket, but an actual linked list (or partitioned linked list) with all elements hashing into that bucket. This is CS101. If you build a hashmap yourself, at least get this right.