February 2012 - tor-commits - lists.torproject.org

r25392: {website} make it clearer you need pkg-config (website/trunk/projects/en)
by Roger Dingledine 10 Feb '12

10 Feb '12

Author: arma Date: 2012-02-10 07:21:37 +0000 (Fri, 10 Feb 2012) New Revision: 25392 Modified: website/trunk/projects/en/obfsproxy-instructions.wml Log: make it clearer you need pkg-config Modified: website/trunk/projects/en/obfsproxy-instructions.wml =================================================================== --- website/trunk/projects/en/obfsproxy-instructions.wml 2012-02-10 06:13:21 UTC (rev 25391) +++ website/trunk/projects/en/obfsproxy-instructions.wml 2012-02-10 07:21:37 UTC (rev 25392) @@ -22,9 +22,10 @@ - You will need a C compiler (gcc), the Autotools - build system, the git revision control system, - libevent-2 and the development headers of + You will need a C compiler (gcc), the autoconf + and autotools build system, the git revision + control system, pkg-config and libtool, + libevent-2 and its headers, and the development headers of OpenSSL.

1 0

r25391: {website} link to build-from-source instructions (website/trunk/projects/en)
by Roger Dingledine 10 Feb '12

10 Feb '12

Author: arma Date: 2012-02-10 06:13:21 +0000 (Fri, 10 Feb 2012) New Revision: 25391 Modified: website/trunk/projects/en/obfsproxy-instructions.wml Log: link to build-from-source instructions Modified: website/trunk/projects/en/obfsproxy-instructions.wml =================================================================== --- website/trunk/projects/en/obfsproxy-instructions.wml 2012-02-10 05:53:58 UTC (rev 25390) +++ website/trunk/projects/en/obfsproxy-instructions.wml 2012-02-10 06:13:21 UTC (rev 25391) @@ -33,10 +33,12 @@ <tt># apt-get install autoconf autotools-dev gcc git pkg-config libtool libevent-2.0-5 libevent-dev libevent-openssl-2.0-5 libssl-dev</tt> - If you're on a more stable Linux, you can either <a + + If you're on a more stable Linux, you can either <a href="https://trac.torproject.org/projects/tor/ticket/5009#comment:9">try - our experimental backport debs</a> or <a href="">build libevent2 from - source</a>. + our experimental backport libevent2 debs</a> or <a + href="https://trac.torproject.org/projects/tor/ticket/5009#comment:17">build + libevent2 from source</a>.

1 0

r25390: {website} explain further dependencies point to libevent 2 debs explai (website/trunk/projects/en)
by Roger Dingledine 10 Feb '12

10 Feb '12

Author: arma Date: 2012-02-10 05:53:58 +0000 (Fri, 10 Feb 2012) New Revision: 25390 Modified: website/trunk/projects/en/obfsproxy-instructions.wml Log: explain further dependencies point to libevent 2 debs explain that you don't need to install obfsproxy as root if you don't want to. Modified: website/trunk/projects/en/obfsproxy-instructions.wml =================================================================== --- website/trunk/projects/en/obfsproxy-instructions.wml 2012-02-10 05:34:57 UTC (rev 25389) +++ website/trunk/projects/en/obfsproxy-instructions.wml 2012-02-10 05:53:58 UTC (rev 25390) @@ -29,10 +29,16 @@ - In a Linux system using the APT package manager you could do: - <tt># apt-get install autotools-dev gcc git libevent-2.0-5 libevent-dev libevent-openssl-2.0-5 libssl-dev</tt> + On Debian testing or Ubuntu oneiric, you could do: + <tt># apt-get install autoconf autotools-dev gcc git pkg-config libtool libevent-2.0-5 libevent-dev libevent-openssl-2.0-5 libssl-dev</tt> + If you're on a more stable Linux, you can either <a + href="https://trac.torproject.org/projects/tor/ticket/5009#comment:9">try + our experimental backport debs</a> or <a href="">build libevent2 from + source</a>. + + Clone obfsproxy from its git repository: <tt>$ git clone https://git.torproject.org/obfsproxy.git</tt> @@ -47,11 +53,18 @@ - And then as root install obfsproxy in your system: + Optionally, as root install obfsproxy in your + system: <tt># make install</tt> + If you prefer not to install obfsproxy as root, you can instead + just modify the Transport lines in your torrc file (explained below) + to point to your obfsproxy binary. + + + You will need Tor 0.2.3.11-alpha or later.

1 0

r25389: {website} early guesses are that you need the libevent-dev deb too. no (website/trunk/projects/en)
by Roger Dingledine 10 Feb '12

10 Feb '12

