What does this log message mean ? : Starting with guard context "default"
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I do wonder about it b/c IMO this message is new - at least for me, or ? - -- Toralf PGP: C4EACDDE 0076E94E -----BEGIN PGP SIGNATURE----- iHYEAREIAB4FAlia5vAXHHRvcmFsZi5mb2Vyc3RlckBnbXguZGUACgkQxOrN3gB2 6U76agD+Ottd3e1K43gdCmz9e9euSICdBFCHe4NCf+gBUA4Qn+gA/j2G7dShXQJ9 JRlIp/GoQ01bOuEuHIu9BjCD68cyosHF =o5+D -----END PGP SIGNATURE-----
On 8 February 2017 at 09:37, Toralf Förster <toralf.foerster@gmx.de> wrote:
I do wonder about it b/c IMO this message is new - at least for me, or ?
The code seems to have been added 2 months ago, so this is probably expected to appear after recent updates: https://github.com/torproject/tor/commit/404e9e5611eff39866c2e45133a60b40d74...
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 02/08/2017 12:19 PM, Pascal Terjan wrote:
The code seems to have been added 2 months ago, so this is probably expected to appear after recent updates:
https://github.com/torproject/tor/commit/404e9e5611eff39866c2e45133a60b40d74...
ah - and I switched to 0.3.0.3 from 0.2.9.9 few days ago, therefore I didn't hit this message before. - -- Toralf PGP: C4EACDDE 0076E94E -----BEGIN PGP SIGNATURE----- iHYEAREIAB4FAlibPoAXHHRvcmFsZi5mb2Vyc3RlckBnbXguZGUACgkQxOrN3gB2 6U4NhgD+JZTSo7AlAI+kCvkDIMpSK57Kz/Msg8re25rlSLYEY1AA/jZJMMB94r5n 0KCp4C+cYFiK0TK7MQmHkx+f4/gcDzmg =xLmd -----END PGP SIGNATURE-----
On 9 Feb 2017, at 02:51, Toralf Förster <toralf.foerster@gmx.de> wrote:
Signed PGP part On 02/08/2017 12:19 PM, Pascal Terjan wrote:
The code seems to have been added 2 months ago, so this is probably expected to appear after recent updates:
https://github.com/torproject/tor/commit/404e9e5611eff39866c2e45133a60b40d74...
ah - and I switched to 0.3.0.3 from 0.2.9.9 few days ago, therefore I didn't hit this message before.
Here are the details of that log message: Changes in version 0.3.0.1-alpha - 2016-12-19 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development series. It...improves the algorithm that clients use to choose and maintain their list of guards... Below are the changes since 0.2.9.8. o Major features (guard selection algorithm): - Tor's guard selection algorithm has been redesigned from the ground up, to better support unreliable networks and restrictive sets of entry nodes, and to better resist guard-capture attacks by hostile local networks. Implements proposal 271; closes ticket 19877. https://gitweb.torproject.org/tor.git/tree/ChangeLog?id=ac04fcd2e758c2258cbd... This is the description of the "normal" guard context: /** Use the normal guard selection algorithm, taking our sample from the * complete list of guards in the consensus. */ GS_TYPE_NORMAL=1, https://gitweb.torproject.org/tor.git/tree/src/or/entrynodes.h?id=ac04fcd2e7... The message comes from create_initial_guard_context(). https://gitweb.torproject.org/tor.git/tree/src/or/entrynodes.c?id=ac04fcd2e7... T -- Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------
participants (3)
-
Pascal Terjan -
teor -
Toralf Förster