tor-commits December 2020

tor-commits@lists.torproject.org

19 participants
1639 discussions

[translation/support-portal_completed] https://gitweb.torproject.org/translation.git/commit/?h=support-portal_completed
by translation＠torproject.org 16 Dec '20

16 Dec '20

commit 39c72957387effb4374d39af3f322a39d84e96e5 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Dec 16 09:48:38 2020 +0000 https://gitweb.torproject.org/translation.git/commit/?h=support-portal_comp… --- contents+es-AR.po | 146 +++++++++++++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 138 insertions(+), 8 deletions(-) diff --git a/contents+es-AR.po b/contents+es-AR.po index 440144bf19..4b1844d7e2 100644 --- a/contents+es-AR.po +++ b/contents+es-AR.po @@ -11476,7 +11476,7 @@ msgstr "Estos scripts también son utilizables para eso.)" #: https//support.torproject.org/abuse/what-about-ddos/ #: (content/abuse/ddos/contents+en.lrquestion.title) msgid "What about distributed denial of service attacks?" -msgstr "" +msgstr "¿Y qué acerca de los ataques distribuídos de denegación de servicio?" #: https//support.torproject.org/abuse/what-about-ddos/ #: (content/abuse/ddos/contents+en.lrquestion.description) @@ -11484,6 +11484,9 @@ msgid "" "Distributed denial of service (DDoS) attacks typically rely on having a " "group of thousands of computers all sending floods of traffic to a victim." msgstr "" +"Los ataques de denegación de servicio distribuídos (DDoS) típicamente se " +"apoyan en poseer un grupo de miles de computadoras, todas enviando un " +"diluvio de tráfico a una víctima." #: https//support.torproject.org/abuse/what-about-ddos/ #: (content/abuse/ddos/contents+en.lrquestion.description) @@ -11491,6 +11494,9 @@ msgid "" "Since the goal is to overpower the bandwidth of the victim, they typically " "send UDP packets since those don't require handshakes or coordination." msgstr "" +"Ya que el objetivo es agotar el ancho de banda de la víctima, típicamente se" +" envían paquetes UDP, ya que esos no requieren intercambio de señales o " +"coordinación." #: https//support.torproject.org/abuse/what-about-ddos/ #: (content/abuse/ddos/contents+en.lrquestion.description) @@ -11498,12 +11504,16 @@ msgid "" "But because Tor only transports correctly formed TCP streams, not all IP " "packets, you cannot send UDP packets over Tor." msgstr "" +"Pero porque Tor solamente transporta flujos TCP correctamente formados, no " +"todos los paquetes IP, no podés enviar paquetes UDP sobre Tor." #: https//support.torproject.org/abuse/what-about-ddos/ #: (content/abuse/ddos/contents+en.lrquestion.description) msgid "" "(You can't do specialized forms of this attack like SYN flooding either.)" msgstr "" +"(Tampoco podés hacer formas especializadas de este ataque, como la " +"inundación SYN)." #: https//support.torproject.org/abuse/what-about-ddos/ #: (content/abuse/ddos/contents+en.lrquestion.description) @@ -11511,6 +11521,9 @@ msgid "" "So ordinary DDoS attacks are not possible over Tor. Tor also doesn't allow " "bandwidth amplification attacks against external sites:" msgstr "" +"Por lo que ataques DDoS ordinarios no son posibles sobre Tor. Tor tampoco " +"permite los ataques de amplificación de ancho de banda contra sitios " +"externos:" #: https//support.torproject.org/abuse/what-about-ddos/ #: (content/abuse/ddos/contents+en.lrquestion.description) @@ -11518,6 +11531,7 @@ msgid "" "you need to send in a byte for every byte that the Tor network will send to " "your destination." msgstr "" +"necesitás enviar un byte por cada byte que la red Tor enviará a tu destino." #: https//support.torproject.org/abuse/what-about-ddos/ #: (content/abuse/ddos/contents+en.lrquestion.description) @@ -11525,22 +11539,27 @@ msgid "" "So in general, attackers who control enough bandwidth to launch an effective" " DDoS attack can do it just fine without Tor." msgstr "" +"Por lo que en general, los atacantes que controlan el ancho de banda " +"suficiente como para lanzar un ataque DDoS efectivo, pueden hacerlo igual de" +" bien sin Tor." #: https//support.torproject.org/abuse/how-exit-policies-work/ #: (content/abuse/exit-policies/contents+en.lrquestion.title) msgid "How do Tor exit policies work?" -msgstr "" +msgstr "¿Cómo funcionan las políticas de salida de Tor?" #: https//support.torproject.org/abuse/how-exit-policies-work/ #: (content/abuse/exit-policies/contents+en.lrquestion.description) msgid "" "[See the main FAQ](https://support.torproject.org/operators/exit-policies/)" msgstr "" +"[Mirá las PMF principales](https://support.torproject.org/operators/exit-" +"policies/)" #: https//support.torproject.org/abuse/exit-relay-expectations/ #: (content/abuse/exit-relay-expectations/contents+en.lrquestion.title) msgid "So what should I expect if I run an exit relay?" -msgstr "" +msgstr "Entonces, ¿qué debería esperar si corro un repetidor de salida?" #: https//support.torproject.org/abuse/exit-relay-expectations/ #: (content/abuse/exit-relay-expectations/contents+en.lrquestion.description) @@ -11549,11 +11568,15 @@ msgid "" "exit policy), it's probably safe to say that you will eventually hear from " "somebody." msgstr "" +"Si corrés un repetidor Tor que permite conexiones de salida (tales como la " +"política de salida por defecto), probablemente es seguro decir que vas a " +"tener que escuchar a alguien, eventualmente." #: https//support.torproject.org/abuse/exit-relay-expectations/ #: (content/abuse/exit-relay-expectations/contents+en.lrquestion.description) msgid "Abuse complaints may come in a variety of forms. For example:" msgstr "" +"Las quejas por abuso pueden venir en una variedad de formas. Por ejemplo:" #: https//support.torproject.org/abuse/exit-relay-expectations/ #: (content/abuse/exit-relay-expectations/contents+en.lrquestion.description) @@ -11562,6 +11585,9 @@ msgid "" "FBI sends you a polite email, you explain that you run a Tor relay, and they" " say \"oh well\" and leave you alone. [Port 80]" msgstr "" +"- Alguien se conecta a Hotmail y envía una nota de rescate a una compañía. " +"El FBI te envía un correo electrónico por cortesía, explicás que corrés un " +"repetidor Tor, y ellos dicen \"oh, bien\" y te dejan tranquilo. [Puerto 80]" #: https//support.torproject.org/abuse/exit-relay-expectations/ #: (content/abuse/exit-relay-expectations/contents+en.lrquestion.description) @@ -11570,6 +11596,9 @@ msgid "" "groups and post spam to Usenet, and then sends an angry mail to your ISP " "about how you're destroying the world. [Port 80]" msgstr "" +"- Alguien intenta bajarte usando Tor para conectar a grupos de Google y " +"postear correo electrónico no deseado en Usenet, y luego envía un correo " +"iracundo a tu ISP acerca de cómo estás destruyendo al mundo. [Puerto 80]" #: https//support.torproject.org/abuse/exit-relay-expectations/ #: (content/abuse/exit-relay-expectations/contents+en.lrquestion.description) @@ -11578,6 +11607,9 @@ msgid "" "ISP gets polite mail about how your computer has been compromised; and/or " "your computer gets DDoSed. [Port 6667]" msgstr "" +"- Alguien se conecta a una red IRC y se convierte en una molestia. Tu ISP " +"recibe correos de cortesía acerca de cómo ha sido comprometida tu " +"computadora y/o la misma cae bajo ataque DDoS. [Puerto 6667]" #: https//support.torproject.org/abuse/exit-relay-expectations/ #: (content/abuse/exit-relay-expectations/contents+en.lrquestion.description) @@ -11588,6 +11620,12 @@ msgid "" "tor-legal-faq/tor-dmca-response/), which explains why your ISP can probably " "ignore the notice without any liability. [Arbitrary ports]" msgstr "" +"- Alguien usa Tor para descargar una película con Vin Diesel, y a tu ISP le " +"llega una misiva DMCA de remoción de material. Mirá la [Plantilla de " +"Respuesta de Tor a la DMCA](https://community.torproject.org/relay" +"/community-resources/eff-tor-legal-faq/tor-dmca-response/) de la EFF, la " +"cual explica por qué tu ISP probabemente puede ignorarla sin ninguna " +"consecuencia. [Puertos arbitrarios]" #: https//support.torproject.org/abuse/exit-relay-expectations/ #: (content/abuse/exit-relay-expectations/contents+en.lrquestion.description) @@ -11597,6 +11635,10 @@ msgid "" "wiki](https://community.torproject.org/relay/community-resources/good-bad-" "isps/)." msgstr "" +"Algunos proveedores de alojamiento son más amigables que otros en lo que " +"hace a las salidas Tor. Por un listado, mirá la [wiki de buenos y malos " +"ISPs](https://community.torproject.org/relay/community-resources/good-bad-" +"isps/)." #: https//support.torproject.org/abuse/exit-relay-expectations/ #: (content/abuse/exit-relay-expectations/contents+en.lrquestion.description) @@ -11605,6 +11647,10 @@ msgid "" " see the [collection of templates](https://community.torproject.org/relay" "/community-resources/tor-abuse-templates/)." msgstr "" +"Por un conjunto completo de plantillas de respuesta a diferentes tipos de " +"quejas por abuso, mirá la [colección de " +"plantillas](https://community.torproject.org/relay/community-resources/tor-" +"abuse-templates/)." #: https//support.torproject.org/abuse/exit-relay-expectations/ #: (content/abuse/exit-relay-expectations/contents+en.lrquestion.description) @@ -11615,6 +11661,11 @@ msgid "" "[running a reduced exit " "policy](https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy)." msgstr "" +"También podés reducir proactivamente la cantidad de abuso que te llega " +"siguiendo [estos consejos para correr un nodo de salida con mínimo " +"acoso](https://blog.torproject.org/blog/tips-running-exit-node) y [corriendo" +" una política de salida " +"reducida](https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPoli…." #: https//support.torproject.org/abuse/exit-relay-expectations/ #: (content/abuse/exit-relay-expectations/contents+en.lrquestion.description) @@ -11622,6 +11673,8 @@ msgid "" "You might also find that your Tor relay's IP is blocked from accessing some " "Internet sites/services." msgstr "" +"También podrías encontrarte con que el IP de tu repetidor Tor está bloqueado" +" para acceder a algunos sitios/servicios de Internet." #: https//support.torproject.org/abuse/exit-relay-expectations/ #: (content/abuse/exit-relay-expectations/contents+en.lrquestion.description) @@ -11629,6 +11682,9 @@ msgid "" "This might happen regardless of your exit policy, because some groups don't " "seem to know or care that Tor has exit policies." msgstr "" +"Esto podría pasar independientemente de tu política de salida, porque " +"algunos grupos parecieran no conocer o importarles que Tor tiene políticas " +"de salida." #: https//support.torproject.org/abuse/exit-relay-expectations/ #: (content/abuse/exit-relay-expectations/contents+en.lrquestion.description) @@ -11636,6 +11692,8 @@ msgid "" "(If you have a spare IP not used for other activities, you might consider " "running your Tor relay on it.)" msgstr "" +"(Si tenés un IP de sobra no usado para otras actividades, podrías considerar" +" correr tu repetidor Tor en él.)" #: https//support.torproject.org/abuse/exit-relay-expectations/ #: (content/abuse/exit-relay-expectations/contents+en.lrquestion.description) @@ -11643,16 +11701,18 @@ msgid "" "In general, it's advisable not to use your home internet connection to " "provide a Tor relay." msgstr "" +"En general, es aconsejable no usar tu conexión a Internet doméstica para " +"proveer un repetidor Tor." #: https//support.torproject.org/abuse/does-tor-get-much-abuse/ #: (content/abuse/how-much-abuse/contents+en.lrquestion.title) msgid "Does Tor get much abuse?" -msgstr "" +msgstr "¿Tor recibe mucho abuso?" #: https//support.torproject.org/abuse/does-tor-get-much-abuse/ #: (content/abuse/how-much-abuse/contents+en.lrquestion.description) msgid "Not much, in the grand scheme of things." -msgstr "" +msgstr "No mucho, en grandes generalidades." #: https//support.torproject.org/abuse/does-tor-get-much-abuse/ #: (content/abuse/how-much-abuse/contents+en.lrquestion.description) @@ -11660,6 +11720,8 @@ msgid "" "The network has been running since October 2003, and it's only generated a " "handful of complaints." msgstr "" +"La red ha estado corriendo desde octubre de 2003, y solamente ha generado un" +" manojo de quejas." #: https//support.torproject.org/abuse/does-tor-get-much-abuse/ #: (content/abuse/how-much-abuse/contents+en.lrquestion.description) @@ -11667,6 +11729,8 @@ msgid "" "Of course, like all privacy-oriented networks on the net, it attracts its " "share of jerks." msgstr "" +"Por supuesto, como todas las redes orientadas a la privacidad en Internet, " +"atrae a una caterva de idiotas." #: https//support.torproject.org/abuse/does-tor-get-much-abuse/ #: (content/abuse/how-much-abuse/contents+en.lrquestion.description) @@ -11676,6 +11740,10 @@ msgid "" "complaints,\" so we hope our network is more sustainable than past attempts " "at anonymity networks." msgstr "" +"Las políticas de salida de Tor ayudan a separar el rol de \"con voluntad de " +"donar recursos a la red\" del de \"con voluntad de lidiar con quejas de " +"abuso en las salidas\", por lo que esperamos que nuestra red sea más " +"sustentable que otros intentos pasados de redes de anonimato." #: https//support.torproject.org/abuse/does-tor-get-much-abuse/ #: (content/abuse/how-much-abuse/contents+en.lrquestion.description) @@ -11684,11 +11752,14 @@ msgid "" "/user-research/persona/), we feel that we're doing pretty well at striking a" " balance currently." msgstr "" +"Como Tor tiene [muchos buenos usos también](https://community.torproject.org" +"/user-research/persona/), en la actualidad sentimos que nos está yendo " +"bastante bien con el logro de un equilibrio." #: https//support.torproject.org/abuse/tor-ip-for-legal-case/ #: (content/abuse/ip-legal-case/contents+en.lrquestion.title) msgid "I have questions about a Tor IP address for a legal case." -msgstr "" +msgstr "Tengo preguntas acerca de una dirección IP de Tor para un caso legal." #: https//support.torproject.org/abuse/tor-ip-for-legal-case/ #: (content/abuse/ip-legal-case/contents+en.lrquestion.description) @@ -11699,6 +11770,11 @@ msgid "" "directory](https://blog.torproject.org/blog/start-tor-legal-support-" "directory) of people who may be able to help you." msgstr "" +"Por favor leé las [PMF legales escritas por los abogados de la " +"EFF](https://community.torproject.org/relay/community-resources/eff-tor-" +"legal-faq/). Hay un creciente [directorio " +"legal](https://blog.torproject.org/blog/start-tor-legal-support-directory) " +"de gente que puede ser capaz de ayudarte." #: https//support.torproject.org/abuse/tor-ip-for-legal-case/ #: (content/abuse/ip-legal-case/contents+en.lrquestion.description) @@ -11708,16 +11784,22 @@ msgid "" "tool](https://exonerator.torproject.org/) to query the historic Tor relay " "lists and get an answer." msgstr "" +"Si necesitás comprobar si una cierta dirección IP estuvo actuando como un " +"nodo de salida Tor en una cierta fecha y hora, podés usar la [herramienta " +"ExoneraTor](https://exonerator.torproject.org/) para consultar las listas " +"históricas de repetidores Tor y obtener una respuesta." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.title) msgid "Tor is banned from the IRC network I want to use." -msgstr "" +msgstr "Tor está prohibido en la red IRC que quiero usar." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) msgid "Sometimes jerks make use of Tor to troll IRC channels." msgstr "" +"Algunas veces, ciertos idiotas hacen uso de Tor para trolear los canales " +"IRC." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11725,11 +11807,16 @@ msgid "" "This abuse results in IP-specific temporary bans (\"klines\" in IRC lingo), " "as the network operators try to keep the troll off of their network." msgstr "" +"Este abuso resulta en prohibiciones temporarias específicas para algunos IP " +"(\"klines\" en la jerga de IRC), mientras los operadores de la red intentan " +"mantener al trol fuera de la misma." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) msgid "This response underscores a fundamental flaw in IRC's security model:" msgstr "" +"Esta respuesta subraya un defecto fundamental en el modelo de seguridad del " +"IRC:" #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11737,6 +11824,8 @@ msgid "" "they assume that IP addresses equate to humans, and by banning the IP " "address they can ban the human." msgstr "" +"asumen que las direcciones IP son equivalentes a seres humanos, y al " +"prohibir a la dirección IP, pueden prohibir al ser humano." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11745,6 +11834,9 @@ msgid "" "the literally millions of open proxies and compromised computers around the " "Internet." msgstr "" +"En realidad, este no es el caso — muchos de esos trols hacen uso rutinario " +"de los, literalmente, millones de proxies abiertos y computadoras " +"comprometidas alrededor de Internet." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11754,11 +11846,15 @@ msgid "" "sprung up based on this flawed security model (not unlike the antivirus " "industry)." msgstr "" +"Las redes IRC están peleando una batalla perdida al intentar bloquear todos " +"estos nodos, y ha florecido una completa industria a pequeña escala de " +"listas negras y antitrols, basada en este modelo de seguridad erróneo " +"(similar a la industria antivirus)." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) msgid "The Tor network is just a drop in the bucket here." -msgstr "" +msgstr "Acá, la red Tor es solo una gota en el balde." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11766,6 +11862,8 @@ msgid "" "On the other hand, from the viewpoint of IRC server operators, security is " "not an all-or-nothing thing." msgstr "" +"Por otro lado, desde el punto de vista de los operadores de servidores IRC, " +"la seguridad no es una cosa a todo o nada." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11773,6 +11871,8 @@ msgid "" "By responding quickly to trolls or any other social attack, it may be " "possible to make the attack scenario less attractive to the attacker." msgstr "" +"Al responder rápidamente a los trols o a cualquier otro ataque social, puede" +" ser posible hacer al escenario del ataque menos atractivo para el atacante." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11780,6 +11880,9 @@ msgid "" "And most individual IP addresses do equate to individual humans, on any " "given IRC network at any given time." msgstr "" +"Y la mayoría de las direcciones IP individuales sí son equivalentes a seres " +"humanos individuales, sobre cualquier red IRC dada en cualquier momento " +"dado." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11787,6 +11890,8 @@ msgid "" "The exceptions include NAT gateways which may be allocated access as special" " cases." msgstr "" +"Las excepciones incluyen puntos de salida NAT a los cuales se les pueden " +"adjudicar accesos como casos especiales." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11795,6 +11900,9 @@ msgid "" "generally a losing battle to keep klining a single ill-behaved IRC user " "until that user gets bored and goes away." msgstr "" +"Mientras que es una batalla perdida el intentar detener el uso de proxies " +"abiertos, generalmente no lo es el seguir haciendo \"klining\" a un único " +"usuario de IRC con mala conducta, hasta que ese usuario se aburra y se vaya." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11802,6 +11910,9 @@ msgid "" "But the real answer is to implement application-level auth systems, to let " "in well-behaving users and keep out badly-behaving users." msgstr "" +"Pero la respuesta real es implementar sistemas de autenticación a nivel de " +"aplicación, para dejar pasar a los usuarios con buen comportamiento y " +"mantener afuera a los de mal comportamiento." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11809,11 +11920,16 @@ msgid "" "This needs to be based on some property of the human (such as a password " "they know), not some property of the way their packets are transported." msgstr "" +"Esto necesita estar basado en alguna propiedad del ser humano (tal como una " +"contraseña que conoce), y no en alguna propiedad de la forma en que sus " +"paquetes son transportados." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) msgid "Of course, not all IRC networks are trying to ban Tor nodes." msgstr "" +"Por supuesto, no todas las redes IRC están intentando prohibir a los nodos " +"Tor." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11821,6 +11937,9 @@ msgid "" "After all, quite a few people use Tor to IRC in privacy in order to carry on" " legitimate communications without tying them to their real-world identity." msgstr "" +"Después de todo, es bastante poca la gente que usa Tor para efectuar IRC con" +" privacidad, con el fin de conducir comunicaciones legítimas sin ser " +"vinculados a sus identidades en el mundo real." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11829,6 +11948,9 @@ msgid "" "millions of IPs that bad people can use is worth losing the contributions " "from the well-behaved Tor users." msgstr "" +"Cada red IRC necesita decidir por sí misma si bloquear unos pocos más de los" +" millones de IPs que las malas personas pueden usar vale la pena, si es que " +"pierden las contribuciones de los usuarios de Tor con buen comportamiento." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11836,6 +11958,8 @@ msgid "" "If you're being blocked, have a discussion with the network operators and " "explain the issues to them." msgstr "" +"Si estás siendo bloqueado, establecé una discusión con los operadores de red" +" y explicales estas cuestiones." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11843,6 +11967,9 @@ msgid "" "They may not be aware of the existence of Tor at all, or they may not be " "aware that the hostnames they're klining are Tor exit nodes." msgstr "" +"Pueden no ser concientes de la existencia de Tor en lo absoluto, o del hecho" +" que los nombres de equipo a los que están haciendo \"klining\" son nodos de" +" salida Tor." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11851,6 +11978,9 @@ msgid "" "you may want to consider moving to a network that is more open to free " "speech." msgstr "" +"Si explicás el problema, y concluyen que Tor debería ser bloqueado, podrías " +"querer considerar elegir una red que sea más abierta a la libertad de " +"palabra." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description)

