tor-commits March 2018

tor-commits@lists.torproject.org

15 participants
1430 discussions

[webwml/staging] Remove Unix/BSD from install on Linux doc
by arma＠torproject.org 29 Mar '18

29 Mar '18

commit 1f96f2aa8d8ebe111dbba669b06f378f71e635ed Author: hiromipaw <hiro(a)torproject.org> Date: Fri Jan 12 16:31:27 2018 +0100 Remove Unix/BSD from install on Linux doc --- docs/en/tor-doc-unix.wml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/en/tor-doc-unix.wml b/docs/en/tor-doc-unix.wml index c543b53b..3a6f49e6 100644 --- a/docs/en/tor-doc-unix.wml +++ b/docs/en/tor-doc-unix.wml @@ -2,15 +2,15 @@ # Revision: $Revision$ # Translation-Priority: 3-low -#include "head.wmi" TITLE="Tor: Linux/BSD/Unix Install Instructions" CHARSET="UTF-8" +#include "head.wmi" TITLE="Tor: Linux Install Instructions" CHARSET="UTF-8" <div id="content" class="clearfix"> <div id="breadcrumbs"> <a href="<page index>">Home » </a> <a href="<page docs/documentation>">Documentation » </a> - <a href="<page docs/tor-doc-unix>">Linux/BSD/Unix Client</a> + <a href="<page docs/tor-doc-unix>">Linux Client</a> </div> <div id="maincol"> - <h1>Running the <a href="<page index>">Tor</a> client on Linux/BSD/Unix</h1> + <h1>Running the <a href="<page index>">Tor</a> client on Linux</h1> <br> <h2>Note that these are the installation instructions for running a

1 0

[webwml/staging] Fix merge conflicts in sidenav
by arma＠torproject.org 29 Mar '18

29 Mar '18

commit c257c6ccac167d74206771f13d63e04335272661 Merge: 8358537e c30e7120 Author: hiromipaw <hiro(a)torproject.org> Date: Tue Jan 23 11:33:17 2018 +0100 Fix merge conflicts in sidenav about/en/contact.wml | 21 +++++++++++++++------ docs/en/openbsd.wml | 39 --------------------------------------- docs/en/sidenav.wmi | 6 +++--- download/en/download-easy.wml | 20 ++++++++++++++++++++ js/dlpage01.js | 8 +++++--- 5 files changed, 43 insertions(+), 51 deletions(-)

1 0

[webwml/staging] Add new Tor Browser version: 7.5
by arma＠torproject.org 29 Mar '18

29 Mar '18

commit 241c6fe588cacb4de77badac1900f00abbb876ae Author: Nicolas Vigier <boklm(a)torproject.org> Date: Tue Jan 23 21:19:49 2018 +0100 Add new Tor Browser version: 7.5 --- include/versions.wmi | 8 ++++---- projects/torbrowser/RecommendedTBBVersions | 4 ++++ 2 files changed, 8 insertions(+), 4 deletions(-) diff --git a/include/versions.wmi b/include/versions.wmi index 2ba70a6a..d42165a8 100644 --- a/include/versions.wmi +++ b/include/versions.wmi @@ -1,12 +1,12 @@ <define-tag version-stable whitespace=delete>0.3.2.9</define-tag>  -<define-tag version-torbrowserdevelopbranch whitespace=delete>maint-7.0</define-tag> +<define-tag version-torbrowserdevelopbranch whitespace=delete>maint-7.5</define-tag> # *** tor browser stable *** -<define-tag version-torbrowserbundle-all whitespace=delete>7.0.11</define-tag> -<define-tag releasedate-torbrowserbundle-all whitespace=delete>2017-12-09</define-tag> -<define-tag version-win32-stable whitespace=delete>0.3.1.9</define-tag> +<define-tag version-torbrowserbundle-all whitespace=delete>7.5</define-tag> +<define-tag releasedate-torbrowserbundle-all whitespace=delete>2018-01-23</define-tag> +<define-tag version-win32-stable whitespace=delete>0.3.2.9</define-tag> # If all platforms are on the same version, you only to update # version-torbrowserbundle-all and releasedate-torbrowserbundle-all diff --git a/projects/torbrowser/RecommendedTBBVersions b/projects/torbrowser/RecommendedTBBVersions index 382fc74b..16200905 100644 --- a/projects/torbrowser/RecommendedTBBVersions +++ b/projects/torbrowser/RecommendedTBBVersions @@ -3,6 +3,10 @@ "7.0.11-MacOS", "7.0.11-Linux", "7.0.11-Windows", +"7.5", +"7.5-MacOS", +"7.5-Linux", +"7.5-Windows", "7.5a9", "7.5a9-MacOS", "7.5a9-Linux",

