January 2015 - tor-commits - lists.torproject.org

[webwml/staging] 4.0.2 is not recommended anymore
by sebastian＠torproject.org 15 Jan '15

15 Jan '15

commit 26eade65d132af8b75a40ff3b8ca8596345d4c48 Author: Georg Koppen <gk(a)torproject.org> Date: Wed Jan 14 07:18:16 2015 +0000 4.0.2 is not recommended anymore --- projects/torbrowser/RecommendedTBBVersions | 4 ---- 1 file changed, 4 deletions(-) diff --git a/projects/torbrowser/RecommendedTBBVersions b/projects/torbrowser/RecommendedTBBVersions index 5839ab7..4785612 100644 --- a/projects/torbrowser/RecommendedTBBVersions +++ b/projects/torbrowser/RecommendedTBBVersions @@ -1,8 +1,4 @@ [ -"4.0.2", -"4.0.2-Linux", -"4.0.2-MacOS", -"4.0.2-Windows", "4.0.3", "4.0.3-Linux", "4.0.3-MacOS",

1 0

[webwml/staging] Bump TBB version to fix 404.
by sebastian＠torproject.org 15 Jan '15

15 Jan '15

commit b238c22b8f850ff9b4f619bb7db31343ea0a8bfc Author: Mike Perry <mikeperry-git(a)torproject.org> Date: Tue Jan 13 21:33:20 2015 -0800 Bump TBB version to fix 404. --- include/versions.wmi | 10 +++++----- projects/torbrowser/RecommendedTBBVersions | 4 ++++ 2 files changed, 9 insertions(+), 5 deletions(-) diff --git a/include/versions.wmi b/include/versions.wmi index 55bb32f..0075fef 100644 --- a/include/versions.wmi +++ b/include/versions.wmi @@ -23,10 +23,10 @@ <define-tag version-osx-ppc-stable whitespace=delete>0.2.3.25</define-tag> <define-tag version-osx-ppc-alpha whitespace=delete>0.2.4.17-rc</define-tag> -<define-tag version-torbrowserbundledir whitespace=delete>4.0.2</define-tag> +<define-tag version-torbrowserbundledir whitespace=delete>4.0.3</define-tag> <define-tag version-torbrowserbundlebetadir whitespace=delete>4.5-alpha-2</define-tag> -<define-tag version-torbrowserbundle whitespace=delete>4.0.2</define-tag> +<define-tag version-torbrowserbundle whitespace=delete>4.0.3</define-tag> <define-tag version-torbrowserbundlebeta whitespace=delete>4.5-alpha-2</define-tag> <define-tag version-torbrowser-tor whitespace=delete>0.2.4.19</define-tag> <define-tag version-torbrowser-tor-components whitespace=delete>libevent-2.0.21-stable, zlib-1.2.8, openssl-1.0.1e</define-tag> @@ -37,8 +37,8 @@ <define-tag version-torbrowser-vidalia whitespace=delete>0.2.21</define-tag> <define-tag version-torimbrowserbundle whitespace=delete>1.3.21</define-tag> -<define-tag version-torbrowserbundlelinux32 whitespace=delete>4.0.2</define-tag> -<define-tag version-torbrowserbundlelinux64 whitespace=delete>4.0.2</define-tag> +<define-tag version-torbrowserbundlelinux32 whitespace=delete>4.0.3</define-tag> +<define-tag version-torbrowserbundlelinux64 whitespace=delete>4.0.3</define-tag> <define-tag version-torbrowserbundlelinux32beta whitespace=delete>4.5-alpha-2</define-tag> <define-tag version-torbrowserbundlelinux64beta whitespace=delete>4.5-alpha-2</define-tag> <define-tag version-gnu-torbrowser-tor whitespace=delete>0.2.4.19</define-tag> @@ -47,7 +47,7 @@ <define-tag version-gnu-torbrowser-torbutton whitespace=delete>1.5.2</define-tag> <define-tag version-gnu-torbrowser-vidalia whitespace=delete>0.2.21</define-tag> -<define-tag version-torbrowserbundleosx32 whitespace=delete>4.0.2</define-tag> +<define-tag version-torbrowserbundleosx32 whitespace=delete>4.0.3</define-tag> <define-tag version-torbrowserbundleosx64 whitespace=delete>2.3.25-15</define-tag> <define-tag version-torbrowserbundleosx64beta whitespace=delete>4.5-alpha-2</define-tag> <define-tag version-osx-torbrowser-tor whitespace=delete>0.2.4.19</define-tag> diff --git a/projects/torbrowser/RecommendedTBBVersions b/projects/torbrowser/RecommendedTBBVersions index c75968c..5839ab7 100644 --- a/projects/torbrowser/RecommendedTBBVersions +++ b/projects/torbrowser/RecommendedTBBVersions @@ -3,6 +3,10 @@ "4.0.2-Linux", "4.0.2-MacOS", "4.0.2-Windows", +"4.0.3", +"4.0.3-Linux", +"4.0.3-MacOS", +"4.0.3-Windows", "4.5-alpha-2", "4.5-alpha-2-Linux", "4.5-alpha-2-MacOS",

1 0

[webwml/staging] Take down the dircomm posting, per Tom's request. We have enough apps now.
by sebastian＠torproject.org 15 Jan '15

15 Jan '15

commit c48620b19ac8783a76bf1fb9806fe30b4ab3b9de Author: Nick Mathewson <nickm(a)torproject.org> Date: Wed Jan 14 08:48:58 2015 -0500 Take down the dircomm posting, per Tom's request. We have enough apps now. --- about/en/jobs-dircomms.wml | 9 ++++++++- about/en/jobs.wml | 2 +- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/about/en/jobs-dircomms.wml b/about/en/jobs-dircomms.wml index 991d739..a9c6c58 100644 --- a/about/en/jobs-dircomms.wml +++ b/about/en/jobs-dircomms.wml @@ -10,8 +10,14 @@ <a href="<page about/jobs>">Jobs</a> </div> <div id="maincol"> + +<h1>Note: we've received sufficient applications for this position, and are sorting through them and interviewing candidates. </h1> + + -<p>(Posted 6 January 2015.)</p> +<p>(Updated 14 January 2015.)</p> </div>  diff --git a/about/en/jobs.wml b/about/en/jobs.wml index f6a0c3a..05cdca4 100644 --- a/about/en/jobs.wml +++ b/about/en/jobs.wml @@ -21,7 +21,6 @@ <ul> <li><a href="<page about/jobs-projectmanager>">Project Manager</a></li> -<li><a href="<page about/jobs-dircomms>">Director of Communications</a></li> </ul> <p>In the past, we looked for the following people:</p> @@ -33,6 +32,7 @@ <li>Pluggable transport developer</li> <li>Lead Automation Engineer</li> <li>Firefox/Thunderbird Extension Developer</li> +<li>Director of Communications</li> </ul> <p>

1 0

[webwml/staging] Make the bridge user documentation usable again
by sebastian＠torproject.org 15 Jan '15

15 Jan '15

commit fdcf771c8ad171138a54c9dace3573788cd5970b Author: Matthew Finkel <Matthew.Finkel(a)gmail.com> Date: Wed Jan 14 17:23:49 2015 +0000 Make the bridge user documentation usable again --- docs/en/bridges.wml | 338 ++++++++++++++++++--------- docs/en/sidenav.wmi | 18 +- images/tb-bridge-networksettings.png | Bin 0 -> 86129 bytes images/tb-bridges-custom-from-browser.png | Bin 0 -> 107151 bytes images/tb-bridges-options-from-browser.png | Bin 0 -> 66972 bytes images/tb-bridges-provided-from-browser.png | Bin 0 -> 84736 bytes images/tb-frontpage.png | Bin 0 -> 36890 bytes images/tb-tor-button-menu.png | Bin 0 -> 58398 bytes images/tb-tor-launcher-bridges-custom.png | Bin 0 -> 88827 bytes images/tb-tor-launcher-bridges-options.png | Bin 0 -> 83439 bytes images/tb-tor-launcher-bridges-provided.png | Bin 0 -> 75365 bytes images/tb-tor-launcher-isp-interference.png | Bin 0 -> 89171 bytes images/tb-tor-launcher-no-proxy.png | Bin 0 -> 74714 bytes images/tb-tor-launcher-startup.png | Bin 0 -> 89215 bytes 14 files changed, 231 insertions(+), 125 deletions(-) diff --git a/docs/en/bridges.wml b/docs/en/bridges.wml index 6da02cc..dd46d43 100644 --- a/docs/en/bridges.wml +++ b/docs/en/bridges.wml @@ -14,7 +14,7 @@ <a href="<page docs/documentation>">Documentation » </a> <a href="<page docs/bridges>">Bridges</a> </div> - <div id="maincol"> + <div id="maincol"> <a id="BridgeIntroduction"></a> <h2><a class="anchor" href="#BridgeIntroduction">Tor: Bridges</a></h2> <hr> @@ -22,106 +22,106 @@ <p> <img width="7%" height="7%" style="float: left;" src="$(IMGROOT)/icon-Obfsproxy.jpg"> <b>Tip:</b> - Having trouble connecting to Tor even when using bridges? You will - need to use <b>pluggable transports</b> and <b>obfuscated - bridges</b>. <a class="anchor" href="#PluggableTransports">Click - here for more information</a>. + Having trouble connecting to Tor? You may need to use a different <b>pluggable + transport</b>. <a class="anchor" href="#PluggableTransports">Click here for + more information</a>. </p> - + <p> Bridge relays (or "bridges" for short) are Tor relays that aren't listed in the main Tor directory. Since there is no complete public list of them, even if your ISP is filtering connections to all the known Tor relays, they probably won't be able to block all the bridges. If you suspect your access to the - Tor network is being blocked, you may want to use the bridge feature of Tor. + Tor network is being blocked, you may want to use bridges. </p> - + <p> The addition of bridges to Tor is a step forward in the blocking resistance race. It is perfectly possible that even if your ISP filters the Internet, you do not require a bridge to use Tor. So you should try to use Tor without bridges first, since it might work. </p> - + <p> Note that it's also possible that Tor is non-functional for other - reasons. The latest version of <a href="<page projects/torbrowser>">The - Tor Browser Bundle</a> on Windows tries to give you better hints about - why Tor is having problems connecting. You should also read <a - href="<wikifaq>#IinstalledTorandPolipobutitsnotworking.">the + reasons. The latest version of <a href="<page projects/torbrowser>"> + Tor Browser</a> tries to give you better hints about why Tor is having + problems connecting. You should also read <a href="<page docs/faq>#DoesntWork">the FAQ about problems with running Tor properly</a> when you have issues. - If you feel that the issue is clearly blocking, or you'd simply like to try - because you're unsure or feeling adventurous, please read on. Ensure - that you're using the <a href="<page download/download>#Dev">latest 0.2.3.x or - 0.2.4.x bundle for your platform</a>. + If you feel that the issue is clearly related to Tor being blocked, or + you'd simply like to try because you're unsure or feeling adventurous, + please read on. Ensure that you're using the <a href="<page download/download>#Dev">latest + Tor Browser for your platform</a>. </p> - + <p> - To use a bridge, you'll need to locate one. Furthermore, you'll need to - configure Tor with whatever bridge address you intend to use. You'll do this - with Vidalia, the Tor controller. - If your Internet connection requires the use of a proxy, you'll probably - need to configure Vidalia to do so first. If you don't think you need - to configure a proxy for your Internet connection, you probably don't. - Give it a try and if you have issues, ask us for help. + To use a bridge, you have two options. Tor Browser now provides some + bridges by default. You can enable these easily. Unfortunately, because + these bridges are publically distributed, it is easy for censors to block + some of them, so some of them may not work. In this case, you'll need to + locate different bridges. Furthermore, you'll need to configure Tor Browser + with whichever bridge address you intend to use. If your Internet connection + requires the use of a proxy, you'll probably need to configure Tor Browser + to use it first. If you don't think you need to configure a proxy for your + Internet connection, you probably don't. Give it a try and if you have + issues, <a href="<page about/contact>#support">ask us for help</a>. </p> - - <p>Freedom House has produced a video on how to get and use Tor bridges. - If you don't see a video below, view it at <a - href="http://www.youtube.com/thetorproject">Youtube: - Freedom4Internet</a> Know of a better video, or one translated into - your language? Let us know!</p> - - <div class="center"> - <p><video id="v1" src="https://media.torproject.org/video/2009-using-a-bridge-relay-to-access-tor.…" autobuffer="true" controls="controls"></video></p> - </div> - + <p> - At the moment, you can get a bridge by visiting - <a href="https://bridges.torproject.org/">https://bridges.torproject.org/</a> - with your web browser. If this page is filtered for you, and you - don't have any other proxies or ways to reach it, there are <a - href="#FindingMore">other ways to find bridges</a> too. + <ul> + <li><a href="#PluggableTransports">Obfuscated Bridges and Pluggable Transports</a></li> + <li><a href="#Understanding">Understanding Bridge Configuration Lines</a></li> + <li><a href="#AddTorNotWorks">Adding bridges in Tor Browser when Tor doesn't work</a></li> + <li><a href="#AddTorWorks">Adding bridges in Tor Browser when Tor does work</a></li> + <li><a href="#FindingMore">Finding more bridges for Tor</a></li> + </ul> </p> - + <a id="PluggableTransports"></a> - <h2><a class="anchor" href="#PluggableTransports">Obfuscated Bridges and Pluggable Transports</a></h2> + <h2><a class="anchor" href="#PluggableTransports">Pluggable Transports</a></h2> <hr> - - <p> Lately, censors have found ways to block Tor even when clients - are using bridges. They usually do this by installing boxes in - ISPs that peek at network traffic and detect Tor; when Tor is - detected they block the traffic flow. + + <p>Over the last few years, censors have found ways to block Tor even when + clients are using bridges. They usually do this by installing special + boxes at ISPs that peek into network traffic and detect Tor; when Tor + is detected they block the traffic flow. </p> <p>To circumvent such sophisticated censorship Tor introduced - <i>obfuscated bridges</i>. These bridges use special plugins - called <i>pluggable transports</i> which obfuscate the traffic - flow of Tor, making its detection harder. + <a href="<page docs/pluggable-transports>"><i>pluggable transports</i></a>. + These transports manipulate all Tor traffic between the client and its + first hop such that it is not identifiable as a Tor connection. If the + censor can't decide if the connection is a Tor connection, then they are + less likely to block it.</p> - To connect to obfuscated bridges you need to use the <a - href="<page projects/obfsproxy>#download">Obfsproxy - Tor Browser Bundle</a>. The bundle includes some pre-configured - obfsproxy bridges and you can get more from <a - href=https://bridges.torproject.org/?transport=obfs2>BridgeDB</a> + <p>Sadly, pluggable transports are not immune to detection, if a censor + is given enough time. In the past, we promoted obfs and obfs2 as safe + transports. These are now deprecated and were replaced by obfs3, + scramblesuit, fte, and obfs4.</p> + + <p>Bridges which support pluggable transports can be used with Tor Browser + easily. Tor Browser includes some pre-configured bridges and you can get + more from <a href="#FindingMore">BridgeDB</a>, if those don't work.</p> <a id="Understanding"></a> - <h2><a class="anchor" href="#Understanding">Understanding bridges</a></h2><hr> + <h2><a class="anchor" href="#Understanding">Understanding A Bridge Configuration Line</a></h2> + <hr> <p> - As an example, you'll get a bridge entry that looks like the - following: + As an example, when you obtain a bridge from https://bridges.torproject.org, + you'll get a bridge entry that looks like the following: </p> <pre><samp> - bridge 141.201.27.48:443 4352e58420e68f5e40bf7c74faddccd9d1349413 + 141.201.27.48:443 4352e58420e68f5e40bf7c74faddccd9d1349413 </samp> </pre> - + <p> Understanding the components of a bridge line isn't strictly required but may prove useful. You can skip this section if you'd like.<br> - The first element is the IP address: <tt>'141.201.27.48'</tt><br> - The second element is the port: <tt>'443'</tt><br> - The third element, the fingerprint, is optional: + The first element is the IP address of the bridge: <tt>'141.201.27.48'</tt><br> + The second element is the port number: <tt>'443'</tt><br> + The third element, the fingerprint (unique identifier of the + bridge), is optional: <tt>'4352e58420e68f5e40bf7c74faddccd9d1349413'</tt><br> <p> @@ -131,82 +131,188 @@ <p> If your bridge line looks like this: <pre><samp> - bridge obfs2 141.201.27.48:420 4352e58420e68f5e40bf7c74faddccd9d1349413 + obfs3 141.201.27.48:420 4352e58420e68f5e40bf7c74faddccd9d1349413 </samp> </pre> - The second element is the name of the pluggable transport + The first element is the name of the pluggable transport technology used by the bridge. For example, in the case above, the - bridge is using the <i>obfs2</i> pluggable transport. + bridge is using the <i>obfs3</i> pluggable transport. </p> <a id="UsingBridges"></a> - <h2><a class="anchor" href="#UsingBridges">Using bridges with Tor and - Vidalia</a></h2> + <h2><a class="anchor" href="#UsingBridges">Using bridges with Tor + Browser</a></h2> <hr> - - <p> - To use the example bridge address above, go to Vidalia's Network settings - page, and click "My ISP blocks connections to the Tor network". Add each - bridge address one at a time in the Vidalia Network settings page, - by pasting it into the "Add a Bridge" window and then clicking the "+" - sign. Adding a bridge is pictured below: - </p> - + + <ul> + <li><a href="#AddTorNotWorks">Adding bridges in Tor Browser when Tor doesn't work</a></li> + <li><a href="#AddTorWorks">Adding bridges in Tor Browser when Tor does work</a></li> + </ul> + + <a id="AddTorNotWorks"></a> + <h3><a href="#AddTorNotWorks">Adding bridges in Tor Browser when Tor <em>does not</em> work:</a></h3> + <hr> + + <p>First, you should read <a href="<page docs/faq>#DoesntWork">the + FAQ about problems with running Tor properly</a> when you have issues. + Sometimes Tor does not work due to a silly mistake rather than your + ISP interfering with your Internet connection.</p> + <br><br> - <img src="$(IMGROOT)/vidalia-bridges.png" alt="Vidalia's Network settings page"> + <h3>1) To add a bridge, follow the instructions on screen. Click the + "Configure" button. + </h3> + <br/> + <img src="$(IMGROOT)/tb-tor-launcher-startup.png" alt="Tor Browser's Initial Configuration page"> + <br><br><br> + <h3>2) If you must configure a proxy then select "Yes" and enter the + details on the following page. + <br/>If you do not use a proxy then select "No" and click "Next". + <br/>If you do not know if you must configure a proxy then you likely + do not need to do it. + </h3> + <br/> + <img src="$(IMGROOT)/tb-tor-launcher-no-proxy.png" alt="Tor Browser's Proxy page"> + <br><br><br> + <h3>3) After you configure a proxy or skip over that configuration page, + the following page asks "Does your Internet Service Provider (ISP) + block or otherwise censor connections to the Tor Network?". Select + "Yes" and then click "Next".</h3> + <br/> + <img src="$(IMGROOT)/tb-tor-launcher-isp-interference.png" alt="Tor Browser's Bridge page"> + <br><br><br> + <h3>4) Now you have two configuration options. You can use bridges which are + preconfigured and provided with Tor Browser, or you can specify your + own bridge(s).</h3> + <br/> + <img src="$(IMGROOT)/tb-tor-launcher-bridges-options.png" alt="Tor Browser's Bridge Configuration page"> + <br><br><br> + <h3>5a) If you want to use one of the provided bridges, then choose the + transport type you want to use. obfs3 is currently the recommend + type, but depending on where you are located another type may work better + for you. If you have any questions, please <a href="<page about/contact>#support">contact + us.</a></h3> + <br/> + <img src="$(IMGROOT)/tb-tor-launcher-bridges-provided.png" alt="Tor Browser's Bridge Configuration page - provided bridges"> + <br><br><br> + <h3>5b) Alternatively, if you want to use a <a href="#FindingMore">custom + bridge</a>, then select "Enter custom bridges" and copy-and-paste the + bridge information into the textbox. + </h3> + <br/> + <img src="$(IMGROOT)/tb-tor-launcher-bridges-custom.png" alt="Tor Browser's Bridge Configuration page - provided bridges"> + <br><br><br> + <h3>6) After you decide which bridges you want to use, click "Connect". + Tor should now be able to load successfully and the browser window + should appear.</h3> + <br/> + <img src="$(IMGROOT)/tb-frontpage.png" alt="Tor Browser's Front Page"> + <br><br><br><br> + + <a id="AddTorWorks"></a> + <h3><a href="#AddTorWorks">Adding bridges in Tor Browser when Tor <em>does</em> work:</a></h3> + <hr> + + <p>The following instructions assume Tor Browser successfully loads and + you are able to surf the web. If you do not see the web browser when you + run Tor Browser (like in step (1) below), you may need to follow the + <a href="#AddTorNotWorks">instructions above</a>. + <br><br> - - <p> - You'll want to add as many bridge addresses as you know about, since - additional bridges will increase reliability. One bridge should be enough - to reach the Tor network, but if you only have one bridge and it goes - down, you will be cut off from the Tor network. - </p> + <h3>1) Start Tor Browser:</h3> + <br> + <img src="$(IMGROOT)/tb-frontpage.png" alt="Tor Browser's Front Page"> + <br><br><br> + <h3>2) To begin using bridges, open Tor Browser's Network Settings:</h3> + <br> + <img src="$(IMGROOT)/tb-tor-button-menu.png" alt="Tor Browser's TorButton Menu"> + <br><br><br> + <h3>3) Select "My Internet Service Provider (ISP) blocks connections to the Tor network":</h3> + <br> + <img src="$(IMGROOT)/tb-bridge-networksettings.png" alt="Tor Browser's Network Settings page"> + <br><br><br> + <h3>4) Now you have two configuration options. You can use bridges which are + preconfigured and provided with Tor Browser, or you can specify your + own bridge(s).</h3> + <br> + <img src="$(IMGROOT)/tb-bridges-options-from-browser.png" alt="Tor Browser's TorButton Menu"> + <br><br><br> + <h3>5a) If you want to use one of the provided bridges, then choose the + transport type you want to use. obfs3 is currently the recommend + type, but depending on where you are located another type may work better + for you. If you have any questions, please <a href="<page about/contact>#support">contact + us.</a></h3> + <br> + <img src="$(IMGROOT)/tb-bridges-provided-from-browser.png" alt="My Internet Service Provider (ISP) blocks connections to the Tor network"> + <br><br><br> + <h3>5b) Alternatively, if you want to use a <a href="#FindingMore">custom + bridge</a>, then select "Enter custom bridges" and copy-and-paste the + bridge information into the textbox. + </h3> + <br> + <img src="$(IMGROOT)/tb-bridges-custom-from-browser.png" alt="Add bridges in the custom bridges textbox"> + <br><br><br> <p> - <img width="7%" height="7%" style="vertical-align:middle" src="$(IMGROOT)/icon-Obfsproxy.jpg"> - <span><b>Pluggable transports tip:</b></span> + Tor will only use one bridge at a time, but it is good to add more than one + bridge so you can continue using Tor even if your first bridge becomes + unavailable. </p> - <p> + <br><br> - If you have managed to get hold of some obfuscated bridge - addresses, you should add them in Vidalia in the same fashion that - you add normal bridges. Just paste the bridge line into the "Add a - bridge" window: - <br><br> - <img src="$(IMGROOT)/vidalia_add_obfsbridge.png" alt="Add obfuscated bridge in Vidalia"> - <br><br> - <a id="FindingMore"></a> <h2><a class="anchor" href="#FindingMore">Finding more bridges for Tor</a></h2> <hr> - + <p> - Another way to find public bridge addresses is to send mail to - bridges(a)bridges.torproject.org with the line "get bridges" by itself in the - body of the mail. You'll need to send this request from a gmail - account, though — otherwise we make it too easy for an attacker - to make a lot of email addresses and learn about all the bridges. - Almost instantly, you'll receive a reply that includes: + If you need to get bridges, you can get a bridge by visiting + <a href="https://bridges.torproject.org/">https://bridges.torproject.org/</a> + with your web browser. + </p> + + <p> + You can also get bridges by sending mail to bridges(a)bridges.torproject.org + with the line "get bridges" by itself in the body of the mail. You'll need + to send this request from a Gmail, Riseup!, or Yahoo! account, though + — we only accept these providers because otherwise we make it too + easy for an attacker to make a lot of email addresses and learn about all + the bridges. Almost instantly, you'll receive a reply that includes: </p> <pre> - Here are your bridge relays: + Here are your bridge: + + 60.16.182.53:9001 + 87.237.118.139:444 + 60.63.97.221:443 - bridge 60.16.182.53:9001 - bridge 87.237.118.139:444 - bridge 60.63.97.221:443 + </pre> + <p> + Similarly, if you need bridges with a specific pluggable transport, the + process is just as easy. First, decide which type you want. Currently we + provide obfs2, obfs3, scramblesuit, and fte. If you don't know which one + you should choose, then obfs3 is usually a good choice. Send an email to + bridges(a)bridges.torproject.org with "get transport obfs3" by itself in + the body of the email (replace "obfs3" with whichever pluggable transport + you want to use). You should receive an email like this: + </p> + <pre> + Here are your bridges: + obfs3 60.16.182.53:9001 cc8ca10a63aae8176a52ca5129ce816d011523f5 + obfs3 87.237.118.139:444 0ed110497858f784dfd32d448dc8c0b93fee20ca + obfs3 60.63.97.221:443 daa5e435819275f88d695cb7fce73ed986878cf3 </pre> <p> - Once you've received the email with bridge information, you can continue the Vidalia configuration steps outlined <a href="#UsingBridges">above</a>. + Once you've received the email with bridge information, you can + continue the configuration steps outlined <a href="#UsingBridges">above</a>. </p> - + <a id="RunningABridge"></a> <h2><a class="anchor" href="#RunningABridge">Running a Tor Bridge</a></h2> <hr> - + <p> If you want to help out, you should <a href="<page docs/faq>#RelayOrBridge">decide whether you want to run a normal Tor @@ -226,18 +332,18 @@ settings page"></li> </ul> </p> - + <p>If you get "Could not bind to 0.0.0.0:443: Permission denied" errors on startup, you'll need to pick a higher ORPort (e.g. 8080) or do <a href="<page docs/faq>#HowcanImakemyrelayaccessibletopeoplestuckbehindrestrictivefirewalls">some complex port forwarding</a>. </p> - + <p> When configured as a bridge, your server will <b>not</b> appear in the public Tor network. </p> - + <p> Your bridge relay will automatically publish its address to the bridge authority, which will give it out via https or email as above. You can @@ -248,7 +354,7 @@ fingerprint in your Tor log files or in <tt>/var/lib/tor/fingerprint</tt> depending on your platform). </p> - + <p> If you would like to learn more about our bridge design from a technical standpoint, please read the <a @@ -265,5 +371,5 @@  </div>  -#include <foot.wmi> +#include <foot.wmi> diff --git a/docs/en/sidenav.wmi b/docs/en/sidenav.wmi index e0867ed..280a318 100644 --- a/docs/en/sidenav.wmi +++ b/docs/en/sidenav.wmi @@ -9,17 +9,17 @@ # # url - the path to the wml page, as used the the <page> tag. This tag ensures # that links will point to the current language if supported, and alternately -# the english version +# the english version # # txt - the link text to be displayed. Different translations will -# need to supply alternate txt +# need to supply alternate txt <: my $sidenav; $sidenav = [ {'url' => 'docs/documentation', 'txt' => 'Documentation Overview', - }, + }, { 'url' => 'docs/installguide', 'txt' => 'Installation Guides', @@ -63,13 +63,13 @@ }, {'url' => 'docs/tor-hidden-service', 'txt' => 'Configuring a Hidden Service', - }, - {'url' => 'docs/bridges', - 'txt' => 'Configuring a Bridge Relay', - }, + }, {'url' => 'docs/running-a-mirror', 'txt' => 'Configuring a Mirror', }, + {'url' => 'docs/bridges', + 'txt' => 'Using a Bridge Relay', + }, {'url' => 'docs/tor-manual', 'txt' => 'Tor -stable Manual', }, @@ -82,7 +82,7 @@ 'txt' => 'Tor Wiki', }, {'url' => 'docs/faq', - 'txt' => 'General FAQ', + 'txt' => 'General FAQ', }, {'url' => 'docs/faq-abuse', 'txt' => 'Abuse FAQ', @@ -95,6 +95,6 @@ }, {'url' => 'eff/tor-dmca-response', 'txt' => 'Tor DMCA Response', - }, + }, ]; :> diff --git a/images/tb-bridge-networksettings.png b/images/tb-bridge-networksettings.png new file mode 100644 index 0000000..15101c9 Binary files /dev/null and b/images/tb-bridge-networksettings.png differ diff --git a/images/tb-bridges-custom-from-browser.png b/images/tb-bridges-custom-from-browser.png new file mode 100644 index 0000000..d18279f Binary files /dev/null and b/images/tb-bridges-custom-from-browser.png differ diff --git a/images/tb-bridges-options-from-browser.png b/images/tb-bridges-options-from-browser.png new file mode 100644 index 0000000..884a8c8 Binary files /dev/null and b/images/tb-bridges-options-from-browser.png differ diff --git a/images/tb-bridges-provided-from-browser.png b/images/tb-bridges-provided-from-browser.png new file mode 100644 index 0000000..adcb309 Binary files /dev/null and b/images/tb-bridges-provided-from-browser.png differ diff --git a/images/tb-frontpage.png b/images/tb-frontpage.png new file mode 100644 index 0000000..b7d0a10 Binary files /dev/null and b/images/tb-frontpage.png differ diff --git a/images/tb-tor-button-menu.png b/images/tb-tor-button-menu.png new file mode 100644 index 0000000..c603753 Binary files /dev/null and b/images/tb-tor-button-menu.png differ diff --git a/images/tb-tor-launcher-bridges-custom.png b/images/tb-tor-launcher-bridges-custom.png new file mode 100644 index 0000000..af98f12 Binary files /dev/null and b/images/tb-tor-launcher-bridges-custom.png differ diff --git a/images/tb-tor-launcher-bridges-options.png b/images/tb-tor-launcher-bridges-options.png new file mode 100644 index 0000000..58683e2 Binary files /dev/null and b/images/tb-tor-launcher-bridges-options.png differ diff --git a/images/tb-tor-launcher-bridges-provided.png b/images/tb-tor-launcher-bridges-provided.png new file mode 100644 index 0000000..e66f708 Binary files /dev/null and b/images/tb-tor-launcher-bridges-provided.png differ diff --git a/images/tb-tor-launcher-isp-interference.png b/images/tb-tor-launcher-isp-interference.png new file mode 100644 index 0000000..a0ebe94 Binary files /dev/null and b/images/tb-tor-launcher-isp-interference.png differ diff --git a/images/tb-tor-launcher-no-proxy.png b/images/tb-tor-launcher-no-proxy.png new file mode 100644 index 0000000..4e8bd6b Binary files /dev/null and b/images/tb-tor-launcher-no-proxy.png differ diff --git a/images/tb-tor-launcher-startup.png b/images/tb-tor-launcher-startup.png new file mode 100644 index 0000000..0f9d4b1 Binary files /dev/null and b/images/tb-tor-launcher-startup.png differ

1 0

[webwml/staging] Merge branch 'master' of ssh://git-rw.torproject.org/project/web/webwml
by sebastian＠torproject.org 15 Jan '15

15 Jan '15

commit fc6478c74d0f541797c4d592c4e5095799e2ce92 Merge: 684578d a1ae777 Author: Andrew Lewman <andrew(a)torproject.is> Date: Tue Jan 6 11:47:35 2015 -0500 Merge branch 'master' of ssh://git-rw.torproject.org/project/web/webwml about/en/gsoc.wml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

1 0

[webwml/staging] Fixed broken link of revamp gettor for gsoc
by sebastian＠torproject.org 15 Jan '15

15 Jan '15

commit a1ae77725a1dc6e01b646be593ac582ba9a39dc8 Author: ileiva <ileiva(a)users.noreply.github.com> Date: Mon Jan 5 16:55:46 2015 -0300 Fixed broken link of revamp gettor for gsoc --- about/en/gsoc.wml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/about/en/gsoc.wml b/about/en/gsoc.wml index 3e5fdcb..2009eed 100644 --- a/about/en/gsoc.wml +++ b/about/en/gsoc.wml @@ -216,7 +216,7 @@ <ul> <li><h4><a href="https://ahmia.fi/gsoc/">Ahmia.fi - Search Engine for Hidden Services</a> by Juha Nurmi</h4></li> <li><h4><a href="http://www.google-melange.com/gsoc/proposal/public/google/gsoc2014/amoghbl1…">Orbot & Orfox</a> by Amogh Pradeep</h4></li> - <li><h4><a href="http://ileiva.github.io/gettor_proposal.html">Revamp GetTor</a> by Israel Leiva</h4></li> + <li><h4><a href="http://ilv.github.io/gettor_proposal.html">Revamp GetTor</a> by Israel Leiva</h4></li> <li><h4><a href="https://sites.google.com/site/sreenathadev/gsoc-2014-weather-rewrite">Weather Rewrite</a> by Sreenatha Bhatlapenumarthi</h4></li> <li><h4><a href="http://kostas.mkj.lt/gsoc2014/gsoc2014.html">BridgeDB Distributor</a> by Kostas Jakeliunas</h4></li> <li><h4><a href="http://kostas.mkj.lt/gsoc2013/gsoc2013.html">Searchable Tor descriptor archive</a> by Kostas Jakeliunas</h4></li>

1 0

[webwml/staging] Updated mirror.
by sebastian＠torproject.org 15 Jan '15

15 Jan '15

commit 71e7d8e4d2084711c02a0ff89dc783b5b603bc1b Author: Andrew Lewman <andrew(a)torproject.is> Date: Tue Jan 6 09:38:49 2015 -0500 Updated mirror. --- include/tor-mirrors.csv | 1 + 1 file changed, 1 insertion(+) diff --git a/include/tor-mirrors.csv b/include/tor-mirrors.csv index ca8ebe0..ca7a470 100644 --- a/include/tor-mirrors.csv +++ b/include/tor-mirrors.csv @@ -104,3 +104,4 @@ hostmaster(a)lucidnetworks.net, Lucid Networks, US, United States, US, TRUE, FALSE hostmaster(a)vieth-server.de, mirror-server.de, DE, Germany, DE, TRUE, TRUE, No, http://tor.mirror-server.de/, , , , http://tor.mirror-server.de/dist/, , , , Thu Jan 1 15:14:41 2015 mirror ntzk de, Netzkonstrukt Berlin, DE, Germany, Europe, TRUE, FALSE, No, http://mirror.ntzk.de/torproject.org/, https://mirror.ntzk.de/torproject.org/, , , http://mirror.ntzk.de/torproject.org/dist/, https://mirror.ntzk.de/torproject.org/dist/, , , Wed Dec 31 18:27:22 2014 mirror(a)xfree.com.ar, Xfree.com.ar, AR, Argentina, South America, TRUE, FALSE, No, http://tor.xfree.com.ar/, , , , http://tor.xfree.com.ar/dist/, , , , Wed Dec 31 18:27:22 2014 +tor AT eprci NET, EPRCI, US, NH, US, TRUE, FALSE, No, http://tor.eprci.net/, https:/www.eprci.com/tor/, , , http://tor.eprci.net/dist/, https://www.eprci.com/tor/dist/, , , \ No newline at end of file

1 0

[webwml/staging] Update the sponsor list for 2014
by sebastian＠torproject.org 15 Jan '15

15 Jan '15

commit 684578da5e9d09f60ef87aea0f81a3190d60c6bb Author: Andrew Lewman <andrew(a)torproject.is> Date: Tue Jan 6 11:47:16 2015 -0500 Update the sponsor list for 2014 --- about/en/sponsors.wml | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/about/en/sponsors.wml b/about/en/sponsors.wml index 16da57a..576d5a2 100644 --- a/about/en/sponsors.wml +++ b/about/en/sponsors.wml @@ -39,6 +39,7 @@ <p>We greatly appreciate the support provided by our past sponsors in keeping the Tor Project progressing through our ambitious goals:</p> <ul> + <li><a href="https://freedom.press/">Freedom of the Press Foundation</a> (2014)</li> <li><a href="http://www.knightfoundation.org/">The Knight Foundation</a> (2012-2013)</li> <li><a href="http://www.sida.se/English/">Sida - Swedish International Development Cooperation Agency</a> (2010-2013)</li> <li>An anonymous North American NGO (2008-2013)</li> @@ -49,7 +50,7 @@ <li><a href="http://www.hrw.org/">Human Rights Watch</a> (2007)</li> <li><a href="http://www.torfox.org/">Torfox</a> (2009)</li> <li><a href="http://www.shinjiru.com/">Shinjiru Technology</a> (2009-2011)</li> - <li><a href="http://www.nationalchristian.com/">National Christian Foundation</a> (2010-2012)</li> + <li><a href="http://www.nationalchristian.com/">National Christian Foundation</a> (2010-2012, 2014)</li> <li><a href="http://www.nlnet.nl/">NLnet Foundation</a> (2008-2009)</li> <li><a href="http://www.nrl.navy.mil/">Naval Research Laboratory</a> (2006-2010)</li> <li>Internews Europe (2006-2008)</li>

1 0

[webwml/staging] Update Ubuntu distribution codenames
by sebastian＠torproject.org 15 Jan '15

15 Jan '15

commit 7bcc1efd81ae53459c9736978fbcb0a8fcb201d2 Author: Sebastian Hahn <sebastian(a)torproject.org> Date: Wed Jan 7 12:58:25 2015 +0100 Update Ubuntu distribution codenames patch by dedal0, implements ticket #13847 --- docs/en/debian-vidalia.wml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/en/debian-vidalia.wml b/docs/en/debian-vidalia.wml index 33a6441..5662917 100644 --- a/docs/en/debian-vidalia.wml +++ b/docs/en/debian-vidalia.wml @@ -26,6 +26,12 @@ You'll need to set up our package repository before you can fetch Tor. First, you need to figure out the name of your distribution. Here's a quick mapping: <ul> +<li> Ubuntu 14.10 is "utopic"</li> +<li> Ubuntu 14.04.* is "trusty"</li> +<li> Ubuntu 13.10 is "saucy"</li> +<li> Ubuntu 13.04 is "raring"</li> +<li> Ubuntu 12.04.* is "precise"</li> +<li> Ubuntu 11.10 is "oneiric"</li> <li> Ubuntu 11.04 is "natty"</li> <li> Ubuntu 10.10 or Trisquel 4.5 is "maverick"</li> <li> Ubuntu 10.04 or Trisquel 4.0 is "lucid"</li>

1 0

[webwml/staging] Add the Director of Communications posting
by sebastian＠torproject.org 15 Jan '15

15 Jan '15

commit bc5577ed2718fc9295cc4cd17ca58d993c54bb73 Author: Nick Mathewson <nickm(a)torproject.org> Date: Tue Jan 6 21:04:34 2015 -0500 Add the Director of Communications posting --- about/en/jobs-dircomms.wml | 108 ++++++++++++++++++++++++++++++++++++++++++++ about/en/jobs.wml | 1 + 2 files changed, 109 insertions(+) diff --git a/about/en/jobs-dircomms.wml b/about/en/jobs-dircomms.wml new file mode 100644 index 0000000..379ca21 --- /dev/null +++ b/about/en/jobs-dircomms.wml @@ -0,0 +1,108 @@ +## translation metadata +# Revision: $Revision$ +# Translation-Priority: 3-low + +#include "head.wmi" TITLE="Tor Project: Jobs (director of communications)" CHARSET="UTF-8" +<div id="content" class="clearfix"> + <div id="breadcrumbs"> + <a href="<page index>">Home » </a> + <a href="<page about/overview>">About » </a> + <a href="<page about/jobs>">Jobs</a> + </div> + <div id="maincol"> +<h1>Director of Communications</h1> + +<p>The Tor Project is seeking an accomplished Director of +Communications who has at least 10 years of communications experience, +ideally in an “in-house” leadership role within a complex (number and +variety of constituents) nonprofit entity. The ability to take +knowledge and transform it into powerful messages, and disseminate it +to the right audiences through the best distribution channels is +critical. The Director of Communications will work closely with a +senior peer group within the organization as the communications +partner on a variety of strategic initiatives.</p> + +<h2>Respnsibilities:</h2> + +<ul> +<li>Work with senior management to develop a communications strategy that will support Tor's organizational goals and will address Tor's diverse audiences: funders, hackers, human rights activists, companies, etc. +</li><li> Implement and evaluate the annual communications plan across the network's discrete audiences in collaboration with the Tor Project team and constituents. +</li><li> Identify challenges and emerging issues faced by the organization. Work with leadership team and staff to recognize communications opportunities and solutions, and define and execute appropriate strategies to support them. +</li><li> Train staff and community members on media and coach/prep/debrief them for specific contacts. +</li><li> Serve as communications counselor to Tor Project leadership. +</li><li> Lead the generation of print and online content that engages audience segments and leads to +measurable action. +</li><li> Put communications vehicles in place to create momentum and awareness and to track +progress toward longer term goals. +</li><li> Track and measure the level of engagement within the Tor Project’s network over time. +</li><li> Manage media contacts. +</li></ul> + +<h2>Qualifications:</h2> + +<ul> +<li>Commitment to Tor’s mission to be “the global resource for technology, advocacy, research and education in the ongoing pursuit of freedom of speech, privacy rights, and censorship circumvention.” +</li><li> Extensive experience as a media strategist or political strategist. +</li><li> Highly collaborative style; experience developing and implementing communications strategies. +</li><li> A strong track record as an implementer who thrives on managing a variety of key initiatives +concurrently. +</li><li> Bachelor's degree in journalism, communications, or related field. +</li><li> Minimum 10 years experience in a senior management role. +</li><li> Demonstrated skill and comfort in proactively building relationships with top tier reporters and +editors, and in positioning subject matter with the media to achieve high-impact placements. +</li><li> Demonstrated experience with crisis management, including media crises, and driving more advantageous coverage of the organization, its projects, and its people. +</li><li> Demonstrated ability to take initiative to work on one’s own, as well as in teams. +</li><li> Demonstrated high-level ability to proactively pitch stories to the mainstream press and tech +press. Experience placing and being part of high profile, high pressure media coverage. +</li><li> Experience writing and placing op-eds and editorials in major newspapers. +</li><li> Experience working with and as part of remote teams. Working with these teams requires +empathy, special communications strategies and adept use of special technologies. +</li><li> Excellent social skills and a sense of humor. +</li><li> Comfortable with highly technical topics and ability to explain them clearly and accurately to a +broader and non-technical audience. +</li><li> Experience with collectives or other alternative organizational structures. +</li><li> Demonstrated experience with complex and high profile social media engagement. +</li><li> Deep understanding and ability to support organizational diversity and to maximize the +strengths and advantages of this diversity. +</li><li> Excellent spoken and written English; fluency in other languages within the Tor Project +community is a plus. +</li><li> Outstanding writer/editor. +</li><li> Understanding and support for Tor’s fundraising efforts, working closely with the development +staff. Fundraising and fundraising communications experience is a plus. +</li></ul> + +<h2>How to apply:</h2> +<ul> +<li>Provide a CV and cover letter explaining your background, experience, skills, and other relevant qualifications. Please include links to writing samples. +</li><li> List some people who can tell us more about you. +</li><li>Email the above to jobs(a)torproject.org, specifying the "Director of Communications" position. +</li></ul> + +<h2>About the company:</h2> + +<p>The Tor Project is a US 501(c)(3) non-profit dedicated to +research, development, and education about online anonymity and +privacy. The Tor network's 6000 volunteer relays carry 48 Gbps for +several million daily users, including ordinary citizens who want +protection from identity theft and prying corporations, corporations +who want to look at a competitor's website in private, people around +the world whose Internet connections are censored, and even +governments and law enforcement. Tor has a staff of 30 paid +developers, researchers, and advocates, plus many dozen volunteers who +help out on a daily basis. Tor is funded in part by government +research and development grants, and in part by individual and +corporate donations. </p> + +<p>(Posted 6 January 2015.)</p> + + </div> +  + <div id = "sidecol"> +#include "side.wmi" +#include "info.wmi" + </div> +  +</div> + +#include <foot.wmi> + diff --git a/about/en/jobs.wml b/about/en/jobs.wml index b3046d6..f6a0c3a 100644 --- a/about/en/jobs.wml +++ b/about/en/jobs.wml @@ -21,6 +21,7 @@ <ul> <li><a href="<page about/jobs-projectmanager>">Project Manager</a></li> +<li><a href="<page about/jobs-dircomms>">Director of Communications</a></li> </ul> <p>In the past, we looked for the following people:</p>

1 0