The interesting aspect that a lot of people are overlooking is that, for a theoretical attack within certain timeframes, this difference can be make-it or break it! Imagine a collision attack that takes about a 1 year with 64bit serial numbers, so with 63bit serial number it should take about half, at 6 months. The average certificate is issued for about 1 year, so being able to mount a collision attack that took 1 y…
Why do you assume that an attack would take 1 year, and not (e.g.) a billion years? A factor of two is only interesting if the number you're dividing was interesting in the first place.
A world of hurt after GoDaddy, Apple, and Google misissue 1M certificates
41–50 of 143 posts
Re: A world of hurt after GoDaddy, Apple, and Google misissue 1M certificates
#42> Adam Caudill, the security researcher who blogged about the mass misissuance last weekend, pointed out that it’s easy to think that a difference of 1 single bit would be largely inconsequential when considering numbers this big. In fact, he said, the difference between 2^63 and 2^64 is more than 9 quintillion. Okay, but, that's because 2^63 itself is more than 9 quintillion. Where the search space was previously 18…
Re: A world of hurt after GoDaddy, Apple, and Google misissue 1M certificates
#43The interesting aspect that a lot of people are overlooking is that, for a theoretical attack within certain timeframes, this difference can be make-it or break it! Imagine a collision attack that takes about a 1 year with 64bit serial numbers, so with 63bit serial number it should take about half, at 6 months. The average certificate is issued for about 1 year, so being able to mount a collision attack that took 1 y…
Re: A world of hurt after GoDaddy, Apple, and Google misissue 1M certificates
#44Re: A world of hurt after GoDaddy, Apple, and Google misissue 1M certificates
#45Re: A world of hurt after GoDaddy, Apple, and Google misissue 1M certificates
#46Presumably 64 bits were originally chosen because it still permitted simple or naive ASN.1 decoders to return the parsed value as a native 64-bit type. But ASN.1 INTEGERs are always signed, so theses serials would now have to be 65 bits. But any ASN.1 decoder interface that permitted directly storing a 65-bit value into a 64-bit type--even an unsigned type--is dangerous if not broken. I'm guessing that most X.509 man…
Yes, now certificates are about half as hard to hack as they were supposed to be.
Re: A world of hurt after GoDaddy, Apple, and Google misissue 1M certificates
#47Re: A world of hurt after GoDaddy, Apple, and Google misissue 1M certificates
#48Re: A world of hurt after GoDaddy, Apple, and Google misissue 1M certificates
#49Re: A world of hurt after GoDaddy, Apple, and Google misissue 1M certificates
#50The true cost of Java not supporting unsigned integers
I'd chalk this up to the author of the relevant module not really grokking the two's complement behavior in java.math.BigInteger.