1 0

[webwml/staging] delete obsolete docs/en/rpms.wml
by arma＠torproject.org 29 Mar '18

29 Mar '18

commit 467ed909e08e152ab32ec986bcf77ddc5f4661f1 Author: nusenu <nusenu-github(a)riseup.net> Date: Tue Jan 23 14:41:06 2018 +0000 delete obsolete docs/en/rpms.wml --- docs/en/rpms.wml | 47 ----------------------------------------------- 1 file changed, 47 deletions(-) diff --git a/docs/en/rpms.wml b/docs/en/rpms.wml deleted file mode 100644 index 77fd243f..00000000 --- a/docs/en/rpms.wml +++ /dev/null @@ -1,47 +0,0 @@ -## translation metadata -# Revision: $Revision$ -# Translation-Priority: 3-low - -#include "head.wmi" TITLE="Tor Project: CentOS/Fedora Instructions" CHARSET="UTF-8" -<div id="content" class="clearfix"> - <div id="breadcrumbs"> - <a href="<page index>">Home » </a> - <a href="<page docs/documentation>">Documentation » </a> - <a href="<page docs/rpms>">RPMs</a> - </div> - <div id="maincol"> - <a id="rpms"></a> - <h2><a class="anchor" href="#rpms">Tor packages for RPM-based - linux distributions.</a></h2> - <br> - - <h3>Fedora, RHEL, CentOS, Scientific Linux packages</h3> - - <p>Use native Fedora packages for the Fedora distribution or <a href="https://fedoraproject.org/wiki/EPEL">EPEL</a> - packages for distribitons derived from RHEL. - </p> - - - <a id="source"></a> - <h2><a class="anchor" href="#source">Building from source</a></h2> - <br> - - <p> - If you'd like to build from source, please follow the <a - href="<gitblob>doc/contrib/tor-rpm-creation.txt">RPM creation instructions</a>. - </p> - - <hr> - - <p>If you have suggestions for improving this document, please <a - href="<page about/contact>">send them to us</a>. Thanks!</p> - </div> -  - <div id = "sidecol"> -#include "side.wmi" -#include "info.wmi" - </div> -  -</div> - -#include <foot.wmi> \ No newline at end of file

1 0

[webwml/staging] Bug 24881: consolidate relay setup information (new guide)
by arma＠torproject.org 29 Mar '18

29 Mar '18

commit 8358537eea329c42e0b6247c1c9efb615c8047a4 Author: nusenu <nusenu-github(a)riseup.net> Date: Fri Jan 19 19:08:37 2018 +0000 Bug 24881: consolidate relay setup information (new guide) Replace old content with a pointer to the new Tor Relay Guide. --- docs/en/tor-doc-relay.wml | 113 +-------------------------- docs/en/tor-relay-debian.wml | 176 +------------------------------------------ 2 files changed, 2 insertions(+), 287 deletions(-) diff --git a/docs/en/tor-doc-relay.wml b/docs/en/tor-doc-relay.wml index 7f897d3e..9cd702cd 100644 --- a/docs/en/tor-doc-relay.wml +++ b/docs/en/tor-doc-relay.wml @@ -10,118 +10,7 @@ <a href="<page docs/tor-doc-relay>">Configure Tor Relay</a> </div> <div id="maincol"> - - <h1>Configuring a Tor relay</h1> - - <hr> - - <p> - The Tor network relies on volunteers to donate bandwidth. The more - people who run relays, the faster the Tor network will be. If you have - at least 2 megabits/s for both upload and download, please help out - Tor by configuring your Tor to be a relay too. - </p> - - <p>You can run a Tor relay on pretty much any operating system. Tor relays - work best on current distributions of Linux, FreeBSD, NetBSD, and - Windows Server. - </p> - - <p> - The best approach for most users is to <a href="<page - docs/tor-relay-debian>">run your relay on Debian or Ubuntu</a> using - the system Tor package — the deb takes care of running Tor as a - separate user, making sure it has enough file descriptors available, - starting it at boot, and so on. Tor relays also run nicely on other - Linux flavors, and on FreeBSD and NetBSD for those who are comfortable - with those operating systems. - </p> - - <hr> - <a id="torrc"></a> - <h2><a class="anchor" href="#torrc">Configure Tor by editing the torrc file</a></h2> - <br /> - - <p> - Tor's - configuration file is named 'torrc'.</p> - <p>Locate the file on your system, open it with a text editor and add the - following lines:</p> - - <pre> - ORPort 443 - Exitpolicy reject *:* - Nickname ididntedittheconfig - ContactInfo human@... - </pre> - -# TODO: Update link to PT setup docs - <p>If you want to be a bridge, read about the BridgeRelay and - ServerTransportPlugin values <a - href="<page docs/pluggable-transports>">on - this page</a>.</p> - - <p>Tor will use all your bandwidth if you don't set limits for it. Some - options are described in <a href="<page docs/faq>#LimitTotalBandwidth">these</a> - <a href="<page docs/faq>#BandwidthShaping">FAQ entries</a>.</p> - - <p>See the <a href="https://gitweb.torproject.org/tor.git/plain/src/config/torrc.sample.in">sample - torrc file</a> and the <a - href="<page docs/tor-manual>">man - page</a> for other Tor options you may want to set.</p> - - <hr> - <a id="check"></a> - <h2><a class="anchor" href="#check">Make sure your relay is reachable</a></h2> - <br> - - <p>If you are using a firewall, open a hole in your firewall - so incoming connections can reach the ports you configured - (ORPort, plus DirPort if you enabled it). If you have a - hardware firewall (Linksys box, cable modem, etc) you might find <a - href="http://portforward.com/">portforward.com</a> useful. Also, make sure you - allow all <em>outgoing</em> connections too, so your relay can reach the - other Tor relays. - </p> - - <p>Restart your relay. If it <a - href="<page docs/faq>#Logs">logs - any warnings</a>, address them. - </p> - - <p>As soon as your relay manages to connect to the network, it will - try to determine whether the ports you configured are reachable from - the outside. This step is usually fast, but may take up to 20 - minutes. Look for a <a href="<page docs/faq>#Logs">log entry</a> like - <pre>Self-testing indicates your ORPort is reachable from the outside. Excellent.</pre> - If you don't see this message, it means that your relay is not reachable - from the outside — you should re-check your firewalls, check that it's - testing the IP and port you think it should be testing, etc. - </p> - - <p>When your relay has decided that it's reachable, it will upload a "server - descriptor" to the directories, to let clients know - what address, ports, keys, etc your relay is using. You can search <a - href="https://atlas.torproject.org/">Atlas</a> or <a - href="https://globe.torproject.org/">Globe</a> for - the nickname you configured, to make sure it's there. You may need to wait - up to one hour for the directories to publish the new server information.</p> - - <hr> - <a id="after"></a> - <h2><a class="anchor" href="#after">Once your relay is working</a></h2> - <br> - - <p>To learn more about the proper care and feeding for your relay, - see the advice on the <a href=<page docs/tor-relay-debian>#after>Tor - relay on Debian/Ubuntu</a> page. - </p> - - <hr> - - <p>If you have suggestions for improving this document, please <a - href="<page about/contact>">send them to us</a>. Thanks - for helping to make the Tor network grow!</p> + The Tor Relay documentation moved to the <a href="<wiki>TorRelayGuide">wiki</a>. </div>  <div id = "sidecol"> diff --git a/docs/en/tor-relay-debian.wml b/docs/en/tor-relay-debian.wml index 10bebc7c..c470c444 100644 --- a/docs/en/tor-relay-debian.wml +++ b/docs/en/tor-relay-debian.wml @@ -10,181 +10,7 @@ <a href="<page docs/tor-doc-relay>">Configure Tor Relay</a> </div> <div id="maincol"> - - <h1>Configuring a Tor relay on Debian/Ubuntu</h1> - - <hr> - - <p> - The Tor network relies on volunteers to donate bandwidth. The more - people who run relays, the faster the Tor network will be. If you have - at least 250 kilobytes/s each way, please help out Tor by configuring your - Tor to be a relay too. - </p> - - <hr> - <a id="zero"></a> - <a id="install"></a> - <h2><a class="anchor" href="#install">Step One: Download and Install Tor</a></h2> - <br> - - <p>If you're on Debian, start with "apt install tor".</p> - - <p><b>Do not use the packages in Ubuntu's universe.</b> If you're - on Ubuntu or if you want to track newer Tor packages, follow the - <a href="<page docs/debian>#ubuntu">Tor on Ubuntu or Debian</a> - instructions to use our repository. - </p> - - <p>For other Unix/Linux users, you can download Tor from one of our - <a href="<page download/download-unix>">repositories</a>.</p> - - <hr> - <a id="setup"></a> - <h2><a class="anchor" href="#setup">Step Two: Set it up as a relay</a></h2> - - <p> - 1. Make sure your clock, date, and timezone are set correctly. Install - the ntp or openntpd (or similar) package to keep it that way. - </p> - - <p> - 2. Edit the bottom part of <a href="<page - docs/faq>#torrc">/etc/tor/torrc</a>. Define an ORPort. <b>Note - that public relays default to being <a href="<page - docs/faq>#ExitPolicies">exit relays</a></b> — either change your - ExitPolicy line or read our <a -href="<wiki>/doc/TorExitGuidelines">guidelines - for exit relay operators</a>. Be sure to set your ContactInfo line - so we can contact you if you need to upgrade or something goes wrong. - </p> - - <p> - 3. If you are using a firewall, open a hole in your firewall - so incoming connections can reach the ports you configured - (ORPort, plus DirPort if you enabled it). If you have a - hardware firewall (Linksys box, cablemodem, etc) you might like <a - href="http://portforward.com/">portforward.com</a>. Also, make sure you - allow all <em>outgoing</em> connections too, so your relay can reach the - other Tor relays. - </p> - - <p> - 4. Restart your relay: "systemctl reload tor" (as root). - </p> - - <hr> - <a id="check"></a> - <h2><a class="anchor" href="#check">Step Three: Make sure it is working</a></h2> - <br> - - <p>Once your relay connects to the network, it will - try to determine whether the ports you configured are reachable from - the outside. This step is usually fast, but it may take a few minutes. - Look for a <a href="<page docs/faq>#Logs">log entry</a> in your - /var/log/tor/log like - <tt>Self-testing indicates your ORPort is reachable from the outside. Excellent.</tt> - If you don't see this message, it means that your relay is not reachable - from the outside — you should re-check your firewalls, check that it's - testing the IP and port you think it should be testing, etc. - </p> - - <p>When it decides that it's reachable, it will upload a "server - descriptor" to the directory authorities, to let clients know - what address, ports, keys, etc your relay is using. After a few - hours (to give it enough time to propagate), you can query - <a href="https://atlas.torproject.org/">Atlas</a> to see whether your - relay has successfully registered in the network.</p> - - <hr> - <a id="after"></a> - <h2><a class="anchor" href="#after">Step Four: Once it is working</a></h2> - <br> - - <p> - 5. Read - <a href="<wiki>doc/OperationalSecurity">about operational security</a> - to get ideas how you can increase the security of your computer. - </p> - - <p> - 6. Decide about rate limiting. Cable modem, DSL, and other users - who have asymmetric bandwidth (e.g. more down than up) should - rate limit to their slower bandwidth, to avoid congestion. See the <a - href="<page docs/faq>#BandwidthShaping">rate - limiting FAQ entry</a> for details. - </p> - - <p> - 7. If your computer isn't running a webserver, and you haven't set - AccountingMax, please consider - changing your ORPort to 443 and/or your DirPort to 80. Many Tor users - are stuck behind firewalls that only let them browse the web, and - this change will let them reach your Tor relay. If you are already - using ports 80 and 443, other useful ports are 22, 110, and 143. - </p> - - <p> - 8. Consider backing up your Tor relay's private keys - ("/var/lib/tor/keys/secret_id_key" and - "/var/lib/tor/keys/ed25519_master_id_secret_key"). - You'll need these identity keys to - <a href="<page docs/faq>#UpgradeOrMove">move or restore your Tor relay</a>. - </p> - - <p> - 9. If you run an exit relay (great!), don't miss out on our <a - href="<wiki>doc/TorExitGuidelines">Exit Guidelines</a>, including - setting your reverse DNS hostname to make it obvious that you're - a Tor exit relay, and serving the <a - href="<gitblob>contrib/operator-tools/tor-exit-notice.html">Tor - exit notice</a> page on your DirPort. - </p> - - <p> - 10. Subscribe to the <a - href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-announce">tor-announce</a> - mailing list. It is very low volume, and it will keep you informed - of new stable releases. - As a relay operator, you should consider subscribing to the - <a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays"> - tor-relays mailing list</a> too. - We have more <a href="<page docs/documentation>#MailingLists">mailing - lists</a> as well. - </p> - - <p> - 11. Read the <a - href="https://blog.torproject.org/blog/lifecycle-of-a-new-relay">"Lifecycle - of a New Relay"</a> document to learn what sort of activity and usage - patterns you can expect during your relay's first weeks of operation. - </p> - - <p> - 12. If you want to run more than one relay that's great, but please set <a - href="<page docs/faq>#MultipleRelays">the - MyFamily option</a> in all your relays' configuration files. - </p> - - <p> - 13. You might like to use the <a - href="https://nyx.torproject.org/">Nyx</a> relay monitor to watch - your relay's activities from the command line. First, "sudo pip install - nyx". Second, as the user that will be running nyx, run - "sudo adduser $USER debian-tor" to add your user to the debian-tor - group so it can reach Tor's controlsocket. Then log out and log back - in (so your user is actually in the group), and run "nyx". - </p> - - <p> - 14. When you change your Tor configuration, remember to verify that - your relay still works correctly after the change. - </p> - - <hr> - - <p>If you have suggestions for improving this document, please <a - href="<page about/contact>">send them to us</a>. Thanks!</p> + The Tor Relay documentation moved to the <a href="<wiki>TorRelayGuide">wiki</a>. </div>  <div id = "sidecol">

