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

"Is IP address a tor exit node?" lookup #14

Open
Sainan opened this issue Aug 8, 2022 · 8 comments
Open

"Is IP address a tor exit node?" lookup #14

Sainan opened this issue Aug 8, 2022 · 8 comments

Comments

@Sainan
Copy link
Member

Sainan commented Aug 8, 2022

https://onionoo.torproject.org/details?search=flag:exit

@Sainan Sainan mentioned this issue Aug 8, 2022
3 tasks
@Sainan Sainan changed the title Tor Node Check: https://onionoo.torproject.org/details?search=flag:exit "Is IP address a tor exit node?" lookup Aug 8, 2022
@alessandromrc
Copy link
Contributor

Could this database be useful for this task?

@Sainan
Copy link
Member Author

Sainan commented Sep 18, 2022

I don't want to rely on companies like IP2Location. The link provided in the issue description is the actual source from the Tor Project itself. The reason I haven't implemented this in Soup is because I have no need for it right now so it would only be an "interesting challenge" kinda thing for another day.

@alessandromrc
Copy link
Contributor

I don't want to rely on companies like IP2Location. The link provided in the issue description is the actual source from the Tor Project itself.

I felt that, on my github you could find a repository called tor-data, it has some more restricted infos already extracted in json format

@Sainan
Copy link
Member Author

Sainan commented Sep 18, 2022

No offense, but parsing the JSON to limit it to a few fields is nothing special. My main concern with all this netIntel stuff is how I want it to work in a more long-term configuration, because data would need to be updated at some point. It also needs to be stored in memory efficiently as it can get quite big.

@alessandromrc
Copy link
Contributor

alessandromrc commented Sep 18, 2022

No offense, but parsing the JSON to limit it to a few fields is nothing special. My main concern with all this netIntel stuff is how I want it to work in a more long-term configuration, because data would need to be updated at some point. It also needs to be stored in memory efficiently as it can get quite big.

Yeah, the main problem is about keeping it efficient as it is really a LOT of data as you said

Ps. Isn't it possible to make a separated repository to keep all the networking databases related stuff with a script that automatically updates everything or you would prefer to have them built into Soup?

@Sainan
Copy link
Member Author

Sainan commented Oct 9, 2022

Ps. Isn't it possible to make a separated repository to keep all the networking databases related stuff with a script that automatically updates everything or you would prefer to have them built into Soup?

It really depends on what the actual use case is, but ideally it would be something auto-updating and efficient.

@alessandromrc
Copy link
Contributor

If you check the repository from mines "tor-data" that I updated yesterday it automatically updates itself every 12h with all the tor nodes and ASNs, wouldn't it be easier to make a script that get's all the data from the various sources like Mullvad, NordVPN and others and then just use the output of it for Soup?

@Sainan
Copy link
Member Author

Sainan commented Oct 9, 2022

Yes, that would likely be easier, but simplicity is not a concern.

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

No branches or pull requests

2 participants