1 0

[translation/support-portal] https://gitweb.torproject.org/translation.git/commit/?h=support-portal
by translation＠torproject.org 16 Dec '20

16 Dec '20

commit c5d9a1efdd8901e6a5f84a9ca79d144d23eb5c42 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Dec 16 09:48:29 2020 +0000 https://gitweb.torproject.org/translation.git/commit/?h=support-portal --- contents+es-AR.po | 30 +++++++++++++++--------------- contents+ru.po | 20 +++++++++++--------- 2 files changed, 26 insertions(+), 24 deletions(-) diff --git a/contents+es-AR.po b/contents+es-AR.po index 4e3d3f598d..94afff717d 100644 --- a/contents+es-AR.po +++ b/contents+es-AR.po @@ -11476,7 +11476,7 @@ msgstr "Estos scripts también son utilizables para eso.)" #: https//support.torproject.org/abuse/what-about-ddos/ #: (content/abuse/ddos/contents+en.lrquestion.title) msgid "What about distributed denial of service attacks?" -msgstr "¿Y qué acerca de los ataques de denegación de servicio distribuídos?" +msgstr "¿Y qué acerca de los ataques distribuídos de denegación de servicio?" #: https//support.torproject.org/abuse/what-about-ddos/ #: (content/abuse/ddos/contents+en.lrquestion.description) @@ -11485,8 +11485,8 @@ msgid "" "group of thousands of computers all sending floods of traffic to a victim." msgstr "" "Los ataques de denegación de servicio distribuídos (DDoS) típicamente se " -"apoyan en tener un grupo de miles de computadoras, todas enviando un diluvio" -" de tráfico a una víctima." +"apoyan en poseer un grupo de miles de computadoras, todas enviando un " +"diluvio de tráfico a una víctima." #: https//support.torproject.org/abuse/what-about-ddos/ #: (content/abuse/ddos/contents+en.lrquestion.description) @@ -11494,8 +11494,8 @@ msgid "" "Since the goal is to overpower the bandwidth of the victim, they typically " "send UDP packets since those don't require handshakes or coordination." msgstr "" -"Ya que el objetivo es dominar el ancho de banda de la víctima, típicamente " -"envían paquetes UDP, ya que esos no requieren intercambio de señales o " +"Ya que el objetivo es agotar el ancho de banda de la víctima, típicamente se" +" envían paquetes UDP, ya que esos no requieren intercambio de señales o " "coordinación." #: https//support.torproject.org/abuse/what-about-ddos/ @@ -11570,7 +11570,7 @@ msgid "" msgstr "" "Si corrés un repetidor Tor que permite conexiones de salida (tales como la " "política de salida por defecto), probablemente es seguro decir que vas a " -"escuchar a alguien, eventualmente." +"tener que escuchar a alguien, eventualmente." #: https//support.torproject.org/abuse/exit-relay-expectations/ #: (content/abuse/exit-relay-expectations/contents+en.lrquestion.description) @@ -11682,9 +11682,9 @@ msgid "" "This might happen regardless of your exit policy, because some groups don't " "seem to know or care that Tor has exit policies." msgstr "" -"Esto podría pasar independientemente de tu política de salida, porque a " -"algunos grupos pareciera no conocer o importarles que Tor tiene políticas de" -" salida." +"Esto podría pasar independientemente de tu política de salida, porque " +"algunos grupos parecieran no conocer o importarles que Tor tiene políticas " +"de salida." #: https//support.torproject.org/abuse/exit-relay-expectations/ #: (content/abuse/exit-relay-expectations/contents+en.lrquestion.description) @@ -11743,7 +11743,7 @@ msgstr "" "Las políticas de salida de Tor ayudan a separar el rol de \"con voluntad de " "donar recursos a la red\" del de \"con voluntad de lidiar con quejas de " "abuso en las salidas\", por lo que esperamos que nuestra red sea más " -"sustentable que otros intentos pasados a redes de anonimato." +"sustentable que otros intentos pasados de redes de anonimato." #: https//support.torproject.org/abuse/does-tor-get-much-abuse/ #: (content/abuse/how-much-abuse/contents+en.lrquestion.description) @@ -11754,7 +11754,7 @@ msgid "" msgstr "" "Como Tor tiene [muchos buenos usos también](https://community.torproject.org" "/user-research/persona/), en la actualidad sentimos que nos está yendo " -"bastante bien en lograr un equilibrio." +"bastante bien con el logro de un equilibrio." #: https//support.torproject.org/abuse/tor-ip-for-legal-case/ #: (content/abuse/ip-legal-case/contents+en.lrquestion.title) @@ -11921,7 +11921,7 @@ msgid "" "they know), not some property of the way their packets are transported." msgstr "" "Esto necesita estar basado en alguna propiedad del ser humano (tal como una " -"contraseña que conoce), y no alguna propiedad de la forma en que sus " +"contraseña que conoce), y no en alguna propiedad de la forma en que sus " "paquetes son transportados." #: https//support.torproject.org/abuse/tor-ban-irc/ @@ -11958,8 +11958,8 @@ msgid "" "If you're being blocked, have a discussion with the network operators and " "explain the issues to them." msgstr "" -"Si estás siendo bloqueado, tené una discusión con los operadores de red y " -"explicales las cuestiones." +"Si estás siendo bloqueado, establecé una discusión con los operadores de red" +" y explicales estas cuestiones." #: https//support.torproject.org/abuse/tor-ban-irc/ #: (content/abuse/irc-ban/contents+en.lrquestion.description) @@ -11979,7 +11979,7 @@ msgid "" "speech." msgstr "" "Si explicás el problema, y concluyen que Tor debería ser bloqueado, podrías " -"querer considerar moverte a una red que sea más abierta a la libertad de " +"querer considerar elegir una red que sea más abierta a la libertad de " "palabra." #: https//support.torproject.org/abuse/tor-ban-irc/ diff --git a/contents+ru.po b/contents+ru.po index 4cd80b91f1..54d717750b 100644 --- a/contents+ru.po +++ b/contents+ru.po @@ -10516,11 +10516,13 @@ msgid "" "In the past they have not been reliably updated. That means you could be " "missing stability and security fixes." msgstr "" +"Известно, что в прошлом они не обновлялись как следует. Вы можете потерять в" +" стабильности, а некоторые ошибки останутся без исправлений." #: https//support.torproject.org/apt/tor-ubuntu/ #: (content/apt/apt-2/contents+en.lrquestion.description) msgid "Instead, please use [Tor Debian repository](/apt/tor-deb-repo)." -msgstr "" +msgstr "Лучше используйте [репозиторий Tor Debian](/apt/tor-deb-repo)." #: https//support.torproject.org/apt/apt-over-tor/ #: (content/apt/apt-3/contents+en.lrquestion.title) @@ -10579,7 +10581,7 @@ msgstr "" #: https//support.torproject.org/apt/apt-over-tor/ #: (content/apt/apt-3/contents+en.lrquestion.description) msgid "Now refresh your sources and try to install tor again:" -msgstr "" +msgstr "Теперь обновите свои источники и попробуйте снова установить Tor:" #: https//support.torproject.org/apt/apt-over-tor/ #: (content/apt/apt-3/contents+en.lrquestion.description) @@ -10646,27 +10648,27 @@ msgstr "" #: https//support.torproject.org/rpm/tor-rpm-install/ #: (content/rpm/install/contents+en.lrquestion.description) msgid "baseurl=https://rpm.torproject.org/centos/$releasever/$basearch" -msgstr "" +msgstr "baseurl=https://rpm.torproject.org/centos/$releasever/$basearch" #: https//support.torproject.org/rpm/tor-rpm-install/ #: (content/rpm/install/contents+en.lrquestion.description) msgid "enabled=1" -msgstr "" +msgstr "enabled=1" #: https//support.torproject.org/rpm/tor-rpm-install/ #: (content/rpm/install/contents+en.lrquestion.description) msgid "gpgcheck=1" -msgstr "" +msgstr "gpgcheck=1" #: https//support.torproject.org/rpm/tor-rpm-install/ #: (content/rpm/install/contents+en.lrquestion.description) msgid "gpgkey=https://rpm.torproject.org/centos/public_gpg.key" -msgstr "" +msgstr "gpgkey=https://rpm.torproject.org/centos/public_gpg.key" #: https//support.torproject.org/rpm/tor-rpm-install/ #: (content/rpm/install/contents+en.lrquestion.description) msgid "cost=100" -msgstr "" +msgstr "cost=100" #: https//support.torproject.org/rpm/tor-rpm-install/ #: (content/rpm/install/contents+en.lrquestion.description) @@ -10681,12 +10683,12 @@ msgstr "" #: https//support.torproject.org/rpm/tor-rpm-install/ #: (content/rpm/install/contents+en.lrquestion.description) msgid "baseurl=https://rpm.torproject.org/fedora/$releasever/$basearch" -msgstr "" +msgstr "baseurl=https://rpm.torproject.org/fedora/$releasever/$basearch" #: https//support.torproject.org/rpm/tor-rpm-install/ #: (content/rpm/install/contents+en.lrquestion.description) msgid "gpgkey=https://rpm.torproject.org/fedora/public_gpg.key" -msgstr "" +msgstr "gpgkey=https://rpm.torproject.org/fedora/public_gpg.key" #: https//support.torproject.org/rpm/tor-rpm-install/ #: (content/rpm/install/contents+en.lrquestion.description)

