aboutsummaryrefslogtreecommitdiff
path: root/scripts/guess-roas-from-routeviews.py
diff options
context:
space:
mode:
authorRob Austein <sra@hactrn.net>2009-09-19 03:25:15 +0000
committerRob Austein <sra@hactrn.net>2009-09-19 03:25:15 +0000
commit8202c7df492d2a3f853620c554f052dc9238f6ed (patch)
treed3d6a068bd74e1a4f687a7c45d5e26076836d82c /scripts/guess-roas-from-routeviews.py
parent62e9e309e515740d425874f43c2786f9f1548be2 (diff)
routeviews DNS hack doesn't really support IPv6 after all.
svn path=/scripts/guess-roas-from-routeviews.py; revision=2775
Diffstat (limited to 'scripts/guess-roas-from-routeviews.py')
-rw-r--r--scripts/guess-roas-from-routeviews.py4
1 files changed, 2 insertions, 2 deletions
diff --git a/scripts/guess-roas-from-routeviews.py b/scripts/guess-roas-from-routeviews.py
index fcfe291c..403c99bf 100644
--- a/scripts/guess-roas-from-routeviews.py
+++ b/scripts/guess-roas-from-routeviews.py
@@ -5,8 +5,8 @@ Pull RFC 3779 resources from a cert, attempt to mine routeviews (via
DNS, using the dnspython toolkit) for what the ROAs might look like
for the addresses found in the cert.
-This doesn't handle IPv6 yet, because I didn't know about the
-dns.reversename module when I wrote this. I'll fix that.
+This doesn't handle IPv6, because neither, apparently, does the
+routeviews DNS interface. Oh well.
NB: this is wild-assed guessing at best. Even if the routeviews data
were signed, which it is not, you have no particular reason to believe