March 2013 - tor-commits - lists.torproject.org

[tor/master] First try on ticket 8590
by nickm＠torproject.org 28 Mar '13

28 Mar '13

commit 5a3eacf88c89c4d29cac2e324a381a3fd4982fa1 Author: Patrick R McDonald <marlowe(a)antagonism.org> Date: Mon Mar 25 17:31:16 2013 -0500 First try on ticket 8590 --- doc/tor.1.txt | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/doc/tor.1.txt b/doc/tor.1.txt index 5727ec3..5dc4bc8 100644 --- a/doc/tor.1.txt +++ b/doc/tor.1.txt @@ -1431,7 +1431,9 @@ is non-zero): that they are in the same \'family', Tor clients will not use them in the same circuit. (Each server only needs to list the other servers in its family; it doesn't need to list itself, but it won't hurt.) Do not list - any bridge relay as it would compromise its concealment. + any bridge relay as it would compromise its concealment. When listing a + node, it is preferable to do so as a fingerprint as opposed to a nickname + as fingerprints are a more reliable mechanism for identifying a node. **Nickname** __name__:: Set the server's nickname to \'name'. Nicknames must be between 1 and 19

1 0

[tor/master] Tighten prose in 8590 manpage fix
by nickm＠torproject.org 28 Mar '13

28 Mar '13

commit cd5048d61e64371ea1f7756cefacd9e731f11002 Author: Nick Mathewson <nickm(a)torproject.org> Date: Wed Mar 27 21:58:07 2013 -0400 Tighten prose in 8590 manpage fix --- doc/tor.1.txt | 7 ++++--- 1 files changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/tor.1.txt b/doc/tor.1.txt index 5dc4bc8..c502c57 100644 --- a/doc/tor.1.txt +++ b/doc/tor.1.txt @@ -1431,9 +1431,10 @@ is non-zero): that they are in the same \'family', Tor clients will not use them in the same circuit. (Each server only needs to list the other servers in its family; it doesn't need to list itself, but it won't hurt.) Do not list - any bridge relay as it would compromise its concealment. When listing a - node, it is preferable to do so as a fingerprint as opposed to a nickname - as fingerprints are a more reliable mechanism for identifying a node. + any bridge relay as it would compromise its concealment. + + + When listing a node, it's better to list it by fingerprint than by + nickname: fingerprints are more reliable. **Nickname** __name__:: Set the server's nickname to \'name'. Nicknames must be between 1 and 19

1 0

[tor/master] Merge remote-tracking branch 'origin/maint-0.2.4'
by nickm＠torproject.org 28 Mar '13

28 Mar '13

commit ece9ef7f41224dbad8c36b735c08877e6193c38b Merge: eb9b282 cd5048d Author: Nick Mathewson <nickm(a)torproject.org> Date: Wed Mar 27 21:58:36 2013 -0400 Merge remote-tracking branch 'origin/maint-0.2.4' doc/tor.1.txt | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-)

1 0

[tor/maint-0.2.4] First try on ticket 8590
by nickm＠torproject.org 28 Mar '13

28 Mar '13

commit 5a3eacf88c89c4d29cac2e324a381a3fd4982fa1 Author: Patrick R McDonald <marlowe(a)antagonism.org> Date: Mon Mar 25 17:31:16 2013 -0500 First try on ticket 8590 --- doc/tor.1.txt | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/doc/tor.1.txt b/doc/tor.1.txt index 5727ec3..5dc4bc8 100644 --- a/doc/tor.1.txt +++ b/doc/tor.1.txt @@ -1431,7 +1431,9 @@ is non-zero): that they are in the same \'family', Tor clients will not use them in the same circuit. (Each server only needs to list the other servers in its family; it doesn't need to list itself, but it won't hurt.) Do not list - any bridge relay as it would compromise its concealment. + any bridge relay as it would compromise its concealment. When listing a + node, it is preferable to do so as a fingerprint as opposed to a nickname + as fingerprints are a more reliable mechanism for identifying a node. **Nickname** __name__:: Set the server's nickname to \'name'. Nicknames must be between 1 and 19

1 0

[tor/maint-0.2.4] Tighten prose in 8590 manpage fix
by nickm＠torproject.org 28 Mar '13

28 Mar '13

commit cd5048d61e64371ea1f7756cefacd9e731f11002 Author: Nick Mathewson <nickm(a)torproject.org> Date: Wed Mar 27 21:58:07 2013 -0400 Tighten prose in 8590 manpage fix --- doc/tor.1.txt | 7 ++++--- 1 files changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/tor.1.txt b/doc/tor.1.txt index 5dc4bc8..c502c57 100644 --- a/doc/tor.1.txt +++ b/doc/tor.1.txt @@ -1431,9 +1431,10 @@ is non-zero): that they are in the same \'family', Tor clients will not use them in the same circuit. (Each server only needs to list the other servers in its family; it doesn't need to list itself, but it won't hurt.) Do not list - any bridge relay as it would compromise its concealment. When listing a - node, it is preferable to do so as a fingerprint as opposed to a nickname - as fingerprints are a more reliable mechanism for identifying a node. + any bridge relay as it would compromise its concealment. + + + When listing a node, it's better to list it by fingerprint than by + nickname: fingerprints are more reliable. **Nickname** __name__:: Set the server's nickname to \'name'. Nicknames must be between 1 and 19

1 0

[torbrowser/master] Update build instructions to mention cleaning components.
by mikeperry＠torproject.org 28 Mar '13

28 Mar '13

commit 1089ae38f1b2005882e4c7472192105d5af49448 Author: Mike Perry <mikeperry-git(a)fscked.org> Date: Sat Mar 16 13:35:30 2013 -0700 Update build instructions to mention cleaning components. --- docs/buildmachine_setups/linux-x86.txt | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/docs/buildmachine_setups/linux-x86.txt b/docs/buildmachine_setups/linux-x86.txt index 598ddb7..2015f5b 100644 --- a/docs/buildmachine_setups/linux-x86.txt +++ b/docs/buildmachine_setups/linux-x86.txt @@ -27,3 +27,12 @@ 12. make -f linux-alpha.mk build-all-binaries 13. make -f linux-alpha.mk compressed-bundle_en-US # or all-bundles + + +To clean the bundle directory (which includes the XPIs, but not the +compiled binaries): + make -f linux-alpha.mk clean + +If you need to rebuild selective components, you can try various clean +targets. For example, to clean firefox: + make -f linux-alpha.mk clean-build-firefox

1 0

[torbrowser/master] Bug 8529: Raise font count limits to improve gmail compose behavior
by mikeperry＠torproject.org 28 Mar '13

28 Mar '13

commit ca6bd331ac75b07dbfc8f8b2e3c086994a2b499a Author: Mike Perry <mikeperry-git(a)fscked.org> Date: Wed Mar 27 18:50:37 2013 -0700 Bug 8529: Raise font count limits to improve gmail compose behavior --- build-scripts/config/pound_tor.js | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/build-scripts/config/pound_tor.js b/build-scripts/config/pound_tor.js index b789b3a..ab98b46 100644 --- a/build-scripts/config/pound_tor.js +++ b/build-scripts/config/pound_tor.js @@ -45,7 +45,7 @@ pref("webgl.disable-extensions", true); pref("dom.battery.enabled", false); // fingerprinting due to differing OS implementations pref("dom.network.enabled",false); // fingerprinting due to differing OS implementations pref("browser.display.max_font_attempts",10); -pref("browser.display.max_font_count",5); +pref("browser.display.max_font_count",10); pref("general.appname.override", "Netscape"); pref("general.appversion.override", "5.0 (Windows)"); pref("general.buildID.override", "0");

1 0

[torbrowser/maint-2.4] Update build instructions to mention cleaning components.
by mikeperry＠torproject.org 28 Mar '13

28 Mar '13

commit 1089ae38f1b2005882e4c7472192105d5af49448 Author: Mike Perry <mikeperry-git(a)fscked.org> Date: Sat Mar 16 13:35:30 2013 -0700 Update build instructions to mention cleaning components. --- docs/buildmachine_setups/linux-x86.txt | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/docs/buildmachine_setups/linux-x86.txt b/docs/buildmachine_setups/linux-x86.txt index 598ddb7..2015f5b 100644 --- a/docs/buildmachine_setups/linux-x86.txt +++ b/docs/buildmachine_setups/linux-x86.txt @@ -27,3 +27,12 @@ 12. make -f linux-alpha.mk build-all-binaries 13. make -f linux-alpha.mk compressed-bundle_en-US # or all-bundles + + +To clean the bundle directory (which includes the XPIs, but not the +compiled binaries): + make -f linux-alpha.mk clean + +If you need to rebuild selective components, you can try various clean +targets. For example, to clean firefox: + make -f linux-alpha.mk clean-build-firefox

1 0

[torbrowser/maint-2.4] Bug 8529: Raise font count limits to improve gmail compose behavior
by mikeperry＠torproject.org 28 Mar '13

28 Mar '13

commit ca6bd331ac75b07dbfc8f8b2e3c086994a2b499a Author: Mike Perry <mikeperry-git(a)fscked.org> Date: Wed Mar 27 18:50:37 2013 -0700 Bug 8529: Raise font count limits to improve gmail compose behavior --- build-scripts/config/pound_tor.js | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/build-scripts/config/pound_tor.js b/build-scripts/config/pound_tor.js index b789b3a..ab98b46 100644 --- a/build-scripts/config/pound_tor.js +++ b/build-scripts/config/pound_tor.js @@ -45,7 +45,7 @@ pref("webgl.disable-extensions", true); pref("dom.battery.enabled", false); // fingerprinting due to differing OS implementations pref("dom.network.enabled",false); // fingerprinting due to differing OS implementations pref("browser.display.max_font_attempts",10); -pref("browser.display.max_font_count",5); +pref("browser.display.max_font_count",10); pref("general.appname.override", "Netscape"); pref("general.appversion.override", "5.0 (Windows)"); pref("general.buildID.override", "0");

1 0

[tor/master] Bug 6572: Use timestamp_created for liveness sanity checks.
by nickm＠torproject.org 28 Mar '13

28 Mar '13

commit 65c0489dd4f0e10230f5c2fbb772a58e03e939bb Author: Mike Perry <mikeperry-git(a)fscked.org> Date: Tue Mar 26 20:28:19 2013 -0700 Bug 6572: Use timestamp_created for liveness sanity checks. This should eliminate potential regressions caused by #7341. --- src/or/circuituse.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/or/circuituse.c b/src/or/circuituse.c index f02597e..14576f1 100644 --- a/src/or/circuituse.c +++ b/src/or/circuituse.c @@ -671,7 +671,7 @@ circuit_expire_building(void) circuit_purpose_to_string(victim->purpose)); } else if (circuit_build_times_count_close(&circ_times, first_hop_succeeded, - victim->timestamp_began.tv_sec)) { + victim->timestamp_created.tv_sec)) { circuit_build_times_set_timeout(&circ_times); } }

1 0