1 0

[translation/communitytpo-contentspot] https://gitweb.torproject.org/translation.git/commit/?h=communitytpo-contentspot
by translation＠torproject.org 16 Dec '20

16 Dec '20

commit f6409a8a480d3d147353f45e7c7df7afa99d0690 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Dec 16 09:45:13 2020 +0000 https://gitweb.torproject.org/translation.git/commit/?h=communitytpo-conten… --- contents+ru.po | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/contents+ru.po b/contents+ru.po index 32496bbd96..4298150072 100644 --- a/contents+ru.po +++ b/contents+ru.po @@ -12,8 +12,8 @@ # Gus, 2020 # erinm, 2020 # Иван Иванов <remove4kebab(a)protonmail.com>, 2020 -# Sergey Smirnov <cj75300(a)gmail.com>, 2020 # Leonid Evdokimov <leon+transifex(a)darkk.net.ru>, 2020 +# Sergey Smirnov <cj75300(a)gmail.com>, 2020 # msgid "" msgstr "" @@ -21,7 +21,7 @@ msgstr "" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2020-11-05 12:55+EST\n" "PO-Revision-Date: 2019-12-11 10:50+0000\n" -"Last-Translator: Leonid Evdokimov <leon+transifex(a)darkk.net.ru>, 2020\n" +"Last-Translator: Sergey Smirnov <cj75300(a)gmail.com>, 2020\n" "Language-Team: Russian (https://www.transifex.com/otf/teams/1519/ru/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -11035,7 +11035,7 @@ msgstr "" #: https//community.torproject.org/relay/setup/bridge/fedora/ #: (content/relay-operations/technical-setup/bridge/fedora/contents+en.lrpage.body) msgid "baseurl=https://rpm.torproject.org/fedora/$releasever/$basearch" -msgstr "" +msgstr "baseurl=https://rpm.torproject.org/fedora/$releasever/$basearch" #: https//community.torproject.org/onion-services/setup/install/ #: (content/onion-services/setup/install/contents+en.lrpage.body) @@ -11048,7 +11048,7 @@ msgstr "" #: https//community.torproject.org/relay/setup/bridge/centos-rhel-opensuse/ #: (content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents+en.lrpage.body) msgid "enabled=1" -msgstr "" +msgstr "enabled=1" #: https//community.torproject.org/onion-services/setup/install/ #: (content/onion-services/setup/install/contents+en.lrpage.body) @@ -11061,7 +11061,7 @@ msgstr "" #: https//community.torproject.org/relay/setup/bridge/centos-rhel-opensuse/ #: (content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents+en.lrpage.body) msgid "gpgcheck=1" -msgstr "" +msgstr "gpgcheck=1" #: https//community.torproject.org/onion-services/setup/install/ #: (content/onion-services/setup/install/contents+en.lrpage.body) @@ -11070,7 +11070,7 @@ msgstr "" #: https//community.torproject.org/relay/setup/bridge/fedora/ #: (content/relay-operations/technical-setup/bridge/fedora/contents+en.lrpage.body) msgid "gpgkey=https://rpm.torproject.org/fedora/public_gpg.key" -msgstr "" +msgstr "gpgkey=https://rpm.torproject.org/fedora/public_gpg.key" #: https//community.torproject.org/onion-services/setup/install/ #: (content/onion-services/setup/install/contents+en.lrpage.body) @@ -11083,7 +11083,7 @@ msgstr "" #: https//community.torproject.org/relay/setup/bridge/centos-rhel-opensuse/ #: (content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents+en.lrpage.body) msgid "cost=100" -msgstr "" +msgstr "cost=100" #: https//community.torproject.org/onion-services/setup/install/ #: (content/onion-services/setup/install/contents+en.lrpage.body) @@ -11927,14 +11927,14 @@ msgstr "" #: https//community.torproject.org/relay/setup/bridge/centos-rhel-opensuse/ #: (content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents+en.lrpage.body) msgid "baseurl=https://rpm.torproject.org/centos/$releasever/$basearch" -msgstr "" +msgstr "baseurl=https://rpm.torproject.org/centos/$releasever/$basearch" #: https//community.torproject.org/relay/setup/guard/centosrhel/ #: (content/relay-operations/technical-setup/guard/centosrhel/contents+en.lrpage.body) #: https//community.torproject.org/relay/setup/bridge/centos-rhel-opensuse/ #: (content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents+en.lrpage.body) msgid "gpgkey=https://rpm.torproject.org/centos/public_gpg.key" -msgstr "" +msgstr "gpgkey=https://rpm.torproject.org/centos/public_gpg.key" #: https//community.torproject.org/relay/setup/guard/centosrhel/ #: (content/relay-operations/technical-setup/guard/centosrhel/contents+en.lrpage.body)

