> Are you *absoultely* certain that the config > was not fiddled with at the time of this event? After grepping some logs, seems 13/12 was the day of a Tor upgrade : 2015-12-13 10:47:31 upgrade tor:amd64 0.2.7.5-1~d80.jessie+1 0.2.7.6-1~d80.jessie+1 2015-12-13 10:48:39 configure tor:amd64 0.2.7.6-1~d80.jessie+1 Timing is good compare to the 10:48:46 of the consensus ! But I donât remember a config change after that, perhaps only on /usr/share/ tor/tor-service-defaults-torrc or on a default config param change ? And perhaps the Tor reboot cause the DirPort to be temporarily disabled (seems not human, only 2s duration) ? Regards, -- Aeris Individual crypto-terrorist group self-radicalized on the digital Internet https://imirhil.fr/ Protect your privacy, encrypt your communications GPG : EFB74277 ECE4E222 OTR : 5769616D 2D3DAC72 https://cafÃ-vie-privÃe.fr/
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ tor-relays mailing list tor-relays@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays