Hi Micah,
Why does longclaw not give the BadExit flag to the UbuntuCore35 relay? My whois says it's in Iran.
Is longclaw not using the AuthDirBadExitCC line?
Or is longclaw using an older geoip database?
--Roger
----- Forwarded message from atagar@torproject.org -----
Date: Sat, 11 Jun 2016 13:11:14 +0000 (UTC) From: atagar@torproject.org To: tor-consensus-health@lists.torproject.org Cc: linus@nordberg.se, tor@sebastianhahn.net, jacob@appelbaum.net Subject: Consensus issues
NOTICE: Downloading the consensus from urras took 27.0s. Median download time is 2.3s: maatuska => 2.3s, tor26 => 1.9s, urras => 27.0s, longclaw => 2.6s, dizum => 1.8s, gabelmoo => 1.6s, moria1 => 3.0s, dannenberg => 1.8s, Faravahar => 2.7s NOTICE: The certificate of the following directory authority expires within the next three weeks: tor26 (2016-07-01 00-00-00) NOTICE: Authorities disagree about the BadExit flag for 14C7359DE6E7F7D98E1ADF48CD624D5156F795D9 (with flag: gabelmoo, tor26, moria1, maatuska, without flag: longclaw)
----- End forwarded message -----
Roger Dingledine arma@mit.edu writes:
Why does longclaw not give the BadExit flag to the UbuntuCore35 relay? My whois says it's in Iran.
I've been wondering that too... but haven't had time to look into it.
Is longclaw not using the AuthDirBadExitCC line?
It is.
Or is longclaw using an older geoip database?
I think you may have nailed it - this doctor warning showed up right after I reinstalled the machine. I moved all the relevant data, and was a bit puzzled why this warning showed up, but everything else worked. I did have some pending updates to packages, including the geoip one, that I applied after I moved everything, but tor had been already started by that time. I've restarted it now, lets see if that helps.
micah
tor-consensus-health@lists.torproject.org
-
micah -
Roger Dingledine