1 0

[tor-browser-spec/master] Update audit for Tor Browser 10.0.7
by sysrqb＠torproject.org 16 Dec '20

16 Dec '20

commit 56702d338fc44f15ebe417d5ef058ca2f4a8a74c Author: Matthew Finkel <sysrqb(a)torproject.org> Date: Wed Dec 16 04:05:17 2020 +0000 Update audit for Tor Browser 10.0.7 --- audits/FF84_NETWORK_AUDIT | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/audits/FF84_NETWORK_AUDIT b/audits/FF84_NETWORK_AUDIT index a4c6ee0..122567b 100644 --- a/audits/FF84_NETWORK_AUDIT +++ b/audits/FF84_NETWORK_AUDIT @@ -1,4 +1,4 @@ -`git diff 1cb2c4893850a5b0a246f821a6390c07064c1227 11898884c81cd84cfaec46dffe1dbf42517e8301` +`git diff 1cb2c4893850a5b0a246f821a6390c07064c1227 7969cebe593fccee033e8533482d4cb3e084d1d8` and then go over all the changes containing the below mentioned potentially dangerous calls and features. Grep the diff for the following strings and examine surrounding usage. @@ -146,14 +146,14 @@ End: 6a234c2b1e1972f11e585551d4cf2e40e84bf16f # v67.0.0 ============ Android Components Portion ============= Start: 0a2993d44aae3d877bb97cee925096f83af01b3a # v63.0.8 -End: 89973898761d54c7512bb74ea2c3489fca07bf8e # v67.0.10 +End: 50435d74a958ad964dd177953a4d15fb0e86bbf8 # v67.0.11 # FF84: Zero new usage found of known proxy-bypass APIs (using `java_audit.sh`) ============ Fenix Portion ============= Start: 5441935698f4d9e3606f3d6baf892f6e0106a2f6 # v83.1.0-rc.1 -End: 8b4b9bde5f2dab9fec1631fbfc70d4e2c3b2d24e # v84.1.0-rc.1 +End: dc3f8958efa103a411f54667f1360fc69bb3208e # v84.1.0 # FF84: Zero new usage found of known proxy-bypass APIs (using `java_audit.sh`)

1 0

[translation/support-portal] https://gitweb.torproject.org/translation.git/commit/?h=support-portal
by translation＠torproject.org 15 Dec '20

15 Dec '20

commit a9a626cdf270cd562521d26f8217c5a765f84373 Author: Translation commit bot <translation(a)torproject.org> Date: Tue Dec 15 22:47:59 2020 +0000 https://gitweb.torproject.org/translation.git/commit/?h=support-portal --- contents+ru.po | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/contents+ru.po b/contents+ru.po index f19c127bc7..4cd80b91f1 100644 --- a/contents+ru.po +++ b/contents+ru.po @@ -9310,6 +9310,11 @@ msgid "" " it will be for us to understand and follow up. Sometimes when we receive " "emails without subject lines, they're marked as spam and we don't see them." msgstr "" +"В поле \"Тема\" своего письма, пожалуйста, укажите суть. Чем содержательнее " +"эта информация, тем проще нам понять вас и принять меры. Удачные примеры: " +"\"Нет соединения\", \"Ошибка на сайте\", \"Отзыв о Tor Browser\", \"Мне " +"нужен мост\". Бывает, что сообщения вообще без поля \"Тема\" автоматически " +"отправляются в спам. Мы их просто не видим." #: https//support.torproject.org/misc/bug-or-feedback/ #: (content/misc/bug-or-feedback/contents+en.lrquestion.description) @@ -10190,6 +10195,8 @@ msgid "" "1. To verify your nick, open a new browser window and go to " "https://webchat.oftc.net/?channels=tor." msgstr "" +"1. Чтобы проверить свой никнейм, откройте новое окно браузера и зайдите на " +"сайт https://webchat.oftc.net/?channels=tor." #: https//support.torproject.org/get-in-touch/why-i-cant-join-tor-channels/ #: (content/get-in-touch/why-i-cant-join-tor-channels/contents+en.lrquestion.description) @@ -10317,6 +10324,10 @@ msgid "" "version of Tor, this might not always give you the latest stable Tor " "version. Therefore, it's recommended to install `tor` from our repository." msgstr "" +"У Tor Project есть собственный [репозиторий " +"Debian](https://deb.torproject.org). В Debian включена LTS-версия Tor. С ней" +" вы не всегда сможете иметь самую свежую и стабильную версию Tor. Поэтому мы" +" рекомендуем устанавливать Tor из нашего репозитория." #: https//support.torproject.org/apt/tor-deb-repo/ #: (content/apt/apt-1/contents+en.lrquestion.description) @@ -10335,6 +10346,10 @@ msgid "" "should have access to a user account with system administration privileges, " "e.g your user should be in the sudo group." msgstr "" +"> **Примечание.** Символ # означает, что команда отдается от лица " +"суперпользователя. Это значит, что вы должны иметь доступ к аккаунту " +"пользователя с правами администратора, например, ваш пользователь может быть" +" в группе sudo." #: https//support.torproject.org/apt/tor-deb-repo/ #: (content/apt/apt-1/contents+en.lrquestion.description)

