[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #13296 [Tor]: Drop or replace turtles
#13296: Drop or replace turtles
------------------------+--------------------------------
Reporter: atagar | Owner:
Type: defect | Status: new
Priority: major | Milestone: Tor: 0.2.6.x-final
Component: Tor | Version:
Resolution: | Keywords:
Actual Points: | Parent ID:
Points: |
------------------------+--------------------------------
Comment (by ioerror):
I think we should ask for specific properties in a dir auth system and
specific properties in a dir auth operator. Mike is someone that we trust
very strongly and we must not disregard this aspect of his dir auth.
We should ask for specific properties from each operator - for example we
- the community - want:
0. A person that is trusted by the tor community
0. A person who wants to run a dir auth
0. A server on a fast connection with a very friendly ISP
0. 99.999% up time
0. Always running git tip or a recommended version
0. We want a response to emails to dir-auth@ within 14 calendar days
0. We want emergency contact information for each operator
0. To know about planned downtime in advance
0. To keep important data up to date (such as measurements, etc)
0. ???
There is probably more - how would we rate the current set and not just
Turtles? What other properties do we want or need?
Given the above list, urras is OK on all points except point 9. Is that
true for all people who run dir-auths?
I think that if we remove turtles, we should add another dir-auth. If we
don't do that, I think it is fine to leave his non-functioning dir-auth in
the mix for everything except bootstrapping.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13296#comment:4>
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