- tor-commits - lists.torproject.org

[tor/master] Add the heartbeat domain in log.c:domain_list[]
by nickm＠torproject.org 06 Jun '11

06 Jun '11

commit 9eab601f10958ad75b3aef0015f32fc339609054 Author: George Kadianakis <desnacked(a)gmail.com> Date: Sun Jun 5 21:27:53 2011 +0200 Add the heartbeat domain in log.c:domain_list[] so that parse_log_domain() doesn't fail. --- src/common/log.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/common/log.c b/src/common/log.c index abdce14..9740062 100644 --- a/src/common/log.c +++ b/src/common/log.c @@ -899,7 +899,7 @@ log_level_to_string(int level) static const char *domain_list[] = { "GENERAL", "CRYPTO", "NET", "CONFIG", "FS", "PROTOCOL", "MM", "HTTP", "APP", "CONTROL", "CIRC", "REND", "BUG", "DIR", "DIRSERV", - "OR", "EDGE", "ACCT", "HIST", "HANDSHAKE", NULL + "OR", "EDGE", "ACCT", "HIST", "HANDSHAKE", "HEARTBEAT", NULL }; /** Return a bitmask for the log domain for which domain is the name,

1 0

[tor/master] Detect insanely large circuit build state; don't give its length to rand_int
by nickm＠torproject.org 06 Jun '11

06 Jun '11

commit 42e4e156d95a1c28a666a5346d491c4ed71435dd Author: Nick Mathewson <nickm(a)torproject.org> Date: Wed Jun 1 12:12:01 2011 -0400 Detect insanely large circuit build state; don't give its length to rand_int --- changes/bug3306 | 4 ++++ src/or/circuitbuild.c | 10 +++++++++- 2 files changed, 13 insertions(+), 1 deletions(-) diff --git a/changes/bug3306 b/changes/bug3306 index b1bb103..f868a24 100644 --- a/changes/bug3306 +++ b/changes/bug3306 @@ -3,3 +3,7 @@ correctly. Previously, it accepted values up to UINT_MAX, but could return a negative number if given a value above INT_MAX+1. Found by George Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14. + + - Avoid a segfault when reading a malformed circuit build state + with more than INT_MAX entries. Found by wanoskarnet. Bugfix on + 0.2.2.4-alpha. diff --git a/src/or/circuitbuild.c b/src/or/circuitbuild.c index 3f08448..6d7e711 100644 --- a/src/or/circuitbuild.c +++ b/src/or/circuitbuild.c @@ -678,7 +678,15 @@ circuit_build_times_shuffle_and_store_array(circuit_build_times_t *cbt, log_notice(LD_CIRC, "The number of circuit times that this Tor version " "uses to calculate build times is less than the number stored " "in your state file. Decreasing the circuit time history from " - "%d to %d.", num_times, CBT_NCIRCUITS_TO_OBSERVE); + "%lu to %d.", (unsigned long)num_times, + CBT_NCIRCUITS_TO_OBSERVE); + } + + if (n > INT_MAX-1) { + log_warn(LD_CIRC, "For some insane reasons, you had %lu circuit build " + "observations in your state file. That's far too many; probably " + "there's a bug here.", (unsigned long)n); + n = INT_MAX-1; } /* This code can only be run on a compact array */

1 0

[tor/master] Check maximum properly in crypto_rand_int()
by nickm＠torproject.org 06 Jun '11

06 Jun '11

commit 5afab5ca197112b01135980d6cb3694a4519e3cf Author: Nick Mathewson <nickm(a)torproject.org> Date: Wed Jun 1 11:48:39 2011 -0400 Check maximum properly in crypto_rand_int() George Kadianakis notes that if you give crypto_rand_int() a value above INT_MAX, it can return a negative number, which is not what the documentation would imply. The simple solution is to assert that the input is in [1,INT_MAX+1]. If in the future we need a random-value function that can return values up to UINT_MAX, we can add one. Fixes bug 3306; bugfix on 0.2.2pre14. --- changes/bug3306 | 5 +++++ src/common/crypto.c | 5 +++-- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/changes/bug3306 b/changes/bug3306 new file mode 100644 index 0000000..b1bb103 --- /dev/null +++ b/changes/bug3306 @@ -0,0 +1,5 @@ + o Minor bugfixes: + - Make our crypto_rand_int() function check the value of its input + correctly. Previously, it accepted values up to UINT_MAX, but + could return a negative number if given a value above INT_MAX+1. + Found by George Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14. diff --git a/src/common/crypto.c b/src/common/crypto.c index d8e6619..851f11b 100644 --- a/src/common/crypto.c +++ b/src/common/crypto.c @@ -2145,13 +2145,14 @@ crypto_rand(char *to, size_t n) } /** Return a pseudorandom integer, chosen uniformly from the values - * between 0 and max-1. */ + * between 0 and max-1 inclusive. max must be between 1 and + * INT_MAX+1, inclusive. */ int crypto_rand_int(unsigned int max) { unsigned int val; unsigned int cutoff; - tor_assert(max < UINT_MAX); + tor_assert(max <= ((unsigned int)INT_MAX)+1); tor_assert(max > 0); /* don't div by 0 */ /* We ignore any values that are >= 'cutoff,' to avoid biasing the

1 0

[tor/master] Merge branch 'bug3306_nm_squashed' into maint-0.2.2
by nickm＠torproject.org 06 Jun '11

06 Jun '11

commit 9e3fc5f61685f937d76e60c5fa1781b80aa5bf68 Merge: 83e3975 42e4e15 Author: Nick Mathewson <nickm(a)torproject.org> Date: Mon Jun 6 16:18:24 2011 -0400 Merge branch 'bug3306_nm_squashed' into maint-0.2.2 changes/bug3306 | 9 +++++++++ src/common/crypto.c | 5 +++-- src/or/circuitbuild.c | 10 +++++++++- 3 files changed, 21 insertions(+), 3 deletions(-)

1 0

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

06 Jun '11

commit 8cd5a3c1865c2115d88b08041a27e2cfdd7d24d2 Merge: 96da10a 9e3fc5f Author: Nick Mathewson <nickm(a)torproject.org> Date: Mon Jun 6 16:20:22 2011 -0400 Merge remote-tracking branch 'origin/maint-0.2.2' changes/bug3306 | 9 +++++++++ src/common/crypto.c | 5 +++-- src/or/circuitbuild.c | 10 +++++++++- 3 files changed, 21 insertions(+), 3 deletions(-)

1 0

[tor/maint-0.2.2] Detect insanely large circuit build state; don't give its length to rand_int
by nickm＠torproject.org 06 Jun '11

06 Jun '11

commit 42e4e156d95a1c28a666a5346d491c4ed71435dd Author: Nick Mathewson <nickm(a)torproject.org> Date: Wed Jun 1 12:12:01 2011 -0400 Detect insanely large circuit build state; don't give its length to rand_int --- changes/bug3306 | 4 ++++ src/or/circuitbuild.c | 10 +++++++++- 2 files changed, 13 insertions(+), 1 deletions(-) diff --git a/changes/bug3306 b/changes/bug3306 index b1bb103..f868a24 100644 --- a/changes/bug3306 +++ b/changes/bug3306 @@ -3,3 +3,7 @@ correctly. Previously, it accepted values up to UINT_MAX, but could return a negative number if given a value above INT_MAX+1. Found by George Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14. + + - Avoid a segfault when reading a malformed circuit build state + with more than INT_MAX entries. Found by wanoskarnet. Bugfix on + 0.2.2.4-alpha. diff --git a/src/or/circuitbuild.c b/src/or/circuitbuild.c index 3f08448..6d7e711 100644 --- a/src/or/circuitbuild.c +++ b/src/or/circuitbuild.c @@ -678,7 +678,15 @@ circuit_build_times_shuffle_and_store_array(circuit_build_times_t *cbt, log_notice(LD_CIRC, "The number of circuit times that this Tor version " "uses to calculate build times is less than the number stored " "in your state file. Decreasing the circuit time history from " - "%d to %d.", num_times, CBT_NCIRCUITS_TO_OBSERVE); + "%lu to %d.", (unsigned long)num_times, + CBT_NCIRCUITS_TO_OBSERVE); + } + + if (n > INT_MAX-1) { + log_warn(LD_CIRC, "For some insane reasons, you had %lu circuit build " + "observations in your state file. That's far too many; probably " + "there's a bug here.", (unsigned long)n); + n = INT_MAX-1; } /* This code can only be run on a compact array */

1 0

[tor/maint-0.2.2] Check maximum properly in crypto_rand_int()
by nickm＠torproject.org 06 Jun '11

06 Jun '11

commit 5afab5ca197112b01135980d6cb3694a4519e3cf Author: Nick Mathewson <nickm(a)torproject.org> Date: Wed Jun 1 11:48:39 2011 -0400 Check maximum properly in crypto_rand_int() George Kadianakis notes that if you give crypto_rand_int() a value above INT_MAX, it can return a negative number, which is not what the documentation would imply. The simple solution is to assert that the input is in [1,INT_MAX+1]. If in the future we need a random-value function that can return values up to UINT_MAX, we can add one. Fixes bug 3306; bugfix on 0.2.2pre14. --- changes/bug3306 | 5 +++++ src/common/crypto.c | 5 +++-- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/changes/bug3306 b/changes/bug3306 new file mode 100644 index 0000000..b1bb103 --- /dev/null +++ b/changes/bug3306 @@ -0,0 +1,5 @@ + o Minor bugfixes: + - Make our crypto_rand_int() function check the value of its input + correctly. Previously, it accepted values up to UINT_MAX, but + could return a negative number if given a value above INT_MAX+1. + Found by George Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14. diff --git a/src/common/crypto.c b/src/common/crypto.c index d8e6619..851f11b 100644 --- a/src/common/crypto.c +++ b/src/common/crypto.c @@ -2145,13 +2145,14 @@ crypto_rand(char *to, size_t n) } /** Return a pseudorandom integer, chosen uniformly from the values - * between 0 and max-1. */ + * between 0 and max-1 inclusive. max must be between 1 and + * INT_MAX+1, inclusive. */ int crypto_rand_int(unsigned int max) { unsigned int val; unsigned int cutoff; - tor_assert(max < UINT_MAX); + tor_assert(max <= ((unsigned int)INT_MAX)+1); tor_assert(max > 0); /* don't div by 0 */ /* We ignore any values that are >= 'cutoff,' to avoid biasing the

1 0

[tor/maint-0.2.2] Merge branch 'bug3306_nm_squashed' into maint-0.2.2
by nickm＠torproject.org 06 Jun '11

06 Jun '11

commit 9e3fc5f61685f937d76e60c5fa1781b80aa5bf68 Merge: 83e3975 42e4e15 Author: Nick Mathewson <nickm(a)torproject.org> Date: Mon Jun 6 16:18:24 2011 -0400 Merge branch 'bug3306_nm_squashed' into maint-0.2.2 changes/bug3306 | 9 +++++++++ src/common/crypto.c | 5 +++-- src/or/circuitbuild.c | 10 +++++++++- 3 files changed, 21 insertions(+), 3 deletions(-)

1 0

r24810: {projects} give my crypto 2011 paper a cc-by license. try not to screw (projects/articles/crypto2011)
by Roger Dingledine 05 Jun '11

05 Jun '11

Author: arma Date: 2011-06-06 03:47:46 +0000 (Mon, 06 Jun 2011) New Revision: 24810 Modified: projects/articles/crypto2011/crypto2011-tor.bib projects/articles/crypto2011/crypto2011-tor.pdf projects/articles/crypto2011/crypto2011-tor.tex Log: give my crypto 2011 paper a cc-by license. try not to screw up the rest of the formatting too much. Modified: projects/articles/crypto2011/crypto2011-tor.bib =================================================================== --- projects/articles/crypto2011/crypto2011-tor.bib 2011-06-06 00:58:54 UTC (rev 24809) +++ projects/articles/crypto2011/crypto2011-tor.bib 2011-06-06 03:47:46 UTC (rev 24810) @@ -1,10 +1,9 @@ @inproceedings{dingledine2004tor, author = {Roger Dingledine and Nick Mathewson and Paul Syverson}, title = {Tor: The Second-Generation Onion Router}, - booktitle = {Proceedings of the 13th USENIX Security Symposium}, + booktitle = {Proc 13th USENIX Security Symposium}, year = {2004}, month = {August}, - pages = {303--320}, } @inproceedings{mccoy2008shining, Modified: projects/articles/crypto2011/crypto2011-tor.pdf =================================================================== (Binary files differ) Modified: projects/articles/crypto2011/crypto2011-tor.tex =================================================================== --- projects/articles/crypto2011/crypto2011-tor.tex 2011-06-06 00:58:54 UTC (rev 24809) +++ projects/articles/crypto2011/crypto2011-tor.tex 2011-06-06 03:47:46 UTC (rev 24810) @@ -6,6 +6,9 @@ \usepackage{color} \pagestyle{empty} +\long\def\symbolfootnote[#1]#2{\begingroup% +\def\thefootnote{\fnsymbol{footnote}}\footnote[#1]{#2}\endgroup} + %\usepackage[pdftex,% % breaklinks=true,% % colorlinks=true,% @@ -72,8 +75,13 @@ research, please talk to us (https://torproject.org/research) so we can explain what's available and help interpret your results. -\subsection*{Some open questions from the anonymity field} +\subsubsection*{Some open questions from the anonymity field.} +% this is smashed into the middle of the paper so the footnote shows +% up on page 2 rather than ruining the formatting on page 1. +\symbolfootnote[0]{This work is available under the Creative Commons +Attribution (CC-BY) License.} + Here are a few examples of open anonymity and blocking-resistance problems:

1 0

[torbrowser/maint-2.2] add that windows suite to the changelog
by erinn＠torproject.org 05 Jun '11

05 Jun '11

commit 58f8bbb9f75da2e183e8b00f28b0ced26bce9171 Author: Erinn Clark <erinn(a)torproject.org> Date: Sun Jun 5 21:10:54 2011 -0300 add that windows suite to the changelog --- build-scripts/osx.mk | 1 - changelog.win-2.2 | 2 +- 2 files changed, 1 insertions(+), 2 deletions(-) diff --git a/build-scripts/osx.mk b/build-scripts/osx.mk index 47ab77f..8bee9e1 100644 --- a/build-scripts/osx.mk +++ b/build-scripts/osx.mk @@ -213,7 +213,6 @@ all-compressed-bundles: compressed-bundle_ar \ ## clean: - rm -fr $(DISTDIR) rm -fr *.app rm -fr $(DEST) *.stamp rm -f *~ diff --git a/changelog.win-2.2 b/changelog.win-2.2 index d77cab1..2acec07 100644 --- a/changelog.win-2.2 +++ b/changelog.win-2.2 @@ -1,4 +1,4 @@ -Tor Browser Bundle (2.2.27-1) alpha; suite=osx +Tor Browser Bundle (2.2.27-1) alpha; suite=windows * Update Tor to 0.2.2.27-beta * Update HTTPS Everywhere to 0.9.9.development.5

1 0