tor-commits February 2012

tor-commits@lists.torproject.org

21 participants
991 discussions

[tor/master] whitespace fix
by arma＠torproject.org 29 Feb '12

29 Feb '12

commit c26aaf9cba8d40017c30b1921466759382032f33 Author: Roger Dingledine <arma(a)torproject.org> Date: Wed Feb 29 13:17:52 2012 -0500 whitespace fix --- src/or/policies.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/or/policies.c b/src/or/policies.c index e5062cd..5eaebfa 100644 --- a/src/or/policies.c +++ b/src/or/policies.c @@ -669,7 +669,7 @@ compare_unknown_tor_addr_to_addr_policy(uint16_t port, SMARTLIST_FOREACH_BEGIN(policy, addr_policy_t *, tmpe) { if (tmpe->prt_min <= port && port <= tmpe->prt_max) { - if (tmpe->maskbits == 0) { + if (tmpe->maskbits == 0) { /* Definitely matches, since it covers all addresses. */ if (tmpe->policy_type == ADDR_POLICY_ACCEPT) { /* If we already hit a clause that might trigger a 'reject', than we

1 0

[torspec/master] add xxx-pluggable-transports-through-proxy.txt by hellais
by ioerror＠torproject.org 29 Feb '12

29 Feb '12

commit 5b2b6b591ee436b9ff1e65247f4f32fe145c2c78 Author: Jacob Appelbaum <jacob(a)appelbaum.net> Date: Wed Feb 29 13:40:14 2012 -0400 add xxx-pluggable-transports-through-proxy.txt by hellais --- .../xxx-pluggable-transports-through-proxy.txt | 79 ++++++++++++++++++++ 1 files changed, 79 insertions(+), 0 deletions(-) diff --git a/proposals/ideas/xxx-pluggable-transports-through-proxy.txt b/proposals/ideas/xxx-pluggable-transports-through-proxy.txt new file mode 100644 index 0000000..221c0d1 --- /dev/null +++ b/proposals/ideas/xxx-pluggable-transports-through-proxy.txt @@ -0,0 +1,79 @@ +Filename: xxx-pluggable-transports-through-proxy.txt +Title: Pluggable Transport through SOCKS proxy +Author: Arturo Filastò +Created: 28 February 2012 +Status: Draft + +Overview + + Tor introduced Pluggable Transports in proposal 180 Pluggable Transports + for circumvention. + + The problem is that Tor currently cannot use a Pluggable Transport proxy + and a SOCKS proxy at the same time. This has been noticed by users in + #5195, where Tor would be failing saying "Unacceptable option value: + You have configured more than one proxy type". + + +Trivia + + This comes from a discussion that came up with Nick and I promised + to write a proposal for it if I wanted to hear what he had to say. + Nick spoke and I am writing this proposal. + +Acknowledgements + + Most of the credit goes to Nick Mathewson for the main idea and + the rest of it goes to George Kadianakis for helping me out in writing + it. + +Motivation + + After looking at some options we decided to go for this solution solution + since it guarantees backwards compatibility and is not particularly + costly to implement. + +Design overview + + When Tor is configured to use both a Pluggable Transport proxy and SOCKS + proxy it should delegate the proxying to the pluggable transport proxy. + + This can be achieved by setting the environment variables for the SOCKS + proxy to that specified inside of the torrc. + + When the pluggable transport proxy starts it will first read the environment + variables and if it detects that it should be using a SOCKS proxy make + all it's traffic go through it. Once the pluggable transport proxy has successfully + established a connection to the SOCKS proxy it should notify Tor of it's + success or failure. + When both the SOCKS and the PluggableTransport directives are set Tor + should set the environemnt variable start the pluggabletransport proxy and wait + for it to report back on the SOCKS proxy status. If the pluggable transport + reports back a failure or it does not report back at all (maybe because + it is an outdated version), Tor should notify the user of the failure + and exit with an error. + + + The environment variables can also contain the credentials for accessing + the proxy. + +Specifications: Tor Pluggable Transport communication + + When Tor detects a SOCKS proxy directive and a Pluggable Transport + proxy directive it sets the environment variable: + + "TOR_PT_PROXY" -- This is the address of the proxy to be used by + the pluggable transport proxy. It is in the format: + <proxy_type>://<user_name?>:<password?>@<ip>:<port> + ex. socks5://tor:test1234@198.51.100.1:8000 + socks4a://198.51.100.2:8001 + + + If the pluggable transport proxy detects that the TOR_PT_PROXY environment + variable is set it attempts connecting to it. On successs it will + write to stdout (as specified in 180-pluggable-transport.txt) + PROXY true. On failure it should write PROXY-ERROR <errormessage>. + + If Tor does not read any PROXY line or it reads a PROXY-ERROR line + and it is configured to use both SOCKS and PluggableTransport it should + exit with error.

1 0

[arm/master] Prevent crash on startup when reading Feb 29th in logs
by atagar＠torproject.org 29 Feb '12

29 Feb '12

commit a570d9f726473b47d48be4f912a8fa0c7bfd639f Author: Sebastian Hahn <sebastian(a)torproject.org> Date: Wed Feb 29 03:01:21 2012 +0100 Prevent crash on startup when reading Feb 29th in logs During prepopulation of log entries, arm tries to parse the date that Tor gives it. Unfortunately Python is a little (read: very) silly and refuses to accept that February 29th can be a valid day when information about the year is missing. As a solution, we just pretend it is the year 2012 forever when parsing dates from logs (Tor doesn't add the year to its date information). Fixes bug 5265, first reported by an anonymous user from IRC. --- src/cli/logPanel.py | 8 ++++++-- 1 files changed, 6 insertions(+), 2 deletions(-) diff --git a/src/cli/logPanel.py b/src/cli/logPanel.py index 179db9f..496fe86 100644 --- a/src/cli/logPanel.py +++ b/src/cli/logPanel.py @@ -302,8 +302,12 @@ def getLogFileEntries(runlevels, readLimit = None, addLimit = None, config = Non # overwrites missing time parameters with the local time (ignoring wday # and yday since they aren't used) - eventTimeComp = list(time.strptime(timestamp, "%b %d %H:%M:%S")) - eventTimeComp[0] = currentLocalTime.tm_year + # Pretend the year is 2012, because 2012 is a leap year, and parsing a + # date with strptime fails if Feb 29th is passed without a year that's + # actually a leap year. We can't just use the current year, because we + # might be parsing old logs which didn't get rotated. + timestamp = "2012 " + timestamp + eventTimeComp = list(time.strptime(timestamp, "%Y %b %d %H:%M:%S")) eventTimeComp[8] = currentLocalTime.tm_isdst eventTime = time.mktime(eventTimeComp) # converts local to unix time

1 0

[arm/master] Minor tweak to commenting around the leap year bug
by atagar＠torproject.org 29 Feb '12

29 Feb '12

commit f2080aad4e069074c8c7320970b51892def719fc Author: Damian Johnson <atagar(a)torproject.org> Date: Wed Feb 29 07:35:00 2012 -0800 Minor tweak to commenting around the leap year bug Tweak for the preceeding comment and including the ticket with the comment. --- src/cli/logPanel.py | 7 +++++-- 1 files changed, 5 insertions(+), 2 deletions(-) diff --git a/src/cli/logPanel.py b/src/cli/logPanel.py index 496fe86..dd22558 100644 --- a/src/cli/logPanel.py +++ b/src/cli/logPanel.py @@ -300,12 +300,15 @@ def getLogFileEntries(runlevels, readLimit = None, addLimit = None, config = Non # strips the decimal seconds if "." in timestamp: timestamp = timestamp[:timestamp.find(".")] - # overwrites missing time parameters with the local time (ignoring wday - # and yday since they aren't used) + # Ignoring wday and yday since they aren't used. + # # Pretend the year is 2012, because 2012 is a leap year, and parsing a # date with strptime fails if Feb 29th is passed without a year that's # actually a leap year. We can't just use the current year, because we # might be parsing old logs which didn't get rotated. + # + # https://trac.torproject.org/projects/tor/ticket/5265 + timestamp = "2012 " + timestamp eventTimeComp = list(time.strptime(timestamp, "%Y %b %d %H:%M:%S")) eventTimeComp[8] = currentLocalTime.tm_isdst

1 0

[translation/vidalia_help] Update translations for vidalia_help
by translation＠torproject.org 29 Feb '12

29 Feb '12

commit 2334ad66ac39ef441adc8d98cd78026c34ea242d Author: Translation commit bot <translation(a)torproject.org> Date: Wed Feb 29 15:15:19 2012 +0000 Update translations for vidalia_help --- el/troubleshooting.po | 20 ++++++++++---------- 1 files changed, 10 insertions(+), 10 deletions(-) diff --git a/el/troubleshooting.po b/el/troubleshooting.po index 0af8acc..c467709 100644 --- a/el/troubleshooting.po +++ b/el/troubleshooting.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-08-03 15:49-0300\n" -"PO-Revision-Date: 2012-02-29 14:42+0000\n" +"PO-Revision-Date: 2012-02-29 14:50+0000\n" "Last-Translator: isv31 <ix4svs(a)gmail.com>\n" "Language-Team: LANGUAGE <LL(a)li.org>\n" "MIME-Version: 1.0\n" @@ -62,7 +62,7 @@ msgstr "Αν αυτό δε βοήθησε, ελέγξτε τη <a href=\"log.htm # type: Content of: <html><body> #: en/troubleshooting.html:43 msgid "<a name=\"connect\"/>" -msgstr "<a name=\"σύνδεση\"/>" +msgstr "<a name=\"connect\"/>" # type: Content of: <html><body><h3> #: en/troubleshooting.html:44 @@ -98,7 +98,7 @@ msgstr "Αν το Tor περιμένει συνδέσεις σε διαφορε # type: Content of: <html><body> #: en/troubleshooting.html:63 msgid "<a name=\"password\"/>" -msgstr "<a name=\"κωδικός\"/>" +msgstr "<a name=\"password\"/>" # type: Content of: <html><body><h3> #: en/troubleshooting.html:64 @@ -156,7 +156,7 @@ msgid "" "Tor for you, you can still fix the problem manually. Simply go into your " "process or task manager, and terminate the Tor process. Then use Vidalia to " "restart Tor and all will work again." -msgstr "" +msgstr "Αν δε βλέπετε το κουμπί Επαναφορά, ή αν το Vidalia δε μπορεί να επανεκκινήσει το Tor, μπορείτε να διορθώσετε το πρόβλημα χειροκίνητα. Ανοίξτε τη λίστα/διαχείρηση διεργασιών και τερματίστε τη διεργασία του Tor. Μετά επανεκκινήστε το Tor με το Vidalia - όλα πρέπει να είναι εντάξει τώρα." # type: Content of: <html><body><ul><li> #: en/troubleshooting.html:106 @@ -182,12 +182,12 @@ msgstr "" # type: Content of: <html><body> #: en/troubleshooting.html:122 msgid "<a name=\"torexited\"/>" -msgstr "" +msgstr "<a name=\"torexited\"/>" # type: Content of: <html><body><h3> #: en/troubleshooting.html:123 msgid "Tor Exited Unexpectedly" -msgstr "" +msgstr "Το Tor σταμάτησε απροσδόκητα" # type: Content of: <html><body> #: en/troubleshooting.html:125 @@ -204,7 +204,7 @@ msgstr "" msgid "" "connection_create_listener(): Could not bind to 127.0.0.1:9050: Address already in use. \n" "Is Tor already running?\n" -msgstr "" +msgstr "connection_create_listener(): Could not bind to 127.0.0.1:9050: Address already in use. \nIs Tor already running?\n" # type: Content of: <html><body> #: en/troubleshooting.html:135 @@ -228,12 +228,12 @@ msgstr "" # type: Content of: <html><body> #: en/troubleshooting.html:147 msgid "<a name=\"stop\"/>" -msgstr "" +msgstr "<a name=\"stop\"/>" # type: Content of: <html><body><h3> #: en/troubleshooting.html:148 msgid "Vidalia Can't Stop Tor" -msgstr "" +msgstr "Το Vidalia δε μπορεί να σταματήσει το Tor" # type: Content of: <html><body> #: en/troubleshooting.html:150 @@ -241,4 +241,4 @@ msgid "" "If Vidalia cannot stop Tor, you should check your <a " "href=\"log.html\">message log</a> to see if Tor reported any errors while " "trying to exit." -msgstr "" +msgstr "Αν το Vidalia δε μπορεί να σταματήσει το Tor, ελέγξτε τα <a href=\"log.html\">μηνύματα συστήματος</a> για να δείτε αν το Tor κατέγραψε λάθη ενώ προσπαθούσε να σταματήσει."

1 0

[translation/vidalia_help] Update translations for vidalia_help
by translation＠torproject.org 29 Feb '12

29 Feb '12

commit dd9c01a273f2990a33da8e72b636f0ad99f9aa21 Author: Translation commit bot <translation(a)torproject.org> Date: Wed Feb 29 14:45:21 2012 +0000 Update translations for vidalia_help --- el/troubleshooting.po | 14 +++++++------- 1 files changed, 7 insertions(+), 7 deletions(-) diff --git a/el/troubleshooting.po b/el/troubleshooting.po index 15a5cc6..0af8acc 100644 --- a/el/troubleshooting.po +++ b/el/troubleshooting.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-08-03 15:49-0300\n" -"PO-Revision-Date: 2012-02-28 15:05+0000\n" +"PO-Revision-Date: 2012-02-29 14:42+0000\n" "Last-Translator: isv31 <ix4svs(a)gmail.com>\n" "Language-Team: LANGUAGE <LL(a)li.org>\n" "MIME-Version: 1.0\n" @@ -41,7 +41,7 @@ msgid "" "is looking for your Tor installation in the wrong directory. You can tell " "Vidalia where Tor is located by updating the Tor Executable option in" " the <a href=\"config.html#general\">general configuration settings</a>." -msgstr "Συνήθως ο λόγος που το Vidalia δε μπορεί να ξεκινήσει το Tor είναι διότι το Vidalia ψάχνει για την εγκατάσταση του Tor σε λανθασμένη τοποθεσία. Μπορείτε να πείτε στο Vidalia πού να βρει το Tor συμπληρώνοντας την επιλογή Tor Executable στις <a href=\"config.html#general\">γενικές ρυθμίσεις</a>." +msgstr "Συνήθως ο λόγος που το Vidalia δε μπορεί να ξεκινήσει το Tor είναι διότι το Vidalia ψάχνει για την εγκατάσταση του Tor σε λανθασμένη τοποθεσία. Μπορείτε να πείτε στο Vidalia πού να βρει το Tor συμπληρώνοντας το πεδίο Tor Executable στις <a href=\"config.html#general\">γενικές ρυθμίσεις</a>." # type: Content of: <html><body> #: en/troubleshooting.html:33 @@ -114,7 +114,7 @@ msgid "" "Vidalia sets a random password for Tor's control port to prevent other " "applications from also connecting to the control port and potentially " "compromising your anonymity." -msgstr "" +msgstr "Το Vidalia δουλεύει με το Tor μέσω της \"θύρας ελέγχου\" του Tor. Η θύρα ελέγχου επιτρέπει στο Vidalia να ενημερώνεται για τη κατάσταση του Tor, να ζητάει νέα ταυτότητα, να ρυθμίζει τις ρυθμίσεις του Tor κτλ. Κάθε φορά που το Vidalia ξεκινάει το Tor, το Vidalia επιλέγει ένα τυχαίο κωδικό για τη θύρα ελέγχου του Tor, ώστε να μην επιτρέπει σε άλλες εφαρμογές να συνδεθούν στη θύρα ελέγχου και να διακινδυνεύσουν την ανωνυμία σας." # type: Content of: <html><body> #: en/troubleshooting.html:75 @@ -122,7 +122,7 @@ msgid "" "Usually this process of generating and setting a random control password " "happens in the background. There are three common situations, though, where " "Vidalia may prompt you for a password:" -msgstr "" +msgstr "Συνήθως αυτή η διαδικασία δημιουργίας και χρήσης ενός τυχαίου κωδικού ελέγχου συμβαίνει στο παρασκήνιο. Υπάρχουν τρεις περιπτώσεις όμως, στις οποίες το Vidalia μπορεί να σας ζητήσει κάποιο κωδικό." # type: Content of: <html><body><ul><li> #: en/troubleshooting.html:82 @@ -131,7 +131,7 @@ msgid "" "happen if you installed the Vidalia bundle and now you're trying to run the " "Tor Browser Bundle. In that case, you'll need to close the old Vidalia and " "Tor before you can run this one." -msgstr "" +msgstr "Τρέχετε ήδη το Vidalia και το Tor. Για παράδειγμα, αυτό μπορεί να συμβεί αν έχετε εγκαταστήσει το πακέτο του Vidalia και τώρα προσπαθείτε να εκτελέσετε το πακέτο Tor Browser. Σε αυτή τη περίπτωση θα πρέπει να τερματίσετε το παλιό Vidalia και το Tor πριν το εκτελέσετε εκ νέου." # type: Content of: <html><body><ul><li> #: en/troubleshooting.html:89 @@ -139,7 +139,7 @@ msgid "" "Vidalia crashed, but left Tor running with the last known random password. " "After you restart Vidalia, it generates a new random password, but Vidalia " "can't talk to Tor, because the random passwords are different." -msgstr "" +msgstr "Το Vidalia κατέρρευσε ή κόλλησε, αλλά άφησε το Tor να τρέχει στο παρασκήνιο με το παλιό τυχαίο κωδικό. Μόλις επανεκκινήσετε το Vidalia δημιουργεί νέο τυχαίο κωδικό, αλλά το Vidalia δε μπορεί να επικοινωνήσει με το Tor επειδή οι δύο κωδικοί είναι διαφορετικοί." # type: Content of: <html><body><ul><li> #: en/troubleshooting.html:94 @@ -147,7 +147,7 @@ msgid "" "If the dialog that prompts you for a control password has a Reset " "button, you can click the button and Vidalia will restart Tor with a new " "random control password." -msgstr "" +msgstr "Αν το παράθυρο διαλόγου που σας ζητάει τον κωδικό ελέγχου έχει ένα κουμπί Επαναφορά, μπορείτε να το πατήσετε και το Vidalia θα επανεκκινήσει το Tor με ένα νέο τυχαίο κωδικό ελέγχου." # type: Content of: <html><body><ul><li> #: en/troubleshooting.html:99

1 0

[tor-cloud/master] We now have images for private bridges
by runa＠torproject.org 29 Feb '12

29 Feb '12

commit 9c3e413e5fa9300898b170afd0a08eda2cd71753 Author: Runa A. Sandvik <runa.sandvik(a)gmail.com> Date: Wed Feb 29 13:24:03 2012 +0000 We now have images for private bridges --- html/index.html | 40 +++++++++++++++++++++++++++++----------- 1 files changed, 29 insertions(+), 11 deletions(-) diff --git a/html/index.html b/html/index.html index 2e84c35..9cea8a5 100644 --- a/html/index.html +++ b/html/index.html @@ -134,18 +134,29 @@ Console. See How much does it cost? on the <a href="https://cloud.torproject.org/">front page</a> for information about pricing. - + <h3>Normal bridges</h3> <ul class="region-nav"> <li><a class="region" href="https://console.aws.amazon.com/ec2/home?region=us-east-1#launchAmi=ami-302a…" target="_blank">us-east-1 Virginia</a></li> <li><a class="region" href="https://console.aws.amazon.com/ec2/home?region=us-west-1#launchAmi=ami-85cd…" target="_blank">us-west-1 N. California</a></li> <li><a class="region" href="https://console.aws.amazon.com/ec2/home?region=us-west-2#launchAmi=ami-4a1f…" target="_blank">us-west-2 Oregon</a></li> - <li><a class="region" href="https://console.aws.amazon.com/ec2/home?region=eu-west-1#launchAmi=ami-0123…" target="_blank">eu-west-1 Ireland</a></li> - <li><a class="region" href="https://console.aws.amazon.com/ec2/home?region=ap-northeast-1#launchAmi=ami…" target="_blank">ap-northeast-1 Tokyo</a></li> - <li><a class="region" href="https://console.aws.amazon.com/ec2/home?region=ap-southeast-1#launchAmi=ami…" target="_blank">ap-southeast-1 Singapore</a></li> + <li><a class="region" href="https://console.aws.amazon.com/ec2/home?region=ap-northeast-1#launchAmi=ami…" target="_blank">ap-northeast-1 Tokyo</a></li> + <li><a class="region" href="https://console.aws.amazon.com/ec2/home?region=ap-southeast-1#launchAmi=ami…" target="_blank">ap-southeast-1 Singapore</a></li> <li><a class="region" href="https://console.aws.amazon.com/ec2/home?region=sa-east-1#launchAmi=ami-c06c…" target="_blank">sa-east-1 Sao Paulo</a></li> - </ul> + </ul> + <h3>Private bridges</h3> + <ul class="region-nav"> + <li><a class="region" href="https://console.aws.amazon.com/ec2/home?region=us-east-1#launchAmi=ami-ce62…" target="_blank">us-east-1 Virginia</a></li> + <li><a class="region" href="https://console.aws.amazon.com/ec2/home?region=us-west-1#launchAmi=ami-2bf8…" target="_blank">us-west-1 N. California</a></li> + <li><a class="region" href="https://console.aws.amazon.com/ec2/home?region=us-west-2#launchAmi=ami-4018…" target="_blank">us-west-2 Oregon</a></li> + <li><a class="region" href="https://console.aws.amazon.com/ec2/home?region=eu-west-1#launchAmi=ami-f512…" target="_blank">eu-west-1 Ireland</a></li> + + <li><a class="region" href="https://console.aws.amazon.com/ec2/home?region=ap-northeast-1#launchAmi=ami…" target="_blank">ap-northeast-1 Tokyo</a></li> + <li><a class="region" href="https://console.aws.amazon.com/ec2/home?region=ap-southeast-1#launchAmi=ami…" target="_blank">ap-southeast-1 Singapore</a></li> + <li><a class="region" href="https://console.aws.amazon.com/ec2/home?region=sa-east-1#launchAmi=ami-de6a…" target="_blank">sa-east-1 Sao Paulo</a></li> + </ul> + <hgroup> <div class="deco"></div> @@ -262,6 +273,12 @@ <h2>Frequently Asked Questions (FAQ)</h2> </hgroup> + 0. Private bridge or normal bridge? + If you set up a private bridge, your bridge will not tell the bridge + authority that it exists. You will have to manually give out your bridge + address to users. + + 1. How much does it cost? There is no fee charged by the Tor Project, Inc for you to run a Tor Cloud image. Amazon does, however, charge instances @@ -273,10 +290,10 @@ 2. The instance is running, what's next? You should not have to do anything once the instance is up and - running. Tor will start up as a bridge, confirm that it is reachable - from the outside, and then tell the bridge authority that it exists. - After that, the address for your bridge will be given out to - users. + running. Tor will start up as a bridge and confirm that it is reachable + from the outside. If you have set up a normal bridge, then it will also + tell the bridge authority that it exists, and the address for your + bridge will be given out to users. 3. How do I find the address of my bridge? To find the address of your bridge, log on to the AWS Management @@ -327,8 +344,9 @@ href="http://www.atagar.com/arm/">here</a>. 9. What's in the Tor configuration file? - The Tor configuration file that the images have been - configured with can be found <a href="https://cloud.torproject.org/torrc.txt">here</a>. + The Tor configuration file for normal bridges can be found <a + href="https://cloud.torproject.org/torrc.txt">here</a>. The configuration + file for private bridges also contain PublishServerDescriptor 0. 10. Will the images automatically download and install package updates? Yes, the images have all been configured with the <a href="https://help.ubuntu.com/community/AutomaticSecurityUpdates">unattended-upgrades</a> package. This means that your system will automatically download and install updates.

1 0

[onionoo/master] Make protocol page the new index.html.
by karsten＠torproject.org 29 Feb '12

29 Feb '12

commit 75465e3584c9e8db2ca132ae5b260f7016298786 Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Wed Feb 29 13:13:09 2012 +0100 Make protocol page the new index.html. --- web/css/stylesheet-ltr.css | 34 +++ web/index.html | 602 ++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 636 insertions(+), 0 deletions(-) diff --git a/web/css/stylesheet-ltr.css b/web/css/stylesheet-ltr.css new file mode 100644 index 0000000..e3c07d5 --- /dev/null +++ b/web/css/stylesheet-ltr.css @@ -0,0 +1,34 @@ +body { + background-color: white; + font-family: Arial, Helvetica, sans-serif; + font-size: 1em; + font-style: normal; + color: #000000; + padding-top: 0px; + background-color: white; + margin: 0px auto 0 auto; + width: 85%; + padding: 15px 0 10px 10px; + text-indent: 0pt; + direction: ltr; + text-align: left; +} + +h2 { + font-size: 1.4em; + font-weight: bold; +} + +h3 { + font-size: 1.2em; + font-weight: bold; +} + +li { + margin: .2em .2em .2em 1em; +} + +img { + margin: .2em .2em .2em .2em; +} + diff --git a/web/index.html b/web/index.html new file mode 100755 index 0000000..3199ea5 --- /dev/null +++ b/web/index.html @@ -0,0 +1,602 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> +<html> +<head> +<title>Onionoo — a Tor network status protocol</title> +<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> +<link href="css/stylesheet-ltr.css" type="text/css" rel="stylesheet"> +</head> +<body> +<h3>Onionoo protocol overview</h3> +The Onionoo service is designed as a RESTful web service. +Onionoo clients send HTTP GET requests to the Onionoo server which +responds with JSON-formatted replies. +Onionoo clients and their developers should follow a few rules: +<ul> +<li>Compression: Clients should include an "Accept-Encoding: +gzip" header in their requests and handle gzip-compressed responses. +Only requests starting at a certain size will be compressed by the +server.</li> +<li>Caching: Clients should cache all responses for up to five +minutes. +A better caching strategy may be employed in the future that will be based +on the server's information when new data is expected to be +available.</li> +<li>Protocol changes: There are plenty of reasons why we may have +to change the protocol described here. +Clients should be able to handle all valid JSON responses, ignoring +unknown fields and not breaking horribly in case of missing fields. +Protocol changes will be announced here by writing deprecated API parts in +red and new parts in +blue. +Deprecated parts will be removed one month after their announcement. +Let us <a href="mailto:karsten.loesing@gmx.net">know</a> that you're +developing a client, and we're going to inform you of upcoming protocol +changes. +</li> +</ul> +The Onionoo API is described by resource types and available methods +below. + +<h3>Summary documents</h3> +Summary documents contain short summaries of relays with nicknames, +fingerprints, IP addresses, and running information as well as bridges +with hashed fingerprints and running information. +Summary documents contain the following fields: +<ul> +<li>"version": Version number of this +document. +Deprecated field. +Deploying a versioning scheme to this service seems like overkill. +Picking new field names and deprecating fields after one month means a lot +less maintenance overhead. +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"valid_after": UTC timestamp +(YYYY-MM-DD hh:mm:ss) when the contents of this document were generated. +Deprecated field. +This field was a quite broken way to implement caching. +The current caching approach is to have clients cache documents for five +minutes. +A future caching mechanism is going to use HTTP headers. +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"fresh_until": UTC timestamp +(YYYY-MM-DD hh:mm:ss) until when the contents of this document shall be +considered fresh. +Deprecated field. +This field was a quite broken way to implement caching. +The current caching approach is to have clients cache documents for five +minutes. +A future caching mechanism is going to use HTTP headers. +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"relays_published": UTC timestamp (YYYY-MM-DD hh:mm:ss) when +the last contained relay network status consensus started being valid. +Indicates how recent the relay summaries in this document are. +Required field.</li> +<li>"relays": Array of objects representing relay summaries. +Required field. +Each array object contains the following key-value pairs: +<ul> +<li>"n": Relay nickname consisting of 1–19 alphanumerical +characters. +Optional field. +Omitted if the relay nickname is "Unnamed".</li> +<li>"f": Relay fingerprint consisting of 40 upper-case hexadecimal +characters. +Required field.</li> +<li>"a": Array of IPv4 or IPv6 addresses where the relay accepts +onion-routing connections. +Required field.</li> +<li>"r": Boolean field saying whether this relay was listed as +running in the last relay network status consensus. +Required field.</li> +</ul> +</li> +<li>"bridges_published": UTC timestamp (YYYY-MM-DD hh:mm:ss) when +the last contained bridge network status was published. +Indicates how recent the bridge summaries in this document are. +Required field.</li> +<li>"bridges": Array of objects representing bridge summaries. +Required field. +Each array object contains the following key-value pairs: +<ul> +<li>"h": SHA-1 hash of the bridge fingerprint consisting of 40 +upper-case hexadecimal characters. +Required field.</li> +<li>"r": Boolean field saying whether this bridge was listed as +running in the last bridge network status. +Required field.</li> +</ul> +</ul> +The following methods are available that all return a single summary +document. +The method and its parameters determines which relay and/or bridge +summaries are included in the response. +<table border="0" cellpadding="4" cellspacing="0" summary=""> +<colgroup> +<col width="350"> +<col width="650"> +</colgroup> +<tr> +<td>GET summary/all</td> +<td>Return summaries of all relays and bridges that are currently running +or that have been running in the past week.</td> +</tr> +<tr> +<td>GET summary/running</td> +<td>Return summaries of all relays and bridges that are currently +running.</td> +</tr> +<tr> +<td>GET summary/relays</td> +<td>Return summaries of all relays that are currently running or that have +been running in the past week, but don't include any bridges.</td> +</tr> +<tr> +<td>GET summary/bridges</td> +<td>Return summaries of all bridges that are currently running or that +have been running in the past week, but don't include any relays.</td> +</tr> +<tr> +<td>GET summary/search/:searchtext</td> +<td>Return summaries of all relays and bridges with :searchtext +matching the beginning of a nickname, (possibly +$-prefixed) fingerprint, IP address, or (possibly $-prefixed) hashed fingerprint. +Added the option to search for $-prefixed (hashed) fingerprints on +February 25, 2012. +Searches are case-insensitive.</td> +</tr> +<tr> +<td>GET summary/lookup/:fingerprint</td> +<td>Return the summary of the relay or bridge with :fingerprint +matching the fingerprint or hashed fingerprint.</td> +</tr> +</table> + +<h3>Detail documents</h3> +Detail documents contain all known details of relays and bridges that +have been running in the past week. +Detail documents are based on the network statuses published by the Tor +directories and the server descriptors published by relays and bridges. +Detail documents contain the following fields: +<ul> +<li>"version": Version number of this +document. +Deprecated field. +Deprecated for the same reason as stated for summary documents. +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"valid_after": UTC timestamp +(YYYY-MM-DD hh:mm:ss) when the contents of this document were generated. +Deprecated field. +Deprecated for the same reason as stated for summary documents. +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"fresh_until": UTC timestamp +(YYYY-MM-DD hh:mm:ss) until when the contents of this document shall be +considered fresh. +Deprecated field. +Deprecated for the same reason as stated for summary documents. +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"relays_published": UTC timestamp (YYYY-MM-DD hh:mm:ss) when +the last contained relay network status consensus started being valid. +Indicates how recent the relay details in this document are. +Required field.</li> +<li>"relays": Array of objects representing relay details. +Required field. +Each array object contains the following key-value pairs: +<ul> +<li>"nickname": Relay nickname consisting of 1–19 +alphanumerical characters. +Optional field. +Omitted if the relay nickname is "Unnamed".</li> +<li>"fingerprint": Relay fingerprint consisting of 40 upper-case +hexadecimal characters. +Required field.</li> +<li>"or_address": Array of IPv4 or IPv6 +addresses where the relay accepts onion-routing connections. +Deprecated field. +Deprecated, because a relay can have a different onion-routing port for +each onion-routing IP address. +Combining address and port in a single string solves this; see +"or_addresses" below. +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"or_port": Onion-routing port. +Deprecated field. +Deprecated, because a relay can have a different onion-routing port for +each onion-routing IP address. +Combining address and port in a single string solves this; see +"or_addresses" below. +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"or_addresses": Array of IPv4 or IPv6 addresses and TCP ports +or port lists where the relay accepts onion-routing connections. +Required field.</li> +<li>"exit_addresses": Array of IPv4 or IPv6 addresses and TCP ports +or port lists that the relay used to exit to the Internet in the past 24 +hours. +Only those addresses are listed that are different from onion-routing +addresses. +Optional field. +Omitted if array is empty.</li> +<li>"dir_port": Directory port. +Deprecated field. +Deprecated, because it's not clear which IP address the directory port +belongs to if there are more than one entries in "or_addresses". +Replaced by "dir_address". +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"dir_address": IPv4 address and TCP port where the relay +accepts directory connections. +Optional field. +Omitted if the relay does not accept directory connections.</li> +<li>"running": Boolean field saying whether this relay was listed as +running in the last relay network status consensus. +Required field.</li> +<li>"flags": Array of relay flags that the directory authorities +assigned to this relay. +Optional field. +Omitted if empty.</li> +<li>"country": Two-letter lower-case country code as found in a +GeoIP database by resolving the relay's first onion-routing IP address. +Optional field. +Omitted if the relay IP address could not be found in the GeoIP +database.</li> +<li>"country_name": Country name as found +in a GeoIP database by resolving the relay's first onion-routing IP +address. +Optional field. +Omitted if the relay IP address could not be found in the GeoIP database. +Added on February 28, 2012.</li> +<li>"region_name": Region name as found +in a GeoIP database by resolving the relay's first onion-routing IP +address. +Optional field. +Omitted if the relay IP address could not be found in the GeoIP database. +Added on February 28, 2012.</li> +<li>"city_name": City name as found in a +GeoIP database by resolving the relay's first onion-routing IP address. +Optional field. +Omitted if the relay IP address could not be found in the GeoIP database. +Added on February 28, 2012.</li> +<li>"latitude": Latitude as found in a +GeoIP database by resolving the relay's first onion-routing IP address. +Optional field. +Omitted if the relay IP address could not be found in the GeoIP database. +Added on February 11, 2012.</li> +<li>"longitude": Longitude as found in a +GeoIP database by resolving the relay's first onion-routing IP address. +Optional field. +Omitted if the relay IP address could not be found in the GeoIP database. +Added on February 11, 2012.</li> +<li>"as_number": AS number as found in an +AS database by resolving the relay's first onion-routing IP address. +Optional field. +Omitted if the relay IP address could not be found in the AS database. +Added on February 28, 2012.</li> +<li>"as_name": AS name as found in an AS +database by resolving the relay's first onion-routing IP address. +Optional field. +Omitted if the relay IP address could not be found in the AS database. +Added on February 28, 2012.</li> +<li>"desc_published": UTC timestamp +(YYYY-MM-DD hh:mm:ss) when the relay last published a descriptor. +Deprecated field. +Deprecated, because this information is only useful to calculate the last +restart time of the relay, together with "uptime". +We can as well provide that time directly in "last_restarted". +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"uptime" Uptime of the relay when +publishing its last descriptor. +Deprecated field. +Deprecated, because this information is only useful to calculate the last +restart time of the relay, together with "desc_published". +Even worse, it may be mistaken for the current uptime of the relay at the +time of publishing this detail document. +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"last_restarted": UTC timestamp (YYYY-MM-DD hh:mm:ss) when the +relay was last (re-)started. +Required field.</li> +<li>"advertised_bandwidth": Bandwidth in bytes per second that this +relay is willing and capable to provide. +Required field.</li> +<li>"exit_policy": Array of exit-policy lines. +Required field.</li> +<li>"contact": Contact address of the relay operator. +Omitted if empty.</li> +<li>"platform": Platform string containing operating system and Tor +version details. +Optional field. +Omitted if empty.</li> +<li>"family": Array of fingerprints or nicknames of relays in the +same family as this relay. +Optional field. +Omitted if empty.</li> +</ul> +</li> +<li>"bridges_published": UTC timestamp (YYYY-MM-DD hh:mm:ss) when +the last contained bridge network status was published. +Indicates how recent the bridge details in this document are. +Required field.</li> +<li>"bridges": Array of objects representing bridge summaries. +Required field. +Each array object contains the following key-value pairs: +<ul> +<li>"hashed_fingerprint": SHA-1 hash of the bridge fingerprint +consisting of 40 upper-case hexadecimal characters. +Required field.</li> +<li>"or_port": TCP port where the bridge +accepts onion-routing connections. +Deprecated field. +Deprecated, because a bridge can use a different port for each +onion-routing address. +Replaced with "or_addresses". +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"or_addresses": Array of sanitized IPv4 or IPv6 addresses and +TCP ports or port lists where the bridge accepts onion-routing +connections. +Sanitized IP addresses are always in 10/8 or +[fd9f:2e19:3bcf/48] IP networks and are only useful to learn which +IP version the bridge uses and to detect whether the bridge changed its +address. +Sanitized IP addresses always change on the 1st of every month at 00:00:00 +UTC, regardless of the bridge actually changing its IP address. +TCP ports are not sanitized. +Required field.</li> +<li>"dir_port": TCP port where the bridge +accepts directory connections. +Deprecated field. +Deprecated, because bridges don't act as directory mirrors and only have a +non-zero directory port if they're misconfigured. +Even then, the directory port number is not relevant. +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"running": Boolean field saying whether this bridge was listed +as running in the last bridge network status. +Required field.</li> +<li>"flags": Array of relay flags that the bridge authority +assigned to this bridge. +Optional field. +Omitted if empty.</li> +<li>"desc_published": UTC timestamp +(YYYY-MM-DD hh:mm:ss) when the bridge last published a descriptor. +Deprecated field. +Deprecated, because this information is only useful to calculate the last +restart time of the bridge, together with "uptime". +We can as well provide that time directly in "last_restarted". +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"uptime" Uptime of the bridge when +publishing its last descriptor. +Deprecated field. +Deprecated, because this information is only useful to calculate the last +restart time of the bridge, together with "desc_published". +Even worse, it may be mistaken for the current uptime of the bridge at the +time of publishing this detail document. +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"last_restarted": UTC timestamp (YYYY-MM-DD hh:mm:ss) when the +bridge was last (re-)started. +Required field.</li> +<li>"advertised_bandwidth": Bandwidth in bytes per second that this +bridge is willing and capable to provide. +Required field.</li> +<li>"exit_policy": Array of exit-policy +lines. +Deprecated field. +Deprecated, because exit policies are not relevant for bridges and only +indicate a (harmless) misconfiguration. +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"platform": Platform string containing operating system and Tor +version details. +Omitted if not provided by the bridge.</li> +<li>"family": Array of hashed fingerprints +or "Unnamed" nicknames of relays or bridges in the same family as this +bridge. +Deprecated field. +Deprecated, because node families are not relevant for bridges and only +indicate a (harmless) misconfiguration. +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"pool_assignment": Information of the pool that BridgeDB +assigned this bridge to, including further assignment information if +available. +Optional field.</li> +</ul> +</li> +</ul> +The following methods are available that all return a single details +document. +The method and its parameters determines which relay and/or bridge +details are included in the response. +<table border="0" cellpadding="4" cellspacing="0" summary=""> +<colgroup> +<col width="350"> +<col width="650"> +</colgroup> +<tr> +<td>GET details/all</td> +<td>Return details of all relays and bridges that are currently running +or that have been running in the past week.</td> +</tr> +<tr> +<td>GET details/running</td> +<td>Return details of all relays and bridges that are currently +running.</td> +</tr> +<tr> +<td>GET details/relays</td> +<td>Return details of all relays that are currently running or that have +been running in the past week, but don't include any bridges.</td> +</tr> +<tr> +<td>GET details/bridges</td> +<td>Return details of all bridges that are currently running or that have +been running in the past week, but don't include any relays.</td> +</tr> +<tr> +<td>GET details/search/:searchtext</td> +<td>Return details of all relays and bridges with :searchtext +matching the beginning of a nickname, (possibly +$-prefixed) fingerprint, IP address, or (possibly $-prefixed) hashed fingerprint. +Added the option to search for $-prefixed (hashed) fingerprints on +February 25, 2012. +Searches are case-insensitive.</td> +</tr> +<tr> +<td>GET details/lookup/:fingerprint</td> +<td>Return the details of the relay or bridge with :fingerprint +matching the fingerprint or hashed fingerprint.</td> +</tr> +</table> + +<h3>Bandwidth documents</h3> +Bandwidth documents contain aggregate statistics of a relay's or +bridge's consumed bandwidth for different time intervals. +Bandwidth documents are available for all relays and bridges that have +been running in the past week. +Bandwidth documents contain the following fields: +<ul> +<li>"version": Version number of this +document. +Deprecated field. +Deprecated for the same reason as stated for summary documents. +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"valid_after": UTC timestamp +(YYYY-MM-DD hh:mm:ss) when the contents of this document were generated. +Deprecated field. +Deprecated for the same reason as stated for summary documents. +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"fresh_until": UTC timestamp +(YYYY-MM-DD hh:mm:ss) until when the contents of this document shall be +considered fresh. +Deprecated field. +Deprecated for the same reason as stated for summary documents. +Announced on January 26, will be removed after March 4, 2012.</li> +<li>"relays_published": UTC timestamp (YYYY-MM-DD hh:mm:ss) when +the last contained relay network status consensus started being valid. +Indicates how recent the relay bandwidth documents in this document are. +Required field.</li> +<li>"relays": Array of objects representing relay bandwidth +documents. +Required field. +Each array object contains the following key-value pairs: +<ul> +<li>"fingerprint": Relay fingerprint consisting of 40 upper-case +hexadecimal characters. +Required field.</li> +<li>"write_history": Object containing bandwidth history objects +for different time periods. +Required field. +Keys are string representation of the time period covered by the bandwidth +history object. +Keys are fixed strings "3_days", "1_week", "1_month", +"3_months", "1_year", and "5_years". +Keys refer to the last known bandwidth history of a relay, not to the time +when the bandwidth document was published. +A bandwidth history object is only contained if the time +period it covers is not already contained in another bandwidth history +object with shorter time period and higher data resolution. +(Announced on February 13, redundant bandwidth history objects will be +removed after March 13, 2012.) +Each bandwidth history object contains the following key-value pairs: +<ul> +<li>"first": UTC timestamp (YYYY-MM-DD hh:mm:ss) of the first data +data point in the bandwidth history. +Required field.</li> +<li>"last": UTC timestamp (YYYY-MM-DD hh:mm:ss) of the last data +data point in the bandwidth history. +Required field.</li> +<li>"interval": Time interval between two data points in seconds. +Required field.</li> +<li>"factor": Factor by which subsequent bandwidth values need to +be multiplied to get a unit of bytes per second. +The idea is that contained bandwidth values are normalized to a range from +0 to 999 to reduce document size while still providing sufficient detail +for both slow and fast relays. +Required field.</li> +<li>"count": Number of provided data points, included mostly for +debugging purposes. +Can also be derived from the number of elements in the subsequent array. +Optional field.</li> +<li>"values": Array of normalized bandwidth values in bytes per +second. +May contain null values if the relay did not provide any bandwidth data or +only data for less than 20% of a given time period. +Only includes non-null values for series of at least two subsequent data +points to enable drawing of line graphs. +Required field.</li> +</ul> +</li> +<li>"read_history": Object containing bandwidth history objects +for different time periods. +Required field. +The specification of bandwidth history objects is similar to those in the +write_history field.</li> +</ul> +</li> +<li>"bridges_published": UTC timestamp (YYYY-MM-DD hh:mm:ss) when +the last contained bridge network status was published. +Indicates how recent the bridge bandwidth documents in this document are. +Required field.</li> +<li>"bridges": Array of objects representing bridge bandwidth +documents. +Required field. +Each array object contains the following key-value pairs: +<ul> +<li>"fingerprint": SHA-1 hash of the bridge fingerprint consisting +of 40 upper-case hexadecimal characters. +Required field.</li> +<li>"write_history": Object containing bandwidth history objects +for different time periods. +Required field. +The specification of bandwidth history objects is similar to those in the +write_history field of relays.</li> +<li>"read_history": Object containing bandwidth history objects +for different time periods. +Required field. +The specification of bandwidth history objects is similar to those in the +write_history field of relays.</li> +</ul> +</li> +</ul> +The following methods are available that all return a single document. +The method and its parameters determines which relay and/or bridge +bandwidth documents are included in the response. +<table border="0" cellpadding="4" cellspacing="0" summary=""> +<colgroup> +<col width="350"> +<col width="650"> +</colgroup> +<tr> +<td>GET bandwidth/all</td> +<td>Return bandwidth documents of all relays and bridges that are +currently running or that have been running in the past week.</td> +</tr> +<tr> +<td>GET bandwidth/running</td> +<td>Return bandwidth documents of all relays and bridges that are +currently running.</td> +</tr> +<tr> +<td>GET bandwidth/relays</td> +<td>Return bandwidth documents of all relays that are currently running or +that have been running in the past week, but don't include any bridges.</td> +</tr> +<tr> +<td>GET bandwidth/bridges</td> +<td>Return bandwidth documents of all bridges that are currently running +or that have been running in the past week, but don't include any +relays.</td> +</tr> +<tr> +<td>GET details/search/:searchtext</td> +<td>Return bandwidth documents of all relays and bridges with +:searchtext matching the beginning of a nickname, (possibly $-prefixed) fingerprint, IP address, or +(possibly $-prefixed) hashed fingerprint. +Added the option to search for $-prefixed (hashed) fingerprints on +February 25, 2012. +Searches are case-insensitive.</td> +</tr> +<tr> +<td>GET bandwidth/lookup/:fingerprint</td> +<td>Return the bandwidth document of the relay or bridge with +:fingerprint matching the fingerprint or hashed fingerprint.</td> +</tr> +</table> +</body> +</html> +

1 0

[tor-cloud/master] Reboot at the right time and it should work
by runa＠torproject.org 29 Feb '12

29 Feb '12

commit 2a0c53b077bbe14116023bdf950fbca626fecbb4 Author: Runa A. Sandvik <runa.sandvik(a)gmail.com> Date: Wed Feb 29 10:19:11 2012 +0000 Reboot at the right time and it should work --- ec2-prep.sh | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/ec2-prep.sh b/ec2-prep.sh index 84249f0..0cad70c 100644 --- a/ec2-prep.sh +++ b/ec2-prep.sh @@ -261,6 +261,7 @@ ExitPolicy reject *:* EOF echo "Done configuring the system, will reboot" echo "Your system has been configured as a Tor bridge, see https://cloud.torproject.org/ for more info" > /etc/ec2-prep.sh +reboot fi if [ $CONFIG == "privatebridge" ]; then @@ -298,10 +299,11 @@ ExitPolicy reject *:* EOF echo "Done configuring the system, will reboot" echo "Your system has been configured as a private Tor bridge, see https://cloud.torproject.org/ for more info" > /etc/ec2-prep.sh +reboot fi # XXX TODO # Generally, we'll want to rm /var/lib/tor/* and remove all state from the system # # We're done; tell the user and then reboot the system -reboot +#reboot

1 0

[doctor/master] Update maatuska's IP.
by karsten＠torproject.org 29 Feb '12

29 Feb '12

commit 5bd2587f8b6f965e5133f55d817c38963a1c744d Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Wed Feb 29 07:46:19 2012 +0100 Update maatuska's IP. --- src/org/torproject/doctor/Downloader.java | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/src/org/torproject/doctor/Downloader.java b/src/org/torproject/doctor/Downloader.java index 6dff6d8..c4d1243 100644 --- a/src/org/torproject/doctor/Downloader.java +++ b/src/org/torproject/doctor/Downloader.java @@ -21,7 +21,7 @@ public class Downloader { downloader.addDirectoryAuthority("gabelmoo", "212.112.245.170", 80); downloader.addDirectoryAuthority("tor26", "86.59.21.38", 80); downloader.addDirectoryAuthority("ides", "216.224.124.114", 9030); - downloader.addDirectoryAuthority("maatuska", "213.115.239.118", 443); + downloader.addDirectoryAuthority("maatuska", "171.25.193.9", 443); downloader.addDirectoryAuthority("dannenberg", "193.23.244.244", 80); downloader.addDirectoryAuthority("urras", "208.83.223.34", 443); downloader.addDirectoryAuthority("moria1", "128.31.0.34", 9131);

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits February 2012