1 0

[community/master] replace CAPTCHA with Captcha
by gus＠torproject.org 15 Dec '20

15 Dec '20

commit 1bd7c21c00285eed6a3b3653af3352dd66c2d07b Author: Kim Le <kle2(a)student.unimelb.edu.au> Date: Sat Oct 17 10:52:46 2020 +1100 replace CAPTCHA with Captcha --- content/gsoc/cloudflare-captcha-monitoring/contents.lr | 18 +++++++++--------- .../tor-abuse-templates/contents.lr | 12 ++++++------ 2 files changed, 15 insertions(+), 15 deletions(-) diff --git a/content/gsoc/cloudflare-captcha-monitoring/contents.lr b/content/gsoc/cloudflare-captcha-monitoring/contents.lr index f511683..eae7c86 100644 --- a/content/gsoc/cloudflare-captcha-monitoring/contents.lr +++ b/content/gsoc/cloudflare-captcha-monitoring/contents.lr @@ -24,40 +24,40 @@ arma --- difficulty: medium --- -title: Cloudflare CAPTCHA Monitoring +title: Cloudflare Captcha Monitoring --- subtitle: -This project should implement a mechanism to track the rate that Cloudflare fronted webpages return CAPTCHAs to Tor users over time. +This project should implement a mechanism to track the rate that Cloudflare fronted webpages return Captchas to Tor users over time. --- body: # Problem -A large number of Tor users report getting hit by infinite CAPTCHA loops when visiting webpages fronted by Cloudflare. This makes them feel punished for using Tor to protect their privacy and prevents them from legitimately accessing websites. +A large number of Tor users report getting hit by infinite Captcha loops when visiting webpages fronted by Cloudflare. This makes them feel punished for using Tor to protect their privacy and prevents them from legitimately accessing websites. # Proposal -For this project we would like to track in practice how often Cloudflare fronted webpages return CAPTCHAs to Tor clients. +For this project we would like to track in practice how often Cloudflare fronted webpages return Captchas to Tor clients. Our proposed approach consists of: 1. Setting up a very simple static webpage to be fronted by Cloudflare -2. Write a web client to periodically fetch this static webpage via Tor and record how often a CAPTCHA is returned -3. Record and graph CAPTCHA vs real page rates +2. Write a web client to periodically fetch this static webpage via Tor and record how often a Captcha is returned +3. Record and graph Captcha vs real page rates 4. Using the pre-existing architecture, run a second client that does not fetch this webpage via Tor. This will allow us to contrast and compare how Cloudflare responds to Tor Browser vs other browsers. 5. Track and publish these details publicly There are two interesting metrics to track over time: -- the fraction of exit relays that are getting hit with CAPTCHAs, and -- the chance that a Tor client, choosing an exit relay in the normal weighted faction, will get hit by a CAPTCHA. +- the fraction of exit relays that are getting hit with Captchas, and +- the chance that a Tor client, choosing an exit relay in the normal weighted faction, will get hit by a Captcha. Then there are other interesting patterns to look for: - Are certain IP addresses punished consistently and others never punished? -- Is whether you get a CAPTCHA much more probabilistic and transient? +- Is whether you get a Captcha much more probabilistic and transient? - Does that pattern change over time? # Getting Started diff --git a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr index 007e0d2..6b4549e 100644 --- a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr +++ b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr @@ -59,8 +59,8 @@ However, be aware that this may be just one jerk amongst many legitimate Tor use You might have luck getting rid of this jerk by temporarily limiting account creation to require Gmail accounts before posting, or by requiring account creation be done over non-Tor before posting. In general, we believe that problems like this are best solved by improving your service to defend against the attack from the Internet at large. -Brute force login attempts can be reduced/slowed by captchas, which is the approach taken by Gmail for this same problem. -In fact, Google provides a free captcha service, complete with code for easy inclusion in a number of systems to help other sites deal +Brute force login attempts can be reduced/slowed by Captchas, which is the approach taken by Gmail for this same problem. +In fact, Google provides a free Captcha service, complete with code for easy inclusion in a number of systems to help other sites deal with this issue: https://code.google.com/apis/recaptcha/intro.html ``` @@ -100,8 +100,8 @@ https://check.torproject.org/cgi-bin/TorBulkExitList.py?ip=YOUR_IP&port=80 In general however, we believe that problems like this are best solved by improving the service to defend against the attack from the Internet at large. -Scraping and robot activity can be reduced/slowed by captchas, which is the approach taken by Gmail for this same problem. -In fact, Google provides a free captcha service, complete with code for easy inclusion in a number of systems to help other sites deal with this issue: https://code.google.com/apis/recaptcha/intro.html +Scraping and robot activity can be reduced/slowed by Captchas, which is the approach taken by Gmail for this same problem. +In fact, Google provides a free Captcha service, complete with code for easy inclusion in a number of systems to help other sites deal with this issue: https://code.google.com/apis/recaptcha/intro.html Slow DoS attacks [aimed to consume the Apache MaxClients limit](http://www.guerilla-ciso.com/archives/2049) can be alleviated by reducing the httpd.conf TimeOut and KeepAliveTimeout config values to 15-30 and raising the ServerLimit and MaxClients values to omething like 3000. @@ -121,8 +121,8 @@ The attacker would probably just chain an open proxy after Tor, or just use open The Tor project does provide an automated DNSRBL for you to query to flag requests from Tor nodes as requiring special treatment: https://www.torproject.org/projects/tordnsel.html.en In general, we believe that problems like this are best solved by improving the service to defend against the attack from the Internet at large rather than specifically tailoring behavior for Tor. -Brute force login attempts can be reduced/slowed by captchas, which is the approach taken by Gmail for this same problem. -In fact, Google provides a free captcha service, complete with code for easy inclusion in a number of systems to help other sites deal with this issue: https://code.google.com/apis/recaptcha/intro.html +Brute force login attempts can be reduced/slowed by Captchas, which is the approach taken by Gmail for this same problem. +In fact, Google provides a free Captcha service, complete with code for easy inclusion in a number of systems to help other sites deal with this issue: https://code.google.com/apis/recaptcha/intro.html ``` ## SSH Bruteforce Attempts

1 0

[community/master] Merge branch 'captcha'
by gus＠torproject.org 15 Dec '20

15 Dec '20

commit 5858da87d5d39692ee6e4efa48072be77a195e36 Merge: 2f66f49 1bd7c21 Author: gus <gus(a)torproject.org> Date: Tue Dec 15 17:44:00 2020 -0500 Merge branch 'captcha' content/gsoc/cloudflare-captcha-monitoring/contents.lr | 18 +++++++++--------- .../tor-abuse-templates/contents.lr | 12 ++++++------ 2 files changed, 15 insertions(+), 15 deletions(-) diff --cc content/relay-operations/community-resources/tor-abuse-templates/contents.lr index 483cb2c,6b4549e..1cd12f9 --- a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr +++ b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr @@@ -100,10 -100,10 +100,10 @@@ https://check.torproject.org/cgi-bin/To In general however, we believe that problems like this are best solved by improving the service to defend against the attack from the Internet at large. - Scraping and robot activity can be reduced/slowed by captchas, which is the approach taken by Gmail for this same problem. - In fact, Google provides a free captcha service, complete with code for easy inclusion in a number of systems to help other sites deal with this issue: https://code.google.com/apis/recaptcha/intro.html + Scraping and robot activity can be reduced/slowed by Captchas, which is the approach taken by Gmail for this same problem. + In fact, Google provides a free Captcha service, complete with code for easy inclusion in a number of systems to help other sites deal with this issue: https://code.google.com/apis/recaptcha/intro.html -Slow DoS attacks [aimed to consume the Apache MaxClients limit](http://www.guerilla-ciso.com/archives/2049) can be alleviated by reducing the httpd.conf TimeOut and KeepAliveTimeout config values to 15-30 and raising the ServerLimit and MaxClients values to omething like 3000. +Slow DoS attacks [aimed to consume the Apache MaxClients limit](http://www.guerilla-ciso.com/archives/2049) can be alleviated by reducing the httpd.conf TimeOut and KeepAliveTimeout config values to 15-30 and raising the ServerLimit and MaxClients values to something like 3000. If this fails, DoS attempts can also be solved with iptables-based rate limiting solutions, load balancers such as nginx, and also IPS devices, but be aware that Internet traffic is not always uniform in quantity by IP, due to large corporate and even national outproxies, NATs, and services like Tor. http://kevin.vanzonneveld.net/techblog/article/block_brute_force_attacks_wi…

1 0

[community/master] Fix typos
by gus＠torproject.org 15 Dec '20

15 Dec '20

