1 # SOME DESCRIPTIVE TITLE
2 # Copyright (C) YEAR Free Software Foundation, Inc.
3 # This file is distributed under the same license as the PACKAGE package.
4 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
8 "Project-Id-Version: PACKAGE VERSION\n"
9 "POT-Creation-Date: 2014-05-27 15:17+0300\n"
10 "PO-Revision-Date: 2014-06-14 21:11-0000\n"
11 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
12 "Language-Team: LANGUAGE <LL@li.org>\n"
15 "Content-Type: text/plain; charset=UTF-8\n"
16 "Content-Transfer-Encoding: 8bit\n"
20 msgid "[[!meta title=\"Warning\"]]\n"
21 msgstr "[[!meta title=\"Warnung\"]]\n"
25 "Even though we're doing our best to offer you good tools to protect your "
26 "privacy while using a computer, **there is no magic or perfect solution to "
27 "such a complex problem**. Understanding well the limits of such tools is a "
28 "crucial step in, first, deciding whether Tails is the right tool for you, "
29 "and second, helping you making a good use of it."
31 "Obwohl wir unser Bestes geben, um Ihnen gute Werkzeuge anzubieten, die Ihre "
32 "Privatsphäre während der Benutzung eines Computers schützen, **gibt es keine "
33 "Magie und keine perfekte Lösung zu einem solch komplexen Problem**. Die "
34 "Grenzen dieser Werkzeuge zu verstehen, ist ein sehr wichtiger Schritt, um "
35 "erstens zu entscheiden, ob Tails das Richtige für Sie ist, und zweitens "
36 "hilft es Ihnen Tails sinnvoll einzusetzen."
40 msgid "[[!toc levels=2]]\n"
45 msgid "<a id=\"exit_node\"></a>\n"
50 msgid "Tor exit nodes can eavesdrop on communications\n"
51 msgstr "Tor Austritts-Knoten können Verbindungen abhören\n"
55 msgid "**Tor is about hiding your location, not about encrypting your communication.**\n"
56 msgstr "**Tor soll deinen Aufenthaltsort verbergen, nicht deine Verbindung verschlüsseln.**\n"
60 "Instead of taking a direct route from source to destination, communications "
61 "using the Tor network take a random pathway through several Tor relays that "
62 "cover your tracks. So no observer at any single point can tell where the "
63 "data came from or where it's going."
65 "Anstatt einen direkten Weg vom Ausgangspunkt zum Ziel zu nehmen, verlaufen "
66 "Verbindungen über das Tor-Netzwerk auf einem zufälligen Weg über mehrere Tor-"
67 "Relais, sodass kein Beobachter an irgendeinem Ort sagen kann, wo die Daten "
68 "herkamen oder wohin sie übertragen werden."
72 msgid "[[!img htw2-tails.png link=no alt=\"A Tor connection usually goes through 3 relays with the last one establishing the actual connection to the final destination\"]]\n"
77 "The last relay on this circuit, called the exit node, is the one that "
78 "establishes the actual connection to the destination server. As Tor does "
79 "not, and by design cannot, encrypt the traffic between an exit node and the "
80 "destination server, **any exit node is in a position to capture any traffic "
81 "passing through it**. See [Tor FAQ: Can exit nodes eavesdrop on "
82 "communications?](https://trac.torproject.org/projects/tor/wiki/"
83 "TheOnionRouter/TorFAQ#CanexitnodeseavesdroponcommunicationsIsntthatbad)."
88 "For example, in 2007, a security researcher intercepted thousands of private "
89 "e-mail messages sent by foreign embassies and human rights groups around the "
90 "world by spying on the connections coming out of an exit node he was "
91 "running. See [Wired: Rogue Nodes Turn Tor Anonymizer Into Eavesdropper's "
92 "Paradise.](http://www.wired.com/politics/security/news/2007/09/"
98 msgid "**To protect yourself from such attacks you should use end-to-end encryption.**\n"
104 "**Tails includes many tools to help you using strong encryption** while\n"
105 "browsing, sending email or chatting, as presented on our [[about\n"
106 "page|/about#cryptography]].\n"
111 msgid "<a id=\"fingerprint\"></a>\n"
116 msgid "Tails makes it clear that you are using Tor and probably Tails\n"
122 "**Your Internet Service Provider (ISP) or your local network administrator**\n"
123 "can see that you're connecting to a Tor relay, and not a normal web server for\n"
124 "example. Using [[Tor bridges in certain\n"
125 "conditions|first_steps/startup_options/bridge_mode]] can help you hide the fact\n"
126 "that you are using Tor.\n"
132 "**The destination server that you are contacting through Tor** can know whether your\n"
133 "communication comes out from a Tor exit node by consulting the publicly\n"
134 "available list of exit nodes that might contact it. For example using the [Tor\n"
135 "Bulk Exit List tool](https://check.torproject.org/cgi-bin/TorBulkExitList.py) of\n"
142 "**So using Tails doesn't make you look like any random Internet user.**\n"
143 "The anonymity provided by Tor and Tails works by trying to make all of their\n"
144 "users look the same so it's not possible to identify who is who amongst them.\n"
148 msgid "See also [[Can I hide the fact that I am using Tails?|fingerprint]]"
153 msgid "<a id=\"man-in-the-middle\"></a>\n"
158 msgid "Man-in-the-middle attacks\n"
163 "A man-in-the-middle attack (MitM) is a form of active eavesdropping in which "
164 "the attacker makes independent connections with the victims and relays "
165 "messages between them, making them believe that they are talking directly to "
166 "each other over a private connection, when in fact the entire conversation "
167 "is controlled by the attacker."
172 msgid "[[!img man-in-the-middle.png link=no alt=\"Illustration of a man-in-the-middle attack\"]]\n"
177 msgid "<!-- Source: wiki/lib/man-in-the-middle.svg -->\n"
182 "While using Tor, man-in-the-middle attacks can still happen between the exit "
183 "node and the destination server. The exit node itself can also act as a man-"
184 "in-the-middle. For an example of such an attack see [MW-Blog: TOR exit-node "
185 "doing MITM attacks](http://www.teamfurry.com/wordpress/2007/11/20/tor-exit-"
186 "node-doing-mitm-attacks)."
192 "**Again, to protect yourself from such attacks you should use end-to-end\n"
193 "encryption** and while doing so taking extra care at verifying the server\n"
200 "Usually, this is automatically done throught SSL certificates checked by your\n"
201 "browser against a given set of recognized [[!wikipedia\n"
202 "Certificate_authority desc=\"certificate authorities\"]]).\n"
203 "If you get a security exception message such as this one you might be victim of\n"
204 "a man-in-the-middle attack and should not bypass it unless you have another\n"
205 "trusted way of checking the certificate's fingerprint with the people running\n"
211 msgid "[[!img ssl_warning.png link=no alt=\"This Connection is Untrusted\"]]\n"
216 "But on top of that the certificate authorities model of trust on Internet is "
217 "susceptible to various methods of compromise."
222 "For example, on March 15, 2011, Comodo, one of the major SSL certificates "
223 "company, reported that a user account with an affiliate registration "
224 "authority had been compromised. It was then used to create a new user "
225 "account that issued nine certificate signing requests for seven domains: "
226 "mail.google.com, login.live.com, www.google.com, login.yahoo.com (three "
227 "certificates), login.skype.com, addons.mozilla.org, and global trustee. See "
228 "[Comodo: The Recent RA Compromise](http://blogs.comodo.com/it-security/data-"
229 "security/the-recent-ra-compromise/)."
234 "Later in 2011, DigiNotar, a Dutch SSL certificate company, incorrectly "
235 "issued certificates to a malicious party or parties. Later on, it came to "
236 "light that they were apparently compromised months before or perhaps even in "
237 "May of 2009 if not earlier. Rogues certificates were issued for domains such "
238 "as google.com, mozilla.org, torproject.org, login.yahoo.com and many more. "
239 "See, [The Tor Project: The DigiNotar Debacle, and what you should do about "
240 "it](https://blog.torproject.org/blog/diginotar-debacle-and-what-you-should-"
247 "**This still leaves open the possibility of a man-in-the-middle attack even when\n"
248 "your browser is trusting an HTTPS connection.**\n"
253 "On one hand, by providing anonymity, Tor makes it more difficult to perform "
254 "a man-in-the-middle attack targeted at **one specific person** with the "
255 "blessing of a rogue SSL certificate. But on the other end, Tor makes it "
256 "easier for people or organizations running exit nodes to perform large scale "
257 "MitM attempts, or attacks targeted at **a specific server**, and especially "
258 "those among its users who happen to use Tor."
264 "<p class=\"quoted-from\">Quoted from [[!wikipedia Man-in-the-middle_attack\n"
265 "desc=\"Wikipedia: %s\"]], [[!wikipedia\n"
266 "Comodo_Group#Iran_SSL_certificate_controversy desc=\"Wikipedia: %s\"]] and <a\n"
267 "href=\"https://blog.torproject.org/blog/detecting-certificate-authority-compromises-and-web-browser-collusion\">Tor\n"
268 "Project: Detecting Certificate Authority compromises and web browser\n"
269 "collusion</a>.</p>\n"
274 msgid "Confirmation attacks\n"
279 "The Tor design doesn't try to protect against an attacker who can see or "
280 "measure both traffic going into the Tor network and also traffic coming out "
281 "of the Tor network. That's because if you can see both flows, some simple "
282 "statistics let you decide whether they match up."
287 "That could also be the case if your ISP (or your local network "
288 "administrator) and the ISP of the destination server (or the destination "
289 "server itself) cooperate to attack you."
294 "Tor tries to protect against traffic analysis, where an attacker tries to "
295 "learn whom to investigate, but Tor can't protect against traffic "
296 "confirmation (also known as end-to-end correlation), where an attacker tries "
297 "to confirm an hypothesis by monitoring the right locations in the network "
298 "and then doing the math."
304 "<p class=\"quoted-from\">Quoted from <a\n"
305 "href=\"https://blog.torproject.org/blog/one-cell-enough\">Tor Project: \"One cell\n"
306 "is enough to break Tor's anonymity\"</a>.</p>\n"
311 msgid "Tails doesn't encrypt your documents by default\n"
316 "The documents that you might save on storage devices will not be encrypted "
317 "by default. But Tails provides you with tools to encrypt your documents, "
318 "such as GnuPG, or encrypt your storage device, such as LUKS. It is likely "
319 "that the files you may create will keep tracks that they were created using "
326 "**If you need to access the local hard-disks** of the computer you are using, be\n"
327 "conscious that you might then leave trace of your activities with Tails on it.\n"
333 "Tails doesn't clear the metadata of your documents for you and doesn't encrypt the Subject: and other headers of your encrypted e-mail messages\n"
334 "===========================================================================================\n"
339 "Numerous files format store hidden data or metadata inside of the files. "
340 "Text processors or PDF files could store the name of the author, the date "
341 "and time of creation of the file, and sometimes even parts of the editing "
342 "history of the file… those hidden data depend on the file format and the "
343 "software used. Please note also, that the Subject: as well as the rest of "
344 "the header lines of your OpenPGP encrypted e-mail messages are not "
345 "encrypted. This is not a bug of Tails or the [OpenPGP](http://www.mozilla-"
346 "enigmail.org/forum/viewtopic.php?f=3&t=328) protocol; it's for backwards "
347 "compatibility with the original SMTP protocol. Unfortunately no RFC standard "
348 "exists yet for Subject encryption."
353 "Images file formats, like TIFF of JPEG, probably take the prize in this "
354 "field. Those files, created by digital cameras or mobile phones, contain a "
355 "metadata format called EXIF which can include the date, time and sometimes "
356 "the GPS coordinates of the picture, the brand and serial number of the "
357 "device which took it as well as a thumbnail of the original image. Image "
358 "processing software tend to keep those data intact. Internet is full of "
359 "cropped or blurred images for which the EXIF thumbnail still contains the "
360 "full original picture."
366 "**Tails doesn't clear the metadata of your files for you**. Yet. Still it's in\n"
367 "Tails' design goal to help you do that. For example, Tails already comes with\n"
368 "the [Metadata anonymisation toolkit](https://mat.boum.org/).\n"
373 msgid "Tor doesn't protect you from a global adversary\n"
378 "A global passive adversary would be a person or an entity able to monitor at "
379 "the same time the traffic between all the computers in a network. By "
380 "studying, for example, the timing and volume patterns of the different "
381 "communications across the network, it would be statistically possible to "
382 "identify Tor circuits and thus matching Tor users and destination servers."
387 "It is part of Tor's initial trade-off not to address such a threat in order "
388 "to create a low-latency communication service usable for web browsing, "
389 "Internet chat or SSH connections."
394 "For more expert information see [Tor Project: The Second-Generation Onion "
395 "Router](https://svn.torproject.org/svn/projects/design-paper/tor-design."
396 "pdf), part 3. Design goals and assumptions."
401 msgid "<a id=\"identities\"></a>\n"
406 msgid "Tails doesn't magically separate your different contextual identities\n"
411 "It is usually not advisable to use the same Tails session to perform two "
412 "tasks or endorse two contextual identities that you really want to keep "
413 "separate from another. For example hiding your location to check your email "
414 "and publishing anonymously a document."
419 "First, because Tor tends to reuse the same circuits, for example amongst a "
420 "same browsing session. Since the exit node of a circuit knows both the "
421 "destination server (and possibly the content of the communication if not "
422 "encrypted) and the address of the previous relay it received the "
423 "communication from, it makes it easier to correlate the several browsing "
424 "requests as part of a same circuit and possibly made by a same user. If you "
425 "are facing a global adversary as described above, it might then also be in "
426 "position to do this correlation."
431 "Second, in case of a security hole or a misuse in using Tails or one of its "
432 "application, information about your session could be leaked. That could "
433 "reveal that the same person was behind the various actions made during the "
440 "**The solution to both threats is to shutdown and restart Tails** every time\n"
441 "you're using a new identity, if you really want to isolate them better.\n"
446 "Vidalia's \"New Identity\" button forces Tor to use new circuits but only "
447 "for new connections: existing connections might stay open. Plus, apart from "
448 "the Tor circuits, other kind of information can reveal your past activities, "
449 "for example the cookies stored by your browser. So this feature of Vidalia "
450 "is not a solution to really separate contextual identities. Shutdown and "
451 "restart Tails instead."
456 msgid "Tails doesn't make your crappy passwords stronger\n"
461 "Tor allows you to be anonymous online; Tails allows you to leave no trace on "
462 "the computer you're using. But again, **neither of both are magic spells for "
463 "computer security**."
469 "If you use weak passwords, they can be guessed by brute-force attacks with or\n"
470 "without Tails in the same way. To know if your passwords are weak and learn good\n"
471 "practices to create better password, you can read [[!wikipedia\n"
472 "Weak_password#Examples_of_weak_passwords desc=\"Wikipedia: Weak Passwords\"]].\n"
477 msgid "Tails is a work in progress\n"
482 "Tails, as well as all the software it includes, are on continuous "
483 "development and might contain programming errors or security holes. [[Stay "
484 "tuned|download#stay_tuned]] to Tails development."