-
-
Notifications
You must be signed in to change notification settings - Fork 439
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
[Analyzer] Tor_Nodes_DanMeUk #1886
Labels
Comments
Hey @mlodic, I would like to work on this issue. |
Hey @mlodic what should be the name of this analyzer? |
Tor_Nodes_DanMeUk we need to complete the other issue before starting a new one |
22 tasks
mlodic
added a commit
that referenced
this issue
Mar 25, 2024
* fixes 1886 observable analyzer Tor_Nodes_DanMeUk added analyzer code for Tor_Node_DanMeUk migrations for Tor_Nodes_DanMeUk analyzer added Tor_Nodes_DanMeUk analyzer to FREE_TO_USE_ANALYZERS updated docs checking pre-commit * Updated Usage.md * Update api_app/analyzers_manager/migrations/0071_analyzer_config_tor_nodes_danmeuk.py --------- Co-authored-by: Matteo Lodi <30625432+mlodic@users.noreply.github.com>
solved with v6.0.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Name
Tor_Nodes_DanMeUk
Link
Extract lists of all Tor nodes from this site periodically:
https://www.dan.me.uk/tornodes
Type of analyzer
observable for IP addresses only
Why should we use it
An user requested this:
Possible implementation
just basically copy/paste TorProject one and change the results based on the type of the node
The text was updated successfully, but these errors were encountered: