June 2014 - tor-commits - lists.torproject.org

r26805: {website} update link to tor-exit-notice (website/trunk/docs/en)
by Roger Dingledine 05 Jun '14

05 Jun '14

Author: arma Date: 2014-06-05 07:50:32 +0000 (Thu, 05 Jun 2014) New Revision: 26805 Modified: website/trunk/docs/en/tor-doc-relay.wml Log: update link to tor-exit-notice Modified: website/trunk/docs/en/tor-doc-relay.wml =================================================================== --- website/trunk/docs/en/tor-doc-relay.wml 2014-06-05 04:44:10 UTC (rev 26804) +++ website/trunk/docs/en/tor-doc-relay.wml 2014-06-05 07:50:32 UTC (rev 26805) @@ -204,7 +204,7 @@ reverse DNS hostname to 'anonymous-relay', 'proxy' or 'tor-proxy', so when other people see the address in their web logs, they will more quickly understand what's going on. Adding the <a - href="<gitblob>contrib/tor-exit-notice.html">Tor + href="<gitblob>contrib/operator-tools/tor-exit-notice.html">Tor exit notice</a> on a vhost for this name can go a long way to deterring abuse complaints to you and your ISP if you are running an exit node.

1 0

r26804: {website} fix typo (website/trunk/docs/en)
by Roger Dingledine 05 Jun '14

05 Jun '14

Author: arma Date: 2014-06-05 04:44:10 +0000 (Thu, 05 Jun 2014) New Revision: 26804 Modified: website/trunk/docs/en/tor-relay-debian.wml Log: fix typo Modified: website/trunk/docs/en/tor-relay-debian.wml =================================================================== --- website/trunk/docs/en/tor-relay-debian.wml 2014-06-05 02:27:43 UTC (rev 26803) +++ website/trunk/docs/en/tor-relay-debian.wml 2014-06-05 04:44:10 UTC (rev 26804) @@ -36,7 +36,7 @@ instructions to use our repository. - For other Unix/Linux uesrs, you can download Tor from one of our + For other Unix/Linux users, you can download Tor from one of our <a href="<page download/download-unix>">repositories</a>. <hr>

1 0

r26803: {website} fix a broken link made by reshuffling tor's contrib director (website/trunk/eff/en)
by Roger Dingledine 05 Jun '14

05 Jun '14

Author: arma Date: 2014-06-05 02:27:43 +0000 (Thu, 05 Jun 2014) New Revision: 26803 Modified: website/trunk/eff/en/tor-legal-faq.wml Log: fix a broken link made by reshuffling tor's contrib directory Modified: website/trunk/eff/en/tor-legal-faq.wml =================================================================== --- website/trunk/eff/en/tor-legal-faq.wml 2014-06-05 02:16:48 UTC (rev 26802) +++ website/trunk/eff/en/tor-legal-faq.wml 2014-06-05 02:27:43 UTC (rev 26803) @@ -154,7 +154,7 @@ <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> +href="https://gitweb.torproject.org/tor.git/blob_plain/HEAD:/contrib/operator-too…">this</a> to explain that you're running an exit relay that's part of the Tor network.</li> <li>If possible, get an <a href="https://www.arin.net/">ARIN</a>

1 0

r26802: {website} updated eff tor legal faq (no big substantive changes) (website/trunk/eff/en)
by Roger Dingledine 05 Jun '14

05 Jun '14