Author: arma Date: 2012-02-10 05:34:57 +0000 (Fri, 10 Feb 2012) New Revision: 25389 Modified: website/trunk/projects/en/obfsproxy-instructions.wml Log: early guesses are that you need the libevent-dev deb too. no idea if installing "libevent-2.0-5 libevent-dev" will get you what you want. Modified: website/trunk/projects/en/obfsproxy-instructions.wml =================================================================== --- website/trunk/projects/en/obfsproxy-instructions.wml 2012-02-10 05:23:44 UTC (rev 25388) +++ website/trunk/projects/en/obfsproxy-instructions.wml 2012-02-10 05:34:57 UTC (rev 25389) @@ -30,7 +30,7 @@ In a Linux system using the APT package manager you could do: - <tt># apt-get install autotools-dev gcc git libevent-2.0-5 libevent-openssl-2.0-5 libssl-dev</tt> + <tt># apt-get install autotools-dev gcc git libevent-2.0-5 libevent-dev libevent-openssl-2.0-5 libssl-dev</tt>

1 0

r25388: {website} point people at the 'running a tor bridge' section (website/trunk/projects/en)
by Roger Dingledine 10 Feb '12

10 Feb '12

Author: arma Date: 2012-02-10 05:23:44 +0000 (Fri, 10 Feb 2012) New Revision: 25388 Modified: website/trunk/projects/en/obfsproxy-instructions.wml Log: point people at the 'running a tor bridge' section Modified: website/trunk/projects/en/obfsproxy-instructions.wml =================================================================== --- website/trunk/projects/en/obfsproxy-instructions.wml 2012-02-10 04:06:28 UTC (rev 25387) +++ website/trunk/projects/en/obfsproxy-instructions.wml 2012-02-10 05:23:44 UTC (rev 25388) @@ -94,13 +94,13 @@ - Add the appropriate lines to your <a href="<page docs/faq>#torrc">tor + Configure your Tor to <a href="<page docs/bridges>#RunningABridge">be + a bridge</a> (e.g. by setting "ORPort 9001" and "BridgeRelay 1"). Then + add this new line to your <a href="<page docs/faq>#torrc">tor configuration file</a>: - <tt> ORPort 9001 </tt> - <tt> BridgeRelay 1 </tt> <tt> ServerTransportPlugin obfs2 exec /usr/local/bin/obfsproxy --managed </tt>

1 0

r25387: {website} bridges need to set orport or they'll refuse to start (website/trunk/projects/en)
by Roger Dingledine 10 Feb '12

10 Feb '12

Author: arma Date: 2012-02-10 04:06:28 +0000 (Fri, 10 Feb 2012) New Revision: 25387 Modified: website/trunk/projects/en/obfsproxy-instructions.wml Log: bridges need to set orport or they'll refuse to start Modified: website/trunk/projects/en/obfsproxy-instructions.wml =================================================================== --- website/trunk/projects/en/obfsproxy-instructions.wml 2012-02-10 02:40:15 UTC (rev 25386) +++ website/trunk/projects/en/obfsproxy-instructions.wml 2012-02-10 04:06:28 UTC (rev 25387) @@ -99,6 +99,7 @@ + <tt> ORPort 9001 </tt> <tt> BridgeRelay 1 </tt> <tt> ServerTransportPlugin obfs2 exec /usr/local/bin/obfsproxy --managed </tt>

1 0

r25386: {website} make it clearer that you need to find an obfsproxy address s (website/trunk/projects/en)
by Roger Dingledine 10 Feb '12

10 Feb '12

Author: arma Date: 2012-02-10 02:40:15 +0000 (Fri, 10 Feb 2012) New Revision: 25386 Modified: website/trunk/projects/en/obfsproxy-instructions.wml Log: make it clearer that you need to find an obfsproxy address somehow. also change the example one to one that (currently) works. Modified: website/trunk/projects/en/obfsproxy-instructions.wml =================================================================== --- website/trunk/projects/en/obfsproxy-instructions.wml 2012-02-09 23:58:38 UTC (rev 25385) +++ website/trunk/projects/en/obfsproxy-instructions.wml 2012-02-10 02:40:15 UTC (rev 25386) @@ -61,18 +61,20 @@ - Add the appropriate lines to your <a href="<page docs/faq>#torrc">tor - configuration file</a>: + First, you need to learn the address of a bridge that supports + obfsproxy. If you don't know any, try asking a friend to set one + up for you. Then the appropriate lines to your <a href="<page + docs/faq>#torrc">tor configuration file</a>: <tt> UseBridges 1 </tt> - <tt> Bridge obfs2 192.0.2.34:34545 </tt> + <tt> Bridge obfs2 128.31.0.34:1051 </tt> <tt> ClientTransportPlugin obfs2 exec /usr/local/bin/obfsproxy --managed </tt> - Don't forget to replace 192.0.2.34:34545 with the IP address + Don't forget to replace 128.31.0.34:1051 with the IP address and port that the bridge's obfsproxy is listening on.

1 0

[flashproxy/master] Document that the experiments require Firefox 8.
by dcf＠torproject.org 10 Feb '12

10 Feb '12

commit 699fac3984e64cc7678b86578ca20065c89738b6 Author: David Fifield <david(a)bamsoftware.com> Date: Tue Feb 7 00:44:44 2012 -0800 Document that the experiments require Firefox 8. Firefox 9 changed the meaning of the -no-remote option. Previously, it meant "don't connect to any already running Firefox, but start a new instance." Now it additionally means "don't accept any future -remote commands in this new instance." This is broken for the experiments, which need the first behavior in order to start multiple instances with different profiles, but can't have the second behavior because the instances need to be driven by -remote. This is the bug that led to the change in the meaning of -no-remote: "-no-remote browser accepts remote commands" https://bugzilla.mozilla.org/show_bug.cgi?id=650078 There are other bugs that propose to restore some way to get the old behavior in a future version. "split -new-instance flag out of existing -no-remote flag" https://bugzilla.mozilla.org/show_bug.cgi?id=716110 Another related bug number: "Firefox 9 Fails To Correctly Use -new-window" https://bugzilla.mozilla.org/show_bug.cgi?id=703021 --- experiments/README | 8 ++++++-- 1 files changed, 6 insertions(+), 2 deletions(-) diff --git a/experiments/README b/experiments/README index ff8b416..bd814dd 100644 --- a/experiments/README +++ b/experiments/README @@ -4,17 +4,21 @@ proxy. == Preparation You need to have installed certain software before running the tests. - Firefox + Firefox 8.0.1 socat Wget Python thttpd Flash Player -Firefox, socat, Wget, and Python are easily installed on most GNU/Linux +socat, Wget, and Python are easily installed on most GNU/Linux distributions. thttpd can be compiled from the packages at http://acme.com/software/thttpd/. A debug version of Flash Player can be downloaded from http://www.adobe.com/support/flashplayer/downloads.html. +Firefox versions 9 and 10 will not work; these versions have a change to +the -no-remote option that prevents the tests from running. This is +supposed to be fixed in version 11. + You need to create some dedicated Firefox profiles. Create profiles named flashexp1 and flashexp2 by running firefox -ProfileManager -no-remote

1 0

[flashproxy/master] Limit retries to 1000 to halt runaways.
by dcf＠torproject.org 10 Feb '12

10 Feb '12

