Thanks! Now I understand. That link was good, it helped me understand a
lot more. Roger Dingledine: On Mon, Jun 04, 2007 at 04:03:07PM +0200, vikingserver@xxxxxxxxx wrote:Before anything else, I must say a BIG THANK YOU to the developers of TOR. I have been running a server now for a year or so, with the purpose of being an entry server for people behind restrictive firewalls. I choose port 995 which is a port often used by SSL-email servers. I choose this port because I didn't find any tor server back then that had a server on the port 995.Great, thanks for helping out!Anyway, today I read this in the release notes:o Security fixes: - Directory authorities now call routers stable if they have an uptime of at least 30 days, even if that's not the median uptime in the network. Implements proposal 107, suggested by Kevin Bauer and Damon McCoy.I have questions about this that might interest others: Is the requirement of "being stable" to have had the server running for at least 30 days in a row without any downtime?Ah, I should have been more clear. Quoting from sec 3.3 of https://tor.eff.org/svn/trunk/doc/spec/dir-spec.txt "A router is 'Stable' if it is active, and either its uptime is at least the median uptime for known active routers, or its uptime is at least 30 days." ("a router is considered "active" if it is running, valid, and not hibernating") Most of the servers in the network get their Stable flag from being in the top half of the servers by uptime, and only a few are affected by the or-30-days exception we added in 0.2.0.1-alpha. The current cutoff for being stable in the Tor network right now is 185878 seconds, or a bit over 51 hours. Hope that helps, --Roger |