Author: arma Date: 2014-06-05 02:16:48 +0000 (Thu, 05 Jun 2014) New Revision: 26802 Modified: website/trunk/eff/en/tor-legal-faq.wml Log: updated eff tor legal faq (no big substantive changes) Modified: website/trunk/eff/en/tor-legal-faq.wml =================================================================== --- website/trunk/eff/en/tor-legal-faq.wml 2014-06-02 20:13:13 UTC (rev 26801) +++ website/trunk/eff/en/tor-legal-faq.wml 2014-06-05 02:16:48 UTC (rev 26802) @@ -10,132 +10,146 @@ <h2>The Legal FAQ for Tor Relay Operators.</h2> <hr> -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 +FAQ written by the Electronic Frontier Foundation (EFF). Last +updated April 21, 2014. + +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 +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/tor-dmca-response>">sample response -letter!</a> + +Got a DMCA notice? Check out our <a href="<page +eff/tor-dmca-response>">sample response letter</a>! + <h2>General Information</h2> -Has anyone ever been sued or prosecuted for running Tor? -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? +<h3>Has anyone ever been sued or prosecuted for running Tor?</h3> + +No, we aren't aware of anyone being sued or prosecuted in the +United States just 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 legal under U.S. law. + +<h3>Should I use Tor or encourage the use of Tor for illegal purposes?</h3> + 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? + +<h3>Can EFF promise that I won't get in trouble for running a Tor +relay?</h3> + 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. +is no exception. We 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. -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 +<h3>Will EFF represent me if I get in trouble for running a Tor relay?</h3> + +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 by sending an email to <a +href="mailto:info@eff.org">info(a)eff.org</a> . 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. + +<h3>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? +purposes?</h3> + 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. +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. -Do Tor's core developers make any promises about the -trustworthiness or reliability of Tor relays that are listed in their -directory? +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. + +<h3>Do Tor's core developers make any promises about the trustworthiness +or reliability of Tor relays that are listed in their directory?</h3> + 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. +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. +that running an exit relay 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? +for running an exit with as little risk as possible. We suggest that +you review their advice before setting up an exit relay. +<h3>Should I run an exit relay from my home?</h3> + 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. +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. +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 +information on the computer hosting your exit relay, and you never should +use that machine for any illegal purpose. + +<h3>Should I tell my ISP that I'm running an exit relay?</h3> + +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. +of ISPs that are particularly Tor-savvy, as well as ones that aren't. -Is it a good idea to let others know that I'm running an exit -relay? +<h3>Is it a good idea to let others know that I'm running an exit relay?</h3> + 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 +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> @@ -143,80 +157,92 @@ 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> - -<li>If possible, get an <a href="https://www.arin.net">ARIN</a> +<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 +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? + +<h3>Should I snoop on the plaintext traffic that exits through my Tor +relay?</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 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? +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 anyone's communications without first +talking to a lawyer. + +<h3>If I receive a subpoena or other information request from law +enforcement or anyone else related to my Tor relay, what should I do?</h3> + 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. +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. 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 +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) 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/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. -jurisdictions, and is intended only to address copyright complaints that -are based on a relay of allegedly infringing material through the Tor -node. +For information on what to do if law enforcement +seeks access to your digital devices, check out EFF’s <a +href="https://www.eff.org/wp/know-your-rights">Know Your Rights</a> +guide. + +<h3>My ISP, university, etc. just sent me a DMCA notice. What should +I do?</h3> + +EFF has written a <a 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. jurisdictions, and is intended only to address copyright +complaints that are based on a relay of allegedly infringing material +through the Tor node. + If you like, you should consider submitting a copy of your notice to -<a href="https://www.chillingeffects.org">Chilling Effects</a>. This +<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 + +EFF believes that Tor relays should be protected from copyright +liability for the acts of their users because a Tor relay operator +can raise an immunity defense under the DMCA as well as defenses +under copyright's secondary liability doctrines. However, no court +has yet addressed these issues in the context of Tor itself. If +you are uncomfortable with this uncertainty, you may consider using +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. </div> #include <foot.wmi> +

1 0

[translation/tor-and-https_completed] Update translations for tor-and-https_completed
by translation＠torproject.org 04 Jun '14

04 Jun '14

commit 5213f0d9724cd9717db4d12e806fbbb3967889f7 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Jun 4 22:15:58 2014 +0000 Update translations for tor-and-https_completed --- nb.po | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nb.po b/nb.po index f41ec2e..c3649cf 100644 --- a/nb.po +++ b/nb.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" "POT-Creation-Date: 2014-05-24 18:11+0000\n" -"PO-Revision-Date: 2014-06-04 21:41+0000\n" +"PO-Revision-Date: 2014-06-04 21:51+0000\n" "Last-Translator: Allan Nordhøy <comradekingu(a)gmail.com>\n" "Language-Team: Norwegian Bokmål (http://www.transifex.com/projects/p/torproject/language/nb/)\n" "MIME-Version: 1.0\n"

1 0

[translation/tor-and-https] Update translations for tor-and-https
by translation＠torproject.org 04 Jun '14

04 Jun '14

commit db740b7b0617ae43a76e609a38e3a315d2a1b52a Author: Translation commit bot <translation(a)torproject.org> Date: Wed Jun 4 22:15:53 2014 +0000 Update translations for tor-and-https --- nb.po | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/nb.po b/nb.po index f41ec2e..c3649cf 100644 --- a/nb.po +++ b/nb.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" "POT-Creation-Date: 2014-05-24 18:11+0000\n" -"PO-Revision-Date: 2014-06-04 21:41+0000\n" +"PO-Revision-Date: 2014-06-04 21:51+0000\n" "Last-Translator: Allan Nordhøy <comradekingu(a)gmail.com>\n" "Language-Team: Norwegian Bokmål (http://www.transifex.com/projects/p/torproject/language/nb/)\n" "MIME-Version: 1.0\n"

1 0

[translation/tails-greeter_completed] Update translations for tails-greeter_completed
by translation＠torproject.org 04 Jun '14

04 Jun '14

commit e346d806ef87004875c8e6aa4661a1f3f0318020 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Jun 4 22:15:26 2014 +0000 Update translations for tails-greeter_completed --- nb/nb.po | 15 ++++++++------- 1 file changed, 8 insertions(+), 7 deletions(-) diff --git a/nb/nb.po b/nb/nb.po index 8300b09..e5c11c0 100644 --- a/nb/nb.po +++ b/nb/nb.po @@ -3,14 +3,15 @@ # This file is distributed under the same license as the PACKAGE package. # # Translators: +# Allan Nordhøy <comradekingu(a)gmail.com>, 2014 # lateralus, 2013-2014 msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2014-05-14 13:14+0200\n" -"PO-Revision-Date: 2014-05-17 14:36+0000\n" -"Last-Translator: lateralus\n" +"POT-Creation-Date: 2014-05-28 22:33+0200\n" +"PO-Revision-Date: 2014-06-04 21:51+0000\n" +"Last-Translator: Allan Nordhøy <comradekingu(a)gmail.com>\n" "Language-Team: Norwegian Bokmål (http://www.transifex.com/projects/p/torproject/language/nb/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -102,13 +103,13 @@ msgstr "<a href=\"doc/first_steps/startup_options/windows_camouflage.en.html\">D #: ../glade/optionswindow.glade.h:12 msgid "" -"This option makes Tails look more like Microsoft Windows XP. This may be " +"This option makes Tails look more like Microsoft Windows 8. This may be " "useful in public places in order to avoid attracting suspicion." -msgstr "Dette alternativet gjør at Tails ligner mer på Microsoft Windows XP. Dette kan være nyttig på offentlige steder for å unngå uønsket oppmerksomhet. " +msgstr "Dette valget tilkjennegir Tails likt Microsoft Windows 8. Dette kan være nyttig i offentlige rom for å unngå å tiltrekke seg mistanke." #: ../glade/optionswindow.glade.h:13 -msgid "Activate Microsoft Windows XP Camouflage" -msgstr "Aktiver Microsoft Windows XP-kamuflasje" +msgid "Activate Microsoft Windows 8 Camouflage" +msgstr "Aktiver Mikrosoft Windows 8-kamuflasje " #: ../glade/optionswindow.glade.h:14 msgid "MAC address spoofing"

1 0

[translation/tails-greeter] Update translations for tails-greeter
by translation＠torproject.org 04 Jun '14

04 Jun '14

commit eab2e01bc8f6891a92990cc3829e0cadc3ddd52a Author: Translation commit bot <translation(a)torproject.org> Date: Wed Jun 4 22:15:24 2014 +0000 Update translations for tails-greeter --- nb/nb.po | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/nb/nb.po b/nb/nb.po index 936739e..e5c11c0 100644 --- a/nb/nb.po +++ b/nb/nb.po @@ -10,7 +10,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2014-05-28 22:33+0200\n" -"PO-Revision-Date: 2014-06-04 21:44+0000\n" +"PO-Revision-Date: 2014-06-04 21:51+0000\n" "Last-Translator: Allan Nordhøy <comradekingu(a)gmail.com>\n" "Language-Team: Norwegian Bokmål (http://www.transifex.com/projects/p/torproject/language/nb/)\n" "MIME-Version: 1.0\n" @@ -105,7 +105,7 @@ msgstr "<a href=\"doc/first_steps/startup_options/windows_camouflage.en.html\">D msgid "" "This option makes Tails look more like Microsoft Windows 8. This may be " "useful in public places in order to avoid attracting suspicion." -msgstr "" +msgstr "Dette valget tilkjennegir Tails likt Microsoft Windows 8. Dette kan være nyttig i offentlige rom for å unngå å tiltrekke seg mistanke." #: ../glade/optionswindow.glade.h:13 msgid "Activate Microsoft Windows 8 Camouflage"

1 0

[translation/bridgedb] Update translations for bridgedb
by translation＠torproject.org 04 Jun '14

04 Jun '14

commit 432a45858070ef0a76186df56ed29ebea1380591 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Jun 4 22:15:02 2014 +0000 Update translations for bridgedb --- nb/LC_MESSAGES/bridgedb.po | 48 ++++++++++++++++++++++---------------------- 1 file changed, 24 insertions(+), 24 deletions(-) diff --git a/nb/LC_MESSAGES/bridgedb.po b/nb/LC_MESSAGES/bridgedb.po index b09f9d0..185a821 100644 --- a/nb/LC_MESSAGES/bridgedb.po +++ b/nb/LC_MESSAGES/bridgedb.po @@ -3,8 +3,8 @@ # This file is distributed under the same license as the BridgeDB project. # # Translators: -# kingu <comradekingu(a)gmail.com>, 2014 -# haarek <haarektrans(a)gmail.com>, 2014 +# Allan Nordhøy <comradekingu(a)gmail.com>, 2014 +# Harald <haarektrans(a)gmail.com>, 2014 # lateralus, 2013 # thor574 <thor.hovden(a)gmail.com>, 2014 msgid "" @@ -12,8 +12,8 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: 'https://trac.torproject.org/projects/tor/newticket?component=BridgeDB&keywo…'\n" "POT-Creation-Date: 2014-05-16 18:39+0000\n" -"PO-Revision-Date: 2014-05-23 11:34+0000\n" -"Last-Translator: kingu <comradekingu(a)gmail.com>\n" +"PO-Revision-Date: 2014-06-04 22:11+0000\n" +"Last-Translator: Allan Nordhøy <comradekingu(a)gmail.com>\n" "Language-Team: Norwegian Bokmål (http://www.transifex.com/projects/p/torproject/language/nb/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -125,7 +125,7 @@ msgstr "Hva er broer?" #: lib/bridgedb/strings.py:66 #, python-format msgid "%s Bridges %s are Tor relays that help you circumvent censorship." -msgstr "" +msgstr "%s Broer %s er Tor-tilknyttninger som hjelper deg med å omgå sensur." #: lib/bridgedb/strings.py:71 msgid "I need an alternative way of getting bridges!" @@ -146,7 +146,7 @@ msgstr "Broene mine virker ikke! Jeg trenger hjelp!" #: lib/bridgedb/strings.py:80 #, python-format msgid "If your Tor doesn't work, you should email %s." -msgstr "" +msgstr "Hvis din Tor ikke virker, burde du skrive epost til %s." #: lib/bridgedb/strings.py:81 msgid "" @@ -157,24 +157,24 @@ msgstr "" #: lib/bridgedb/strings.py:88 msgid "Here are your bridge lines:" -msgstr "" +msgstr "Her er dine bro-linjer:" #: lib/bridgedb/strings.py:89 msgid "Get Bridges!" -msgstr "" +msgstr "Få broer!" #: lib/bridgedb/strings.py:93 msgid "Please select options for bridge type:" -msgstr "" +msgstr "Gjør valg for brotype:" #: lib/bridgedb/strings.py:94 msgid "Do you need IPv6 addresses?" -msgstr "" +msgstr "Trenger du IPv6-adresser?" #: lib/bridgedb/strings.py:95 #, python-format msgid "Do you need a %s?" -msgstr "" +msgstr "Trenger du en %s?" #: lib/bridgedb/strings.py:99 msgid "Your browser is not displaying images properly." @@ -182,18 +182,18 @@ msgstr "Nettleseren din viser ikke bilder ordentlig." #: lib/bridgedb/strings.py:100 msgid "Enter the characters from the image above..." -msgstr "" +msgstr "Skriv inn bokstavene fra bildet ovenfor..." #: lib/bridgedb/strings.py:104 msgid "How to start using your bridges" -msgstr "" +msgstr "Hvordan starte med bruk av dine broer" #: lib/bridgedb/strings.py:105 #, python-format msgid "" "To enter bridges into Tor Browser, follow the instructions on the %s Tor\n" "Browser download page %s to start Tor Browser." -msgstr "" +msgstr "For å oppføre broer i Tor-nettleseren, følg instruksjonene på %s Tor\nnettleser nedlastingsside %s for å starte Tor-nettleser." #: lib/bridgedb/strings.py:108 msgid "" @@ -205,7 +205,7 @@ msgstr "" msgid "" "Does your Internet Service Provider (ISP) block or otherwise censor connections\n" "to the Tor network?" -msgstr "" +msgstr "Sensurerer, eller blokkerer på annen måte, din internetttilbyder (ISP) tilkoblinger\ntil Tor-nettverket?" #: lib/bridgedb/strings.py:114 msgid "" @@ -217,11 +217,11 @@ msgstr "" #: lib/bridgedb/strings.py:122 msgid "Displays this message." -msgstr "" +msgstr "Vis denne meldingen." #: lib/bridgedb/strings.py:123 msgid "Request vanilla bridges." -msgstr "" +msgstr "Forespørr broer med fabrikkoppsett." #: lib/bridgedb/strings.py:124 msgid "Request IPv6 bridges." @@ -234,7 +234,7 @@ msgstr "" #: lib/bridgedb/strings.py:127 msgid "Get a copy of BridgeDB's public GnuPG key." -msgstr "" +msgstr "Få kopi av BridgeDBs offentlige GnuPG-nøkkel." #: lib/bridgedb/templates/base.html:91 msgid "Report a Bug" @@ -254,18 +254,18 @@ msgstr "Kontakt" #: lib/bridgedb/templates/bridges.html:65 msgid "Uh oh, spaghettios!" -msgstr "" +msgstr "På tryne i myra!" #: lib/bridgedb/templates/bridges.html:70 msgid "There currently aren't any bridges available..." -msgstr "" +msgstr "Det er for tiden ingen tilgjengelige broer..." #: lib/bridgedb/templates/bridges.html:71 #, python-format msgid "" " Perhaps you should try %s going back %s and choosing a different bridge " "type!" -msgstr "" +msgstr "Kanskje du bør prøve %s gå tilbake til %s og velge en annen brotype!" #: lib/bridgedb/templates/index.html:11 #, python-format @@ -275,7 +275,7 @@ msgstr "Steg %s1%s" #: lib/bridgedb/templates/index.html:13 #, python-format msgid "Download %s Tor Browser %s" -msgstr "" +msgstr "Last ned %s Tor-nettleser %s" #: lib/bridgedb/templates/index.html:25 #, python-format @@ -295,7 +295,7 @@ msgstr "Steg %s3%s" #: lib/bridgedb/templates/index.html:38 #, python-format msgid "Now %s add the bridges to Tor Browser %s" -msgstr "" +msgstr "Nå %s legg til broer til Tor-nettleser %s" #. TRANSLATORS: Please make sure the '%s' surrounding single letters at the #. beginning of words are present in your final translation. Thanks! @@ -309,7 +309,7 @@ msgstr "" #: lib/bridgedb/templates/options.html:53 msgid "Advanced Options" -msgstr "" +msgstr "Avanserte valg" #: lib/bridgedb/templates/options.html:89 msgid "No"

1 0

[translation/tor-and-https_completed] Update translations for tor-and-https_completed
by translation＠torproject.org 04 Jun '14

04 Jun '14

commit 03a8b0e7ce83687058df98f49834eb01d65113aa Author: Translation commit bot <translation(a)torproject.org> Date: Wed Jun 4 21:45:56 2014 +0000 Update translations for tor-and-https_completed --- nb.po | 80 +++++++++++++++++++++++++++++++++++++++++++++++++---------------- 1 file changed, 61 insertions(+), 19 deletions(-) diff --git a/nb.po b/nb.po index 1c38861..f41ec2e 100644 --- a/nb.po +++ b/nb.po @@ -1,12 +1,13 @@ # # Translators: +# Allan Nordhøy <comradekingu(a)gmail.com>, 2014 # haakon <haakonn(a)gmail.com>, 2014 msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" -"POT-Creation-Date: 2014-05-21 09:17+0200\n" -"PO-Revision-Date: 2014-05-21 17:25+0000\n" -"Last-Translator: haakon <haakonn(a)gmail.com>\n" +"POT-Creation-Date: 2014-05-24 18:11+0000\n" +"PO-Revision-Date: 2014-06-04 21:41+0000\n" +"Last-Translator: Allan Nordhøy <comradekingu(a)gmail.com>\n" "Language-Team: Norwegian Bokmål (http://www.transifex.com/projects/p/torproject/language/nb/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -14,82 +15,123 @@ msgstr "" "Language: nb\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" -#: C/tor-and-https.svg223(svg/title) +#. (itstool) path: C/tor-and-https.svg/svg@direction +#. (itstool) comment: C/tor-and-https.svg/svg@direction +#. Specify "ltr" for left-to-right languages or "rtl" for right-to-left +#. languages (e.g. Arabic or Hebrew). +#: C/tor-and-https.svg:3 +msgid "ltr" +msgstr "vth" + +#. (itstool) path: svg/title +#: C/tor-and-https.svg:14 #, no-wrap msgid "Tor and HTTPS" msgstr "Tor og HTTPS" -#: C/tor-and-https.svg224(defs/text) +#. (itstool) path: defs/text +#. Keep it short: 7em max. Seven times the capital letter "M". +#: C/tor-and-https.svg:346 #, no-wrap msgid "Site.com" msgstr "Side.no" -#: C/tor-and-https.svg224(defs/text) +#. (itstool) path: defs/text +#. Keep it short: 7em max. Seven times the capital letter "M". +#: C/tor-and-https.svg:346 #, no-wrap msgid "user / pw" msgstr "bruker / pw" -#: C/tor-and-https.svg224(defs/text) +#. (itstool) path: defs/text +#. Keep it short: 7em max. Seven times the capital letter "M". +#: C/tor-and-https.svg:346 #, no-wrap msgid "data" msgstr "data" -#: C/tor-and-https.svg224(defs/text) +#. (itstool) path: defs/text +#. Keep it short: 7em max. Seven times the capital letter "M". +#: C/tor-and-https.svg:346 #, no-wrap msgid "location" msgstr "Lokalisering" -#: C/tor-and-https.svg224(defs/text) +#. (itstool) path: defs/text +#. Keep it short: 3em max. +#: C/tor-and-https.svg:346 +#, no-wrap +msgid "WiFi" +msgstr "WiFi" + +#. (itstool) path: defs/text +#. Keep it short: 4em max. +#: C/tor-and-https.svg:346 #, no-wrap msgid "ISP" msgstr "ISP" -#: C/tor-and-https.svg224(defs/text) +#. (itstool) path: defs/text +#. Keep it short: 8em is ok, 9em is max. +#: C/tor-and-https.svg:346 #, no-wrap msgid "Hacker" msgstr "Hacker" -#: C/tor-and-https.svg224(defs/text) +#. (itstool) path: defs/text +#. Keep it short: 8em is ok, 9em is max. +#: C/tor-and-https.svg:346 #, no-wrap msgid "Lawyer" msgstr "Advokat" -#: C/tor-and-https.svg224(defs/text) +#. (itstool) path: defs/text +#. Keep it short: 8em is ok, 9em is max. +#: C/tor-and-https.svg:346 #, no-wrap msgid "Sysadmin" msgstr "Sysadmin" -#: C/tor-and-https.svg224(defs/text) +#. (itstool) path: defs/text +#. Keep it short: 8em is ok, 9em is max. +#: C/tor-and-https.svg:346 #, no-wrap msgid "Police" msgstr "Politi" -#: C/tor-and-https.svg224(defs/text) +#. (itstool) path: defs/text +#: C/tor-and-https.svg:346 #, no-wrap msgid "NSA" msgstr "NSA" -#: C/tor-and-https.svg224(defs/text) +#. (itstool) path: defs/text +#. Keep it short: 8em is ok, 9em is max. +#: C/tor-and-https.svg:346 #, no-wrap msgid "Tor relay" msgstr "Tor-relay" -#: C/tor-and-https.svg224(defs/text) +#. (itstool) path: defs/text +#: C/tor-and-https.svg:346 #, no-wrap msgid "Key" msgstr "Nøkkel" -#: C/tor-and-https.svg224(defs/text) +#. (itstool) path: defs/text +#: C/tor-and-https.svg:346 #, no-wrap msgid "Internet connection" msgstr "Internett-tilkobling" -#: C/tor-and-https.svg224(defs/text) +#. (itstool) path: defs/text +#: C/tor-and-https.svg:346 #, no-wrap msgid "Eavesdropping" msgstr "Avlytting" -#: C/tor-and-https.svg224(defs/text) +#. (itstool) path: defs/text +#: C/tor-and-https.svg:346 #, no-wrap msgid "Data sharing" msgstr "Datadeling"

1 0