@@ -45,7 +45,7 @@ You picked your project, you're ready to go, now, what do you do?
Now would be the right time to create an account on the [bug tracker](labs.riseup.net/code/projects/tails) so you can update the ticket and assign it to yourself.
Sent an e-mail to the [tails-dev](https://mailman.boum.org/listinfo/tails-dev/) mailing list with who you are, what you're going to work on. This is also the best medium to ask questions when you're stuck or to start discussions.
Sent an email to the [tails-dev](https://mailman.boum.org/listinfo/tails-dev/) mailing list with who you are, what you're going to work on. This is also the best medium to ask questions when you're stuck or to start discussions.
Here's an handy link with a start on how to start [hacking on Tails](https://tails.boum.org/contribute/how/code/#index6h1).
"For example, in 2007, a security researcher intercepted thousands of private e-mail messages sent by foreign embassies and human rights groups around the world by spying on the connections coming out of an exit node he was running. See [Wired: Rogue Nodes Turn Tor Anonymizer Into Eavesdropper's Paradise](http://archive.wired.com/politics/security/news/2007/09/"
"For example, in 2007, a security researcher intercepted thousands of private email messages sent by foreign embassies and human rights groups around the world by spying on the connections coming out of an exit node he was running. See [Wired: Rogue Nodes Turn Tor Anonymizer Into Eavesdropper's Paradise](http://archive.wired.com/politics/security/news/2007/09/"
"embassy_hacks)."
msgstr ""
"Beispielsweise hat ein Sicherheitsforscher im Jahr 2007 weltweit tausende private E-Mails zwischen ausländischen Botschaften und Menschenrechtsgruppen abgehört, indem er die aus von ihm betriebenen Ausgangsrelais ausgehenden Verbindungen überwacht hat. Siehe [Wired: Rogue Nodes Turn Tor Anonymizer Into Eavesdropper's Paradise](http://archive.wired.com/politics/"
...
...
@@ -372,7 +372,7 @@ msgstr ""
#. type: Plain text
#, no-wrap
msgid ""
"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"
"Tails doesn't clear the metadata of your documents for you and doesn't encrypt the Subject: and other headers of your encrypted email messages\n"
"Tails bereinigt Ihre Dokumente nicht von Metadaten und verschlüsselt weder die Betreffzeile noch andere Header-Zeilen Ihrer verschlüsselten E-Mails\n"
...
...
@@ -386,7 +386,7 @@ msgstr ""
#. type: Plain text
msgid ""
"Please note also, that the Subject: as well as the rest of the header lines of your OpenPGP encrypted e-mail messages are not encrypted. This is not a bug of Tails or the [OpenPGP](http://www.mozilla-enigmail.org/forum/viewtopic.php?f=3&t=328) protocol; it's due to backwards compatibility with the original SMTP protocol. Unfortunately no RFC standard exists yet "
"Please note also, that the Subject: as well as the rest of the header lines of your OpenPGP encrypted email messages are not encrypted. This is not a bug of Tails or the [OpenPGP](http://www.mozilla-enigmail.org/forum/viewtopic.php?f=3&t=328) protocol; it's due to backwards compatibility with the original SMTP protocol. Unfortunately no RFC standard exists yet "
"for Subject: line encryption."
msgstr ""
"Bitte beachten Sie auch, dass die Betreffzeile und die anderen Header-Zeilen in einer OpenPGP-verschlüsselten E-Mail nicht verschlüsselt sind. Das ist kein Fehler in Tails oder dem [OpenPGP](http://www.mozilla-enigmail.org/forum/viewtopic.php?f=3&t=328) Protokoll; es ist ein Ergebnis der Abwärtskompatibilität mit dem ursprünglichen SMTP Protokoll. Leider "
#| "For example, in 2007, a security researcher intercepted thousands of private e-mail messages sent by foreign embassies and human rights groups around the world by spying on the connections coming out of an exit node he was running. See [Wired: Rogue Nodes Turn Tor Anonymizer Into Eavesdropper's Paradise]"
#| "For example, in 2007, a security researcher intercepted thousands of private email messages sent by foreign embassies and human rights groups around the world by spying on the connections coming out of an exit node he was running. See [Wired: Rogue Nodes Turn Tor Anonymizer Into Eavesdropper's Paradise]"
"For example, in 2007, a security researcher intercepted thousands of private e-mail messages sent by foreign embassies and human rights groups around the world by spying on the connections coming out of an exit node he was running. See [Wired: Rogue Nodes Turn Tor Anonymizer Into Eavesdropper's Paradise]"
"For example, in 2007, a security researcher intercepted thousands of private email messages sent by foreign embassies and human rights groups around the world by spying on the connections coming out of an exit node he was running. See [Wired: Rogue Nodes Turn Tor Anonymizer Into Eavesdropper's Paradise]"
"Per esempio, nel 2007, un ricercatore in ambito della sicurezza ha intercettato migliaia di messaggi e-mail privati inviati da ambasciate straniere e gruppi sui diritti umani in giro per il mondo spiando le connessioni che arrivavano fuori dal nodo di uscita che stava facendo girare sul proprio server. Guarda "
...
...
@@ -405,7 +405,7 @@ msgstr ""
#. type: Plain text
#, no-wrap
msgid ""
"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"
"Tails doesn't clear the metadata of your documents for you and doesn't encrypt the Subject: and other headers of your encrypted email messages\n"
"Tails non cancella i metadati dei tuoi documenti per te e non cifra l'Oggetto e le altre intestazioni dei tuoi messaggi crittografati\n"
...
...
@@ -417,7 +417,7 @@ msgstr "Numerosi formati di file nascondono dati o metadati nascosti dentro al f
#. type: Plain text
msgid ""
"Please note also, that the Subject: as well as the rest of the header lines of your OpenPGP encrypted e-mail messages are not encrypted. This is not a bug of Tails or the [OpenPGP](http://www.mozilla-enigmail.org/forum/viewtopic.php?f=3&t=328) protocol; it's due to backwards compatibility with the original SMTP "
"Please note also, that the Subject: as well as the rest of the header lines of your OpenPGP encrypted email messages are not encrypted. This is not a bug of Tails or the [OpenPGP](http://www.mozilla-enigmail.org/forum/viewtopic.php?f=3&t=328) protocol; it's due to backwards compatibility with the original SMTP "
"protocol. Unfortunately no RFC standard exists yet for Subject: line encryption."
msgstr ""
"Si segnala inoltre, che l' Oggetto: così come il resto delle linee delle tue intestazioni e-mail crittografate con OpenPGP non sono cifrate. Questo non è un baco di Tails o del protocollo [OpenPGP](http://www.mozilla-enigmail.org/forum/viewtopic.php?f=3&t=328); questo dipende dalla compatibilità con il "
"Tails não limpa os metadados dos seus documentos para você e não criptografa o Assunto: e outros cabeçalhos das suas mensagens de email criptografadas\n"
...
...
@@ -595,14 +595,14 @@ msgstr ""
#| "and time of creation of the file, and sometimes even parts of the editing "
#| "history of the file… those hidden data depend on the file format and the "
#| "software used. Please note also, that the Subject: as well as the rest of "
#| "the header lines of your OpenPGP encrypted e-mail messages are not "
#| "the header lines of your OpenPGP encrypted email messages are not "
#| "encrypted. This is not a bug of Tails or the [OpenPGP](http://www.mozilla-"
#| "enigmail.org/forum/viewtopic.php?f=3&t=328) protocol; it's for backwards "
#| "compatibility with the original SMTP protocol. Unfortunately no RFC "
#| "standard exists yet for Subject encryption."
msgid ""
"Please note also, that the Subject: as well as the rest of the header lines "
"of your OpenPGP encrypted e-mail messages are not encrypted. This is not a "
"of your OpenPGP encrypted email messages are not encrypted. This is not a "
"bug of Tails or the [OpenPGP](http://www.mozilla-enigmail.org/forum/"
"viewtopic.php?f=3&t=328) protocol; it's due to backwards compatibility with "
"the original SMTP protocol. Unfortunately no RFC standard exists yet for "