tor-commits September 2011

tor-commits@lists.torproject.org

19 participants
865 discussions

r25086: {website} actually really truly link to the vidalia foo bundle correct (website/trunk/include)
by Roger Dingledine 18 Sep '11

18 Sep '11

Author: arma Date: 2011-09-18 15:50:03 +0000 (Sun, 18 Sep 2011) New Revision: 25086 Modified: website/trunk/include/versions.wmi Log: actually really truly link to the vidalia foo bundle correctly this time for sure! Modified: website/trunk/include/versions.wmi =================================================================== --- website/trunk/include/versions.wmi 2011-09-18 15:37:57 UTC (rev 25085) +++ website/trunk/include/versions.wmi 2011-09-18 15:50:03 UTC (rev 25086) @@ -67,19 +67,19 @@ <define-tag file-win32-bundle-alpha whitespace=delete>vidalia-bundle-<version-win32-bundle-alpha>-0.2.14.exe</define-tag> <define-tag package-win32-bundle-alpha whitespace=delete>/dist/vidalia-bundles/<file-win32-bundle-alpha></define-tag> -<define-tag file-win32-bridge-bundle-stable whitespace=delete>vidalia-bundle-<version-win32-bundle-stable>-0.2.14.exe</define-tag> +<define-tag file-win32-bridge-bundle-stable whitespace=delete>vidalia-bridge-bundle-<version-win32-bundle-stable>-0.2.14.exe</define-tag> <define-tag package-win32-bridge-bundle-stable whitespace=delete>/dist/vidalia-bundles/<file-win32-bridge-bundle-stable></define-tag> -<define-tag file-win32-bridge-bundle-alpha whitespace=delete>vidalia-bundle-<version-win32-bundle-alpha>-0.2.14.exe</define-tag> +<define-tag file-win32-bridge-bundle-alpha whitespace=delete>vidalia-bridge-bundle-<version-win32-bundle-alpha>-0.2.14.exe</define-tag> <define-tag package-win32-bridge-bundle-alpha whitespace=delete>/dist/vidalia-bundles/<file-win32-bridge-bundle-alpha></define-tag> -<define-tag file-win32-relay-bundle-stable whitespace=delete>vidalia-bundle-<version-win32-bundle-stable>-0.2.14.exe</define-tag> +<define-tag file-win32-relay-bundle-stable whitespace=delete>vidalia-relay-bundle-<version-win32-bundle-stable>-0.2.14.exe</define-tag> <define-tag package-win32-relay-bundle-stable whitespace=delete>/dist/vidalia-bundles/<file-win32-relay-bundle-stable></define-tag> -<define-tag file-win32-relay-bundle-alpha whitespace=delete>vidalia-bundle-<version-win32-bundle-alpha>-0.2.14.exe</define-tag> +<define-tag file-win32-relay-bundle-alpha whitespace=delete>vidalia-relay-bundle-<version-win32-bundle-alpha>-0.2.14.exe</define-tag> <define-tag package-win32-relay-bundle-alpha whitespace=delete>/dist/vidalia-bundles/<file-win32-relay-bundle-alpha></define-tag> -<define-tag file-win32-exit-bundle-stable whitespace=delete>vidalia-bundle-<version-win32-bundle-stable>-0.2.14.exe</define-tag> +<define-tag file-win32-exit-bundle-stable whitespace=delete>vidalia-exit-bundle-<version-win32-bundle-stable>-0.2.14.exe</define-tag> <define-tag package-win32-exit-bundle-stable whitespace=delete>/dist/vidalia-bundles/<file-win32-exit-bundle-stable></define-tag> -<define-tag file-win32-exit-bundle-alpha whitespace=delete>vidalia-bundle-<version-win32-bundle-alpha>-0.2.14.exe</define-tag> +<define-tag file-win32-exit-bundle-alpha whitespace=delete>vidalia-exit-bundle-<version-win32-bundle-alpha>-0.2.14.exe</define-tag> <define-tag package-win32-exit-bundle-alpha whitespace=delete>/dist/vidalia-bundles/<file-win32-exit-bundle-alpha></define-tag> <define-tag file-osx-x86-bundle-stable whitespace=delete>vidalia-bundle-<version-osx-x86-bundle-stable>-0.2.14-i386.dmg</define-tag>

1 0

r25085: {website} the windows bridge/exit/relay bundles were all pointing to h (website/trunk/download/en)
by Roger Dingledine 18 Sep '11

18 Sep '11

Author: arma Date: 2011-09-18 15:37:57 +0000 (Sun, 18 Sep 2011) New Revision: 25085 Modified: website/trunk/download/en/download.wml Log: the windows bridge/exit/relay bundles were all pointing to https://www.torproject.org/dist/vidalia-bundles/vidalia-bundle-0.2.2.33-0.2… Modified: website/trunk/download/en/download.wml =================================================================== --- website/trunk/download/en/download.wml 2011-09-18 15:36:21 UTC (rev 25084) +++ website/trunk/download/en/download.wml 2011-09-18 15:37:57 UTC (rev 25085) @@ -85,7 +85,7 @@  <div class="package"> <div class="downloads"> - <a class="button" href="<package-win32-relay-bundle-stable>.exe">DownloadVidalia Relay Bundle (Beta)</a> + <a class="button" href="<package-win32-relay-bundle-stable>">DownloadVidalia Relay Bundle (Beta)</a> <div class="sig"> (<a href="<package-win32-relay-bundle-stable>.asc">sig</a>) <a class="siginfo" href="<page docs/verifying-signatures>">What's This?</a> </div> @@ -99,7 +99,7 @@  <div class="package"> <div class="downloads"> - <a class="button" href="<package-win32-exit-bundle-stable>.exe">DownloadVidalia Exit Bundle (Beta)</a> + <a class="button" href="<package-win32-exit-bundle-stable>">DownloadVidalia Exit Bundle (Beta)</a> <div class="sig"> (<a href="<package-win32-exit-bundle-stable>.asc">sig</a>) <a class="siginfo" href="<page docs/verifying-signatures>">What's This?</a> </div>

1 0

r25084: {website} the windows bridge/relay/exit bundle links were pointing at (website/trunk/include)
by Roger Dingledine 18 Sep '11

18 Sep '11

Author: arma Date: 2011-09-18 15:36:21 +0000 (Sun, 18 Sep 2011) New Revision: 25084 Modified: website/trunk/include/versions.wmi Log: the windows bridge/relay/exit bundle links were pointing at the main bundle only Modified: website/trunk/include/versions.wmi =================================================================== --- website/trunk/include/versions.wmi 2011-09-17 00:59:13 UTC (rev 25083) +++ website/trunk/include/versions.wmi 2011-09-18 15:36:21 UTC (rev 25084) @@ -68,19 +68,19 @@ <define-tag package-win32-bundle-alpha whitespace=delete>/dist/vidalia-bundles/<file-win32-bundle-alpha></define-tag> <define-tag file-win32-bridge-bundle-stable whitespace=delete>vidalia-bundle-<version-win32-bundle-stable>-0.2.14.exe</define-tag> -<define-tag package-win32-bridge-bundle-stable whitespace=delete>/dist/vidalia-bundles/<file-win32-bundle-stable></define-tag> +<define-tag package-win32-bridge-bundle-stable whitespace=delete>/dist/vidalia-bundles/<file-win32-bridge-bundle-stable></define-tag> <define-tag file-win32-bridge-bundle-alpha whitespace=delete>vidalia-bundle-<version-win32-bundle-alpha>-0.2.14.exe</define-tag> -<define-tag package-win32-bridge-bundle-alpha whitespace=delete>/dist/vidalia-bundles/<file-win32-bundle-alpha></define-tag> +<define-tag package-win32-bridge-bundle-alpha whitespace=delete>/dist/vidalia-bundles/<file-win32-bridge-bundle-alpha></define-tag> <define-tag file-win32-relay-bundle-stable whitespace=delete>vidalia-bundle-<version-win32-bundle-stable>-0.2.14.exe</define-tag> -<define-tag package-win32-relay-bundle-stable whitespace=delete>/dist/vidalia-bundles/<file-win32-bundle-stable></define-tag> +<define-tag package-win32-relay-bundle-stable whitespace=delete>/dist/vidalia-bundles/<file-win32-relay-bundle-stable></define-tag> <define-tag file-win32-relay-bundle-alpha whitespace=delete>vidalia-bundle-<version-win32-bundle-alpha>-0.2.14.exe</define-tag> -<define-tag package-win32-relay-bundle-alpha whitespace=delete>/dist/vidalia-bundles/<file-win32-bundle-alpha></define-tag> +<define-tag package-win32-relay-bundle-alpha whitespace=delete>/dist/vidalia-bundles/<file-win32-relay-bundle-alpha></define-tag> <define-tag file-win32-exit-bundle-stable whitespace=delete>vidalia-bundle-<version-win32-bundle-stable>-0.2.14.exe</define-tag> -<define-tag package-win32-exit-bundle-stable whitespace=delete>/dist/vidalia-bundles/<file-win32-bundle-stable></define-tag> +<define-tag package-win32-exit-bundle-stable whitespace=delete>/dist/vidalia-bundles/<file-win32-exit-bundle-stable></define-tag> <define-tag file-win32-exit-bundle-alpha whitespace=delete>vidalia-bundle-<version-win32-bundle-alpha>-0.2.14.exe</define-tag> -<define-tag package-win32-exit-bundle-alpha whitespace=delete>/dist/vidalia-bundles/<file-win32-bundle-alpha></define-tag> +<define-tag package-win32-exit-bundle-alpha whitespace=delete>/dist/vidalia-bundles/<file-win32-exit-bundle-alpha></define-tag> <define-tag file-osx-x86-bundle-stable whitespace=delete>vidalia-bundle-<version-osx-x86-bundle-stable>-0.2.14-i386.dmg</define-tag> <define-tag package-osx-x86-bundle-stable whitespace=delete>/dist/vidalia-bundles/<file-osx-x86-bundle-stable></define-tag>

1 0

[metrics-web/master] Fix a typo.
by karsten＠torproject.org 17 Sep '11

17 Sep '11

commit d1a9d14a45c15c054e083ef57d50ab5d1deadfa6 Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Sat Sep 17 20:22:22 2011 +0200 Fix a typo. --- web/WEB-INF/formats.jsp | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/web/WEB-INF/formats.jsp b/web/WEB-INF/formats.jsp index 0326d5b..31078c0 100644 --- a/web/WEB-INF/formats.jsp +++ b/web/WEB-INF/formats.jsp @@ -817,7 +817,7 @@ Tor Check makes the list of known exits and corresponding exit IP addresses available in a specific format. The document below shows an entry of the exit list written on December 28, 2010 at 15:21:44 UTC. -This entry means that the relay with fingerprint <tt>63Ba..</tt> which +This entry means that the relay with fingerprint <tt>63BA..</tt> which published a descriptor at 07:35:55 and was contained in a version 2 network status from 08:10:11 uses two different IP addresses for exiting. The first address <tt>91.102.152.236</tt> was found in a test performed at

1 0

r25083: {website} 2010 financial results are now available. Maybe someone will (in website/trunk/about: en findoc)
by Andrew Lewman 17 Sep '11

17 Sep '11

Author: phobos Date: 2011-09-17 00:59:13 +0000 (Sat, 17 Sep 2011) New Revision: 25083 Added: website/trunk/about/findoc/2010-TorProject-combined-Form990_PC_Audit_Results.pdf website/trunk/about/findoc/2010-TorProject-combined-Form990_PC_Audit_Results.pdf.asc Modified: website/trunk/about/en/financials.wml Log: 2010 financial results are now available. Maybe someone will leak these public documents again. Modified: website/trunk/about/en/financials.wml =================================================================== --- website/trunk/about/en/financials.wml 2011-09-16 02:32:04 UTC (rev 25082) +++ website/trunk/about/en/financials.wml 2011-09-17 00:59:13 UTC (rev 25083) @@ -13,6 +13,8 @@ <div id="maincol"> <h1>Tor: Financial Reports</h1> <dl> + <dt>Fiscal Year 2010</dt> + <dd><a href="findoc/2010-TorProject-combined-Form990_PC_Audit_Results.pdf">2010 IRS Form 990, State of MA Form PC, and Independent Audit Results</a></dd> <dt>Fiscal Year 2009</dt> <dd><a href="findoc/2009-TorProject-Annual-Report.pdf">2009 Annual Report</a></dd> <dd><a href="findoc/2009-TorProject-Form990andPC.pdf">2009 IRS Form 990 and State of MA Form PC</a></dd> Added: website/trunk/about/findoc/2010-TorProject-combined-Form990_PC_Audit_Results.pdf =================================================================== (Binary files differ) Property changes on: website/trunk/about/findoc/2010-TorProject-combined-Form990_PC_Audit_Results.pdf ___________________________________________________________________ Added: svn:mime-type + application/octet-stream Added: website/trunk/about/findoc/2010-TorProject-combined-Form990_PC_Audit_Results.pdf.asc =================================================================== --- website/trunk/about/findoc/2010-TorProject-combined-Form990_PC_Audit_Results.pdf.asc (rev 0) +++ website/trunk/about/findoc/2010-TorProject-combined-Form990_PC_Audit_Results.pdf.asc 2011-09-17 00:59:13 UTC (rev 25083) @@ -0,0 +1,16 @@ +-----BEGIN PGP SIGNATURE----- + +iQIcBAABCAAGBQJOc+/xAAoJEM3X9rV07TNrlHcQAMBB1WLDi+uQwTGqcA/j68QB +uaF2ncd+IHKb1WCgvZi1FravA55yTZmTjXhE95iY1SZqLIzGabY3H1F+3d12lNLx +iPepQhXuBvumk0/+Ioc30W1ZOJxzimcuGCQ5hbqhyGAOZoFO7LHvp/tl1bZn6w8N +5D5kJedWGACoLCJIzSIM8xUUksaq5n3H8ERd/Z8qcnNAluCl5QDsdrnKj78q5fqp +l17sK8ZUi54fp0iccewSSme8Qfoe6uBtqEZDuBW+obd/283A8JKs9Q7qSLIdit9/ +KJOHbmwy6IrDnfd5aUpKWAr+ajAVhrt/p4Tr5wxqlBaFxvOGmCOWZppqnD7v38At +T40sX0jIsaXTLX90R7luZuNWdHkoBbN4Wpj8RfH6DXE/gsOb88Tb4m/D4Sr0XxTO +Di1KQG65ZUmFb9hpihJcE+xwh9SpzPHF3Yq1+NIem+iwHrNG5f3Ugon1rSzYHLmU +iKAETw+xiRExUwqFoVZgPb0iDLplcI9bKgzm8hAkUzctyTQaUkpovixgleqIkrHI +Ft2Q6TAXpi/pw4mCPiNnzzOgHcvwAUIoAR2iMrMthkZ61OSwHIFqDTTUfuNkRf67 +RTwi+8lVVmXXquJFjs30FDiWzISydfQZFiqFbO2cEdMi0xiGVsMK/zSZQwuqvqMh +PTQE1Q4mNB6AVQWwrTff +=O/R2 +-----END PGP SIGNATURE----- Property changes on: website/trunk/about/findoc/2010-TorProject-combined-Form990_PC_Audit_Results.pdf.asc ___________________________________________________________________ Added: svn:mime-type + text/plain

1 0

r25082: {website} fix the odd character encodings. (website/trunk/eff/en)
by Andrew Lewman 16 Sep '11

16 Sep '11

Author: phobos Date: 2011-09-16 02:32:04 +0000 (Fri, 16 Sep 2011) New Revision: 25082 Modified: website/trunk/eff/en/tor-dmca-response.wml Log: fix the odd character encodings. Modified: website/trunk/eff/en/tor-dmca-response.wml =================================================================== --- website/trunk/eff/en/tor-dmca-response.wml 2011-09-16 02:26:27 UTC (rev 25081) +++ website/trunk/eff/en/tor-dmca-response.wml 2011-09-16 02:32:04 UTC (rev 25082) @@ -14,7 +14,7 @@ Note to Tor relay operators: In this litigious era, anyone providing routing services may face copyright complaints for transmitted content. Fortunately, the Digital Millennium Copyright Act safe harbors should -provide protections from many of them�both to you and to your upstream +provide protections from many of them both to you and to your upstream provider. If your Internet host forwards a DMCA copyright complaint to you, you can use this template to write a response, though you will need to customize it to your situation. Please also ensure all the statements @@ -56,7 +56,7 @@ run. As you know, the DMCA creates four "safe harbors" for service providers to protect them from copyright liability for the acts of their -users, when the ISPs fulfill certain requirements. (17 U.S.C. � 512) The +users, when the ISPs fulfill certain requirements. (17 U.S.C. § 512) The DMCA's requirements vary depending on the ISP's role. You may be familiar with the "notice and takedown" provisions of section 512(c) of the DMCA; however, those do not apply when an ISP merely acts as a @@ -80,7 +80,7 @@ terminates subscribers who are repeat infringers. The notification you received is certainly not proof of the "repeat infringement" that is required under the law before you need to terminate my account. In fact, -it�s not even proof of any copyright infringement; a notice claiming +it's not even proof of any copyright infringement; a notice claiming infringement is not the same as a determination of infringement. I have not infringed any copyrights and do not intend to do so. Therefore, you should continue to be protected under the DMCA 512(a) safe harbor

1 0

r25081: {website} remove the tor challenge link at the bottom, update the tor- (website/trunk/eff/en)
by Andrew Lewman 16 Sep '11

16 Sep '11

Author: phobos Date: 2011-09-16 02:26:27 +0000 (Fri, 16 Sep 2011) New Revision: 25081 Modified: website/trunk/eff/en/tor-dmca-response.wml website/trunk/eff/en/tor-legal-faq.wml Log: remove the tor challenge link at the bottom, update the tor-dmca-template to the shiny new one from eff. Modified: website/trunk/eff/en/tor-dmca-response.wml =================================================================== --- website/trunk/eff/en/tor-dmca-response.wml 2011-09-16 02:21:22 UTC (rev 25080) +++ website/trunk/eff/en/tor-dmca-response.wml 2011-09-16 02:26:27 UTC (rev 25081) @@ -7,124 +7,110 @@  -<h2>Response template for Tor relay maintainer to ISP</h2> +<h2>Response template for Tor relay operator to ISP</h2> <hr> -Written by the Electronic Frontier -Foundation (<a href="http://www.eff.org/">EFF</a>). Last updated 19 Feb 2005. - -Note to Tor relay operators: In this litigous era, anyone -providing routing services may face copyright complaints under the -Digital Millennium Copyright Act. Thankfully, the DMCA safe harbors -provide immunity from many of them -- both to you and to your -upstream provider. If your Internet host forwards a DMCA complaint -to you, here's a template you can use to write a response. You can -tailor this to your own circumstances: if you think your host would -be disturbed to hear you're running a relay on the network, you may -want to take that part out. Of course it's up to you to comply with -your ISP's terms of service. If you're not comfortable including so -much legal explanation, feel free to invite the ISP to contact EFF -for a fuller discussion. - +Written by the Electronic Frontier Foundation (<a +href="https://www.eff.org">EFF</a>). Last updated May 31, 2011. +Note to Tor relay operators: In this litigious era, anyone providing +routing services may face copyright complaints for transmitted content. +Fortunately, the Digital Millennium Copyright Act safe harbors should +provide protections from many of them�both to you and to your upstream +provider. If your Internet host forwards a DMCA copyright complaint to +you, you can use this template to write a response, though you will need +to customize it to your situation. Please also ensure all the statements +are true for you. (The Tor Project has an <a +href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorAbuseTempla…">abuse +collection of templates</a> to help you respond to other types of abuse +complaints, too.) Before sending any response to your ISP, you may want +to seek the advice of an attorney licensed to practice in your +jurisdiction. This template letter is for informational purposes only and does not constitute legal advice. Whether and how you should respond when you or -your ISP has received a DMCA notice will turn on the particular facts -of your situation. This template is intended as a starting point. Before -sending any response to your ISP, you may want to seek the advice of an -attorney licensed to practice in your jurisdiction. +your ISP has received a DMCA notice will turn on the particular facts of +your situation. This template is intended as a starting point, but you +should tailor it to your own circumstances. In addition, it's up to you +to comply with your ISP's terms of service. If you're not comfortable +including so much legal explanation, feel free to invite the ISP to +contact EFF for a fuller discussion. +If you do not believe the safe harbors apply to your particular +situation, don't use this template as a basis for your response. +Specific information about safe harbor qualification for "transitory +digital network communications" is provided on the Chilling Effects +website <a +href="https://www.chillingeffects.org/dmca512/faq.cgi#QID586">here</a> +and also in the template, below. -Also, if you received this document from anywhere besides <a -href="https://torproject.org/eff/tor-dmca-response.html">https://www.torproject.org/eff/tor-dmca-response.html</a>, +Also, if you received this document from anywhere other than the EFF +web site or <a +href="<page eff/tor-dmca-response>" +title="<page eff/tor-dmca-response>"><page eff/tor-dmca-response></a>, it may be out of date. Follow the link to get the latest version. - -<hr> - -Dear [ISP]: - +<blockquote> +Dear [ISP]: Thank you for forwarding me the notice you received from [copyright -claimant] regarding [content]. I would like to assure you that, -contrary to the assertions in the notice, 1) I am not hosting or -making available the claimed infringing materials, and 2) you are -already protected by the Digital Millennium Copyright Act's ("DMCA") -safe harbor from any liability arising from this complaint. The -notice is incorrect, probably based upon misunderstandings about law -and about some of the software I run. - - - -First, in terms of legal liability, this notice does not create any -risk for you as a service provider. As you know, the DMCA creates -four "safe harbors" for service providers to protect them from -copyright liability for the acts of their users, when the ISPs -fulfill certain requirements. (17 U.S.C. � 512) The DMCA's -requirements vary depending on the ISP's role. You may be most -familiar with the "notice and takedown" provisions of DMCA 512(c), -but those apply only to content hosted on your servers, or to linking -and caching activity. The "takedown notice" provisions do not apply -when an ISP merely acts as a conduit. Instead, the "conduit" safe -harbor of DMCA 512(a) has different and less burdensome requirements, -as the D.C. Circuit Court of Appeals held in RIAA v. Verizon (see -<a href="http://www.eff.org/legal/cases/RIAA_v_Verizon/opinion-20031219.pdf">http://www.eff.org/legal/cases/RIAA_v_Verizon/opinion-20031219.pdf</a>) +claimant] regarding [content]. I would like to assure you that I am not +hosting the claimed infringing materials, and furthermore, the Digital +Millennium Copyright Act's ("DMCA") safe harbors likely protect you from +liability arising from this complaint. The notice is likely based upon +misunderstandings about the law and about some of the software I +run. +As you know, the DMCA creates four "safe harbors" for service +providers to protect them from copyright liability for the acts of their +users, when the ISPs fulfill certain requirements. (17 U.S.C. � 512) The +DMCA's requirements vary depending on the ISP's role. You may be +familiar with the "notice and takedown" provisions of section 512(c) of +the DMCA; however, those do not apply when an ISP merely acts as a +conduit. Instead, the "conduit" safe harbor of section 512(a) of the +DMCA has different and less burdensome eligibility requirements, as the +D.C. Circuit Court of Appeals held in RIAA v. Verizon (see <a +href="https://www.eff.org/legal/cases/RIAA_v_Verizon/opinion-20031219.pdf" +title="https://www.eff.org/legal/cases/RIAA_v_Verizon/opinion-20031219.pdf">https://www.eff.org/legal/cases/RIAA_v_Verizon/opinion-20031219.pdf</a>) and the Eighth Circuit Court of Appeals confirmed in RIAA v. Charter -(see <a href="http://www.eff.org/IP/P2P/Charter/033802P.pdf">http://www.eff.org/IP/P2P/Charter/033802P.pdf</a>). - +(see <a href="https://w2.eff.org/IP/P2P/Charter/033802P.pdf" +title="https://w2.eff.org/IP/P2P/Charter/033802P.pdf">https://w2.eff.org/IP/P2P/Charter/033802P.pdf</a>). +Under DMCA 512(a), service providers like you are typically protected +from damages for copyright infringement claims if you also maintain "a +policy that provides for termination in appropriate circumstances of +subscribers and account holders of the service provider's system or +network who are repeat infringers." If you have and implement such a +policy, and you otherwise qualify for the safe harbor, you should be +free from fear of copyright damages. - -Here, any content that came from or through my computers merely -passed through your network, so DMCA 512(a) applies. Under DMCA -512(a), you are immune from money damages for copyright infringement -claims if you maintain "a policy that provides for termination in -appropriate circumstances of subscribers and account holders of the -service provider's system or network who are repeat infringers." If -you have and implement such a policy, you are free from fear of -copyright damages, period. - - - -As for what makes a reasonable policy, as the law says, it's one that -only terminates subscribers who are repeat infringers. A notice -claiming infringement is not the same as a determination of -infringement. The notification you received is not proof of any -copyright infringement, and it certainly is not proof of the "repeat -infringement" that is required under the law before you need to -terminate my account. I have not infringed any copyrights and do not -intend to do so. Therefore, you continue to be protected under the -DMCA 512(a) safe harbor, without taking any further action. - - - -You might be curious, though, about what did trigger the notice. The -software that likely triggered the faulty notice is a program I run -called Tor. Tor is network software that helps users to enhance -their privacy, security, and safety online. It does not host or make -available any content. Rather, it is part of a network of nodes on -the Internet that simply pass packets among themselves before sending -them to their destinations, just as any Internet host does. The +As for what makes a reasonable policy, as the law says, it's one that +terminates subscribers who are repeat infringers. The notification you +received is certainly not proof of the "repeat infringement" that is +required under the law before you need to terminate my account. In fact, +it�s not even proof of any copyright infringement; a notice claiming +infringement is not the same as a determination of infringement. I have +not infringed any copyrights and do not intend to do so. Therefore, you +should continue to be protected under the DMCA 512(a) safe harbor +without taking any further action. +You may be curious about what prompted the faulty notice. It was +likely triggered by a program I run called Tor. Tor is network software +that helps users to enhance their privacy, security, and safety online. +It does not host any content. Rather, it is part of a network of nodes +on the Internet that simply pass packets among themselves before sending +them to their destinations, just as any Internet intermediary does. The difference is that Tor tunnels the connections such that no hop can learn both the source and destination of the packets, giving users -protection from nefarious snooping on network traffic. Tor protects +protection from nefarious snooping on network traffic. The result is +that, unlike most other Internet traffic, the final IP address that the +recipient receives is not the IP address of the sender. Tor protects users against hazards such as harassment, spam, and identity theft. -In fact, initial development of Tor, including deployment of a -public-use Tor network, was a project of the U.S. Naval Research -Laboratory, with funding from ONR and DARPA. (For more on Tor, -see <a -href="https://www.torproject.org/">https://www.torproject.org/</a>.) -As an organization committed to -protecting the privacy of its customers, I hope you'll agree that -this is a valuable technology. - - - -Thank you for working with me on this matter. As a loyal subscriber, +Initial development of Tor, including deployment of a public-use Tor +network, was a project of the U.S. Naval Research Laboratory, with +funding from ONR and DARPA. (For more on Tor, see <a +href="https://www.torproject.org/" +title="https://www.torproject.org/">https://www.torproject.org/</a>.) I +hope, as an organization committed to protecting the privacy of its +customers, you'll agree that this is a valuable technology. +Thank you for working with me on this matter. As a loyal subscriber, I appreciate your notifying me of this issue and hope that the -complete protections of DMCA 512 put any concerns you may have at -rest. If not, please contact me with any further questions. - +protections of DMCA 512 put any concerns you may have to rest. If not, +please contact me with any further questions. +Very truly yours, +Your customer, [User]</blockquote> - -Very truly yours, -Your customer, [User] - - </div> #include <foot.wmi> Modified: website/trunk/eff/en/tor-legal-faq.wml =================================================================== --- website/trunk/eff/en/tor-legal-faq.wml 2011-09-16 02:21:22 UTC (rev 25080) +++ website/trunk/eff/en/tor-legal-faq.wml 2011-09-16 02:26:27 UTC (rev 25081) @@ -216,10 +216,7 @@ providers, EFF is interested in hearing from you. Read more <a href="https://lists.torproject.org/pipermail/tor-talk/2005-October/016301.html">here</a> about being EFF's test case. -<a href=https://www.eff.org/torchallenge/setting-up/>» Set up a Tor -Relay now!</a> - </div> #include <foot.wmi>

1 0

r25080: {website} point to the correct dmca response template. (website/trunk/eff/en)
by Andrew Lewman 16 Sep '11

16 Sep '11

Author: phobos Date: 2011-09-16 02:21:22 +0000 (Fri, 16 Sep 2011) New Revision: 25080 Modified: website/trunk/eff/en/tor-legal-faq.wml Log: point to the correct dmca response template. Modified: website/trunk/eff/en/tor-legal-faq.wml =================================================================== --- website/trunk/eff/en/tor-legal-faq.wml 2011-09-16 02:19:31 UTC (rev 25079) +++ website/trunk/eff/en/tor-legal-faq.wml 2011-09-16 02:21:22 UTC (rev 25080) @@ -25,7 +25,7 @@ href="<page eff/tor-legal-faq>">https://www.torproject.org/eff/tor-legal-faq.html</a>, it may be out of date. Follow the link to get the latest version. Got a DMCA notice? Check out our <a -href="<page eff/dmca-template>">sample response +href="<page eff/tor-dmca-response>">sample response letter!</a> <h2>General Information</h2> Has anyone ever been sued or prosecuted for running Tor? @@ -189,7 +189,7 @@ My ISP, university, etc. just sent me a DMCA notice. What should I do? EFF has written a <a -href="<page eff/dmca-template>">short template</a> to help +href="<page eff/tor-dmca-response>">short template</a> to help you write a response to your ISP, university, etc., to let them know about the details of the Digital Millennium Copyright Act’s safe harbor, and how Tor fits in. Note that template only refers to U.S.

1 0

r25079: {website} replace our old 2005 vintage legal faq with the shiny 2011 l (website/trunk/eff/en)
by Andrew Lewman 16 Sep '11

16 Sep '11

Author: phobos Date: 2011-09-16 02:19:31 +0000 (Fri, 16 Sep 2011) New Revision: 25079 Modified: website/trunk/eff/en/tor-legal-faq.wml Log: replace our old 2005 vintage legal faq with the shiny 2011 legal faq. Modified: website/trunk/eff/en/tor-legal-faq.wml =================================================================== --- website/trunk/eff/en/tor-legal-faq.wml 2011-09-15 19:00:05 UTC (rev 25078) +++ website/trunk/eff/en/tor-legal-faq.wml 2011-09-16 02:19:31 UTC (rev 25079) @@ -7,176 +7,219 @@  -<h2>Legal FAQ for Tor Relay Operators</h2> +<h2>The Legal FAQ for Tor Relay Operators.</h2> <hr> -FAQ written by the Electronic Frontier -Foundation (<a href="http://www.eff.org/">EFF</a>). Last updated 25 Apr 2005. -NOTE: This FAQ is for informational purposes only -and does not constitute legal advice. EFF has not analyzed any -particular factual situation or laws in drafting this FAQ. Our aim is -to provide a general description of the legal issues surrounding -Tor in the United States. Different factual situations and different legal -jurisdictions will -result in different answers to a number of questions. Therefore, please -do not act on this information alone; if you have any -specific legal problems, issues, or questions, seek a complete review of -your situation with a lawyer licensed to practice in your jurisdiction. - - -Also, if you received this document from anywhere besides <a -href="https://www.torproject.org/eff/tor-legal-faq.html">https://www.torproject.org/eff/tor-legal-faq.html</a>, +FAQ written by the Electronic Frontier Foundation (<a +href="https://www.eff.org">EFF</a>). Last updated August 24, 2011. +NOTE: This FAQ is for informational purposes only and does not +constitute legal advice. Our aim is to provide a general description of +the legal issues surrounding Tor in the United States. Different factual +situations and different legal jurisdictions will result in different +answers to a number of questions. Therefore, please do not act on this +information alone; if you have any specific legal problems, issues, or +questions, seek a complete review of your situation with a lawyer +licensed to practice in your jurisdiction. +Also, if you received this document from anywhere besides the EFF web +site or <a +href="<page eff/tor-legal-faq>">https://www.torproject.org/eff/tor-legal-faq.html</a>, it may be out of date. Follow the link to get the latest version. +Got a DMCA notice? Check out our <a +href="<page eff/dmca-template>">sample response +letter!</a> +<h2>General Information</h2> +Has anyone ever been sued or prosecuted for running Tor? -<hr> +No, we aren’t aware of anyone being sued or prosecuted in the +United States for running a Tor relay. Further, we believe that running +a Tor relay — including an exit relay that allows people to +anonymously send and receive traffic — is lawful under U.S. +law. +Should I use Tor or encourage the use of Tor for illegal +purposes? +No. Tor has been developed to be a tool for free expression, +privacy, and human rights. It is not a tool designed or intended to be +used to break the law, either by Tor users or Tor relay operators. +Can EFF promise that I won't get in trouble for running a Tor +relay? +No. All new technologies create legal uncertainties, and Tor +is no exception. Presently, no court has ever considered any case +involving the Tor technology, and we therefore cannot guarantee that you +will never face any legal liability as a result of running a Tor relay. +However, EFF believes so strongly that those running Tor relays +shouldn't be liable for traffic that passes through the relay that we're +running our own middle relay. -<a id="Lawsuits"></a> -<h3><a class="anchor" href="#Lawsuits">Has anyone ever been sued for running Tor? -</a></h3> - -No. Further, we believe that running a Tor node, -including a Tor exit node that allows people to anonymously send and -receive traffic, is lawful under U.S. law. - -<a id="IllegalPurposes"></a> -<h3><a class="anchor" href="#IllegalPurposes">Should I use Tor, -or encourage the use of Tor, for illegal purposes -such as spamming, harassment, distribution of child porn, or copyright -infringement?</a></h3> - -No. Tor has been developed to be a tool for free -speech, privacy, and human rights. It is not a tool designed or intended -to be used to break the law, either by Tor users or Tor relay -operators. - -We further recommend that you not keep any potentially illegal files -on the same machine you use for Tor, nor use that machine for any illegal -purpose. Although no Tor relay in the US has ever been seized, nor any relay -operator sued, the future possibility cannot be ruled out. If that -happens, you will want your machine to be clean. - -<a id="Promise"></a> -<h3><a class="anchor" href="#Promise">Can EFF promise that I won't get -in trouble for running a Tor relay?</a></h3> - -No. All new technologies create legal uncertainties, -and Tor is no exception to the rule. Presently, no court has ever considered any -case involving the Tor technology, and we therefore cannot guarantee -that you will never face any legal liability as a result of running a -Tor relay. However, EFF believes so strongly that those running Tor -relays shouldn't be liable for traffic that passes through the relay -that we're running our own Tor relay. - - -<a id="Represent"></a> -<h3><a class="anchor" href="#Represent">Will EFF represent me if I get -in trouble for running a Tor relay?</a></h3> - -Maybe. While EFF cannot promise legal representation -of all Tor relay operators, it will assist relay operators in -assessing the situation and will try to locate qualified legal counsel -when necessary. Inquiries to EFF for the purpose of securing legal -representation or referrals should be directed to staff attorney Kevin -Bankston (bankston at eff.org or US +1 (415) 436-9333 x 126). Such -inquiries will be kept -confidential subject to the limits of the attorney/client privilege. -Note that although EFF cannot practice law outside of the U.S., it will -still try to assist non-U.S. relay operators in finding local -representation. - -<a id="DevelopersAreNotLawyers"></a> -<h3><a class="anchor" href="#DevelopersAreNotLawyers">Should I contact -the Tor developers when I have legal questions about Tor or to inform -them if I suspect Tor is being used for illegal purposes?</a></h3> - -No. Tor's core developers, Roger Dingledine -and Nick Mathewson, are available to answer technical questions, but -they are not lawyers and cannot give legal advice. Nor do they have any -ability to prevent illegal activity that may occur through Tor relays. -Furthermore, your communications with Tor's core developers are +Will EFF represent me if I get in trouble for running a Tor +relay? +Maybe. While EFF cannot promise legal representation for all +Tor relay operators, it will assist relay operators in assessing the +situation and will try to locate qualified legal counsel when necessary. +Inquiries to EFF for the purpose of securing legal representation or +referrals should be directed to our intake coordinator (<a +href="mailto:info@eff.org">info(a)eff.org</a> or US +1 (415) 436-9333). +Such inquiries will be kept confidential subject to the limits of the +attorney/client privilege. Note that although EFF cannot practice law +outside of the United States, it will still try to assist non-U.S. relay +operators in finding local representation. +Should I contact the Tor developers when I have legal questions +about Tor or to inform them if I suspect Tor is being used for illegal +purposes? +No. Tor's developers are available to answer technical +questions, but they are not lawyers and cannot give legal advice. Nor do +they have any ability to prevent illegal activity that may occur through +Tor relays. Furthermore, your communications with Tor's developers are not protected by any legal privilege, so law enforcement or civil litigants could subpoena and obtain any information you give to them. +You can contact <a href="mailto:info@eff.org">info(a)eff.org</a> if you +face a specific legal issue. We will try to assist you, but given EFF's +small size, we cannot guarantee that we can help everyone. -<a id="RequestForLogs"></a> -<h3><a class="anchor" href="#RequestForLogs">If I receive a request from -law enforcement or anyone else for my Tor relay's logs, what should -I do?</a></h3> +Do Tor's core developers make any promises about the +trustworthiness or reliability of Tor relays that are listed in their +directory? +No. Although the developers attempt to verify that Tor relays +listed in the directory maintained by the core developers are stable and +have adequate bandwidth, neither they nor EFF can guarantee the personal +trustworthiness or reliability of the individuals who run those relays. +Tor's core developers further reserve the right to refuse a Tor relay +operator's request to be listed in their directory or to remove any +relay from their directory for any reason. +<h2>Exit Relays</h2> +Exit relays raise special concerns because the traffic that exits +from them can be traced back to the relay's IP address. While we believe +that running an exit is legal, it is statistically likely that an exit +relay will at some point be used for illegal purposes, which may attract +the attention of private litigants or law enforcement. An exit relay may +forward traffic that is considered unlawful, and that traffic may be +attributed to the operator of a relay. If you are not willing to deal +with that risk, a bridge or middle relay may be a better fit for you. +These relays do not directly forward traffic to the Internet and so +can't be easily mistaken for the origin of allegedly unlawful +content. +The Tor Project's blog has some excellent <a +href="https://blog.torproject.org/blog/tips-running-exit-node-minimal-harassment">recommendations</a> +for running an exit with as little risk as possible. We suggest that you +review their advice before setting up an exit relay. +Should I run an exit relay from my home? -Educate them about Tor. In most instances, properly -configured Tor relays will have no useful data for inquiring parties, -and you should feel free to educate them on this point. To the extent -you do maintain logs, however, you should not disclose them to any third -party without first consulting a lawyer. In the U.S., such a disclosure -may violate the Electronic Communications Privacy Act, and relay -operators outside of the U.S. may be subject to similar data protection -laws. +No. If law enforcement becomes interested in traffic from your +exit relay, it's possible that officers will seize your computer. For +that reason, it's best not to run your exit relay in your home or using +your home Internet connection. +Instead, consider running your exit relay in a <a +href="https://trac.torproject.org/projects/tor/wiki/doc/GoodBadISPs">commercial +facility</a> that is supportive of Tor. Have a separate IP address for +your exit relay, and don't route your own traffic through it. +Of course, you should avoid keeping any sensitive or personal +information on the computer hosting your exit relay, and you never +should use that machine for any illegal purpose. +Should I tell my ISP that I'm running an exit relay? +Yes. Make sure you have a Tor-friendly ISP that knows you're +running an exit relay and supports you in that goal. This will help +ensure that your Internet access isn't cut off due to abuse complaints. +The Tor community maintains a <a +href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/GoodBadISPs">list</a> +of ISPs that are particularly Tor-savvy, as well as ones that +aren't. -You may receive legal inquiries where you are prohibited by law from -telling anyone about the request. We believe that, at least in the -U.S., such gag orders do not prevent you from talking to a lawyer, -including calling a lawyer to find representation. Inquiries to EFF for -the purpose of securing legal representation should be directed to staff -attorney Kevin Bankston (bankston at eff.org or US +1 (415) 436-9333 -x126). Such inquiries -will be kept confidential subject to the limits of the attorney/client -privilege. +Is it a good idea to let others know that I'm running an exit +relay? +Yes. Be as transparent as possible about the fact that you're +running an exit relay. If your exit traffic draws the attention of the +government or disgruntled private party, you want them to figure out +quickly and easily that you are part of the Tor network and not +responsible for the content. This could mean the difference between +having your computer seized by law enforcement and being left alone. +The Tor Project <a +href="https://blog.torproject.org/blog/tips-running-exit-node-minimal-harassment">suggests</a> +the following ways to let others know that you're running an exit +relay: +<ul> +<li>Set up a reverse DNS name for the IP address that makes clear that +the computer is an exit relay.</li> +<li>Set up a notice like <a +href="https://gitweb.torproject.org/tor.git/blob_plain/HEAD:/contrib/tor-exit-not…">this</a> +to explain that you're running an exit relay that's part of the Tor +network.</li> -EFF is currently working on informational materials to help you -respond to the most likely types of legal requests or notices, so watch -this space. +<li>If possible, get an <a href="https://www.arin.net">ARIN</a> +registration for your exit relay that displays contact information for +you, not your ISP. This way, you'll receive any abuse complaints and can +respond to them directly. Otherwise, try to ensure that your ISP +forwards abuse complaints that it receives to you.</li> +</ul> +Should I snoop on the plaintext traffic that exits through my Tor +relay? +No. You may be technically capable of modifying the Tor source +code or installing additional software to monitor or log plaintext that +exits your relay. However, Tor relay operators in the United States can +possibly create civil and even criminal liability for themselves under +state or federal wiretap laws if they monitor, log, or disclose Tor +users' communications, while non-U.S. operators may be subject to +similar laws. Do not examine the contents of anyone's communications +without first talking to a lawyer. +If I receive a subpoena or other information request from law +enforcement or anyone else related to my Tor relay, what should I +do? +Educate them about Tor. In most instances, properly configured +Tor relays will have no useful data for inquiring parties, and you +should feel free to educate them on this point. To the extent you do +maintain logs, however, you should not disclose them to any third party +without first consulting a lawyer. In the United States, such a +disclosure may violate the Electronic Communications Privacy Act, and +relay operators outside of the United States may be subject to similar +data protection laws. -<a id="DMCA"></a> -<h3><a class="anchor" href="#DMCA">My ISP/University/etc just sent me -a DMCA notice. What should I do?</a></h3> +You may receive legal inquiries where you are prohibited by law from +telling anyone about the request. We believe that, at least in the +United States, such gag orders do not prevent you from talking to a +lawyer, including calling a lawyer to find representation. Inquiries to +EFF for the purpose of securing legal representation should be directed +to our intake coordinator (info at eff.org or US +1 (415) 436-9333). +Such inquiries will be kept confidential subject to the limits of the +attorney/client privilege. +For more information about responding to abuse complaints and other +inquiries, check out the <a +href="<page docs/faq-abuse>">Tor Abuse +FAQ</a> and the collection of <a +href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorAbuseTempla…">abuse +response templates</a> on the Tor Project’s website. +My ISP, university, etc. just sent me a DMCA notice. What should I +do? +EFF has written a <a +href="<page eff/dmca-template>">short template</a> to help +you write a response to your ISP, university, etc., to let them know +about the details of the Digital Millennium Copyright Act’s safe harbor, +and how Tor fits in. Note that template only refers to U.S. +jurisdictions, and is intended only to address copyright complaints that +are based on a relay of allegedly infringing material through the Tor +node. -The EFF has written a <a -href="tor-dmca-response.html">short template</a> -to help you write a response to your ISP/University/etc, to let them -know about the details of DMCA safe harbor, and how Tor fits in. Note -that this only refers to a U.S. jurisdiction. - -If you like, you should consider submitting a copy of your notice -to <a href="http://www.chillingeffects.org/">Chilling Effects</a>. This +If you like, you should consider submitting a copy of your notice to +<a href="https://www.chillingeffects.org">Chilling Effects</a>. This will help us recognize trends and issues that the lawyers might want to focus on. Chilling Effects encourages submissions from people outside the United States too. +EFF believes that Tor relays are protected from copyright liability +under the DMCA, although no court has yet addressed the issue in the +context of Tor itself. If you are uncomfortable with this uncertainty, +you may consider using a <a +href="<page docs/faq>#ExitPolicies">reduced +exit policy</a> (such as the default policy suggested by the Tor +Project) to try to minimize traffic types that are often targeted in +copyright complaints. +If you are a Tor relay operator willing to stand up and help set a +clear legal precedent establishing that merely running a relay does not +create copyright liability for either operators or their bandwidth +providers, EFF is interested in hearing from you. Read more <a +href="https://lists.torproject.org/pipermail/tor-talk/2005-October/016301.html">here</a> +about being EFF's test case. +<a href=https://www.eff.org/torchallenge/setting-up/>» Set up a Tor +Relay now!</a> -EFF is actively seeking Tor relay operators willing to stand up -and help set a clear legal precedent establishing that merely running -a node does not create copyright liability for either node operators -or their bandwidth providers. If you want to be the EFF's test case, -<a href="https://lists.torproject.org/pipermail/tor-talk/2005-October/016301.html">read -more here</a>. -<a id="ExitSnooping"></a> -<h3><a class="anchor" href="#ExitSnooping">Should I snoop on the plaintext -that exits through my Tor relay?</a></h3> - -No. You may be technically capable of modifying -the Tor source code or installing additional software to monitor -or log plaintext that exits your node. However, -Tor relay operators in the U.S. can create legal and possibly even -criminal liability for themselves under state or federal wiretap laws if -they affirmatively monitor, log, or disclose Tor users' -communications, while non-U.S. operators may be subject to similar laws. -Do not examine the contents of anyone's communications without -first talking to a lawyer. - -<a id="DirectoryWarranty"></a> -<h3><a class="anchor" href="#DirectoryWarranty">Do Tor's core developers -make any promises about the trustworthiness or reliability of Tor relays -that are listed in their directory?</a></h3> - -No. Although the developers attempt to verify that -Tor relays listed in the directory the core developers maintain are -stable and have adequate bandwidth, neither they nor EFF can guarantee -the personal trustworthiness or reliability of the individuals who run -those relays. Tor's core developers further reserve the right to -refuse a Tor relay operator's request to be listed in their -directory or to remove any relay from their directory for any -reason. - </div> #include <foot.wmi>

1 0

[bridgedb/master] change our hard-coded smtp server
by arma＠torproject.org 16 Sep '11

16 Sep '11

commit 3c70eb4eb8ab675ecdf797c60b742e0d36adcc8e Author: Roger Dingledine <arma(a)torproject.org> Date: Thu Sep 15 20:38:53 2011 -0400 change our hard-coded smtp server --- lib/bridgedb/Server.py | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/lib/bridgedb/Server.py b/lib/bridgedb/Server.py index 2becee8..20b349b 100644 --- a/lib/bridgedb/Server.py +++ b/lib/bridgedb/Server.py @@ -338,7 +338,8 @@ class MailContext: # Reject any mail longer than this. self.maximumSize = 32*1024 # Use this server for outgoing mail. - self.smtpServer = "127.0.0.1" +# self.smtpServer = "127.0.0.1" # XXX should make configurable + self.smtpServer = "172.22.121.1" self.smtpPort = 25 # Use this address in the MAIL FROM line for outgoing mail. self.smtpFromAddr = (cfg.EMAIL_SMTP_FROM_ADDR or

1 0

← Newer
1
...
33
34
35
36
37
38
39
...
87
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits September 2011