July 2016 - tor-commits - lists.torproject.org

[translation/https_everywhere_completed] Update translations for https_everywhere_completed
by translation＠torproject.org 15 Jul '16

15 Jul '16

commit bac96e7d640babb41d8071a53910e5ad33b81135 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jul 15 14:15:34 2016 +0000 Update translations for https_everywhere_completed --- es/https-everywhere.dtd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/es/https-everywhere.dtd b/es/https-everywhere.dtd index c87be68..ec51838 100644 --- a/es/https-everywhere.dtd +++ b/es/https-everywhere.dtd @@ -20,7 +20,7 @@ <!ENTITY https-everywhere.menu.observatory "Opciones del Observatorio SSL"> <!ENTITY https-everywhere.menu.globalEnable "Activar HTTPS Everywhere"> <!ENTITY https-everywhere.menu.globalDisable "Desactivar HTTPS Everywhere"> -<!ENTITY https-everywhere.menu.blockHttpRequests "Bloquear todas las peticiones HTTP"> +<!ENTITY https-everywhere.menu.blockUnencryptedRequests "Bloquear todas las peticiones no cifradas"> <!ENTITY https-everywhere.menu.showCounter "Mostrar contador"> <!ENTITY https-everywhere.menu.viewAllRules "Ver todas las reglas">

1 0

[translation/https_everywhere] Update translations for https_everywhere
by translation＠torproject.org 15 Jul '16

15 Jul '16

commit 094c6ca3352fd38e69594fe057b510f997b8b366 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jul 15 14:15:27 2016 +0000 Update translations for https_everywhere --- es/https-everywhere.dtd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/es/https-everywhere.dtd b/es/https-everywhere.dtd index b7c488e..ec51838 100644 --- a/es/https-everywhere.dtd +++ b/es/https-everywhere.dtd @@ -20,7 +20,7 @@ <!ENTITY https-everywhere.menu.observatory "Opciones del Observatorio SSL"> <!ENTITY https-everywhere.menu.globalEnable "Activar HTTPS Everywhere"> <!ENTITY https-everywhere.menu.globalDisable "Desactivar HTTPS Everywhere"> -<!ENTITY https-everywhere.menu.blockUnencryptedRequests "Block all unencrypted requests"> +<!ENTITY https-everywhere.menu.blockUnencryptedRequests "Bloquear todas las peticiones no cifradas"> <!ENTITY https-everywhere.menu.showCounter "Mostrar contador"> <!ENTITY https-everywhere.menu.viewAllRules "Ver todas las reglas">

1 0

[tor-browser/tor-browser-45.2.0esr-6.0-1] fixup! Bug 13252 - Do not store data in the app bundle
by gk＠torproject.org 15 Jul '16

15 Jul '16

commit 3cf0ed64dc038b41605bf6c9d5e59bdeddb9e9bc Author: Kathy Brade <brade(a)pearlcrescent.com> Date: Wed Jun 22 15:58:14 2016 -0400 fixup! Bug 13252 - Do not store data in the app bundle Avoid compilation errors when MOZ_UPDATER is not defined. Fixes bug 19484. --- toolkit/xre/nsAppRunner.cpp | 27 ++++++++++++++++++--------- 1 file changed, 18 insertions(+), 9 deletions(-) diff --git a/toolkit/xre/nsAppRunner.cpp b/toolkit/xre/nsAppRunner.cpp index 67bb2d3..1426d77 100644 --- a/toolkit/xre/nsAppRunner.cpp +++ b/toolkit/xre/nsAppRunner.cpp @@ -2712,7 +2712,10 @@ static bool gDoProfileReset = false; // 6) display the profile-manager UI static nsresult SelectProfile(nsIProfileLock* *aResult, nsIToolkitProfileService* aProfileSvc, - nsIFile *aAppDir, nsINativeAppSupport* aNative, +#ifdef TOR_BROWSER_DATA_OUTSIDE_APP_DIR + nsIFile *aAppDir, +#endif + nsINativeAppSupport* aNative, bool* aStartOffline, nsACString* aProfileName) { StartupTimeline::Record(StartupTimeline::SELECT_PROFILE); @@ -4303,10 +4306,19 @@ XREMain::XRE_mainStartup(bool* aExitFlag) } #endif +#if (defined(MOZ_UPDATER) && !defined(MOZ_WIDGET_ANDROID)) || defined(TOR_BROWSER_DATA_OUTSIDE_APP_DIR) + nsCOMPtr<nsIFile> exeFile, exeDir; + bool persistent; + rv = mDirProvider.GetFile(XRE_EXECUTABLE_FILE, &persistent, + getter_AddRefs(exeFile)); + NS_ENSURE_SUCCESS(rv, 1); + rv = exeFile->GetParent(getter_AddRefs(exeDir)); + NS_ENSURE_SUCCESS(rv, 1); +#endif + #if defined(MOZ_UPDATER) && !defined(MOZ_WIDGET_ANDROID) // Check for and process any available updates nsCOMPtr<nsIFile> updRoot; - bool persistent; rv = mDirProvider.GetFile(XRE_UPDATE_ROOT_DIR, &persistent, getter_AddRefs(updRoot)); // XRE_UPDATE_ROOT_DIR may fail. Fallback to appDir if failed @@ -4341,12 +4353,6 @@ XREMain::XRE_mainStartup(bool* aExitFlag) if (CheckArg("test-process-updates")) { SaveToEnv("MOZ_TEST_PROCESS_UPDATES=1"); } - nsCOMPtr<nsIFile> exeFile, exeDir; - rv = mDirProvider.GetFile(XRE_EXECUTABLE_FILE, &persistent, - getter_AddRefs(exeFile)); - NS_ENSURE_SUCCESS(rv, 1); - rv = exeFile->GetParent(getter_AddRefs(exeDir)); - NS_ENSURE_SUCCESS(rv, 1); #ifdef TOR_BROWSER_UPDATE nsAutoCString compatVersion(TOR_BROWSER_VERSION); #endif @@ -4395,7 +4401,10 @@ XREMain::XRE_mainStartup(bool* aExitFlag) return 1; } - rv = SelectProfile(getter_AddRefs(mProfileLock), mProfileSvc, exeDir, + rv = SelectProfile(getter_AddRefs(mProfileLock), mProfileSvc, +#ifdef TOR_BROWSER_DATA_OUTSIDE_APP_DIR + exeDir, +#endif mNativeApp, &mStartOffline, &mProfileName); if (rv == NS_ERROR_LAUNCHED_CHILD_PROCESS || rv == NS_ERROR_ABORT) {

1 0

[tor-browser/tor-browser-45.2.0esr-6.5-1] fixup! Bug 13252 - Do not store data in the app bundle
by gk＠torproject.org 15 Jul '16

15 Jul '16

commit 1ca4e649547a905449f81f154fa3055a8364d1f3 Author: Kathy Brade <brade(a)pearlcrescent.com> Date: Wed Jun 22 15:58:14 2016 -0400 fixup! Bug 13252 - Do not store data in the app bundle Avoid compilation errors when MOZ_UPDATER is not defined. Fixes bug 19484. --- toolkit/xre/nsAppRunner.cpp | 27 ++++++++++++++++++--------- 1 file changed, 18 insertions(+), 9 deletions(-) diff --git a/toolkit/xre/nsAppRunner.cpp b/toolkit/xre/nsAppRunner.cpp index 67bb2d3..1426d77 100644 --- a/toolkit/xre/nsAppRunner.cpp +++ b/toolkit/xre/nsAppRunner.cpp @@ -2712,7 +2712,10 @@ static bool gDoProfileReset = false; // 6) display the profile-manager UI static nsresult SelectProfile(nsIProfileLock* *aResult, nsIToolkitProfileService* aProfileSvc, - nsIFile *aAppDir, nsINativeAppSupport* aNative, +#ifdef TOR_BROWSER_DATA_OUTSIDE_APP_DIR + nsIFile *aAppDir, +#endif + nsINativeAppSupport* aNative, bool* aStartOffline, nsACString* aProfileName) { StartupTimeline::Record(StartupTimeline::SELECT_PROFILE); @@ -4303,10 +4306,19 @@ XREMain::XRE_mainStartup(bool* aExitFlag) } #endif +#if (defined(MOZ_UPDATER) && !defined(MOZ_WIDGET_ANDROID)) || defined(TOR_BROWSER_DATA_OUTSIDE_APP_DIR) + nsCOMPtr<nsIFile> exeFile, exeDir; + bool persistent; + rv = mDirProvider.GetFile(XRE_EXECUTABLE_FILE, &persistent, + getter_AddRefs(exeFile)); + NS_ENSURE_SUCCESS(rv, 1); + rv = exeFile->GetParent(getter_AddRefs(exeDir)); + NS_ENSURE_SUCCESS(rv, 1); +#endif + #if defined(MOZ_UPDATER) && !defined(MOZ_WIDGET_ANDROID) // Check for and process any available updates nsCOMPtr<nsIFile> updRoot; - bool persistent; rv = mDirProvider.GetFile(XRE_UPDATE_ROOT_DIR, &persistent, getter_AddRefs(updRoot)); // XRE_UPDATE_ROOT_DIR may fail. Fallback to appDir if failed @@ -4341,12 +4353,6 @@ XREMain::XRE_mainStartup(bool* aExitFlag) if (CheckArg("test-process-updates")) { SaveToEnv("MOZ_TEST_PROCESS_UPDATES=1"); } - nsCOMPtr<nsIFile> exeFile, exeDir; - rv = mDirProvider.GetFile(XRE_EXECUTABLE_FILE, &persistent, - getter_AddRefs(exeFile)); - NS_ENSURE_SUCCESS(rv, 1); - rv = exeFile->GetParent(getter_AddRefs(exeDir)); - NS_ENSURE_SUCCESS(rv, 1); #ifdef TOR_BROWSER_UPDATE nsAutoCString compatVersion(TOR_BROWSER_VERSION); #endif @@ -4395,7 +4401,10 @@ XREMain::XRE_mainStartup(bool* aExitFlag) return 1; } - rv = SelectProfile(getter_AddRefs(mProfileLock), mProfileSvc, exeDir, + rv = SelectProfile(getter_AddRefs(mProfileLock), mProfileSvc, +#ifdef TOR_BROWSER_DATA_OUTSIDE_APP_DIR + exeDir, +#endif mNativeApp, &mStartOffline, &mProfileName); if (rv == NS_ERROR_LAUNCHED_CHILD_PROCESS || rv == NS_ERROR_ABORT) {

1 0

[webwml/master] updated pt page organizing content according to audience
by sebastian＠torproject.org 15 Jul '16

15 Jul '16

commit 41612b5f7d12a764c8f4673e682ed9d2e0b7377f Author: toya <toya(a)muamba.muamba> Date: Thu Jul 14 22:17:09 2016 -0700 updated pt page organizing content according to audience --- docs/en/pluggable-transports.wml | 235 ++++++++++++++++++++------------------- 1 file changed, 122 insertions(+), 113 deletions(-) diff --git a/docs/en/pluggable-transports.wml b/docs/en/pluggable-transports.wml index 3cd7033..44e4736 100644 --- a/docs/en/pluggable-transports.wml +++ b/docs/en/pluggable-transports.wml @@ -10,85 +10,123 @@ <a href="<page docs/pluggable-transports>">Pluggable Transports</a> </div> <div id="maincol"> - <h2>Tor: Pluggable Transports</h2> + <h1>Tor: Pluggable Transports</h1> + <hr> - - <p> - An increasing number of censoring countries are using Deep Packet - Inspection (DPI) to classify Internet traffic flows by protocol. - While Tor uses <a href="<page docs/bridges>">bridge relays</a> to - get around a censor that blocks by IP address, the censor can use - DPI to recognize and filter Tor traffic flows even when they connect - to unexpected IP addresses. + + <h3>Sometimes the Tor network is censored, and you can't connect it.</h3> + + <br /> + + <p>An increasing number of censoring countries are using Deep Packet Inspection (DPI) to classify Internet traffic flows by protocol. While Tor uses <a href="<page docs/bridges>">bridge relays</a> to get around a censor that blocks by IP address, the censor can use DPI to recognize and filter Tor traffic flows even when they connect to unexpected IP addresses. </p> - <p> - Pluggable Transports (PT) transform the Tor traffic flow between the client - and the bridge. This way, censors who monitor traffic between the - client and the bridge will see innocent-looking transformed traffic - instead of the actual Tor traffic. - External programs can talk to Tor clients and Tor bridges using the <a -href="https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt">pluggable -transport API</a>, to make it easier to build interoperable programs. + <h3>Pluggable Transports help you bypass censorship against Tor.</h3> + + <br /> + + <p>Pluggable Transports (PT) transform the Tor traffic flow between the client and the bridge. This way, censors who monitor traffic between the client and the bridge will see innocent-looking transformed traffic instead of the actual Tor traffic. External programs can talk to Tor clients and Tor bridges using the <a href="https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt">pluggable transport API</a>, to make it easier to build interoperable programs. </p> - <h3>How to use PTs to bypass censorship</h3> - <p> - If connections to the Tor network are being blocked by your ISP or - country, follow these instructions: + + <h3>Here you will learn:</h3> + + <br /> + + <ul> + <li><a href="#user">How to use a Pluggable Transport</a></li> + <li><a href="#operator">How to become a PT bridge operator</a></li> + <li><a href="#developer">How to become a PT developer</a></li> + <li><a href="#list-of-pts">List of PTs organized by their status</a></li> + </ul> + <br /><hr> + + <h2 id="user">How to use PTs to bypass censorship</h2> + <p>If connections to the Tor network are being blocked by your ISP or country, follow these instructions: </p> - <a href="$(IMGROOT)/PT/2016-07-how-to-use-PT.png"> - <img src="$(IMGROOT)/PT/2016-07-how-to-use-PT.png" width="830" - alt="How to use PTs: 1-download tor (send email to gettor(a)torproject.org) 2-select configure 3-check 'my isp blocks tor...' - 4-select obfs4 5-press connect" /></a> + + <a href="$(IMGROOT)/PT/2016-07-how-to-use-PT.png"> <img src="$(IMGROOT)/PT/2016-07-how-to-use-PT.png" width="830" alt="How to use PTs: 1-download tor (send email to gettor(a)torproject.org) 2 select configure 3; check my isp blocks tor option; 4 select obfs4; 5 press connect" /></a>  + <br /><br /> + + <hr> + + <h2 id="operator">Become a PT brigde operator:</h2> + <h3>How to run PTs to help censored users</h3> - <p> - obfs4 is currently the most effective transport to bypass censorship. - To learn how to run this transport, please visit the <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/obfs4…">obfs4proxy wiki page</a>. + + <br /> + + <p>Anyone can set up a PT bridge server and help provide bandwidth to users who needs it. Once you set up a transport type, your bridge will automatically advertise support for the transport in its descriptor.</p> + + <p><strong>obfs4</strong> is currently the most effective transport to bypass censorship. We are asking voluntters to run bridges for it.<br /> + To learn how to run this transport, please visit the <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/obfs4…">obfs4proxy wiki page</a>. </p> + <p><a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports#Becom…">Go to our wiki</a> to learn how to set up other types of PTs.</p> + + <hr> + + <h2 id="developer">Become a PT developer:</h2> + + <p> The links below are the main documentation that will help guide through what you should consider while designing your PT:</p> + + <ul> + <li><a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/Guide…">Guidelines for deploying Pluggable Transports on Tor Browser</a></li> + <li><a href="https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt">PT technical spec</a></li> + <li><a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/PTEva…">Pluggable Transports Evaluation Criteria</a></li> + </ul> + + <p><a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports">Our wiki</a> is also a great source of information, such as how to <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports#Wayst…:">get in touch with the community</a>, <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/ideas">ideas for new PTs</a>, how to <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/WorkL…">help with PTs already deployed</a> and much more.</p> + <hr> + <h2 id="list-of-pts">List of PTs organized by status:</h2> + <h3>Currently deployed PTs</h3> - <p> - These Pluggable Transports are currently deployed in Tor Browser, and you can start using them by <a href="<page download/download-easy>">downloading and using Tor Browser</a>. + + <p>These Pluggable Transports are currently deployed in Tor Browser, and you can start using them by <a href="<page download/download-easy>">downloading and using Tor Browser</a>. </p> <ul> - - <li><a href="https://github.com/Yawning/obfs4/blob/master/doc/obfs4-spec.txt"><b>obfs4</b></a> - is a transport with the same features as <a href="http://www.cs.kau.se/philwint/scramblesuit/"><b>ScrambleSuit</b></a> - but utilizing Dan Bernstein's <a href="http://elligator.cr.yp.to/elligator-20130828.pdf">elligator2</b></a> - technique for public key obfuscation, and the - <a href="https://gitweb.torproject.org/torspec.git/tree/proposals/216-ntor-handshake…">ntor protocol</a> - for one-way authentication. This results in a faster protocol. Written in Go. - Maintained by Yawning Angel. + <li><a href="https://github.com/Yawning/obfs4/blob/master/doc/obfs4-spec.txt"><b>obfs4</b></a></li> + <ul> + <li><strong>Description:</strong> Is a transport with the same features as <a href="http://www.cs.kau.se/philwint/scramblesuit/"><b>ScrambleSuit</b></a> but utilizing Dan Bernstein's <a href="http://elligator.cr.yp.to/elligator-20130828.pdf">elligator2</b></a> technique for public key obfuscation, and the <a href="https://gitweb.torproject.org/torspec.git/tree/proposals/216-ntor-handshake…">ntor protocol</a> for one-way authentication. This results in a faster protocol.</li> + <li><strong>Language:</strong> Go</li> + <li><strong>Maintainer:</strong> Yawning Angel</li> + <li><strong>Evaluation:</strong> <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/Obfs4…">obfs4 Evaluation</a></li> + </ul> </li>  - <li><a href="https://trac.torproject.org/projects/tor/wiki/doc/meek"><b>meek</b></a> - is a transport that uses HTTP for carrying bytes and TLS for - obfuscation. Traffic is relayed through a third-party server - (Google App Engine). It uses a trick to talk to the third party so - that it looks like it is talking to an unblocked server. - Maintained by David Fifield. + <li><a href="https://trac.torproject.org/projects/tor/wiki/doc/meek"><b>meek</b></a></li> + <ul> + <li><strong>Description:</strong> Is a transport that uses HTTP for carrying bytes and TLS for obfuscation. Traffic is relayed through a third-party server (Google App Engine). It uses a trick to talk to the third party so that it looks like it is talking to an unblocked server.</li> + <li><strong>Language:</strong> Go</li> + <li><strong>Maintainer:</strong> David Fifield</li> + <li><strong>Evaluation:</strong> <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/MeekE…">meek Evaluation</a></li> + </ul> </li>  - <li><a href="https://fteproxy.org/"><b>Format-Transforming - Encryption</b></a> (FTE) transforms Tor traffic to arbitrary - formats using their language descriptions. See the <a - href="https://kpdyer.com/publications/ccs2013-fte.pdf">research - paper</a>.</li> - - <li><a href="http://www.cs.kau.se/philwint/scramblesuit/"><b>ScrambleSuit</b></a> - is a pluggable transport that protects - against follow-up probing attacks and is also capable of changing - its network fingerprint (packet length distribution, - inter-arrival times, etc.). It's part of the Obfsproxy framework. - Maintained by Philipp Winter. + <li><a href="https://fteproxy.org/"><b>Format-Transforming Encryption</b></a> (FTE)</li> + <ul> + <li><strong>Description:</strong> It transforms Tor traffic to arbitrary + formats using their language descriptions. See the <a href="https://kpdyer.com/publications/ccs2013-fte.pdf">research paper</a>.</li> + <li><strong>Language:</strong> Python/C++</li> + <li><strong>Maintainger:</strong> Kevin Dyer</li> + <li><strong>Evaluation:</strong> <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/FteEv…">FTE Evaluation</a></li> + </ul> + </li> + + <li><a href="http://www.cs.kau.se/philwint/scramblesuit/"><b>ScrambleSuit</b></a></li> + <ul> + <li><strong>Description:</strong> Is a pluggable transport that protects against follow-up probing attacks and is also capable of changing its network fingerprint (packet length distribution, inter-arrival times, etc.).</li> + <li><strong>Language:</strong> Python</li> + <li><strong>Maintainger:</strong> Philipp Winter</li> + <li><strong>Evaluation:</strong> <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/Scram…"> ScrambleSuit Evaluation</a></li> + </ul> </li>  - <li><b>Obfsproxy</b> is a Python framework for implementing new - pluggable transports. It uses Twisted for its networking needs, and - <a href="https://gitweb.torproject.org/pluggable-transports/pyptlib.git/tree/README.…">pyptlib</a> - for some pluggable transport-related features. It supports the - <a href="https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/tree/doc/o…">obfs2</a> - and - <a href="https://gitweb.torproject.org/pluggable-transports/obfsproxy.git/tree/doc/o…">obfs3</a> - pluggable transports. Maintained by asn. - </li> - - <li><a href="https://crypto.stanford.edu/flashproxy/"><b>Flashproxy</b></a> turns ordinary web browsers into bridges using - websockets, and has a little python stub to hook Tor clients to the - websocket connection. See its - <a href="https://gitweb.torproject.org/flashproxy.git">git repository</a>, - and - <a href="https://crypto.stanford.edu/flashproxy/flashproxy.pdf">design paper</a>. - Maintained by David Fifield. -  - </li> - - </ul> - - <hr> - - <h3>Undeployed PTs</h3> - <br> + <h3>Undeployed PTs</h3> + <br />   <ul> - - <li><b>StegoTorus</b> is an Obfsproxy fork that extends it to a) - split Tor streams across multiple connections to avoid packet size - signatures, and b) embed the traffic flows in traces that look like - HTML, JavasCript, or PDF. See its - <a href="https://gitweb.torproject.org/stegotorus.git">git repository</a>. - Maintained by Zack Weinberg. <br> + <li><b>StegoTorus</b></li> + <ul> + <li><strong>Description:</strong>is an Obfsproxy fork that extends it to a) split Tor streams across multiple connections to avoid packet size signatures, and b) embed the traffic flows in traces that look like HTML, JavasCript, or PDF. See its <a href="https://gitweb.torproject.org/stegotorus.git">git repository</a>.</li> + <li><strong>Language:</strong> C++</li> + <li><strong>Maintainger:</strong> Zack Weinberg</li> + <li><strong>Evaluation:</strong> none</li> + </ul> </li> - <li><b>SkypeMorph</b> transforms Tor traffic flows so they look like - Skype Video. See its - <a href="http://crysp.uwaterloo.ca/software/SkypeMorph-0.5.1.tar.gz">source code</a> - and - <a href="http://cacr.uwaterloo.ca/techreports/2012/cacr2012-08.pdf">design paper</a>. - Maintained by Ian Goldberg. <br> + <li><b>SkypeMorph</b></li> + <ul> + <li><strong>Description:</strong> It transforms Tor traffic flows so they look like Skype Video. See its <a href="http://crysp.uwaterloo.ca/software/SkypeMorph-0.5.1.tar.gz">source code</a> and <a href="http://cacr.uwaterloo.ca/techreports/2012/cacr2012-08.pdf">design paper</a>.</li> + <li><strong>Language:</strong></li> + <li><strong>Maintainger:</strong> Ian Goldberg.</li> + <li><strong>Evaluation:</strong> none</li> + </ul> </li> - <li><b>Dust</b> aims to provide a packet-based (rather than - connection-based) DPI-resistant protocol. See its - <a href="https://github.com/blanu/Dust">git repository</a>. - Maintained by Brandon Wiley. <br> + <li><b>Dust</b></li> + <ul> + <li><strong>Description:</strong> It aims to provide a packet-based (rather than connection-based) DPI-resistant protocol. See its <a href="https://github.com/blanu/Dust">git repository</a>.</li> + <li><strong>Language:</strong> Python</li> + <li><strong>Maintainger:</strong> Brandon Wiley.</li> + <li><strong>Evaluation:</strong> none</li> + </ul> </li> - + </ul> + + <br /><br /> <p> Also see the <emph>unofficial</emph> pluggable transports <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports">wiki page</a> for more pluggable transport information.</p> - <hr> + <p>Our goal is to have a wide variety of Pluggable Transport designs. You can check out a <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/list">full list of Pluggables Transports here</a>.</p> - <p> - Our goal is to have a wide variety of Pluggable Transport designs. - Many are at the research phase now, so it's a perfect time to play - with them or suggest new designs. Please let us know if you find or - start other projects that could be useful for making Tor's traffic - flows more DPI-resistant! + <p>Many are at the research phase now, so it's a perfect time to play with them or suggest new designs. Please let us know if you find or start other projects that could be useful for making Tor's traffic flows more DPI-resistant! </p> </div>

1 0

[webwml/master] Some tweaks to pt page
by sebastian＠torproject.org 15 Jul '16

15 Jul '16

commit e11c4d8a1b59ac4f6b9e1e24f72a86bb3e061a1c Author: Sebastian Hahn <sebastian(a)torproject.org> Date: Fri Jul 15 13:31:43 2016 +0200 Some tweaks to pt page --- docs/en/pluggable-transports.wml | 72 +++++++++++++++++++++++++++------------- 1 file changed, 49 insertions(+), 23 deletions(-) diff --git a/docs/en/pluggable-transports.wml b/docs/en/pluggable-transports.wml index 44e4736..5e15422 100644 --- a/docs/en/pluggable-transports.wml +++ b/docs/en/pluggable-transports.wml @@ -11,28 +11,42 @@ </div> <div id="maincol"> <h1>Tor: Pluggable Transports</h1> - + <hr> - - <h3>Sometimes the Tor network is censored, and you can't connect it.</h3> - + + <h3>Sometimes the Tor network is censored, and you can't connect to + it.</h3> + <br /> - - <p>An increasing number of censoring countries are using Deep Packet Inspection (DPI) to classify Internet traffic flows by protocol. While Tor uses <a href="<page docs/bridges>">bridge relays</a> to get around a censor that blocks by IP address, the censor can use DPI to recognize and filter Tor traffic flows even when they connect to unexpected IP addresses. + + <p> + An increasing number of censoring countries are using Deep Packet + Inspection (DPI) to classify Internet traffic flows by protocol. + While Tor uses <a href="<page docs/bridges>">bridge relays</a> to + get around a censor that blocks by IP address, the censor can use + DPI to recognize and filter Tor traffic flows even when they connect + to unexpected IP addresses. </p> <h3>Pluggable Transports help you bypass censorship against Tor.</h3> - + <br /> - - <p>Pluggable Transports (PT) transform the Tor traffic flow between the client and the bridge. This way, censors who monitor traffic between the client and the bridge will see innocent-looking transformed traffic instead of the actual Tor traffic. External programs can talk to Tor clients and Tor bridges using the <a href="https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt">pluggable transport API</a>, to make it easier to build interoperable programs. + + <p> + Pluggable Transports (PT) transform the Tor traffic flow between the client + and the bridge. This way, censors who monitor traffic between the client + and the bridge will see innocent-looking transformed traffic instead of the + actual Tor traffic. + External programs can talk to Tor clients and Tor bridges using the <a + href="https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt">pluggable + transport API</a>, to make it easier to build interoperable programs. </p> - <h3>Here you will learn:</h3> - + <h3>Learn more:</h3> + <br /> - + <ul> <li><a href="#user">How to use a Pluggable Transport</a></li> <li><a href="#operator">How to become a PT bridge operator</a></li> @@ -44,7 +58,7 @@ <h2 id="user">How to use PTs to bypass censorship</h2> <p>If connections to the Tor network are being blocked by your ISP or country, follow these instructions: </p> - + <a href="$(IMGROOT)/PT/2016-07-how-to-use-PT.png"> <img src="$(IMGROOT)/PT/2016-07-how-to-use-PT.png" width="830" alt="How to use PTs: 1-download tor (send email to gettor(a)torproject.org) 2 select configure 3; check my isp blocks tor option; 4 select obfs4; 5 press connect" /></a>  @@ -58,27 +72,39 @@ <br /> - <p>Anyone can set up a PT bridge server and help provide bandwidth to users who needs it. Once you set up a transport type, your bridge will automatically advertise support for the transport in its descriptor.</p> + <p> + Anyone can set up a PT bridge server and help provide bandwidth to users + who needs it. Once you set up a transport type, your bridge will + automatically advertise support for the transport in its descriptor. + </p> - <p><strong>obfs4</strong> is currently the most effective transport to bypass censorship. We are asking voluntters to run bridges for it.<br /> - To learn how to run this transport, please visit the <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/obfs4…">obfs4proxy wiki page</a>. + <p> + <strong>obfs4</strong> is currently the most effective transport to bypass + censorship. We are asking voluntters to run bridges for it.<br /> To learn + how to run this transport, please visit the <a + href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/obfs4…">obfs4proxy + wiki page</a>. </p> - <p><a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports#Becom…">Go to our wiki</a> to learn how to set up other types of PTs.</p> + <p> + <a + href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports#Becom…">Go + to our wiki</a> to learn how to set up other types of PTs. + </p> <hr> <h2 id="developer">Become a PT developer:</h2> - <p> The links below are the main documentation that will help guide through what you should consider while designing your PT:</p> + <p> The links below are the main documentation for PT developers</p> <ul> <li><a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/Guide…">Guidelines for deploying Pluggable Transports on Tor Browser</a></li> - <li><a href="https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt">PT technical spec</a></li> + <li><a href="https://gitweb.torproject.org/torspec.git/tree/pt-spec.txt">PT technical spec</a></li> <li><a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/PTEva…">Pluggable Transports Evaluation Criteria</a></li> </ul> - <p><a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports">Our wiki</a> is also a great source of information, such as how to <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports#Wayst…:">get in touch with the community</a>, <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/ideas">ideas for new PTs</a>, how to <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/WorkL…">help with PTs already deployed</a> and much more.</p> + <p><a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports">Our wiki</a> is also a great source of information, such as how to <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports#Wayst…">get in touch with the community</a>, <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/ideas">ideas for new PTs</a>, how to <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/WorkL…">help with PTs already deployed</a> and much more.</p> <hr> @@ -102,7 +128,7 @@ <li><a href="https://trac.torproject.org/projects/tor/wiki/doc/meek"><b>meek</b></a></li> <ul> - <li><strong>Description:</strong> Is a transport that uses HTTP for carrying bytes and TLS for obfuscation. Traffic is relayed through a third-party server (Google App Engine). It uses a trick to talk to the third party so that it looks like it is talking to an unblocked server.</li> + <li><strong>Description:</strong> Is a transport that uses HTTP for carrying bytes and TLS for obfuscation. Traffic is relayed through a third-party server (Google App Engine). It uses a trick to talk to the third party so that it looks like it is talking to an unblocked server.</li> <li><strong>Language:</strong> Go</li> <li><strong>Maintainer:</strong> David Fifield</li> <li><strong>Evaluation:</strong> <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/MeekE…">meek Evaluation</a></li> @@ -173,9 +199,9 @@ <li><strong>Evaluation:</strong> none</li> </ul> </li> - + </ul> - + <br /><br /> <p> Also see the <emph>unofficial</emph> pluggable transports <a