commit 2f66f498aafc2df826acaba85346e0c83f5e5eaf Author: Dimitris Apostolou <dimitris.apostolou(a)icloud.com> Date: Tue Dec 15 23:12:44 2020 +0200 Fix typos --- README.md | 4 ++-- content/gsoc/onion-toolbox/contents.lr | 4 ++-- content/gsoc/privacy-friendly-web/contents.lr | 2 +- content/localization/becoming-tor-translator/contents.lr | 2 +- content/onion-services/setup/install/contents.lr | 2 +- content/relay-operations/community-resources/bad-relays/contents.lr | 2 +- content/relay-operations/community-resources/contents.lr | 2 +- .../community-resources/eff-tor-legal-faq/contents.lr | 2 +- .../relay-operations/community-resources/good-bad-isps/contents.lr | 2 +- .../community-resources/tor-abuse-templates/contents.lr | 4 ++-- .../community-resources/tor-exit-guidelines/contents.lr | 4 ++-- .../community-resources/tor-relay-universities/contents.lr | 2 +- content/relay-operations/technical-setup/bridge/freebsd/contents.lr | 2 +- 13 files changed, 17 insertions(+), 17 deletions(-) diff --git a/README.md b/README.md index fc5b24c..d0d917a 100644 --- a/README.md +++ b/README.md @@ -41,7 +41,7 @@ You can click ```Edit this page``` and submit your content changes in a [Pull Re ```$ cd community/lego && git submodule update --init --recursive``` -5. Translations for the website are imported by Jenkins when bulding the page, but if you want to test them, download the correct branch of the translations repo to the ./i18n/ folder. +5. Translations for the website are imported by Jenkins when building the page, but if you want to test them, download the correct branch of the translations repo to the ./i18n/ folder. 6. Finally: @@ -75,7 +75,7 @@ This is the workflow that Tor Internal people should use when making changes on - Contents file, containing your changes where it would be located on the **reviewer's repo**, e.g. `https://gitlab.torproject.org/steph/community/blob/develop/content/onion-services/contents.lr`. - For the review workflow, please see (Reviewer Workflow). 5. Once the work has been reviewed and any necessary changes and merge request has been made, a repo maintainer or team members with write access to gitweb master will then merge or cherry-pick these changes to master, following the workflow outlined in [How to use our git flow](https://gitlab.torproject.org/web/tpo/wikis/Git-flow-and-merge-reques…. -6. Merger should then move the the ticket to the `Closed` column. +6. Merger should then move the ticket to the `Closed` column. ### Reviewer Workflow diff --git a/content/gsoc/onion-toolbox/contents.lr b/content/gsoc/onion-toolbox/contents.lr index 1d52e87..fa998f7 100644 --- a/content/gsoc/onion-toolbox/contents.lr +++ b/content/gsoc/onion-toolbox/contents.lr @@ -49,7 +49,7 @@ Ultimately myonion is about creating a better experience for onion services deve Myonion is a developer tool box, providing a command line interface and a GUI to configure and deploy existing services via .onion. A minimal prototype for myonion already [exists](https://github.com/hiromipaw/myonion). -Someone that may want to run an onion service can use the myonion wrapper app to start a .onion from their computer and sharea static website or a web application. +Someone that may want to run an onion service can use the myonion wrapper app to start a .onion from their computer and share a static website or a web application. Myonion can also be used to deploy the resulting configured app to a defined set of cloud providers. @@ -57,7 +57,7 @@ Myonion provides a way to build and deploy onion ready applications, allowing de The experience for developers will be similar to using other industry solutions, like the [Docker desktop app](https://www.docker.com/products/docker-desktop). -Developers using myonion are provided with pre-defined and customizable application templates, with corresponding configuration and a test set, eliminating error-prone manual setup and known onion service configuration mistakes. +Developers using myonion are provided with pre-defined and customizable application templates, with corresponding configuration and a test set, eliminating error-prone manual setup and known onion service configuration mistakes. The resulting application is therefore deployable via a set of endpoint management tools to known providers. Providing a way to deploy onion services at scale. diff --git a/content/gsoc/privacy-friendly-web/contents.lr b/content/gsoc/privacy-friendly-web/contents.lr index 7ab642b..36cdd00 100644 --- a/content/gsoc/privacy-friendly-web/contents.lr +++ b/content/gsoc/privacy-friendly-web/contents.lr @@ -49,7 +49,7 @@ Websites can work seamlessly with the Tor Browser and other privacy enhancing br The Tor Browser is in fact, based on Mozilla's Extended Support Release (ESR) Firefox branch. We have a series of patches against this browser to enhance privacy and security. Browser behavior is additionally augmented through the Torbutton extension, and we also change a number of Firefox preferences from their defaults. -The Tor Project has developed over the years a set of web development guidelines that allow websites to work with security enhanced browsers without causing any or minimal functionality destruption to their users. These guidelines have been shaped in an internal styleguide that has been adopted across all torproject.org websites. +The Tor Project has developed over the years a set of web development guidelines that allow websites to work with security enhanced browsers without causing any or minimal functionality disruption to their users. These guidelines have been shaped in an internal styleguide that has been adopted across all torproject.org websites. We are now formalizing these web development patterns and some security concerns that need to be considered when developing websites for users surfing the web with security enhanced browsers and tools. The scope of this project is creating a open-source community-driven browsable list of patterns and release a css/js framework that web developers can extend and use in their work. diff --git a/content/localization/becoming-tor-translator/contents.lr b/content/localization/becoming-tor-translator/contents.lr index 9f5e07b..362df91 100644 --- a/content/localization/becoming-tor-translator/contents.lr +++ b/content/localization/becoming-tor-translator/contents.lr @@ -20,7 +20,7 @@ Thank you for your interest in helping us with translations. # Localization mailing list <a name="tor-l10n" /> -To communicate with other translators, please join the [Tor localization mailing list](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-l10n), where we organize translations, take decisions, report errors in source strings, etc. Please introduce yourself and ask any questions you may have after following up this instructions. +To communicate with other translators, please join the [Tor localization mailing list](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-l10n), where we organize translations, take decisions, report errors in source strings, etc. Please introduce yourself and ask any questions you may have after following up these instructions. # Translation platform diff --git a/content/onion-services/setup/install/contents.lr b/content/onion-services/setup/install/contents.lr index 2796c55..6f12cc9 100644 --- a/content/onion-services/setup/install/contents.lr +++ b/content/onion-services/setup/install/contents.lr @@ -90,7 +90,7 @@ cost=100 ### Installing Tor from source -1. Download latest release and dependecies +1. Download latest release and dependencies The latest release of Tor can be found on the [download](https://www.torproject.org/download/tor/) page. diff --git a/content/relay-operations/community-resources/bad-relays/contents.lr b/content/relay-operations/community-resources/bad-relays/contents.lr index 520a40d..4de7718 100644 --- a/content/relay-operations/community-resources/bad-relays/contents.lr +++ b/content/relay-operations/community-resources/bad-relays/contents.lr @@ -49,7 +49,7 @@ We have three types of flags we can apply: Which we use depends on the severity of the issue, and if it can still be safely used in certain situations. -### My relays was given the BadExit flag. What's up? +### My relay was given the BadExit flag. What's up? In just about all cases we're unable to contact the operator to resolve the issue, so if your relay has been flagged as a BadExit then please let us know (see above for contact info) so we can work together to fix the issue. diff --git a/content/relay-operations/community-resources/contents.lr b/content/relay-operations/community-resources/contents.lr index f2e2f0e..392fbfa 100644 --- a/content/relay-operations/community-resources/contents.lr +++ b/content/relay-operations/community-resources/contents.lr @@ -33,7 +33,7 @@ Also see the [Tor Exit Guidelines](tor-exit-guidelines). Operators can put together their own abuse complaint template responses from one of many templates that Tor has created: [Tor Abuse Templates](tor-abuse-templates). -It is important to respond to abuse complaints in a timely manner (usually within 24 hours). If the hoster gets annoyed by the amount of abuse you can reduce the amount of ports allowed in your exit policy. +It is important to respond to abuse complaints in a timely manner (usually within 24 hours). If the hoster gets annoyed by the amount of abuse you can reduce the amount of ports allowed in your exit policy. Please document your experience with new hosters on the following page: [GoodBadISPs](good-bad-isps) Other docs we like: diff --git a/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr b/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr index 1a9ba2c..a50fdd8 100644 --- a/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr +++ b/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr @@ -136,7 +136,7 @@ For information on what to do if law enforcement seeks access to your digital de EFF has written a [short template](tor-dmca-response) 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 the Lumen DatabaseThe email address for submissions is team(a)lumendatabase.org. +If you like, you should consider submitting a copy of your notice to the Lumen Database. The email address for submissions is team(a)lumendatabase.org. This will help us recognize trends and issues that the lawyers might want to focus on. Lumen encourages submissions from people outside the United States too. diff --git a/content/relay-operations/community-resources/good-bad-isps/contents.lr b/content/relay-operations/community-resources/good-bad-isps/contents.lr index 98eca4c..54e6759 100644 --- a/content/relay-operations/community-resources/good-bad-isps/contents.lr +++ b/content/relay-operations/community-resources/good-bad-isps/contents.lr @@ -32,7 +32,7 @@ For network diversity and stronger anonymity, you should avoid providers and cou |-------------------------|-------------|-----------------|--------------|-------------|---------------------|------------------------| | [UPC Austria GmbH](https://www.upc.at/) | - | - | Yes | Yes | (ISP) does not care what their customers do at all (unless you have a business connection) | 12/2011 | | [Silver Server GmbH](http://sil.at/) | - | -| Yes | Yes | Forwards abuse. Hosts already some big exit/entry nodes which seem to have no problems. Very expensive traffic. | 12/2011 | -| [Tele2 Austria GmbH](https://tele2.at/) | - | - | Yes | Yes | Forwards abuse at business connections, good quality traffic, does not like "proxys" on private lines. Cheap synchronous (SDSL) connections. | 12/2011 | +| [Tele2 Austria GmbH](https://tele2.at/) | - | - | Yes | Yes | Forwards abuse at business connections, good quality traffic, does not like "proxies" on private lines. Cheap synchronous (SDSL) connections. | 12/2011 | | [A1(former Telekom Austria)](http://a1.net) | - | - | Yes | No | Does not like Abuse (in any form) at all. Seems to give out customer data at alleged abuse. Not recommended but cheap. | 12/2011 | | [xpirio GmbH](http://xpirio.at) | - | - | Yes | ? | In general rather relaxed at all services, but better get in touch with their (very understanding) support when you expect abuse. | 12/2011 | diff --git a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr index a590159..483cb2c 100644 --- a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr +++ b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr @@ -92,7 +92,7 @@ We're sorry your site is experiencing this heavy load from Tor. However, it is possible that your rate limiting alarms simply experienced a false positive due to the amount of traffic that flows through the router. We provide service to almost a gigabit of traffic per second, 98% of which is web traffic. -If the attack is real and ongoing, however, the Tor project provides an automated DNSRBL for you to query to block login attempts coming +If the attack is real and ongoing, however, the Tor project provides an automated DNSRBL for you to query to block login attempts coming from Tor nodes: https://www.torproject.org/projects/tordnsel.html.en It is also possible to download a list of all Tor exit IPs that will connect to your server port: @@ -103,7 +103,7 @@ In general however, we believe that problems like this are best solved by improv Scraping and robot activity can be reduced/slowed by captchas, which is the approach taken by Gmail for this same problem. In fact, Google provides a free captcha service, complete with code for easy inclusion in a number of systems to help other sites deal with this issue: https://code.google.com/apis/recaptcha/intro.html -Slow DoS attacks [aimed to consume the Apache MaxClients limit](http://www.guerilla-ciso.com/archives/2049) can be alleviated by reducing the httpd.conf TimeOut and KeepAliveTimeout config values to 15-30 and raising the ServerLimit and MaxClients values to omething like 3000. +Slow DoS attacks [aimed to consume the Apache MaxClients limit](http://www.guerilla-ciso.com/archives/2049) can be alleviated by reducing the httpd.conf TimeOut and KeepAliveTimeout config values to 15-30 and raising the ServerLimit and MaxClients values to something like 3000. If this fails, DoS attempts can also be solved with iptables-based rate limiting solutions, load balancers such as nginx, and also IPS devices, but be aware that Internet traffic is not always uniform in quantity by IP, due to large corporate and even national outproxies, NATs, and services like Tor. http://kevin.vanzonneveld.net/techblog/article/block_brute_force_attacks_wi… diff --git a/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr b/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr index 7ad8ffd..61e4084 100644 --- a/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr +++ b/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr @@ -39,7 +39,7 @@ Once you identified your ISP, you can follow the two-step advice of TorServers.n 2. If they come back positively, ask them if they are OK with an IP range reassignment. If not, you can still explain that you are a non-profit superb large organization filled with security professionals, and that all will be good, and why IP reassignment helps reduce their workload. -The two-step process usually helps in elevating your request to higher levels of support staff without scaring them off too early, even if you don't end up with your own IP range. Here is template you can use: [Inquiry](https://www.torservers.net/wiki/hoster/inquiry) +The two-step process usually helps in elevating your request to higher levels of support staff without scaring them off too early, even if you don't end up with your own IP range. Here is template you can use: [Inquiry](https://www.torservers.net/wiki/hoster/inquiry) ## Legal @@ -134,7 +134,7 @@ A simple notice can be published without a separate webserver using Tor's "DirPo * Disk encryption might be useful to protect your node keys, but on the other hand unencrypted machines are easier to "audit" if required. We feel it's best to be able to easily show that you do Tor exiting, and nothing else (on that IP or server). -* Set reverse DNS to something that signals its use, e.g. 'anonymous-relay', 'proxy', 'tor-proxy'. so when other people see the address in their web logs, they will more quickly understand what's going on. +* Set reverse DNS to something that signals its use, e.g. 'anonymous-relay', 'proxy', 'tor-proxy'. So when other people see the address in their web logs, they will more quickly understand what's going on. If you do, and if SMTP is allowed in your exit policy, consider configuring [SPF](https://en.wikipedia.org/wiki/Sender_Policy_Framework) on your domain: this will protect you from users using your exit node to forge e-mails which look like they come from you. --- html: two-columns-page.html diff --git a/content/relay-operations/community-resources/tor-relay-universities/contents.lr b/content/relay-operations/community-resources/tor-relay-universities/contents.lr index 5d57cac..6fa5dc9 100644 --- a/content/relay-operations/community-resources/tor-relay-universities/contents.lr +++ b/content/relay-operations/community-resources/tor-relay-universities/contents.lr @@ -19,7 +19,7 @@ Most likely it is ambiguously worded, to let them allow or deny things based on But it might be extremely restrictive ("no services of any kind"), in which case you're going to have a tough road ahead of you. * Second, learn about your local laws with respect to liability of traffic that exits from your Tor relay. -In the US, these appear to be mainly the [DMCA](/relay/community-resources/eff-tor-legal-faq/) and [CDA](/relay/community-resources/eff-tor-legal-faq/), and the good news is that many lawyers believe that Tor exit node operators are in the same boat as the ISPs themselves. +In the US, these appear to be mainly the [DMCA](/relay/community-resources/eff-tor-legal-faq/) and [CDA](/relay/community-resources/eff-tor-legal-faq/), and the good news is that many lawyers believe that Tor exit node operators are in the same boat as the ISPs themselves. Become familiar with [the EFF's template letter regarding DMCA notices for Tor](/relay/community-resources/eff-tor-legal-faq/tor-dmca-response/), which is quite clear about not putting liability on service providers. The CDA is less clear, because it was written before the modern Internet emerged, but EFF and ACLU are optimistic. Of course, you need to understand that without actual clear precedent (and even then), it's still possible that a given judge will not interpret things the way the lawyers expect. diff --git a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr index 28ed6ba..e1cef75 100644 --- a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr @@ -85,7 +85,7 @@ To confirm your bridge is running with no issues, you should see something like ``` -### 6. To get the fastest package updates, switch from the "quarterly" package repo to the "latest" repo. +### 6. To get the fastest package updates, switch from the "quarterly" package repo to the "latest" repo. Create the following folder:

1 0

[translation/support-portal] https://gitweb.torproject.org/translation.git/commit/?h=support-portal
by translation＠torproject.org 15 Dec '20

15 Dec '20

commit 7dced007595515d9f35a754049e743743ec6b3dc Author: Translation commit bot <translation(a)torproject.org> Date: Tue Dec 15 22:18:12 2020 +0000 https://gitweb.torproject.org/translation.git/commit/?h=support-portal --- contents+ru.po | 50 ++++++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 42 insertions(+), 8 deletions(-) diff --git a/contents+ru.po b/contents+ru.po index 5013f8e2ca..f19c127bc7 100644 --- a/contents+ru.po +++ b/contents+ru.po @@ -8327,6 +8327,10 @@ msgid "" "support](https://community.torproject.org/relay/setup/bridge). In that case " "you should have at least 1 MBit/s of available bandwidth." msgstr "" +"Даже если у вас нет этих 10 Мбит/с, вы можете помочь сети Tor, если станете " +"поддерживать у себя [мост Tor с " +"obfs4](https://community.torproject.org/relay/setup/bridge). В этом случае " +"понадобится минимум 1 Мбит/с в обе стороны." #: https//support.torproject.org/operators/upgrade-or-move/ #: (content/operators/upgrade-or-move/contents+en.lrquestion.title) @@ -8612,7 +8616,7 @@ msgstr "" #: https//support.torproject.org/metrics/2011-archive/ #: (content/metrics/2011-archive/contents+en.lrquestion.title) msgid "Why are no numbers available before September 2011?" -msgstr "" +msgstr "Почему нет данных за период до сентября 2011 года?" #: https//support.torproject.org/metrics/2011-archive/ #: (content/metrics/2011-archive/contents+en.lrquestion.description) @@ -8620,17 +8624,22 @@ msgid "" "We do have descriptor archives from before that time, but those descriptors " "didn't contain all the data we use to estimate user numbers." msgstr "" +"У нас есть архивы до 2011 года, но в них нет достаточных данных, чтобы " +"оценить число пользователей." #: https//support.torproject.org/metrics/2011-archive/ #: (content/metrics/2011-archive/contents+en.lrquestion.description) msgid "Please find the following tarball for more details:" msgstr "" +"Если вам нужна более подробная информация, пожалуйста, загляните в этот " +"архив:" #: https//support.torproject.org/metrics/2011-archive/ #: (content/metrics/2011-archive/contents+en.lrquestion.description) msgid "" "[Tarball](https://archive.org/details/tor_metrics_old_user_number_estimates_…" msgstr "" +"[Tarball](https://archive.org/details/tor_metrics_old_user_number_estimates_…" #: https//support.torproject.org/metrics/bridge-users/ #: (content/metrics/bridge-users/contents+en.lrquestion.title) @@ -8638,6 +8647,8 @@ msgid "" "And what about the advantage of the current approach over the old one when " "it comes to bridge users?" msgstr "" +"В чем преимущество нового подхода над старым, когда речь идет о " +"пользователях мостов?" #: https//support.torproject.org/metrics/bridge-users/ #: (content/metrics/bridge-users/contents+en.lrquestion.description) @@ -8646,23 +8657,28 @@ msgid "" "report](https://research.torproject.org/techreports/counting-daily-bridge-" "users-2012-10-24.pdf) explaining the reasons for retiring the old approach." msgstr "" +"Это другая история. Мы написали 13-страничный [технический " +"отчет](https://research.torproject.org/techreports/counting-daily-bridge-" +"users-2012-10-24.pdf), в котором объясняется, почему мы отказались от " +"прежнего подхода." #: https//support.torproject.org/metrics/bridge-users/ #: (content/metrics/bridge-users/contents+en.lrquestion.description) msgid "" "tl;dr: in the old approach we measured the wrong thing, and now we measure " "the right thing." -msgstr "" +msgstr "tl;dr: раньше мы измеряли неправильные вещи, а сейчас правильные." #: https//support.torproject.org/metrics/bridges-reports/ #: (content/metrics/bridges-reports/contents+en.lrquestion.title) msgid "Why are there so few bridge users that are not using the default OR" msgstr "" +"Почему так мало пользователей мостов используют протокол OR по умолчанию" #: https//support.torproject.org/metrics/bridges-reports/ #: (content/metrics/bridges-reports/contents+en.lrquestion.title) msgid "protocol or that are using IPv6?" -msgstr "" +msgstr "или используют IPv6?" #: https//support.torproject.org/metrics/bridges-reports/ #: (content/metrics/bridges-reports/contents+en.lrquestion.description) @@ -8670,18 +8686,21 @@ msgid "" "Very few bridges report data on transports or IP versions yet, and by " "default we consider requests to use the default OR protocol and IPv4." msgstr "" +"Пока очень небольшое число мостов сообщает данные о транспортах или IP-" +"версиях. По умолчанию мы считаем, что используется протокол OR и IPv4." #: https//support.torproject.org/metrics/bridges-reports/ #: (content/metrics/bridges-reports/contents+en.lrquestion.description) msgid "" "Once more bridges report these data, the numbers will become more accurate." msgstr "" +"Чем больше мостов будет сообщать эти данные, тем аккуратнее будут значения." #: https//support.torproject.org/metrics/censorship-events/ #: (content/metrics/censorship-events/contents+en.lrquestion.title) msgid "" "What are these red and blue dots indicating possible censorship events?" -msgstr "" +msgstr "Что за красные и синие точки рядом с возможными инцидентами цензуры?" #: https//support.torproject.org/metrics/censorship-events/ #: (content/metrics/censorship-events/contents+en.lrquestion.description) @@ -8690,6 +8709,9 @@ msgid "" "user numbers over a series of days and predicts the user number in the next " "days." msgstr "" +"У нас есть система определения цензуры на основе выявления аномалий. Эта " +"система следит за числом пользователей на протяжении нескольких дней и " +"предсказывает, сколько их будет в следующие дни." #: https//support.torproject.org/metrics/censorship-events/ #: (content/metrics/censorship-events/contents+en.lrquestion.description) @@ -8697,6 +8719,8 @@ msgid "" "If the actual number is higher or lower, this might indicate a possible " "censorship event or release of censorship." msgstr "" +"Если реальное число оказывается больше или меньше, это может сигнализировать" +" об инциденте начале масштабной цензуры." #: https//support.torproject.org/metrics/censorship-events/ #: (content/metrics/censorship-events/contents+en.lrquestion.description) @@ -8704,6 +8728,8 @@ msgid "" "For more details, see our [technical " "report](https://research.torproject.org/techreports/detector-2011-09-09.pdf)." msgstr "" +"Подробности можно прочесть в нашем [техническом " +"отчете](https://research.torproject.org/techreports/detector-2011-09-09.pdf)." #: https//support.torproject.org/metrics/concurrent-users/ #: (content/metrics/concurrent-users/contents+en.lrquestion.title) @@ -8711,6 +8737,8 @@ msgid "" "So, are these distinct users per day, average number of users connected over" " the day, or what?" msgstr "" +"Получается, это точное число пользователей в день, среднее число " +"подключившихся... или что?" #: https//support.torproject.org/metrics/concurrent-users/ #: (content/metrics/concurrent-users/contents+en.lrquestion.description) @@ -8718,11 +8746,14 @@ msgid "" "Average number of concurrent users, estimated from data collected over a " "day. We can't say how many distinct users there are." msgstr "" +"Среднее число одновременно подключившихся пользователей. Рассчитывается из " +"данных, собранных в течение дня. Мы не можем делать утверждения о точном " +"числе пользователей." #: https//support.torproject.org/metrics/country-origin/ #: (content/metrics/country-origin/contents+en.lrquestion.title) msgid "How do you know which countries users come from?" -msgstr "" +msgstr "Откуда вы знаете, из каких стран приходят пользователи?" #: https//support.torproject.org/metrics/country-origin/ #: (content/metrics/country-origin/contents+en.lrquestion.description) @@ -8731,11 +8762,14 @@ msgid "" "numbers in aggregate form. This is one of the reasons why tor ships with a " "GeoIP database." msgstr "" +"В директориях IP-адреса сопоставляются с кодами стран. Эта информация " +"собирается в обобщенном виде. Одна из причин, по которой в комплект Tor " +"включена база GeoIP." #: https//support.torproject.org/metrics/directories-reports/ #: (content/metrics/directories-reports/contents+en.lrquestion.title) msgid "Do all directories report these directory request numbers?" -msgstr "Все папки сообщают количество запросов?" +msgstr "Все директории сообщают количество запросов?" #: https//support.torproject.org/metrics/directories-reports/ #: (content/metrics/directories-reports/contents+en.lrquestion.description) @@ -8743,8 +8777,8 @@ msgid "" "No, but we can see what fraction of directories reported them, and then we " "can extrapolate the total number in the network." msgstr "" -"Нет. Мы смотрим, какая часть папок сообщила данные, а потом экстраполируем и" -" оцениваем общий результат." +"Нет. Мы смотрим, какая часть директорий сообщила данные, а потом " +"экстраполируем и оцениваем общий результат." #: https//support.torproject.org/metrics/graph-data-point/ #: (content/metrics/graph-data-point/contents+en.lrquestion.title)

1 0

[translation/support-portal] https://gitweb.torproject.org/translation.git/commit/?h=support-portal
by translation＠torproject.org 15 Dec '20

15 Dec '20

commit 668f48e10d556c74f859254adca05554b202f81e Author: Translation commit bot <translation(a)torproject.org> Date: Tue Dec 15 21:48:08 2020 +0000 https://gitweb.torproject.org/translation.git/commit/?h=support-portal --- contents+ru.po | 28 ++++++++++++++++++++++++++-- 1 file changed, 26 insertions(+), 2 deletions(-) diff --git a/contents+ru.po b/contents+ru.po index 60c663e3be..5013f8e2ca 100644 --- a/contents+ru.po +++ b/contents+ru.po @@ -3711,6 +3711,9 @@ msgid "" "something went wrong with one of the previous steps, or you forgot that " "these commands use example file names and yours will be a little different." msgstr "" +"Если увидите сообщение об ошибке вроде \"Нет такого файла или папки\", " +"значит, что-то пошло не так на одном из предыдущих шагов. Другая причина: вы" +" использовали названия файлов из примеров (ваши реальные названия другие)." #: https//support.torproject.org/tbb/how-to-verify-signature/ #: (content/tbb/how-to-verify-signature/contents+en.lrquestion.description) @@ -4364,6 +4367,9 @@ msgid "" "(\"≡\")](../../glossary/hamburger-menu), then click on \"Preferences\", and " "finally on \"Tor\" in the side bar." msgstr "" +"Откройте Tor Browser, далее зайдите в меню через [кнопку с тремя полосками " +"(\"≡\")](../../glossary/hamburger-menu), затем \"Настройки\" и в левом " +"столбце пункт меню \"Tor\"." #: https//support.torproject.org/tbb/tbb-21/ #: (content/tbb/tbb-21/contents+en.lrquestion.description) @@ -4561,6 +4567,8 @@ msgid "" "Both options are located in the [hamburger menu (\"≡\")](../../glossary" "/hamburger-menu)." msgstr "" +"Обе опции доступны в меню [с тремя полосками (\"≡\")](../../glossary" +"/hamburger-menu)." #: https//support.torproject.org/tbb/tbb-29/ #: (content/tbb/tbb-29/contents+en.lrquestion.description) @@ -4789,6 +4797,8 @@ msgid "" "There are methods for setting Tor Browser as your default browser, but those" " methods may not work always or in every operating system." msgstr "" +"Есть способы сделать Tor Browser вашим браузером по умолчанию. Однако не все" +" эти методы работают в каждой операционной системе." #: https//support.torproject.org/tbb/tbb-32/ #: (content/tbb/tbb-32/contents+en.lrquestion.description) @@ -6150,6 +6160,9 @@ msgid "" "menu), then click on \"Preferences\", and finally on \"Tor\" in the side " "bar." msgstr "" +"Как вариант, если вы не видите эту опцию, а Tor Browser открыт, загляните в " +"меню по кнопке [с тремя полосками (\"≡\")](../../glossary/hamburger-menu), " +"затем выберите \"Настройки\", затем в левом столбце \"Tor\"." #: https//support.torproject.org/connecting/connecting-2/ #: (content/connecting/connecting-2/contents+en.lrquestion.description) @@ -6723,7 +6736,9 @@ msgstr "" msgid "" "#### This visualization shows what information is visible to eavesdroppers " "with and without Tor Browser and HTTPS encryption." -msgstr "#### Tor Browser и HTTPS" +msgstr "" +"#### На этой иллюстрации показано, какие данные видны злоумышленникам при " +"работе с/без Tor Browser и HTTPS." #: https//support.torproject.org/https/https-2/ #: (content/https/https-2/contents+en.lrquestion.title) @@ -6765,7 +6780,7 @@ msgstr "" #: https//support.torproject.org/operators/bandwidth-shaping/ #: (content/operators/bandwidth-shaping/contents+en.lrquestion.title) msgid "What bandwidth shaping options are available to Tor relays?" -msgstr "Какие можно ограничить полосу пропускания на узле Tor?" +msgstr "Как можно ограничить полосу пропускания на узле Tor?" #: https//support.torproject.org/operators/bandwidth-shaping/ #: (content/operators/bandwidth-shaping/contents+en.lrquestion.description) @@ -7132,6 +7147,11 @@ msgid "" "running an exit node with minimal " "harassment](https://blog.torproject.org/blog/tips-running-exit-node)." msgstr "" +"Если вы используете выходную политику по умолчанию, прочтите на нашем сайте " +"о [возможных проблемах](https://support.torproject.org/abuse/exit-relay-" +"expectations/). Мы также рекомендуем советы Майка Перри (Mike Perry) о том, " +"[как поддерживать выходной узел с минимальными " +"рисками](https://blog.torproject.org/blog/tips-running-exit-node)." #: https//support.torproject.org/operators/exit-policies/ #: (content/operators/exit-policies/contents+en.lrquestion.description) @@ -8294,6 +8314,10 @@ msgid "" " please consider [running a Tor " "relay](https://community.torproject.org/relay/)." msgstr "" +"Мы ищем людей с относительно стабильным интернетом, готовых поделиться как " +"минимум 10 Mбитi/с в обе стороны. Если это вы, пожалуйста, подумайте о том, " +"чтобы [поддерживать у себя узел " +"Tor](https://community.torproject.org/relay/)." #: https//support.torproject.org/operators/should-i-run-a-relay/ #: (content/operators/should-i-run-a-relay/contents+en.lrquestion.description)

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits December 2020