1 0

[webwml/staging] Add back file that was accidentally deleted
by arma＠torproject.org 29 Mar '18

29 Mar '18

commit 91cdf3901b1782e261865f77138d467569ad4224 Author: hiromipaw <hiro(a)torproject.org> Date: Tue Jan 23 14:25:40 2018 +0100 Add back file that was accidentally deleted --- docs/en/rpms.wml | 47 +++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 47 insertions(+) diff --git a/docs/en/rpms.wml b/docs/en/rpms.wml new file mode 100644 index 00000000..77fd243f --- /dev/null +++ b/docs/en/rpms.wml @@ -0,0 +1,47 @@ +## translation metadata +# Revision: $Revision$ +# Translation-Priority: 3-low + +#include "head.wmi" TITLE="Tor Project: CentOS/Fedora Instructions" CHARSET="UTF-8" +<div id="content" class="clearfix"> + <div id="breadcrumbs"> + <a href="<page index>">Home » </a> + <a href="<page docs/documentation>">Documentation » </a> + <a href="<page docs/rpms>">RPMs</a> + </div> + <div id="maincol"> + <a id="rpms"></a> + <h2><a class="anchor" href="#rpms">Tor packages for RPM-based + linux distributions.</a></h2> + <br> + + <h3>Fedora, RHEL, CentOS, Scientific Linux packages</h3> + + <p>Use native Fedora packages for the Fedora distribution or <a href="https://fedoraproject.org/wiki/EPEL">EPEL</a> + packages for distribitons derived from RHEL. + </p> + + + <a id="source"></a> + <h2><a class="anchor" href="#source">Building from source</a></h2> + <br> + + <p> + If you'd like to build from source, please follow the <a + href="<gitblob>doc/contrib/tor-rpm-creation.txt">RPM creation instructions</a>. + </p> + + <hr> + + <p>If you have suggestions for improving this document, please <a + href="<page about/contact>">send them to us</a>. Thanks!</p> + </div> +  + <div id = "sidecol"> +#include "side.wmi" +#include "info.wmi" + </div> +  +</div> + +#include <foot.wmi> \ No newline at end of file