1 0

[webwml/master] Remove redundant sentence
by sebastian＠torproject.org 15 Jul '16

15 Jul '16

commit c4cd913c38b541935c2254ed09e85181eeb1c3b9 Author: Sebastian Hahn <sebastian(a)torproject.org> Date: Fri Jul 15 13:32:05 2016 +0200 Remove redundant sentence --- docs/en/pluggable-transports.wml | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/en/pluggable-transports.wml b/docs/en/pluggable-transports.wml index 5e15422..d729353 100644 --- a/docs/en/pluggable-transports.wml +++ b/docs/en/pluggable-transports.wml @@ -204,10 +204,6 @@ <br /><br /> - <p> Also see the <emph>unofficial</emph> pluggable transports <a - href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports">wiki - page</a> for more pluggable transport information.</p> - <p>Our goal is to have a wide variety of Pluggable Transport designs. You can check out a <a href="https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/list">full list of Pluggables Transports here</a>.</p> <p>Many are at the research phase now, so it's a perfect time to play with them or suggest new designs. Please let us know if you find or start other projects that could be useful for making Tor's traffic flows more DPI-resistant!

1 0

[webwml/master] Merge pull request #1 from isabelabagueros/pt-updated
by sebastian＠torproject.org 15 Jul '16

15 Jul '16

