-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
When a new version of Tor is released, one which makes significant changes to routing rules, covers security vulnerabilities, etc. - how do all the ~6000 relays upgrade to the latest version automatically and simultaneously so the peers in the network can talk to each other? On a normal client which uses the Tor Browser Bundle, the update does not take place at all unless the user does it manually. Is it the same case to relays? It has to be, since some normal clients act as relays also in order to help the network (this is my case also). So, when something with important changes takes place - how are all the peers in the network convinced to upgrade simultaneously and automatically? - -- PGP Public key: http://www.sky-ip.org/s...@sky-ip.org.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (MingW32) iQEcBAEBAgAGBQJTC+Y0AAoJEIN/pSyBJlsRNtUH/3/9tdnehg4i6I8wsfSq9VOU Zx1ko7jo9bUKMYgxUNwShgvF9Vp2rHvCN+JgSbxcqJT/fT72dCtuJjdQS4XDuDu6 k7siwwgj/KZJ+yBielFx3g+GTjqetF5aa3UztYkaqfwIcL9TzpMRZbotd4SL9Lke 2IOJbe53urTrWCi6xESw0m9tp75lKflBf6DNDPkTuxJBjGN7Gup5DV/MR0nZReZN IacNx7z8MCIz0E0FHV3HM7b+h7UuV8VY9gjrAYwJ26dn0gdrkRLXKwLsv4aV7Myp +XbaIVARf1bB8+gMl19hK1pvnwBPk+0Ra34kajMhI6EbUHGuDICLM5AWJHiOVWk= =e11R -----END PGP SIGNATURE----- -- tor-talk mailing list - tor-talk@lists.torproject.org To unsubscribe or change other settings go to https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk
