- tor-commits - lists.torproject.org

[translation/bridgedb_completed] Update translations for bridgedb_completed
by translation＠torproject.org 23 Aug '12

23 Aug '12

commit 22a482147a2e857154f98aa7509ac15738d2fa70 Author: Translation commit bot <translation(a)torproject.org> Date: Thu Aug 23 09:45:04 2012 +0000 Update translations for bridgedb_completed --- pl/bridgedb.po | 73 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 73 insertions(+), 0 deletions(-) diff --git a/pl/bridgedb.po b/pl/bridgedb.po new file mode 100644 index 0000000..f0d1ed2 --- /dev/null +++ b/pl/bridgedb.po @@ -0,0 +1,73 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER +# This file is distributed under the same license as the PACKAGE package. +# +# Translators: +# <ayurveda63(a)gmail.com>, 2012. +msgid "" +msgstr "" +"Project-Id-Version: The Tor Project\n" +"Report-Msgid-Bugs-To: https://trac.torproject.org/projects/tor\n" +"POT-Creation-Date: 2011-01-01 07:48-0800\n" +"PO-Revision-Date: 2012-08-23 09:17+0000\n" +"Last-Translator: JerBen <ayurveda63(a)gmail.com>\n" +"Language-Team: LANGUAGE <LL(a)li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: pl\n" +"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2)\n" + +#: lib/bridgedb/I18n.py:21 +msgid "Here are your bridge relays: " +msgstr "To są twoje przekaźniki mostowe." + +#: lib/bridgedb/I18n.py:23 +msgid "" +"Bridge relays (or \"bridges\" for short) are Tor relays that aren't listed\n" +"in the main directory. Since there is no complete public list of them,\n" +"even if your ISP is filtering connections to all the known Tor relays,\n" +"they probably won't be able to block all the bridges." +msgstr "Przekaźniki mostowe \"Tor bridges\" (lub \"mosty\" w skrócie) są przekaźnikami Tora, które NIE SĄ wyszczególnione w katalogu głównym. Z racji, iż nie ma pełnej, publicznej listy mostów, nawet jeżeli twój dostawca usług internetowych ISP filtruję połączenia z częścią widocznych mostów Tora, najprawdopodobniej nie będzie on w stanie wyszukać i zablokować wszystkich." + +#: lib/bridgedb/I18n.py:28 +msgid "" +"To use the above lines, go to Vidalia's Network settings page, and click\n" +"\"My ISP blocks connections to the Tor network\". Then add each bridge\n" +"address one at a time." +msgstr "By użyć powyższych mostów, wejdź do zakładki Ustawienia sieciowe w Vidalii, naciśnij opcję \"mój dostawca usług internetowych ISP blokuje połączenia z siecią Tor\". Następnie dodaj każdy adres mostu pojedynczo. " + +#: lib/bridgedb/I18n.py:32 +msgid "" +"Configuring more than one bridge address will make your Tor connection\n" +"more stable, in case some of the bridges become unreachable." +msgstr "Skonfigurowanie więcej niż jednego adresu mostu, sprawi iż połączenie z siecią Tor będzie stabilniejsze w wypadku gdy jeden z mostów stanie się niedostępny." + +#: lib/bridgedb/I18n.py:35 +msgid "" +"Another way to find public bridge addresses is to send mail to\n" +"bridges(a)torproject.org with the line \"get bridges\" by itself in the body\n" +"of the mail. However, so we can make it harder for an attacker to learn\n" +"lots of bridge addresses, you must send this request from an email address at\n" +"one of the following domains:" +msgstr "Kolejnym sposobem na znalezienie publicznych adresów mostów jest wysłanie maila na bridges(a)torproject.org z samym dopiskiem \"get bridges\" w treści maila. By utrudnić atakującym dostęp do dużej ilości adresów mostów musisz wysłać prośbę z adresów emailowych z jednej z następujących domen:" + +#: lib/bridgedb/I18n.py:41 +msgid "[This is an automated message; please do not reply.]" +msgstr "[To jest wiadomość generowana automatycznie; prosimy na nią nie odpisywać.]" + +#: lib/bridgedb/I18n.py:43 +msgid "" +"Another way to find public bridge addresses is to visit\n" +"https://bridges.torproject.org/. The answers you get from that page\n" +"will change every few days, so check back periodically if you need more\n" +"bridge addresses." +msgstr "Innym sposobem na odnalezienie adresów mostów jest odwiedzenie https://bridges.torproject.org/. Informacje na tej stronie zmieniają się co kilka dni, tak więc odwiedzaj ją co jakiś czas jeżeli potrzebujesz listę nowych adresów mostów." + +#: lib/bridgedb/I18n.py:48 +msgid "(no bridges currently available)" +msgstr "(obecnie brak dostępnych adresów mostów)" + +#: lib/bridgedb/I18n.py:50 +msgid "(e-mail requests not currently supported)" +msgstr "(prośba e-mail obecnie nieobsługiwana)"

1 0

[translation/bridgedb] Update translations for bridgedb
by translation＠torproject.org 23 Aug '12

23 Aug '12

commit 4ec0e65bb389560365fdcd5d8e6c6a1463b63528 Author: Translation commit bot <translation(a)torproject.org> Date: Thu Aug 23 09:45:02 2012 +0000 Update translations for bridgedb --- pl/bridgedb.po | 8 ++++---- 1 files changed, 4 insertions(+), 4 deletions(-) diff --git a/pl/bridgedb.po b/pl/bridgedb.po index 187e33e..f0d1ed2 100644 --- a/pl/bridgedb.po +++ b/pl/bridgedb.po @@ -9,7 +9,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: https://trac.torproject.org/projects/tor\n" "POT-Creation-Date: 2011-01-01 07:48-0800\n" -"PO-Revision-Date: 2012-08-23 09:14+0000\n" +"PO-Revision-Date: 2012-08-23 09:17+0000\n" "Last-Translator: JerBen <ayurveda63(a)gmail.com>\n" "Language-Team: LANGUAGE <LL(a)li.org>\n" "MIME-Version: 1.0\n" @@ -54,7 +54,7 @@ msgstr "Kolejnym sposobem na znalezienie publicznych adresów mostów jest wysł #: lib/bridgedb/I18n.py:41 msgid "[This is an automated message; please do not reply.]" -msgstr "[To jest wiadomość generowana automatycznie; prosimy na niąnie odpisywać.]" +msgstr "[To jest wiadomość generowana automatycznie; prosimy na nią nie odpisywać.]" #: lib/bridgedb/I18n.py:43 msgid "" @@ -66,8 +66,8 @@ msgstr "Innym sposobem na odnalezienie adresów mostów jest odwiedzenie https:/ #: lib/bridgedb/I18n.py:48 msgid "(no bridges currently available)" -msgstr "" +msgstr "(obecnie brak dostępnych adresów mostów)" #: lib/bridgedb/I18n.py:50 msgid "(e-mail requests not currently supported)" -msgstr "" +msgstr "(prośba e-mail obecnie nieobsługiwana)"

1 0

[translation/vidalia_help_completed] Update translations for vidalia_help_completed
by translation＠torproject.org 23 Aug '12

23 Aug '12

commit f88bbf0fd7c767566a6813bbbce87156d35485bc Author: Translation commit bot <translation(a)torproject.org> Date: Thu Aug 23 09:15:28 2012 +0000 Update translations for vidalia_help_completed --- pl/running.po | 150 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 150 insertions(+), 0 deletions(-) diff --git a/pl/running.po b/pl/running.po new file mode 100644 index 0000000..8a08a06 --- /dev/null +++ b/pl/running.po @@ -0,0 +1,150 @@ +# +# Translators: +# <ayurveda63(a)gmail.com>, 2012. +msgid "" +msgstr "" +"Project-Id-Version: The Tor Project\n" +"Report-Msgid-Bugs-To: https://trac.torproject.org/projects/tor\n" +"POT-Creation-Date: 2010-06-26 17:00+0200\n" +"PO-Revision-Date: 2012-08-23 08:51+0000\n" +"Last-Translator: JerBen <ayurveda63(a)gmail.com>\n" +"Language-Team: LANGUAGE <LL(a)li.org>\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: pl\n" +"Plural-Forms: nplurals=3; plural=(n==1 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2)\n" + +#. type: Content of: <html><body><h1> +#: en/running.html:16 +msgid "Running Tor" +msgstr "Uruchamianie Tora" + +#. type: Content of: <html><body> +#: en/running.html:20 +msgid "" +"Vidalia can help you control your Tor process by letting you start and stop " +"Tor, as well as monitoring Tor's status and letting you know if it exits " +"unexpectedly." +msgstr "Vidalia może pomóc ci w kontroli procesów Tora przez możliwość uruchamiania oraz zatrzymywania pracy Tora jak i monitorowania jego statusu oraz wyświetlania informacji jeżeli tor nieoczekiwanie wstrzyma pracę." + +#. type: Content of: <html><body> +#: en/running.html:25 +msgid "<a name=\"starting\"/>" +msgstr "<a name=\"uruchamianie\"/>" + +#. type: Content of: <html><body><h3> +#: en/running.html:26 +msgid "Starting and Stopping Tor" +msgstr "Uruchamianie i zatrzymywanie Tora" + +#. type: Content of: <html><body> +#: en/running.html:28 +msgid "To start Tor," +msgstr "By uruchomić Tora," + +#. type: Content of: <html><body><ol><li> +#: en/running.html:30 +msgid "Select Start from Vidalia's tray menu or press Ctrl+S" +msgstr "Wybierz Start z pasku Vidalii lub naciśnij Ctrl+S" + +#. type: Content of: <html><body><ol> +#: en/running.html:30 en/running.html:45 +msgid "." +msgstr "." + +#. type: Content of: <html><body><ol><li> +#: en/running.html:32 +msgid "" +"Vidalia's tray icon will change from an onion with a red X to a green onion " +"when Tor has started." +msgstr "Ikona Vidalii na pasku zmieni się z ikony cebuli z czerwonym znakiem X na ikonę zielonej cebuli gdy Tor rozpoczyna działanie. " + +#. type: Content of: <html><body> +#: en/running.html:36 +msgid "" +"If Vidalia is unable to start Tor, Vidalia will display an error message " +"telling you what went wrong. You can also look at your <a " +"href=\"log.html\">message log</a> to see if Tor printed any more information" +" about what went wrong." +msgstr "Gdy Vidalia nie może uruchomić Tora, wyświetli wiadomość, że wystąpił błąd. Możesz przejrzeć <a href=\"log.html\">message log</a> by zobaczyć czy Tor wygenerował jakieś informacje o błędach." + +#. type: Content of: <html><body> +#: en/running.html:43 +msgid "To stop Tor," +msgstr "By zatrzymać Tora," + +#. type: Content of: <html><body><ol><li> +#: en/running.html:45 +msgid "Select Stop from Vidalia's tray menu or press Ctrl+T" +msgstr "Wybierz Stop z zakładki Vidalii lub naciśnij Ctrl+T" + +#. type: Content of: <html><body><ol><li> +#: en/running.html:47 +msgid "" +"Vidalia's tray icon will change from a green onion to a gray onion with a " +"red X when Tor has stopped." +msgstr "Ikona Vidalii na pasku zmieni się z ikony zielonej cebuli na ikonę szarej cebuli z czerwonym znakiem X gdy Tor wstrzymał pracę." + +#. type: Content of: <html><body> +#: en/running.html:51 +msgid "" +"If Vidalia was unable to stop Tor, Vidalia will display an error message " +"telling you what went wrong. You can also look at your <a " +"href=\"log.html\">message log</a> to see if Tor printed any more information" +" about what went wrong." +msgstr "Jeżeli Vidalia nie jest w stanie zatrzymać pracy Tora, wyświetli wiadomość, że wystąpił błąd. Możesz przejrzeć <a href=\"log.html\">message log</a> by zobaczyć czy Tor wygenerował jakieś informacje o błędach." + +#. type: Content of: <html><body> +#: en/running.html:57 +msgid "<a name=\"monitoring\"/>" +msgstr "<a name=\"monitorowanie\"/>" + +#. type: Content of: <html><body><h3> +#: en/running.html:58 +msgid "Monitoring Tor's Status" +msgstr "Monitorowanie statusu Tora" + +#. type: Content of: <html><body> +#: en/running.html:60 +msgid "" +"Vidalia tells you about the status of Tor by displaying an icon in your " +"system tray or dock area. The following table shows the different states " +"indicated by an icon in your system's notification area:" +msgstr "Vidalia informuje cię o statusie działania Tora przez wyświetlanie ikony na pasku zadań. Poniższa tabele pokazuje różne statusy, wyświetlane w postaci ikon na pasku zadań: " + +#. type: Content of: <html><body><table><tr><td> +#: en/running.html:69 +msgid "" +"Tor is stopped. Select Start from the Vidalia menu to start Tor." +msgstr "Tor przestał działać. Naciśnij Start Z menu Vidalii by uruchomić Tora." + +#. type: Content of: <html><body><table><tr><td> +#: en/running.html:76 +msgid "" +"Tor is starting up. You can check the <a href=\"log.html\">message log</a> " +"for status information about Tor while it is starting." +msgstr "Tor uruchamia się. Możesz sprawdzić w <a href=\"log.html\">message log</a> informacje na temat statusu Tora podczas jego uruchamiania." + +#. type: Content of: <html><body><table><tr><td> +#: en/running.html:84 +msgid "" +"Tor is running. If you want to stop Tor, select Stop from the Vidalia" +" menu. Tor will print informational messages to the <a " +"href=\"log.html\">message log</a> while it is running, if you want to see " +"what Tor is doing." +msgstr "Tor jest uruchomiony. Jeżeli chcesz wstrzymać pracę Tora, wciśnij Stop w manu Vidalii. Jeżeli chcesz sprawdzić co robi Tor podczas działania, sprawdź wygenerowane informacje w <a href=\"log.html\">message log</a>." + +#. type: Content of: <html><body><table><tr><td> +#: en/running.html:92 +msgid "Tor is in the process of shutting down." +msgstr "Tor jest w trakcie wyłączania się." + +#. type: Content of: <html><body> +#: en/running.html:98 +msgid "" +"If Tor exits unexpectedly, Vidalia will change its icon to the dark onion " +"with a red X and display an error message letting you know what went wrong. " +"You can also check the <a href=\"log.html\">message log</a> for details " +"about any problems Tor encountered before it exited." +msgstr "Jeżeli Tor nieoczekiwanie zakończy pracę, Vidalia zmieni kolor ikony na ciemną cebulę z czerwonym znakiem X po czym wyświetli informacje o błędzie. Możesz również sprawdzić w <a href=\"log.html\">message log</a> błędy na jakie natknął się Tor tuż przed wyłączeniem"

1 0

[translation/vidalia_help] Update translations for vidalia_help
by translation＠torproject.org 23 Aug '12

23 Aug '12

commit 221bffbf477b57c88c35c540010ac7dddc3fea7e Author: Translation commit bot <translation(a)torproject.org> Date: Thu Aug 23 09:15:23 2012 +0000 Update translations for vidalia_help --- pl/running.po | 10 +++++----- 1 files changed, 5 insertions(+), 5 deletions(-) diff --git a/pl/running.po b/pl/running.po index 156b07f..8a08a06 100644 --- a/pl/running.po +++ b/pl/running.po @@ -6,7 +6,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: https://trac.torproject.org/projects/tor\n" "POT-Creation-Date: 2010-06-26 17:00+0200\n" -"PO-Revision-Date: 2012-08-23 08:43+0000\n" +"PO-Revision-Date: 2012-08-23 08:51+0000\n" "Last-Translator: JerBen <ayurveda63(a)gmail.com>\n" "Language-Team: LANGUAGE <LL(a)li.org>\n" "MIME-Version: 1.0\n" @@ -26,7 +26,7 @@ msgid "" "Vidalia can help you control your Tor process by letting you start and stop " "Tor, as well as monitoring Tor's status and letting you know if it exits " "unexpectedly." -msgstr "" +msgstr "Vidalia może pomóc ci w kontroli procesów Tora przez możliwość uruchamiania oraz zatrzymywania pracy Tora jak i monitorowania jego statusu oraz wyświetlania informacji jeżeli tor nieoczekiwanie wstrzyma pracę." #. type: Content of: <html><body> #: en/running.html:25 @@ -133,12 +133,12 @@ msgid "" " menu. Tor will print informational messages to the <a " "href=\"log.html\">message log</a> while it is running, if you want to see " "what Tor is doing." -msgstr "" +msgstr "Tor jest uruchomiony. Jeżeli chcesz wstrzymać pracę Tora, wciśnij Stop w manu Vidalii. Jeżeli chcesz sprawdzić co robi Tor podczas działania, sprawdź wygenerowane informacje w <a href=\"log.html\">message log</a>." #. type: Content of: <html><body><table><tr><td> #: en/running.html:92 msgid "Tor is in the process of shutting down." -msgstr "" +msgstr "Tor jest w trakcie wyłączania się." #. type: Content of: <html><body> #: en/running.html:98 @@ -147,4 +147,4 @@ msgid "" "with a red X and display an error message letting you know what went wrong. " "You can also check the <a href=\"log.html\">message log</a> for details " "about any problems Tor encountered before it exited." -msgstr "" +msgstr "Jeżeli Tor nieoczekiwanie zakończy pracę, Vidalia zmieni kolor ikony na ciemną cebulę z czerwonym znakiem X po czym wyświetli informacje o błędzie. Możesz również sprawdzić w <a href=\"log.html\">message log</a> błędy na jakie natknął się Tor tuż przed wyłączeniem"

1 0

[translation/bridgedb] Update translations for bridgedb
by translation＠torproject.org 23 Aug '12

23 Aug '12

commit 147c50d5ccdfa6221bdef0389edd6a566135f48a Author: Translation commit bot <translation(a)torproject.org> Date: Thu Aug 23 09:15:03 2012 +0000 Update translations for bridgedb --- pl/bridgedb.po | 19 ++++++++++--------- 1 files changed, 10 insertions(+), 9 deletions(-) diff --git a/pl/bridgedb.po b/pl/bridgedb.po index ab72860..187e33e 100644 --- a/pl/bridgedb.po +++ b/pl/bridgedb.po @@ -3,13 +3,14 @@ # This file is distributed under the same license as the PACKAGE package. # # Translators: +# <ayurveda63(a)gmail.com>, 2012. msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: https://trac.torproject.org/projects/tor\n" "POT-Creation-Date: 2011-01-01 07:48-0800\n" -"PO-Revision-Date: 2011-02-19 16:53+0000\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"PO-Revision-Date: 2012-08-23 09:14+0000\n" +"Last-Translator: JerBen <ayurveda63(a)gmail.com>\n" "Language-Team: LANGUAGE <LL(a)li.org>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -19,7 +20,7 @@ msgstr "" #: lib/bridgedb/I18n.py:21 msgid "Here are your bridge relays: " -msgstr "" +msgstr "To są twoje przekaźniki mostowe." #: lib/bridgedb/I18n.py:23 msgid "" @@ -27,20 +28,20 @@ msgid "" "in the main directory. Since there is no complete public list of them,\n" "even if your ISP is filtering connections to all the known Tor relays,\n" "they probably won't be able to block all the bridges." -msgstr "" +msgstr "Przekaźniki mostowe \"Tor bridges\" (lub \"mosty\" w skrócie) są przekaźnikami Tora, które NIE SĄ wyszczególnione w katalogu głównym. Z racji, iż nie ma pełnej, publicznej listy mostów, nawet jeżeli twój dostawca usług internetowych ISP filtruję połączenia z częścią widocznych mostów Tora, najprawdopodobniej nie będzie on w stanie wyszukać i zablokować wszystkich." #: lib/bridgedb/I18n.py:28 msgid "" "To use the above lines, go to Vidalia's Network settings page, and click\n" "\"My ISP blocks connections to the Tor network\". Then add each bridge\n" "address one at a time." -msgstr "" +msgstr "By użyć powyższych mostów, wejdź do zakładki Ustawienia sieciowe w Vidalii, naciśnij opcję \"mój dostawca usług internetowych ISP blokuje połączenia z siecią Tor\". Następnie dodaj każdy adres mostu pojedynczo. " #: lib/bridgedb/I18n.py:32 msgid "" "Configuring more than one bridge address will make your Tor connection\n" "more stable, in case some of the bridges become unreachable." -msgstr "" +msgstr "Skonfigurowanie więcej niż jednego adresu mostu, sprawi iż połączenie z siecią Tor będzie stabilniejsze w wypadku gdy jeden z mostów stanie się niedostępny." #: lib/bridgedb/I18n.py:35 msgid "" @@ -49,11 +50,11 @@ msgid "" "of the mail. However, so we can make it harder for an attacker to learn\n" "lots of bridge addresses, you must send this request from an email address at\n" "one of the following domains:" -msgstr "" +msgstr "Kolejnym sposobem na znalezienie publicznych adresów mostów jest wysłanie maila na bridges(a)torproject.org z samym dopiskiem \"get bridges\" w treści maila. By utrudnić atakującym dostęp do dużej ilości adresów mostów musisz wysłać prośbę z adresów emailowych z jednej z następujących domen:" #: lib/bridgedb/I18n.py:41 msgid "[This is an automated message; please do not reply.]" -msgstr "" +msgstr "[To jest wiadomość generowana automatycznie; prosimy na niąnie odpisywać.]" #: lib/bridgedb/I18n.py:43 msgid "" @@ -61,7 +62,7 @@ msgid "" "https://bridges.torproject.org/. The answers you get from that page\n" "will change every few days, so check back periodically if you need more\n" "bridge addresses." -msgstr "" +msgstr "Innym sposobem na odnalezienie adresów mostów jest odwiedzenie https://bridges.torproject.org/. Informacje na tej stronie zmieniają się co kilka dni, tak więc odwiedzaj ją co jakiś czas jeżeli potrzebujesz listę nowych adresów mostów." #: lib/bridgedb/I18n.py:48 msgid "(no bridges currently available)"

1 0

[translation/vidalia_help] Update translations for vidalia_help
by translation＠torproject.org 23 Aug '12

23 Aug '12

commit de856800f177c4a875f7931ea1d79d75198a9549 Author: Translation commit bot <translation(a)torproject.org> Date: Thu Aug 23 08:45:19 2012 +0000 Update translations for vidalia_help --- pl/running.po | 39 ++++++++++++++++++++------------------- 1 files changed, 20 insertions(+), 19 deletions(-) diff --git a/pl/running.po b/pl/running.po index 66c9c36..156b07f 100644 --- a/pl/running.po +++ b/pl/running.po @@ -1,12 +1,13 @@ # # Translators: +# <ayurveda63(a)gmail.com>, 2012. msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: https://trac.torproject.org/projects/tor\n" "POT-Creation-Date: 2010-06-26 17:00+0200\n" -"PO-Revision-Date: 2010-11-30 05:03+0000\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" +"PO-Revision-Date: 2012-08-23 08:43+0000\n" +"Last-Translator: JerBen <ayurveda63(a)gmail.com>\n" "Language-Team: LANGUAGE <LL(a)li.org>\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -17,7 +18,7 @@ msgstr "" #. type: Content of: <html><body><h1> #: en/running.html:16 msgid "Running Tor" -msgstr "" +msgstr "Uruchamianie Tora" #. type: Content of: <html><body> #: en/running.html:20 @@ -30,34 +31,34 @@ msgstr "" #. type: Content of: <html><body> #: en/running.html:25 msgid "<a name=\"starting\"/>" -msgstr "" +msgstr "<a name=\"uruchamianie\"/>" #. type: Content of: <html><body><h3> #: en/running.html:26 msgid "Starting and Stopping Tor" -msgstr "" +msgstr "Uruchamianie i zatrzymywanie Tora" #. type: Content of: <html><body> #: en/running.html:28 msgid "To start Tor," -msgstr "" +msgstr "By uruchomić Tora," #. type: Content of: <html><body><ol><li> #: en/running.html:30 msgid "Select Start from Vidalia's tray menu or press Ctrl+S" -msgstr "" +msgstr "Wybierz Start z pasku Vidalii lub naciśnij Ctrl+S" #. type: Content of: <html><body><ol> #: en/running.html:30 en/running.html:45 msgid "." -msgstr "" +msgstr "." #. type: Content of: <html><body><ol><li> #: en/running.html:32 msgid "" "Vidalia's tray icon will change from an onion with a red X to a green onion " "when Tor has started." -msgstr "" +msgstr "Ikona Vidalii na pasku zmieni się z ikony cebuli z czerwonym znakiem X na ikonę zielonej cebuli gdy Tor rozpoczyna działanie. " #. type: Content of: <html><body> #: en/running.html:36 @@ -66,24 +67,24 @@ msgid "" "telling you what went wrong. You can also look at your <a " "href=\"log.html\">message log</a> to see if Tor printed any more information" " about what went wrong." -msgstr "" +msgstr "Gdy Vidalia nie może uruchomić Tora, wyświetli wiadomość, że wystąpił błąd. Możesz przejrzeć <a href=\"log.html\">message log</a> by zobaczyć czy Tor wygenerował jakieś informacje o błędach." #. type: Content of: <html><body> #: en/running.html:43 msgid "To stop Tor," -msgstr "" +msgstr "By zatrzymać Tora," #. type: Content of: <html><body><ol><li> #: en/running.html:45 msgid "Select Stop from Vidalia's tray menu or press Ctrl+T" -msgstr "" +msgstr "Wybierz Stop z zakładki Vidalii lub naciśnij Ctrl+T" #. type: Content of: <html><body><ol><li> #: en/running.html:47 msgid "" "Vidalia's tray icon will change from a green onion to a gray onion with a " "red X when Tor has stopped." -msgstr "" +msgstr "Ikona Vidalii na pasku zmieni się z ikony zielonej cebuli na ikonę szarej cebuli z czerwonym znakiem X gdy Tor wstrzymał pracę." #. type: Content of: <html><body> #: en/running.html:51 @@ -92,17 +93,17 @@ msgid "" "telling you what went wrong. You can also look at your <a " "href=\"log.html\">message log</a> to see if Tor printed any more information" " about what went wrong." -msgstr "" +msgstr "Jeżeli Vidalia nie jest w stanie zatrzymać pracy Tora, wyświetli wiadomość, że wystąpił błąd. Możesz przejrzeć <a href=\"log.html\">message log</a> by zobaczyć czy Tor wygenerował jakieś informacje o błędach." #. type: Content of: <html><body> #: en/running.html:57 msgid "<a name=\"monitoring\"/>" -msgstr "" +msgstr "<a name=\"monitorowanie\"/>" #. type: Content of: <html><body><h3> #: en/running.html:58 msgid "Monitoring Tor's Status" -msgstr "" +msgstr "Monitorowanie statusu Tora" #. type: Content of: <html><body> #: en/running.html:60 @@ -110,20 +111,20 @@ msgid "" "Vidalia tells you about the status of Tor by displaying an icon in your " "system tray or dock area. The following table shows the different states " "indicated by an icon in your system's notification area:" -msgstr "" +msgstr "Vidalia informuje cię o statusie działania Tora przez wyświetlanie ikony na pasku zadań. Poniższa tabele pokazuje różne statusy, wyświetlane w postaci ikon na pasku zadań: " #. type: Content of: <html><body><table><tr><td> #: en/running.html:69 msgid "" "Tor is stopped. Select Start from the Vidalia menu to start Tor." -msgstr "" +msgstr "Tor przestał działać. Naciśnij Start Z menu Vidalii by uruchomić Tora." #. type: Content of: <html><body><table><tr><td> #: en/running.html:76 msgid "" "Tor is starting up. You can check the <a href=\"log.html\">message log</a> " "for status information about Tor while it is starting." -msgstr "" +msgstr "Tor uruchamia się. Możesz sprawdzić w <a href=\"log.html\">message log</a> informacje na temat statusu Tora podczas jego uruchamiania." #. type: Content of: <html><body><table><tr><td> #: en/running.html:84

1 0

[research-web/master] Add George's morpher report.
by karsten＠torproject.org 22 Aug '12

22 Aug '12

commit 3873053b6280c9e9df5398752c85b9cb09deed88 Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Wed Aug 22 20:28:08 2012 +0200 Add George's morpher report. --- techreports.html | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/techreports.html b/techreports.html index 2d7f316..e2dc191 100644 --- a/techreports.html +++ b/techreports.html @@ -48,10 +48,11 @@ March 17, 2012. March 16, 2012. <a href="https://www.cl.cam.ac.uk/~sjm217/papers/tor12datagramtesting.pdf">PDF</a>.--> - +<a href="techreports/morpher-2012-03-13.pdf">PDF</a>. Karsten Loesing. What if the Tor network had 50,000 bridges?

1 0

[tech-reports/master] Add morpher sources.
by karsten＠torproject.org 22 Aug '12

22 Aug '12

commit e1eb25efc0eef9ed51cb23fd81d70a2bd655a4f4 Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Mon Aug 20 19:55:58 2012 +0200 Add morpher sources. https://trac.torproject.org/projects/tor/attachment/ticket/5023/morpher_2.t… --- 2012/morpher/.gitignore | 3 + 2012/morpher/500000_cs.pdf | Bin 0 -> 27094 bytes 2012/morpher/500000_sc.pdf | Bin 0 -> 25864 bytes 2012/morpher/https_cs.pdf | Bin 0 -> 20287 bytes 2012/morpher/morpher.tex | 298 ++++++++++++++++++++++++++++++++++++++++++++ 2012/morpher/tor_cs.pdf | Bin 0 -> 12335 bytes 6 files changed, 301 insertions(+), 0 deletions(-) diff --git a/2012/morpher/.gitignore b/2012/morpher/.gitignore new file mode 100644 index 0000000..5f59b41 --- /dev/null +++ b/2012/morpher/.gitignore @@ -0,0 +1,3 @@ +morpher.pdf +morpher-2012-03-13.pdf + diff --git a/2012/morpher/500000_cs.pdf b/2012/morpher/500000_cs.pdf new file mode 100644 index 0000000..dd7abd0 Binary files /dev/null and b/2012/morpher/500000_cs.pdf differ diff --git a/2012/morpher/500000_sc.pdf b/2012/morpher/500000_sc.pdf new file mode 100644 index 0000000..fe954fe Binary files /dev/null and b/2012/morpher/500000_sc.pdf differ diff --git a/2012/morpher/https_cs.pdf b/2012/morpher/https_cs.pdf new file mode 100644 index 0000000..b4e5d55 Binary files /dev/null and b/2012/morpher/https_cs.pdf differ diff --git a/2012/morpher/morpher.tex b/2012/morpher/morpher.tex new file mode 100644 index 0000000..8fd4935 --- /dev/null +++ b/2012/morpher/morpher.tex @@ -0,0 +1,298 @@ +\documentclass[]{article} +\usepackage{graphicx} + +\usepackage[parfill]{parskip} +\begin{document} + +\title{Packet Size Pluggable Transport and Traffic Morphing} +\author{George Kadianakis} +\maketitle + +\section{Traffic Morphing} + +\subsection{Overview} + +It is well known \cite{herrmann} that Tor traffic can be distinguished +from other network protocols by its distinctive packet size. Due to the +sized Tor cells, most TCP packets of Tor traffic are 586 bytes in size +(See Figure \ref{tor_cs.pdf}). + +\begin{figure}[h] +\begin{center} +\includegraphics[scale=0.65]{tor_cs.pdf} +\end{center} +\caption{Packet size probability distribution of Tor Client-to-Server traffic \cite{caida}} +\label{tor_cs.pdf} +\end{figure} + +On the other hand, HTTPS, the protocol that Tor tries to simulate +\cite{tls_norm}, has a much more spread out packet size probability +distribution (See Figure \ref{https_cs.pdf}) + +\begin{figure}[h] +\begin{center} +\includegraphics[scale=0.65]{https_cs.pdf} +\end{center} +\caption{Packet size probability distribution of HTTPS Client-to-Server traffic \cite{caida}} +\label{https_cs.pdf} +\end{figure} + +This means that an adversary can detect Tor traffic by using packets +of size \textit{586} as distinguishers \cite{ll} \cite{herrmann}. + +\subsection{Solutions} + +An obvious solution to this problem is to introduce a padding scheme +to Tor. + +Some network protocols already use padding to defend against traffic +fingerprinting attacks. SSH and TLS, for example, both support padding +in their messages \cite{ssh} \cite{gnutls}. Most implementations of +those protocols don't pad by default. The ones that do, add a random +amount of padding to the protocol message. + +The Tor protocol also supports padding cells (named \textit{PADDING} +and \textit{VPADDING}) which attempt to generate covert traffic. + +While the random padding solution effectively hides the \textit{586} +bytes identifier, it does not fully make Tor traffic resemble HTTPS +traffic. This means that a sophisticated attacker can distinguish Tor +traffic, by searching for SSL handshakes that try to look like HTTPS +but actually follow a packet size probability distribution different +from the one of HTTPS. + +A solution to that, is to collect a large amount of HTTPS packets and +form their packet size probability distribution. We can then randomly +sample that probability distribution for every packet we need to +send. Specifically, for every Tor packet, we would sample the HTTPS +probability distribution, find a target packet size and split or pad +our packet accordingly. We call this method \textit{random sampling}. + +The problem with random sampling, is that it radically increases our +bandwidth overhead. + +To reduce this overhead, we looked into a paper of Charles Wright, +Scott Coulls and Fabian Monrose called \emph{Traffic Morphing: An + efficient defense against statistical traffic analysis} \cite{tm}. + +\subsection{Traffic Morphing} + +Traffic Morphing minimizes bandwidth overhead when transforming +packets from one packet size probability distribution to another. That +is, given two packet size probability distributions, one for the +source protocol and another for the target protocol, it produces a +\emph{morphing matrix} that acts as an oracle and describes how to +efficiently morph packets between those two probability distributions. + +Traffic Morphing works by modeling the problem of transforming packets +as a problem of linear programming. To construct the morphing matrix, +we consider \textit{bandwidth overhead} as the objective function of +our linear program, and use appropriate problem constraints that +transform the source probability distribution to the target +probability distribution. + +\section{Woes of Traffic Morphing} + +\subsection{Issues} + +Unfortunately, morphing matrices are not a panacea, for the following +reasons: + +\subsubsection{Statelessnes} + +Morphing matrices are not stateful. In other words, morphing matrices +don't handle protocols whose packet size probability distribution +changes through the protocol runtime. + +For example, HTTPS follows different packet size probability +distributions between the handshake and the data phase, and morphing +matrices are unable to understand the difference. + +\subsubsection{Splitting} + +The original traffic morphing paper did not specify an algorithm for +splitting packets: When a morphing matrix suggests a packet size +\textbf{smaller} than the original packet size, we have to split the +original packet into two parts. The problem is that the original paper +does not clearly define what should be done with the second half of +the split packet. + +Sending the second half of the packet to the network is not correct, +because its packet size does not belong to the packet size probability +distribution of the target protocol (specifically, it belongs to the +packet size probability distribution of the target protocol when split +once by its morphing matrix). + +Querying the morphing matrix again, for the size of the second half of +the split packet, is also not correct, since that packet size does +not belong to the probability distribution of the source protocol and +morphing matrices mishandle unknown packet sizes. + +Even though the original paper didn't specify the splitting algorithm +that should be used, it hinted that doing a random sampling of the +target probability distribution for the length of the split packet +is what they did in their implementation. + +\subsection{Evaluation of issues} + +Unfortunately, the splitting problem of the previous section is not +only theoretical. To evaluate the bandwidth overhead of morphing +matrices, we made software \cite{morpher_eval} that simulates the +morphing of a large number of packets. Specifically, our software +morphs 500000 packets using both random sampling and traffic morphing, +and plots the overhead. (In traffic morphing, we use random sampling +for the second parts of a split packet.) + +We can see that in the case of Server-to-Client Tor-to-HTTPS packet +morphing, morphing matrices actually reduce the bandwidth overhead by +a substantial amount (See Figure \ref{0.5m_sc}). + +\begin{figure}[h] +\begin{center} +\includegraphics[scale=0.65]{500000_sc.pdf} +\end{center} +\caption{Bandwidth overhead for 0.5 million Server-to-Client packets} +\label{0.5m_sc} +\end{figure} + +However, in the case of Client-to-Server Tor-to-HTTPS packet size +morphing, the bandwidth overhead of morphing matrices is actually +larger than the bandwidth overhead of random sampling (See Figure +\ref{0.5mcs}). +\begin{figure}[h] +\begin{center} +\includegraphics[scale=0.65]{500000_cs.pdf} +\end{center} +\caption{Bandwidth overhead for 0.5 million Client-to-server packets} +\label{0.5mcs} +\end{figure} + +Our guess is that this happens because in the Client-to-Server case, +HTTPS has large probabilities of outputting small packet sizes (See +Figure \ref{https_cs.pdf}). + +This means that our morphing matrix tries to split our packets into +small packets, and then when random sampling is used for the second +half of our packet it tries to pad it to 1460 (which is also a very +popular packet size in HTTPS): + +For example: + +\begin{verbatim} +Packet size 586. We must morph it to 127. Splitting to 127+459 and sending 127. +Packet size 459. We must morph it to 123. Splitting to 123+336 and sending 123. +Packet size 336. We must morph it to 1459. Padding with 1123 and sending. +\end{verbatim} + +In this case, morpher gets a packet of 586 bytes to morph. It queries +the morphing matrix which suggests a packet size of 127 bytes. Morpher +splits the original packet to 127+459 bytes, sends 127 bytes to the +network, and is left with 459 bytes. Since the packet was split, our +faulty splitting algorithm says that morpher should do a direct +sampling over the HTTPS probability distribution. Morpher gets 123 +bytes as the result of random sampling, and splits the packet to +123+336 bytes. It sends 123 bytes to the network, and is left with 459 +bytes. Morpher again does random sampling over the HTTPS probability +distribution, and gets 1459 bytes as the result. This means that it +must pad the 336 bytes packet to 1459 bytes. This results in an +overhead of 1123 bytes. + +For the same case, random sampling was better due to the randomness of +random sampling. + +\subsection{Fixes} + +A potential fix for the statelessness of morphing matrices, is to +generate multiple morphing matrices for each phase of the protocol. We +have not attempted this approach. + +A potential fix for the splitting algorithm issue, is to generate a +morphing matrix for every split level (since the number of splits that +can happen to a packet are finite), and use the appropriate morphing +matrix everytime we have a split packet. We have not implemented or +evaluated this fix yet. + +\section{Future} + +For the short-term future, we decided to postpone the development of +pluggable transports based on Traffic Morphing. We think that more +research is needed, as well as a stronger focus towards realistic +adversaries. + +Specifically, we believe that if we investigate the strength and +limitations of modern Deep Packet Inspection kits, we can provide +adequate defences without the implementation complexity and drawbacks +of the Traffic Morphing technology. + +We plan on investigating packet size pluggable transports with less +overhead, even if they don't deliver a perfect probability +distribution match to the target protocol, since we believe that such +pluggable transports can effectively mitigate many practical +packet-size-based detection attacks. + +At the same time, we also think it's important to remain up-to-date +with modern academic research. For example, modern website +fingerprinting research has showed that any kind of padding scheme is +insufficient to protect against sophisticated packet size +distinguishers \cite{ll} \cite{herrmann}. Furthermore, the academic +community has found other network traffic features that can be used as +distinguishers with surprisingly high accuracy \cite{panchenko}. + +Meanwhile, we are also researching alternative pluggable transports +with better resistance against payload fingerprinting, which we think +real-life attackers are likely to do, and also pluggable transports +which can get through HTTP proxy servers. + +\section{Acknowledgments} + +Thanks to Steven J. Murdoch and the Tor Project for the fruitful +conversations on packet size pluggable transports. + +\bibliographystyle{plain} +\begin{thebibliography}{9} + +\bibitem{ssh} https://www.ietf.org/rfc/rfc4344.txt + +\bibitem{gnutls} https://www.gnu.org/software/gnutls/manual/gnutls.html\#On-Record-Padding + +\bibitem{ll} + M. Liberatore, B. N. Levine, \textit{Inferring the Source + of Encrypted HTTP Connections}, CCS2006, October 2006. + +\bibitem{herrmann} + Dominik Herrmann, Rolf Wendolsky, and Hannes + Federrath. 2009. Website fingerprinting: attacking popular privacy + enhancing technologies with the multinomial naïve-bayes classifier. + +\bibitem{tls_norm} + http://archives.seul.org/or/dev/Jan-2011/msg00029.html + +\bibitem{morpher_eval} + \textit{Morpher pluggable transport: Select algorithm for packet size morphing} + + https://trac.torproject.org/projects/tor/ticket/5023 + http://archives.seul.org/or/dev/Jan-2011/msg00029.html + +\bibitem{panchenko} + Andriy Panchenko, Lukas Niessen, Andreas Zinnen, and Thomas + Engel. 2011. \textit{Website fingerprinting in onion routing based + anonymization networks}. + +\bibitem{tm} + Charles Wright, Scott Coulls , Fabian Monrose. \textit{Traffic + Morphing: An efficient defense against statistical traffic + analysis.} In Proceedings of the 14th Annual Network and + Distributed Systems Symposium (NDSS), Feb, 2009. + +\bibitem{caida} + The packet length probability distributions were formed after + analysis of traffic traces kindly provided by CAIDA. The traffic + traces were captured by monitoring an Equinix datacenter in Chicago, + IL. + + https://gitorious.org/morpher/morpher/blobs/master/ACKNOWLEDGMENTS + https://gitorious.org/morpher/morpher/trees/master/data + +\end{thebibliography} + +\end{document} diff --git a/2012/morpher/tor_cs.pdf b/2012/morpher/tor_cs.pdf new file mode 100644 index 0000000..5fe6483 Binary files /dev/null and b/2012/morpher/tor_cs.pdf differ

1 0

[tech-reports/master] Force morpher.tex into the Tor Tech Report template.
by karsten＠torproject.org 22 Aug '12

22 Aug '12

commit f117ab4b4303f480466c61856bda835565dccb37 Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Mon Aug 20 20:23:07 2012 +0200 Force morpher.tex into the Tor Tech Report template. --- 2012/morpher/morpher.tex | 34 ++++++++++++++++++++-------------- 2012/morpher/tortechrep.cls | 1 + 2 files changed, 21 insertions(+), 14 deletions(-) diff --git a/2012/morpher/morpher.tex b/2012/morpher/morpher.tex index 8fd4935..43442df 100644 --- a/2012/morpher/morpher.tex +++ b/2012/morpher/morpher.tex @@ -1,11 +1,13 @@ -\documentclass[]{article} +\documentclass{tortechrep} \usepackage{graphicx} -\usepackage[parfill]{parskip} \begin{document} \title{Packet Size Pluggable Transport and Traffic Morphing} \author{George Kadianakis} +\contact{asn(a)torproject.org} +\date{March 13, 2012} +\reportid{2012-03-004} \maketitle \section{Traffic Morphing} @@ -19,7 +21,7 @@ sized Tor cells, most TCP packets of Tor traffic are 586 bytes in size \begin{figure}[h] \begin{center} -\includegraphics[scale=0.65]{tor_cs.pdf} +\includegraphics[width=\textwidth]{tor_cs.pdf} \end{center} \caption{Packet size probability distribution of Tor Client-to-Server traffic \cite{caida}} \label{tor_cs.pdf} @@ -31,7 +33,7 @@ distribution (See Figure \ref{https_cs.pdf}) \begin{figure}[h] \begin{center} -\includegraphics[scale=0.65]{https_cs.pdf} +\includegraphics[width=\textwidth]{https_cs.pdf} \end{center} \caption{Packet size probability distribution of HTTPS Client-to-Server traffic \cite{caida}} \label{https_cs.pdf} @@ -149,7 +151,7 @@ a substantial amount (See Figure \ref{0.5m_sc}). \begin{figure}[h] \begin{center} -\includegraphics[scale=0.65]{500000_sc.pdf} +\includegraphics[width=\textwidth]{500000_sc.pdf} \end{center} \caption{Bandwidth overhead for 0.5 million Server-to-Client packets} \label{0.5m_sc} @@ -161,7 +163,7 @@ larger than the bandwidth overhead of random sampling (See Figure \ref{0.5mcs}). \begin{figure}[h] \begin{center} -\includegraphics[scale=0.65]{500000_cs.pdf} +\includegraphics[width=\textwidth]{500000_cs.pdf} \end{center} \caption{Bandwidth overhead for 0.5 million Client-to-server packets} \label{0.5mcs} @@ -251,9 +253,11 @@ conversations on packet size pluggable transports. \bibliographystyle{plain} \begin{thebibliography}{9} -\bibitem{ssh} https://www.ietf.org/rfc/rfc4344.txt +\bibitem{ssh} + \url{https://www.ietf.org/rfc/rfc4344.txt} -\bibitem{gnutls} https://www.gnu.org/software/gnutls/manual/gnutls.html\#On-Record-Padding +\bibitem{gnutls} + \url{https://www.gnu.org/software/gnutls/manual/gnutls.html\#On-Record-Padding} \bibitem{ll} M. Liberatore, B. N. Levine, \textit{Inferring the Source @@ -265,13 +269,14 @@ conversations on packet size pluggable transports. enhancing technologies with the multinomial naïve-bayes classifier. \bibitem{tls_norm} - http://archives.seul.org/or/dev/Jan-2011/msg00029.html + \url{https://lists.torproject.org/pipermail/tor-dev/2011-January/001077.html} \bibitem{morpher_eval} \textit{Morpher pluggable transport: Select algorithm for packet size morphing} - https://trac.torproject.org/projects/tor/ticket/5023 - http://archives.seul.org/or/dev/Jan-2011/msg00029.html + \url{https://trac.torproject.org/projects/tor/ticket/5023} + + \url{https://lists.torproject.org/pipermail/tor-dev/2011-January/001077.html} \bibitem{panchenko} Andriy Panchenko, Lukas Niessen, Andreas Zinnen, and Thomas @@ -279,7 +284,7 @@ conversations on packet size pluggable transports. anonymization networks}. \bibitem{tm} - Charles Wright, Scott Coulls , Fabian Monrose. \textit{Traffic + Charles Wright, Scott Coulls, Fabian Monrose. \textit{Traffic Morphing: An efficient defense against statistical traffic analysis.} In Proceedings of the 14th Annual Network and Distributed Systems Symposium (NDSS), Feb, 2009. @@ -290,8 +295,9 @@ conversations on packet size pluggable transports. traces were captured by monitoring an Equinix datacenter in Chicago, IL. - https://gitorious.org/morpher/morpher/blobs/master/ACKNOWLEDGMENTS - https://gitorious.org/morpher/morpher/trees/master/data + \url{https://gitorious.org/morpher/morpher/blobs/master/ACKNOWLEDGMENTS} + + \url{https://gitorious.org/morpher/morpher/trees/master/data} \end{thebibliography} diff --git a/2012/morpher/tortechrep.cls b/2012/morpher/tortechrep.cls new file mode 120000 index 0000000..4c24db2 --- /dev/null +++ b/2012/morpher/tortechrep.cls @@ -0,0 +1 @@ +../../tortechrep.cls \ No newline at end of file

1 0

[tech-reports/master] Merge branch 'asn-report'
by karsten＠torproject.org 22 Aug '12

22 Aug '12

commit 24885cc6851d45dbab8be135dac8a91f7cf0413f Merge: df7b370 da2d794 Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Wed Aug 22 20:07:54 2012 +0200 Merge branch 'asn-report' 2012/morpher/.gitignore | 3 + 2012/morpher/500000_cs.pdf | Bin 0 -> 27094 bytes 2012/morpher/500000_sc.pdf | Bin 0 -> 25864 bytes 2012/morpher/https_cs.pdf | Bin 0 -> 20287 bytes 2012/morpher/morpher.bib | 44 +++++++ 2012/morpher/morpher.tex | 272 +++++++++++++++++++++++++++++++++++++++++++ 2012/morpher/tor_cs.pdf | Bin 0 -> 12335 bytes 2012/morpher/tortechrep.cls | 1 + 8 files changed, 320 insertions(+), 0 deletions(-)

1 0