commit 95f432a9c2f7e50ba07172276b60273ad801e018 Merge: c21cddf 41612b5 Author: isabelabagueros <isabelabagueros(a)gmail.com> Date: Thu Jul 14 22:21:20 2016 -0700 Merge pull request #1 from isabelabagueros/pt-updated updated pt page organizing content according to audience docs/en/pluggable-transports.wml | 235 ++++++++++++++++++++------------------- 1 file changed, 122 insertions(+), 113 deletions(-)

1 0

[tor-commits] [translation/tor-messenger-loggerproperties_completed] Update translations for tor-messenger-loggerproperties_completed
by translation＠torproject.org 15 Jul '16

15 Jul '16

commit 090db17f0268878ebcd8a886148eed0b8f807491 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jul 15 11:18:22 2016 +0000 Update translations for tor-messenger-loggerproperties_completed --- sk_SK/logger.properties | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/sk_SK/logger.properties b/sk_SK/logger.properties new file mode 100644 index 0000000..69fd977 --- /dev/null +++ b/sk_SK/logger.properties @@ -0,0 +1,7 @@ +# This Source Code Form is subject to the terms of the Mozilla Public +# License, v. 2.0. If a copy of the MPL was not distributed with this +# file, You can obtain one at http://mozilla.org/MPL/2.0/. + +# LOCALIZATION NOTE (badLogfile): +# %S is the filename of the log file. +badLogfile=Prázdny alebo poškodený záznam: %S

1 0

[translation/tor-messenger-loggerproperties] Update translations for tor-messenger-loggerproperties
by translation＠torproject.org 15 Jul '16

15 Jul '16

commit 432e16a11ad82ff8d9727f8b39f3901a1f916bae Author: Translation commit bot <translation(a)torproject.org> Date: Fri Jul 15 11:18:19 2016 +0000 Update translations for tor-messenger-loggerproperties --- sk_SK/logger.properties | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sk_SK/logger.properties b/sk_SK/logger.properties index 2228c50..69fd977 100644 --- a/sk_SK/logger.properties +++ b/sk_SK/logger.properties @@ -4,4 +4,4 @@ # LOCALIZATION NOTE (badLogfile): # %S is the filename of the log file. -badLogfile=Empty or corrupt log file: %S +badLogfile=Prázdny alebo poškodený záznam: %S

1 0