Tonight, I spent a few hours implementing RFC5952: https://github.com/colmmacc/s2n/commit/4e7d2424b059b1350353fbb95c251d5ff024535e … ... because it turns out that there's no portable way to be sure that IPv6 strings will be in a canonical format. How is that not fixed in 2019? Crazy! Exact-match is needed in many applications.
-
Show this thread
-
By my count, there are 926,834 different legally valid ways to express the all-zeroes IPv6 address "::" as a string, which I think is the worst case. That's a huge search space, so looking for them all isn't going to do. Showing my work:https://gist.github.com/colmmacc/aa0013c571ab9deeccbf67670ef1b778 …
1 reply 3 retweets 16 likesShow this thread
@andrew729 points out that I might be stretching it with "legally" because the RFC says :: is a "MUST". So these are the 926,834 ways that inet_pton or getaddrinfo will accept the same address. This whole thing started because we saw 0:0:0:0... in an X509 dump.
2:15 PM - 2 Apr 2019
0 replies
0 retweets
5 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.