[tor-commits] [translation/communitytpo-contentspot] new translations in communitytpo-contentspot
translation at torproject.org
translation at torproject.org
Sun Dec 5 11:15:15 UTC 2021
commit dbb22081a5c6f615aac9dc220c6aad9fb93081f0
Author: Translation commit bot <translation at torproject.org>
Date: Sun Dec 5 11:15:15 2021 +0000
new translations in communitytpo-contentspot
---
contents+de.po | 58 ++++++++++++++++++++++++++++++++++++++++++++++++++++++----
1 file changed, 54 insertions(+), 4 deletions(-)
diff --git a/contents+de.po b/contents+de.po
index 969dad7bcf..933fc4d984 100644
--- a/contents+de.po
+++ b/contents+de.po
@@ -9832,7 +9832,7 @@ msgid ""
"challenges-opportunities), and how we're working on onion services usability"
" and adoption."
msgstr ""
-"Wir haben über [Sicherheitserwartungen an den Tor-"
+"Wir haben über [Sicherheitserwartungen an Tor "
"Browser](https://blog.torproject.org/tor-brower-onion-services-challenges-"
"opportunities) geschrieben und darüber, wie wir an der "
"Benutzerfreundlichkeit und Akzeptanz von Onion-Diensten arbeiten."
@@ -9842,6 +9842,8 @@ msgstr ""
msgid ""
"There are some alternatives you might want to try to address this problem:"
msgstr ""
+"Es gibt einige Alternativen, die du ausprobieren könntest, um dieses Problem"
+" zu lösen:"
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9849,6 +9851,9 @@ msgid ""
"* To avoid using an HTTPS certificate for your onion, the easiest answer is "
"to write all your content so it uses only relative links."
msgstr ""
+"* Um die Verwendung eines HTTPS-Zertifikats für dein Onion zu vermeiden, ist"
+" es am einfachsten, deinen gesamten Inhalt so zu schreiben, dass er nur "
+"relative Links verwendet."
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9856,6 +9861,8 @@ msgid ""
"This way the content will work smoothly, independently of what website name "
"it's being served from."
msgstr ""
+"Auf diese Weise funktioniert der Inhalt reibungslos, unabhängig davon, von "
+"welchem Website-Namen er abgerufen wird."
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9863,6 +9870,8 @@ msgid ""
"* Another option is to use webserver rules to rewrite absolute links on the "
"fly."
msgstr ""
+"* Eine andere Möglichkeit ist die Verwendung von Webserver-Regeln, um "
+"absolute Links im laufenden Betrieb umzuschreiben."
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9870,6 +9879,8 @@ msgid ""
"* Or use a reverse proxy in the middle (more specifically EOTK with an HTTPS"
" certificate)."
msgstr ""
+"* Oder verwende einen Reverse-Proxy in der Mitte (genauer gesagt EOTK mit "
+"einem HTTPS-Zertifikat)."
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9878,6 +9889,9 @@ msgid ""
"infrastructures use SSL as a technical requirement; they won't work if they "
"don't see an \"https://\" link."
msgstr ""
+"5. In Verbindung mit dem vorherigen Punkt verwenden einige Protokolle, "
+"Frameworks und Infrastrukturen SSL als technische Voraussetzung; sie "
+"funktionieren nicht, wenn sie keinen \"https://\"-Link sehen."
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9885,11 +9899,13 @@ msgid ""
"In that case, your onion service will need to use an HTTPS certificate in "
"order to function."
msgstr ""
+"In diesem Fall muss dein Onion-Dienst ein HTTPS-Zertifikat verwenden, um zu "
+"funktionieren."
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
msgid "6. Actually HTTPS does give you a little bit more than onion services."
-msgstr ""
+msgstr "6. Tatsächlich bietet HTTPS ein wenig mehr als die Onion-Dienste."
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9898,6 +9914,10 @@ msgid ""
"the Tor program, you would need to use an HTTPS certificate to avoid "
"exposing unencrypted traffic to the network in between the two."
msgstr ""
+"Wenn sich zum Beispiel der Webserver nicht am selben Ort wie das Tor-"
+"Programm befindet, musst du ein HTTPS-Zertifikat verwenden, um zu "
+"verhindern, dass unverschlüsselter Datenverkehr in das dazwischen liegende "
+"Netzwerk gelangt."
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9905,11 +9925,13 @@ msgid ""
"Remember that there's no requirement for the webserver and the Tor process "
"to be on the same machine."
msgstr ""
+"Vergiss nicht, dass der Webserver und der Tor-Prozess nicht auf dem gleichen"
+" Rechner laufen müssen."
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
msgid "### What's next"
-msgstr ""
+msgstr "### Wie geht es weiter?"
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9921,6 +9943,12 @@ msgid ""
"Validation (DV) and Organization Validation (OV) certificates containing Tor"
" onion addresses."
msgstr ""
+"Kürzlich, im Jahr 2020, stimmte das Certificate Authority/Browser Forum ab "
+"und [genehmigte Version 3 der Onion-"
+"Zertifikate](https://archive.cabforum.org/pipermail/servercert-"
+"wg/2020-February/001637.html), so dass CAs nun Domain Validation (DV) und "
+"Organization Validation (OV) Zertifikate ausstellen dürfen, die Tor-Onion-"
+"Adressen enthalten."
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9928,6 +9956,8 @@ msgid ""
"In the nearby future, we hope that [Let's Encrypt](https://letsencrypt.org/)"
" CA can start issuing v3 onion certificates for free."
msgstr ""
+"Wir hoffen, dass die [Let's Encrypt](https://letsencrypt.org/) CA in naher "
+"Zukunft damit beginnen kann, v3-Onion-Zertifikate kostenlos auszustellen."
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9936,11 +9966,14 @@ msgid ""
"service deprecation](https://blog.torproject.org/v2-deprecation-timeline) "
"will happen between July - October 2021."
msgstr ""
+"Wenn du ein HTTPS-Zertifikat kaufen willst, solltest du wissen, dass "
+"zwischen Juli und Oktober 2021 [v2 Onion-Dienste abgelöst "
+"werden](https://blog.torproject.org/v2-deprecation-timeline)."
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
msgid "### Read more"
-msgstr ""
+msgstr "### Mehr dazu erfährst du hier"
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9948,6 +9981,9 @@ msgid ""
"* For a detailed step by step how to create an HTTPS onion certificate, "
"check [Brave's blog post](https://brave.com/new-onion-service/)."
msgstr ""
+"* Eine ausführliche Schritt-für-Schritt-Anleitung zur Erstellung eines "
+"HTTPS-Onion-Zertifikats findest du in [Brave's blog post](https://brave.com"
+"/new-onion-service/)."
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9956,6 +9992,9 @@ msgid ""
"(2020)](https://blog.torproject.org/tor-brower-onion-services-challenges-"
"opportunities)"
msgstr ""
+"* [Tor-Browser und Onion-Dienste - Herausforderungen und Möglichkeiten "
+"(2020)](https://blog.torproject.org/tor-brower-onion-services-challenges-"
+"opportunities)"
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9964,6 +10003,9 @@ msgid ""
"(2014)](https://blog.torproject.org/facebook-hidden-services-and-https-"
"certs)"
msgstr ""
+"* [Facebook, versteckte Dienste und https-Zertifikate "
+"(2014)](https://blog.torproject.org/facebook-hidden-services-and-https-"
+"certs)"
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9972,6 +10014,9 @@ msgid ""
"onion site (2015)](https://www.digicert.com/blog/onion-officially-"
"recognized-special-use-domain/)"
msgstr ""
+"* [DigiCert: Holen Sie sich ein TLS-Zertifikat mit Extended Validation (EV) "
+"für Ihre Onion-Site (2015)](https://www.digicert.com/blog/onion-officially-"
+"recognized-special-use-domain/)"
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9979,6 +10024,9 @@ msgid ""
"* [HARICA: Get a TLS certificate with Domain Validation (DV) for your onion "
"site (2021)](https://blog.torproject.org/tls-certificate-for-onion-site)"
msgstr ""
+"* [HARICA: Holen Sie sich ein TLS-Zertifikat mit Domain Validation (DV) für "
+"Ihre Onion-Site (2021)](https://blog.torproject.org/tls-certificate-for-"
+"onion-site)"
#: https//community.torproject.org/onion-services/advanced/https/
#: (content/onion-services/advanced/https/contents+en.lrpage.body)
@@ -9986,6 +10034,8 @@ msgid ""
"* [The \".onion\" Special-Use Domain Name - IETF RFC "
"7686](https://tools.ietf.org/html/rfc7686)"
msgstr ""
+"* [Der \".onion\"-Domänenname für besondere Zwecke - IETF RFC "
+"7686](https://tools.ietf.org/html/rfc7686)"
#: https//community.torproject.org/onion-services/advanced/opsec/
#: (content/onion-services/advanced/opsec/contents+en.lrpage.subtitle)
More information about the tor-commits
mailing list