Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Include code for fetching updated map from upstream #11

Closed
willscott opened this issue Feb 11, 2021 · 5 comments · Fixed by #17
Closed

Include code for fetching updated map from upstream #11

willscott opened this issue Feb 11, 2021 · 5 comments · Fixed by #17

Comments

@willscott
Copy link
Contributor

This package needs to be periodically updated as new assignments occur if it's to be used.

@aschmahmann - do you know where generate/ipv6_asn.asset.tsv came from and how we can provide code for getting new versions of that source file?

@aschmahmann
Copy link
Contributor

aschmahmann commented Feb 11, 2021

@aarshkshah1992 would know best here, but I think its from the website linked to from the README https://iptoasn.com/

@aarshkshah1992
Copy link
Contributor

@aschmahmann is correct.

@willscott
Copy link
Contributor Author

that site indicates it's deprecated and will go away, and doesn't include a methodology for how the database is generated (the source code linked runs the website to provide an API over the database, but doesn't give information on how to update or regenerate the database itself). What's our plan as it falls out of date?

@aarshkshah1992
Copy link
Contributor

@willscott When we did this, the goal was to get it working for immediate DHT resilience against attacks. I couldn't find any free & open source reliable dataset that's updated regularly when I was working on this.

The best I could find was https://lite.ip2location.com/ but IIRC, there were some licensing concerns around using that.

So yeah, this is as an yet unsolved problem.

@willscott
Copy link
Contributor Author

a reasonable authoritative upstream is http://archive.routeviews.org/dnszones/

It's gonna be hard to notice how far out of date this thing gets, so at some point we're gonna need to queue up someone spending a week to get this into shape. @aschmahmann i guess you're maybe the right person to try and track this for prioritization?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants