October 2011 - tor-commits - lists.torproject.org

[tor/master] Merge remote-tracking branch 'origin/maint-0.2.2'
by nickm＠torproject.org 28 Oct '11

28 Oct '11

commit a2517fa77c066e34d58fd50f930529b84e30946e Merge: ba91272 f6b1dc2 Author: Nick Mathewson <nickm(a)torproject.org> Date: Fri Oct 28 09:53:23 2011 -0400 Merge remote-tracking branch 'origin/maint-0.2.2' changes/bug4331 | 4 ++++ src/or/hibernate.c | 2 +- 2 files changed, 5 insertions(+), 1 deletions(-)

1 0

[tor/maint-0.2.2] Fix typo, spotted by tmpname0901. Thanks!
by nickm＠torproject.org 28 Oct '11

28 Oct '11

commit f6b1dc2805ce23d4f7fddcf2714b13f718d20038 Author: Sebastian Hahn <sebastian(a)torproject.org> Date: Fri Oct 28 11:19:16 2011 +0200 Fix typo, spotted by tmpname0901. Thanks! --- changes/bug4331 | 4 ++++ src/or/hibernate.c | 2 +- 2 files changed, 5 insertions(+), 1 deletions(-) diff --git a/changes/bug4331 b/changes/bug4331 new file mode 100644 index 0000000..011238a --- /dev/null +++ b/changes/bug4331 @@ -0,0 +1,4 @@ + o Trivial fixes: + - Fixed a typo in a … [View More]

1 0

[torflow/master] Remove the early consensus fetching options.
by mikeperry＠torproject.org 28 Oct '11

28 Oct '11

commit 6427947869151b93a56bf91f44aadc093cafe919 Author: Mike Perry <mikeperry-git(a)fscked.org> Date: Thu Oct 27 18:34:55 2011 -0700 Remove the early consensus fetching options. Too much consensus control port activity causes scanners not to make progress, and certainly doesn't help disk io issues. --- NetworkScanners/BwAuthority/data/tor/torrc | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/NetworkScanners/BwAuthority/data/tor/torrc b/… [View More]

1 0

[tor/master] bump maint-0.2.2 to 0.2.2.34-dev
by arma＠torproject.org 28 Oct '11

28 Oct '11

commit 48bafb47acc19c2bee54f0731a73b8b2fc980359 Author: Roger Dingledine <arma(a)torproject.org> Date: Thu Oct 27 20:50:48 2011 -0400 bump maint-0.2.2 to 0.2.2.34-dev --- configure.in | 2 +- contrib/tor-mingw.nsi.in | 2 +- src/win32/orconfig.h | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/configure.in b/configure.in index 047545d..a9339cc 100644 --- a/configure.in +++ b/configure.in @@ -4,7 +4,7 @@ dnl Copyright (c) 2007-2008, … [View More]

1 0

[tor/master] Merge branch 'maint-0.2.2'
by arma＠torproject.org 28 Oct '11

28 Oct '11

commit ba91272dedf9bacd7e7ef176c8a549f3aa5da452 Merge: 6258013 48bafb4 Author: Roger Dingledine <arma(a)torproject.org> Date: Thu Oct 27 20:53:17 2011 -0400 Merge branch 'maint-0.2.2'

1 0

[tor/release-0.2.2] bump maint-0.2.2 to 0.2.2.34-dev
by arma＠torproject.org 28 Oct '11

28 Oct '11

commit 48bafb47acc19c2bee54f0731a73b8b2fc980359 Author: Roger Dingledine <arma(a)torproject.org> Date: Thu Oct 27 20:50:48 2011 -0400 bump maint-0.2.2 to 0.2.2.34-dev --- configure.in | 2 +- contrib/tor-mingw.nsi.in | 2 +- src/win32/orconfig.h | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/configure.in b/configure.in index 047545d..a9339cc 100644 --- a/configure.in +++ b/configure.in @@ -4,7 +4,7 @@ dnl Copyright (c) 2007-2008, … [View More]

1 0

[tor/release-0.2.2] Merge branch 'maint-0.2.2' into release-0.2.2
by arma＠torproject.org 28 Oct '11

28 Oct '11

commit f0e1ee98af44310721fa871146ea72459e02f01c Merge: 30722de 48bafb4 Author: Roger Dingledine <arma(a)torproject.org> Date: Thu Oct 27 20:52:54 2011 -0400 Merge branch 'maint-0.2.2' into release-0.2.2

1 0

[tor/maint-0.2.2] bump maint-0.2.2 to 0.2.2.34-dev
by arma＠torproject.org 28 Oct '11

28 Oct '11

commit 48bafb47acc19c2bee54f0731a73b8b2fc980359 Author: Roger Dingledine <arma(a)torproject.org> Date: Thu Oct 27 20:50:48 2011 -0400 bump maint-0.2.2 to 0.2.2.34-dev --- configure.in | 2 +- contrib/tor-mingw.nsi.in | 2 +- src/win32/orconfig.h | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/configure.in b/configure.in index 047545d..a9339cc 100644 --- a/configure.in +++ b/configure.in @@ -4,7 +4,7 @@ dnl Copyright (c) 2007-2008, … [View More]

1 0

[tor/release-0.2.1] minor cleanup on already published changelog text
by arma＠torproject.org 28 Oct '11

28 Oct '11

commit e234c1cd237af464f53d8b318ce72aef2b7439aa Author: Roger Dingledine <arma(a)torproject.org> Date: Thu Oct 27 20:16:33 2011 -0400 minor cleanup on already published changelog text --- ChangeLog | 10 +++++----- ReleaseNotes | 10 +++++----- 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/ChangeLog b/ChangeLog index 5c85e92..3ff5326 100644 --- a/ChangeLog +++ b/ChangeLog @@ -17,11 +17,11 @@ Changes in version 0.2.1.31 - 2011-10-26 o Privacy/… [View More]anonymity fixes (also included in 0.2.2.x): - Clients and bridges no longer send TLS certificate chains on - outgoing OR connections. Previously, each client or bridge - would use the same cert chain for all outgoing OR connections - for up to 24 hours, which allowed any relay that the client or - bridge contacted to determine which entry guards it is using. - Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by frosty_un. + outgoing OR connections. Previously, each client or bridge would + use the same cert chain for all outgoing OR connections until + its IP address changes, which allowed any relay that the client + or bridge contacted to determine which entry guards it is using. + Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un". - If a relay receives a CREATE_FAST cell on a TLS connection, it no longer considers that connection as suitable for satisfying a circuit EXTEND request. Now relays can protect clients from the diff --git a/ReleaseNotes b/ReleaseNotes index b9d32eb..e3de631 100644 --- a/ReleaseNotes +++ b/ReleaseNotes @@ -22,11 +22,11 @@ Changes in version 0.2.1.31 - 2011-10-26 o Privacy/anonymity fixes (also included in 0.2.2.x): - Clients and bridges no longer send TLS certificate chains on - outgoing OR connections. Previously, each client or bridge - would use the same cert chain for all outgoing OR connections - for up to 24 hours, which allowed any relay that the client or - bridge contacted to determine which entry guards it is using. - Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by frosty_un. + outgoing OR connections. Previously, each client or bridge would + use the same cert chain for all outgoing OR connections until + its IP address changes, which allowed any relay that the client + or bridge contacted to determine which entry guards it is using. + Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un". - If a relay receives a CREATE_FAST cell on a TLS connection, it no longer considers that connection as suitable for satisfying a circuit EXTEND request. Now relays can protect clients from the [View Less]

1 0

[tor/master] find all those stanzas in master too
by arma＠torproject.org 28 Oct '11

28 Oct '11

commit 6258013e412dbabcb2482648d84b6199381740fd Author: Roger Dingledine <arma(a)torproject.org> Date: Thu Oct 27 20:15:50 2011 -0400 find all those stanzas in master too --- ChangeLog | 26 +++++++++++++------------- ReleaseNotes | 18 +++++++++--------- 2 files changed, 22 insertions(+), 22 deletions(-) diff --git a/ChangeLog b/ChangeLog index c721e70..73e83f0 100644 --- a/ChangeLog +++ b/ChangeLog @@ -16,10 +16,10 @@ Changes in version 0.2.3.6-alpha - 2011-10-26 o … [View More]Privacy/anonymity fixes (clients): - Clients and bridges no longer send TLS certificate chains on - outgoing OR connections. Previously, each client or bridge - would use the same cert chain for all outgoing OR connections - for up to 24 hours, which allowed any relay that the client or - bridge contacted to determine which entry guards it is using. + outgoing OR connections. Previously, each client or bridge would + use the same cert chain for all outgoing OR connections until + its IP address changes, which allowed any relay that the client + or bridge contacted to determine which entry guards it is using. Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un". - If a relay receives a CREATE_FAST cell on a TLS connection, it no longer considers that connection as suitable for satisfying a @@ -160,10 +160,10 @@ Changes in version 0.2.2.34 - 2011-10-26 o Privacy/anonymity fixes (clients): - Clients and bridges no longer send TLS certificate chains on - outgoing OR connections. Previously, each client or bridge - would use the same cert chain for all outgoing OR connections - for up to 24 hours, which allowed any relay that the client or - bridge contacted to determine which entry guards it is using. + outgoing OR connections. Previously, each client or bridge would + use the same cert chain for all outgoing OR connections until + its IP address changes, which allowed any relay that the client + or bridge contacted to determine which entry guards it is using. Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un". - If a relay receives a CREATE_FAST cell on a TLS connection, it no longer considers that connection as suitable for satisfying a @@ -264,11 +264,11 @@ Changes in version 0.2.1.31 - 2011-10-26 o Privacy/anonymity fixes (also included in 0.2.2.x): - Clients and bridges no longer send TLS certificate chains on - outgoing OR connections. Previously, each client or bridge - would use the same cert chain for all outgoing OR connections - for up to 24 hours, which allowed any relay that the client or - bridge contacted to determine which entry guards it is using. - Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by frosty_un. + outgoing OR connections. Previously, each client or bridge would + use the same cert chain for all outgoing OR connections until + its IP address changes, which allowed any relay that the client + or bridge contacted to determine which entry guards it is using. + Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un". - If a relay receives a CREATE_FAST cell on a TLS connection, it no longer considers that connection as suitable for satisfying a circuit EXTEND request. Now relays can protect clients from the diff --git a/ReleaseNotes b/ReleaseNotes index 879028a..cbc8f0e 100644 --- a/ReleaseNotes +++ b/ReleaseNotes @@ -32,10 +32,10 @@ Changes in version 0.2.2.34 - 2011-10-26 o Privacy/anonymity fixes (clients): - Clients and bridges no longer send TLS certificate chains on - outgoing OR connections. Previously, each client or bridge - would use the same cert chain for all outgoing OR connections - for up to 24 hours, which allowed any relay that the client or - bridge contacted to determine which entry guards it is using. + outgoing OR connections. Previously, each client or bridge would + use the same cert chain for all outgoing OR connections until + its IP address changes, which allowed any relay that the client + or bridge contacted to determine which entry guards it is using. Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un". - If a relay receives a CREATE_FAST cell on a TLS connection, it no longer considers that connection as suitable for satisfying a @@ -136,11 +136,11 @@ Changes in version 0.2.1.31 - 2011-10-26 o Privacy/anonymity fixes (also included in 0.2.2.x): - Clients and bridges no longer send TLS certificate chains on - outgoing OR connections. Previously, each client or bridge - would use the same cert chain for all outgoing OR connections - for up to 24 hours, which allowed any relay that the client or - bridge contacted to determine which entry guards it is using. - Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by frosty_un. + outgoing OR connections. Previously, each client or bridge would + use the same cert chain for all outgoing OR connections until + its IP address changes, which allowed any relay that the client + or bridge contacted to determine which entry guards it is using. + Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un". - If a relay receives a CREATE_FAST cell on a TLS connection, it no longer considers that connection as suitable for satisfying a circuit EXTEND request. Now relays can protect clients from the [View Less]

1 0