1 0

[webwml/staging] Remove "Installing Tor on Fedora/CentOS" from sidenav
by arma＠torproject.org 29 Mar '18

29 Mar '18

commit 97ff406ac1fc4b6f444be76b8e8d2b5896868299 Author: nusenu <nusenu-github(a)riseup.net> Date: Tue Jan 23 14:38:12 2018 +0000 Remove "Installing Tor on Fedora/CentOS" from sidenav --- docs/en/sidenav.wmi | 3 --- 1 file changed, 3 deletions(-) diff --git a/docs/en/sidenav.wmi b/docs/en/sidenav.wmi index 764c556d..c86c811d 100644 --- a/docs/en/sidenav.wmi +++ b/docs/en/sidenav.wmi @@ -39,9 +39,6 @@ {'url' => 'docs/debian', 'txt' => 'Installing Tor on Debian/Ubuntu', }, - {'url' => 'docs/rpms', - 'txt' => 'Installing Tor on Fedora/CentOS', - }, {'url' => 'docs/tor-doc-unix', 'txt' => 'Installing Tor Source', },

1 0

[webwml/staging] Deprecate old Tor Browser versions
by arma＠torproject.org 29 Mar '18

29 Mar '18

commit ed0609de66fba4a6b8c6cbb8e0034aa8a10ea46c Author: Georg Koppen <gk(a)torproject.org> Date: Thu Jan 25 12:21:44 2018 +0000 Deprecate old Tor Browser versions --- projects/torbrowser/RecommendedTBBVersions | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/projects/torbrowser/RecommendedTBBVersions b/projects/torbrowser/RecommendedTBBVersions index 0e66d29c..852bf2ac 100644 --- a/projects/torbrowser/RecommendedTBBVersions +++ b/projects/torbrowser/RecommendedTBBVersions @@ -1,20 +1,8 @@ [ -"7.0.11", -"7.0.11-MacOS", -"7.0.11-Linux", -"7.0.11-Windows", "7.5", "7.5-MacOS", "7.5-Linux", "7.5-Windows", -"7.5a9", -"7.5a9-MacOS", -"7.5a9-Linux", -"7.5a9-Windows", -"7.5a10", -"7.5a10-MacOS", -"7.5a10-Linux", -"7.5a10-Windows", "8.0a1", "8.0a1-MacOS", "8.0a1-Linux",

1 0

[webwml/staging] Update torbrowser changelog urls
by arma＠torproject.org 29 Mar '18

29 Mar '18

commit 4db67fabfd74d8ffe6ac68339f57c40964017b65 Author: Nicolas Vigier <boklm(a)torproject.org> Date: Tue Jan 23 21:18:34 2018 +0100 Update torbrowser changelog urls --- projects/en/torbrowser.wml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/projects/en/torbrowser.wml b/projects/en/torbrowser.wml index a799034b..c5da8497 100644 --- a/projects/en/torbrowser.wml +++ b/projects/en/torbrowser.wml @@ -740,9 +740,9 @@ <a href="https://www.torproject.org/projects/torbrowser/design/">design document</a>, the <a - href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/Bundle-D…<version-torbrowserdevelopbranch>">ChangeLog + href="https://gitweb.torproject.org/builders/tor-browser-build.git/tree/projects/…<version-torbrowserdevelopbranch>">ChangeLog for the branch <version-torbrowserdevelopbranch></a>, and the <a - href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/Bundle-D…">ChangeLog + href="https://gitweb.torproject.org/builders/tor-browser-build.git/tree/projects/…">ChangeLog for the alpha branch</a>. </p> <p><strong><em>How can I make my own bundle?</em></strong>

1 0

[webwml/staging] We are in 2018 right now
by arma＠torproject.org 29 Mar '18

29 Mar '18

commit cc4b630d058ece9636801ddb9dc2843543535089 Author: Georg Koppen <gk(a)torproject.org> Date: Wed Jan 24 09:20:06 2018 +0000 We are in 2018 right now --- projects/torbrowser/design/index.html.en | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/projects/torbrowser/design/index.html.en b/projects/torbrowser/design/index.html.en index c12ef668..79c00f2a 100644 --- a/projects/torbrowser/design/index.html.en +++ b/projects/torbrowser/design/index.html.en @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="UTF-8"?> -<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>The Design and Implementation of the Tor Browser [DRAFT]</title><meta name="generator" content="DocBook XSL Stylesheets V1.79.1" /></head><body><div class="article"><div class="titlepage"><div><div><h2 class="title"><a id="design"></a>The Design and Implementation of the Tor Browser [DRAFT]</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Mike</span> <span class="surname">Perry</span></h3><div class="affiliation"><div class="address"><p><code class="email"><<a class="email" href="mailto:mikeperry#torproject org">mikeperry#torproject org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Erinn</span> <span class="surname">Clark</span></h3><div class="a ffiliation"><div class="address"><p><code class="email"><<a class="email" href="mailto:erinn#torproject org">erinn#torproject org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Steven</span> <span class="surname">Murdoch</span></h3><div class="affiliation"><div class="address"><p><code class="email"><<a class="email" href="mailto:sjmurdoch#torproject org">sjmurdoch#torproject org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Georg</span> <span class="surname">Koppen</span></h3><div class="affiliation"><div class="address"><p><code class="email"><<a class="email" href="mailto:gk#torproject org">gk#torproject org</a>></code></p></div></div></div></div><div><p class="pubdate">January 24th, 2017</p></div></div><hr /></div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="sect1"><a href="#idm29">1. Introduct ion</a></span></dt><dd><dl><dt><span class="sect2"><a href="#components">1.1. Browser Component Overview</a></span></dt></dl></dd><dt><span class="sect1"><a href="#DesignRequirements">2. Design Requirements and Philosophy</a></span></dt><dd><dl><dt><span class="sect2"><a href="#security">2.1. Security Requirements</a></span></dt><dt><span class="sect2"><a href="#privacy">2.2. Privacy Requirements</a></span></dt><dt><span class="sect2"><a href="#philosophy">2.3. Philosophy</a></span></dt></dl></dd><dt><span class="sect1"><a href="#adversary">3. Adversary Model</a></span></dt><dd><dl><dt><span class="sect2"><a href="#adversary-goals">3.1. Adversary Goals</a></span></dt><dt><span class="sect2"><a href="#adversary-positioning">3.2. Adversary Capabilities - Positioning</a></span></dt><dt><span class="sect2"><a href="#attacks">3.3. Adversary Capabilities - Attacks</a></span></dt></dl></dd><dt><span class="sect1"><a href="#Implementation">4. Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="#proxy-obedience">4.1. Proxy Obedience</a></span></dt><dt><span class="sect2"><a href="#state-separation">4.2. State Separation</a></span></dt><dt><span class="sect2"><a href="#disk-avoidance">4.3. Disk Avoidance</a></span></dt><dt><span class="sect2"><a href="#app-data-isolation">4.4. Application Data Isolation</a></span></dt><dt><span class="sect2"><a href="#identifier-linkability">4.5. Cross-Origin Identifier Unlinkability</a></span></dt><dt><span class="sect2"><a href="#fingerprinting-linkability">4.6. Cross-Origin Fingerprinting Unlinkability</a></span></dt><dt><span class="sect2"><a href="#new-identity">4.7. Long-Term Unlinkability via "New Identity" button</a></span></dt><dt><span class="sect2"><a href="#other-security">4.8. Other Security Measures</a></span></dt></dl></dd><dt><span class="sect1"><a href="#BuildSecurity">5. Build Security and Package Integrity</a></span></dt><dd><dl><dt><span class="sect2"><a href="#idm1107">5.1. Achieving Binary Reprod ucibility</a></span></dt><dt><span class="sect2"><a href="#idm1139">5.2. Package Signatures and Verification</a></span></dt><dt><span class="sect2"><a href="#idm1146">5.3. Anonymous Verification</a></span></dt><dt><span class="sect2"><a href="#update-safety">5.4. Update Safety</a></span></dt></dl></dd><dt><span class="appendix"><a href="#Transparency">A. Towards Transparency in Navigation Tracking</a></span></dt><dd><dl><dt><span class="sect1"><a href="#deprecate">A.1. Deprecation Wishlist</a></span></dt><dt><span class="sect1"><a href="#idm1189">A.2. Promising Standards</a></span></dt></dl></dd></dl></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="idm29"></a>1. Introduction</h2></div></div></div><p> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>The Design and Implementation of the Tor Browser [DRAFT]</title><meta name="generator" content="DocBook XSL Stylesheets V1.79.1" /></head><body><div class="article"><div class="titlepage"><div><div><h2 class="title"><a id="design"></a>The Design and Implementation of the Tor Browser [DRAFT]</h2></div><div><div class="author"><h3 class="author"><span class="firstname">Mike</span> <span class="surname">Perry</span></h3><div class="affiliation"><div class="address"><p><code class="email"><<a class="email" href="mailto:mikeperry#torproject org">mikeperry#torproject org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Erinn</span> <span class="surname">Clark</span></h3><div class="a ffiliation"><div class="address"><p><code class="email"><<a class="email" href="mailto:erinn#torproject org">erinn#torproject org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Steven</span> <span class="surname">Murdoch</span></h3><div class="affiliation"><div class="address"><p><code class="email"><<a class="email" href="mailto:sjmurdoch#torproject org">sjmurdoch#torproject org</a>></code></p></div></div></div></div><div><div class="author"><h3 class="author"><span class="firstname">Georg</span> <span class="surname">Koppen</span></h3><div class="affiliation"><div class="address"><p><code class="email"><<a class="email" href="mailto:gk#torproject org">gk#torproject org</a>></code></p></div></div></div></div><div><p class="pubdate">January 24th, 2018</p></div></div><hr /></div><div class="toc"><p><strong>Table of Contents</strong></p><dl class="toc"><dt><span class="sect1"><a href="#idm29">1. Introduct ion</a></span></dt><dd><dl><dt><span class="sect2"><a href="#components">1.1. Browser Component Overview</a></span></dt></dl></dd><dt><span class="sect1"><a href="#DesignRequirements">2. Design Requirements and Philosophy</a></span></dt><dd><dl><dt><span class="sect2"><a href="#security">2.1. Security Requirements</a></span></dt><dt><span class="sect2"><a href="#privacy">2.2. Privacy Requirements</a></span></dt><dt><span class="sect2"><a href="#philosophy">2.3. Philosophy</a></span></dt></dl></dd><dt><span class="sect1"><a href="#adversary">3. Adversary Model</a></span></dt><dd><dl><dt><span class="sect2"><a href="#adversary-goals">3.1. Adversary Goals</a></span></dt><dt><span class="sect2"><a href="#adversary-positioning">3.2. Adversary Capabilities - Positioning</a></span></dt><dt><span class="sect2"><a href="#attacks">3.3. Adversary Capabilities - Attacks</a></span></dt></dl></dd><dt><span class="sect1"><a href="#Implementation">4. Implementation</a></span></dt><dd><dl><dt><span class="sect2"><a href="#proxy-obedience">4.1. Proxy Obedience</a></span></dt><dt><span class="sect2"><a href="#state-separation">4.2. State Separation</a></span></dt><dt><span class="sect2"><a href="#disk-avoidance">4.3. Disk Avoidance</a></span></dt><dt><span class="sect2"><a href="#app-data-isolation">4.4. Application Data Isolation</a></span></dt><dt><span class="sect2"><a href="#identifier-linkability">4.5. Cross-Origin Identifier Unlinkability</a></span></dt><dt><span class="sect2"><a href="#fingerprinting-linkability">4.6. Cross-Origin Fingerprinting Unlinkability</a></span></dt><dt><span class="sect2"><a href="#new-identity">4.7. Long-Term Unlinkability via "New Identity" button</a></span></dt><dt><span class="sect2"><a href="#other-security">4.8. Other Security Measures</a></span></dt></dl></dd><dt><span class="sect1"><a href="#BuildSecurity">5. Build Security and Package Integrity</a></span></dt><dd><dl><dt><span class="sect2"><a href="#idm1107">5.1. Achieving Binary Reprod ucibility</a></span></dt><dt><span class="sect2"><a href="#idm1139">5.2. Package Signatures and Verification</a></span></dt><dt><span class="sect2"><a href="#idm1146">5.3. Anonymous Verification</a></span></dt><dt><span class="sect2"><a href="#update-safety">5.4. Update Safety</a></span></dt></dl></dd><dt><span class="appendix"><a href="#Transparency">A. Towards Transparency in Navigation Tracking</a></span></dt><dd><dl><dt><span class="sect1"><a href="#deprecate">A.1. Deprecation Wishlist</a></span></dt><dt><span class="sect1"><a href="#idm1189">A.2. Promising Standards</a></span></dt></dl></dd></dl></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="idm29"></a>1. Introduction</h2></div></div></div><p> This document describes the <a class="link" href="#adversary" title="3. Adversary Model">adversary model</a>, <a class="link" href="#DesignRequirements" title="2. Design Requirements and Philosophy">design requirements</a>, and <a class="link" href="#Implementation" title="4. Implementation">implementation</a> of the Tor Browser. It is current as of Tor Browser

1 0

← Newer
1
...
6
7
8
9
10
11
12
...
143
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits March 2018