commit d7d69baec734fdaad2c50a24cf11916854c44247 Author: David Fifield <david(a)bamsoftware.com> Date: Tue Feb 7 09:46:45 2012 -0800 Limit retries to 1000 to halt runaways. --- experiments/switching/local-http-alternating.sh | 4 ++-- experiments/switching/local-http-constant.sh | 4 ++-- experiments/switching/remote-tor-alternating.sh | 2 +- experiments/switching/remote-tor-constant.sh | 4 ++-- experiments/switching/remote-tor-direct.sh | 4 ++-- 5 files changed, 9 insertions(+), 9 deletions(-) diff --git a/experiments/switching/local-http-alternating.sh b/experiments/switching/local-http-alternating.sh index 696f1d5..08cca91 100755 --- a/experiments/switching/local-http-alternating.sh +++ b/experiments/switching/local-http-alternating.sh @@ -60,7 +60,7 @@ visible_sleep 2 if [ -n "$OUTPUT_FILENAME" ]; then - real_time wget http://127.0.0.1:2000/dump --wait=0 --waitretry=0 -t 0 -O /dev/null >> "$OUTPUT_FILENAME" + real_time wget http://127.0.0.1:2000/dump --wait=0 --waitretry=0 -t 1000 -O /dev/null >> "$OUTPUT_FILENAME" else - real_time wget http://127.0.0.1:2000/dump --wait=0 --waitretry=0 -t 0 -O /dev/null + real_time wget http://127.0.0.1:2000/dump --wait=0 --waitretry=0 -t 1000 -O /dev/null fi diff --git a/experiments/switching/local-http-constant.sh b/experiments/switching/local-http-constant.sh index c1a52f8..ff73c2a 100755 --- a/experiments/switching/local-http-constant.sh +++ b/experiments/switching/local-http-constant.sh @@ -54,7 +54,7 @@ PIDS_TO_KILL+=($!) visible_sleep 2 if [ -n "$OUTPUT_FILENAME" ]; then - real_time wget http://127.0.0.1:2000/dump --wait=0 --waitretry=0 -t 0 -O /dev/null >> "$OUTPUT_FILENAME" + real_time wget http://127.0.0.1:2000/dump --wait=0 --waitretry=0 -t 1000 -O /dev/null >> "$OUTPUT_FILENAME" else - real_time wget http://127.0.0.1:2000/dump --wait=0 --waitretry=0 -t 0 -O /dev/null + real_time wget http://127.0.0.1:2000/dump --wait=0 --waitretry=0 -t 1000 -O /dev/null fi diff --git a/experiments/switching/remote-tor-alternating.sh b/experiments/switching/remote-tor-alternating.sh index 26070d9..2dcfbcc 100755 --- a/experiments/switching/remote-tor-alternating.sh +++ b/experiments/switching/remote-tor-alternating.sh @@ -57,7 +57,7 @@ PIDS_TO_KILL+=($!) visible_sleep 15 repeat_download() { - until torify wget http://torperf.torproject.org/.5mbfile --wait=0 --waitretry=0 -c -t 0 -O "$DATA_FILE_NAME"; do + until torify wget http://torperf.torproject.org/.5mbfile --wait=0 --waitretry=0 -c -t 1000 -O "$DATA_FILE_NAME"; do echo "retrying" done } diff --git a/experiments/switching/remote-tor-constant.sh b/experiments/switching/remote-tor-constant.sh index 939aef9..9d842c8 100755 --- a/experiments/switching/remote-tor-constant.sh +++ b/experiments/switching/remote-tor-constant.sh @@ -52,7 +52,7 @@ browser_goto "$PROFILE_1" "$PROXY_URL" visible_sleep 15 if [ -n "$OUTPUT_FILENAME" ]; then - real_time torify wget http://torperf.torproject.org/.5mbfile --wait=0 --waitretry=0 -c -t 0 -O "$DATA_FILE_NAME" >> "$OUTPUT_FILENAME" + real_time torify wget http://torperf.torproject.org/.5mbfile --wait=0 --waitretry=0 -c -t 1000 -O "$DATA_FILE_NAME" >> "$OUTPUT_FILENAME" else - real_time torify wget http://torperf.torproject.org/.5mbfile --wait=0 --waitretry=0 -c -t 0 -O "$DATA_FILE_NAME" + real_time torify wget http://torperf.torproject.org/.5mbfile --wait=0 --waitretry=0 -c -t 1000 -O "$DATA_FILE_NAME" fi diff --git a/experiments/switching/remote-tor-direct.sh b/experiments/switching/remote-tor-direct.sh index 1b6bdaa..9b0740c 100755 --- a/experiments/switching/remote-tor-direct.sh +++ b/experiments/switching/remote-tor-direct.sh @@ -31,7 +31,7 @@ PIDS_TO_KILL+=($!) visible_sleep 15 if [ -n "$OUTPUT_FILENAME" ]; then - real_time torify wget http://torperf.torproject.org/.5mbfile --wait=0 --waitretry=0 -c -t 0 -O "$DATA_FILE_NAME" >> "$OUTPUT_FILENAME" + real_time torify wget http://torperf.torproject.org/.5mbfile --wait=0 --waitretry=0 -c -t 1000 -O "$DATA_FILE_NAME" >> "$OUTPUT_FILENAME" else - real_time torify wget http://torperf.torproject.org/.5mbfile --wait=0 --waitretry=0 -c -t 0 -O "$DATA_FILE_NAME" + real_time torify wget http://torperf.torproject.org/.5mbfile --wait=0 --waitretry=0 -c -t 1000 -O "$DATA_FILE_NAME" fi

1 0

r25385: {website} i thought wml was supposed to do this, not humans, attempt t (website/trunk/projects/en)
by Andrew Lewman 09 Feb '12

09 Feb '12

Author: phobos Date: 2012-02-09 23:58:38 +0000 (Thu, 09 Feb 2012) New Revision: 25385 Modified: website/trunk/projects/en/obfsproxy-instructions.wml Log: i thought wml was supposed to do this, not humans, attempt to address ticket 5064. Modified: website/trunk/projects/en/obfsproxy-instructions.wml =================================================================== --- website/trunk/projects/en/obfsproxy-instructions.wml 2012-02-09 14:33:40 UTC (rev 25384) +++ website/trunk/projects/en/obfsproxy-instructions.wml 2012-02-09 23:58:38 UTC (rev 25385) @@ -108,7 +108,7 @@ - <img src="$(IMGROOT)/obfs-spawn_tor_bridge.png" alt="spawn tor" height="101" width="882"></a> + <img src="$(IMGROOT)/obfs-spawn_tor_bridge.png" alt="spawn tor" height="117" width="879"></a>

1 0