[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #24102 [Core Tor/Tor]: Help DirAuths rejecting certain relays based on their properties
#24102: Help DirAuths rejecting certain relays based on their properties
------------------------------+--------------------
Reporter: cypherpunks | Owner: (none)
Type: enhancement | Status: new
Priority: Medium | Milestone:
Component: Core Tor/Tor | Version:
Severity: Normal | Keywords:
Actual Points: | Parent ID:
Points: | Reviewer:
Sponsor: |
------------------------------+--------------------
There is an ongoing group of bad exit relays that are removed from the
network by dir auths and added on the next day with new keys and IPs.
This a slow and manual process and puts tor users at risk.
Allow dirauths to reject relays based on their properties before they are
included in consensuses and distributed to clients.
The rejected relay should get an immediate feedback about their rejection
when uploading the descriptor.
Properties can be:
* IPv4 / IPv6 address
* AS number
* AS name
* (partial) ContactInfo
* (partial) nickname
* exit policy
* OS
* tor version
* OR port
* Dir Port
* first seen date
This ticket is about providing a configuration possibility for dirauths to
reject relays based on a set of properties **IFF** they would actually use
such a feature.
Examples:
* reject new (fingerprint never seen before) relays added in AS 123
**and** exit policy ...
* reject new relays with nickname "abc" and contactinfo "123"
each rule should have an expiry time (i.e 10 days, 1 month, ..)
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24102>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs