- tor-commits - lists.torproject.org

[torflow/master] Update pythonpath to modern versions.
by mikeperry＠torproject.org 17 Nov '11

17 Nov '11

commit f261978b21b987b3304eb3d486a82949f7d46def Author: Mike Perry <mikeperry-git(a)fscked.org> Date: Mon Nov 14 17:35:33 2011 -0800 Update pythonpath to modern versions. --- NetworkScanners/BwAuthority/run_scan.sh | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/NetworkScanners/BwAuthority/run_scan.sh b/NetworkScanners/BwAuthority/run_scan.sh index b3e1355..bc25489 100755 --- a/NetworkScanners/BwAuthority/run_scan.sh +++ b/NetworkScanners/BwAuthority/run_scan.sh @@ -6,7 +6,7 @@ SCANNER_COUNT=4 # This tor must have the w status line fix as well as the stream bw fix # Ie git master or 0.2.2.x TOR_EXE=../../../tor.git/src/or/tor -PYTHONPATH=../../../SQLAlchemy-0.5.5/lib:../../../Elixir-0.6.1/ +PYTHONPATH=../../../SQLAlchemy-0.7.3/lib:../../../Elixir-0.7.1/ for n in `seq $SCANNER_COUNT`; do PIDFILE=./data/scanner.${n}/bwauthority.pid

1 0

[torflow/master] Update scanner cutoffs and timeouts in config.
by mikeperry＠torproject.org 17 Nov '11

17 Nov '11

commit 781e4d11eb38deaf9b509438b7b7a1a771e5efa1 Author: Mike Perry <mikeperry-git(a)fscked.org> Date: Mon Nov 14 18:10:54 2011 -0800 Update scanner cutoffs and timeouts in config. --- .../BwAuthority/data/scanner.1/bwauthority.cfg | 4 ++-- .../BwAuthority/data/scanner.2/bwauthority.cfg | 4 ++-- .../BwAuthority/data/scanner.3/bwauthority.cfg | 2 +- .../BwAuthority/data/scanner.4/bwauthority.cfg | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/NetworkScanners/BwAuthority/data/scanner.1/bwauthority.cfg b/NetworkScanners/BwAuthority/data/scanner.1/bwauthority.cfg index 5d986d0..c15f5c5 100644 --- a/NetworkScanners/BwAuthority/data/scanner.1/bwauthority.cfg +++ b/NetworkScanners/BwAuthority/data/scanner.1/bwauthority.cfg @@ -18,11 +18,11 @@ db_url = #db_url = postgresql://bwscanner:password@127.0.0.1/BwScan1 tor_dir = ./data/tor start_pct = 0 -stop_pct = 12 +stop_pct = 10 save_every = 0 nodes_per_slice = 50 circs_per_node = 5 min_streams = 1 -max_fetch_time = 300 +max_fetch_time = 600 sleep_start = 01:30 sleep_stop = 01:30 diff --git a/NetworkScanners/BwAuthority/data/scanner.2/bwauthority.cfg b/NetworkScanners/BwAuthority/data/scanner.2/bwauthority.cfg index a9544a1..68d5f9c 100644 --- a/NetworkScanners/BwAuthority/data/scanner.2/bwauthority.cfg +++ b/NetworkScanners/BwAuthority/data/scanner.2/bwauthority.cfg @@ -17,8 +17,8 @@ db_url = #db_url = mysql+mysqldb://bwscanner:password@127.0.0.1/BwScan2 #db_url = postgresql://bwscanner:password@127.0.0.1/BwScan2 tor_dir = ./data/tor -start_pct = 12 -stop_pct = 35 +start_pct = 10 +stop_pct = 40 save_every = 0 nodes_per_slice = 50 circs_per_node = 5 diff --git a/NetworkScanners/BwAuthority/data/scanner.3/bwauthority.cfg b/NetworkScanners/BwAuthority/data/scanner.3/bwauthority.cfg index 7999781..7ee1808 100644 --- a/NetworkScanners/BwAuthority/data/scanner.3/bwauthority.cfg +++ b/NetworkScanners/BwAuthority/data/scanner.3/bwauthority.cfg @@ -17,7 +17,7 @@ db_url = #db_url = mysql+mysqldb://bwscanner:password@127.0.0.1/BwScan3 #db_url = postgresql://bwscanner:password@127.0.0.1/BwScan3 tor_dir = ./data/tor -start_pct =35 +start_pct =30 stop_pct = 60 save_every = 0 nodes_per_slice = 50 diff --git a/NetworkScanners/BwAuthority/data/scanner.4/bwauthority.cfg b/NetworkScanners/BwAuthority/data/scanner.4/bwauthority.cfg index c21be4f..d0db161 100644 --- a/NetworkScanners/BwAuthority/data/scanner.4/bwauthority.cfg +++ b/NetworkScanners/BwAuthority/data/scanner.4/bwauthority.cfg @@ -17,7 +17,7 @@ db_url = #db_url = mysql+mysqldb://bwscanner:password@127.0.0.1/BwScan4 #db_url = postgresql://bwscanner:password@127.0.0.1/BwScan4 tor_dir = ./data/tor -start_pct =60 +start_pct =70 stop_pct = 100 save_every = 0 nodes_per_slice = 50

1 0

[torflow/master] Add some comments about potential timeout issues.
by mikeperry＠torproject.org 17 Nov '11

17 Nov '11

commit 1efe897f89b6ff113862dd0d418a17873962b836 Author: Mike Perry <mikeperry-git(a)fscked.org> Date: Mon Nov 14 18:11:35 2011 -0800 Add some comments about potential timeout issues. --- NetworkScanners/BwAuthority/bwauthority_child.py | 7 ++++++- 1 files changed, 6 insertions(+), 1 deletions(-) diff --git a/NetworkScanners/BwAuthority/bwauthority_child.py b/NetworkScanners/BwAuthority/bwauthority_child.py index c42e163..65063a9 100755 --- a/NetworkScanners/BwAuthority/bwauthority_child.py +++ b/NetworkScanners/BwAuthority/bwauthority_child.py @@ -225,8 +225,11 @@ def speedrace(hdlr, start_pct, stop_pct, circs_per_node, save_every, out_dir, hdlr.new_exit() attempt += 1 - # FIXME: This noise is due to a difficult to find Tor bug that + # TODO: This noise is due to a difficult to find Tor bug that # causes some exits to hang forever on streams :( + # FIXME: Hrmm, should we change the reason on this? Right now, + # 7 == TIMEOUT, which means we do not count the bandwidth of this + # stream.. however, we count it as 'successful' below timer = threading.Timer(max_fetch_time, lambda: hdlr.close_streams(7)) timer.start() url = choose_url(start_pct) @@ -240,6 +243,8 @@ def speedrace(hdlr, start_pct, stop_pct, circs_per_node, save_every, out_dir, plog('WARN', 'Timer exceeded limit: ' + str(delta_build) + '\n') build_exit = hdlr.get_exit_node() + # FIXME: Timeouts get counted as 'sucessful' here, but do not + # count in the SQL stats! if ret == 1 and build_exit: successful += 1 plog('DEBUG', str(start_pct) + '-' + str(stop_pct) + '% circuit build+fetch took ' + str(delta_build) + ' for ' + str(build_exit))

1 0

[torflow/master] Submodule.
by mikeperry＠torproject.org 17 Nov '11

17 Nov '11

commit 8637ba1e6afb792c332b0a14f535f7c6d7d54c28 Author: Mike Perry <mikeperry-git(a)fscked.org> Date: Tue Nov 15 18:45:16 2011 -0800 Submodule. --- TorCtl | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/TorCtl b/TorCtl index 391b439..3de9176 160000 --- a/TorCtl +++ b/TorCtl @@ -1 +1 @@ -Subproject commit 391b4399adda91e8b68ffd6e1fa294efe846debd +Subproject commit 3de91767e208d1642a8cf89dc1b645f637abaf8e

1 0

[torflow/master] Allow desc bw to be used in feedback.
by mikeperry＠torproject.org 17 Nov '11

17 Nov '11

commit 0e9738d8d5670472ae0e503629f1bbfca3ff6d9b Author: Mike Perry <mikeperry-git(a)fscked.org> Date: Tue Nov 15 21:06:34 2011 -0800 Allow desc bw to be used in feedback. It may be equivalent to NS bw, since the NS bw functions as an accumulator.. We may want to set T_i_decay to 0 for this code. --- NetworkScanners/BwAuthority/aggregate.py | 76 +++++++++++++++++++++-------- 1 files changed, 55 insertions(+), 21 deletions(-) diff --git a/NetworkScanners/BwAuthority/aggregate.py b/NetworkScanners/BwAuthority/aggregate.py index fb5cc7a..c55b9a1 100755 --- a/NetworkScanners/BwAuthority/aggregate.py +++ b/NetworkScanners/BwAuthority/aggregate.py @@ -88,6 +88,7 @@ class Node: self.ratio = None self.new_bw = None self.change = None + self.use_bw = -1 # measurement vars from bwauth lines self.measured_at = 0 @@ -100,24 +101,32 @@ class Node: self.updated_at = 0 def revert_to_vote(self, vote): - self.new_bw = vote.bw*1000 - self.pid_bw = vote.pid_bw - self.pid_error = vote.pid_error - self.pid_error_sum = vote.pid_error_sum - self.pid_delta = vote.pid_delta - self.measured_at = vote.measured_at - - # Derivative of error for pid control - def get_pid_bw(self, prev_vote, kp, ki, kd, kidecay): + self.copy_vote(vote) + self.pid_error = vote.pid_error # Set + self.measured_at = vote.measured_at # Set + + def copy_vote(self, vote): + self.new_bw = vote.bw*1000 # Not set yet + self.pid_bw = vote.pid_bw # Not set yet + self.pid_error_sum = vote.pid_error_sum # Not set yet + self.pid_delta = vote.pid_delta # Not set yet + + def get_pid_bw(self, prev_vote, kp, ki, kd, kidecay, update=True): + if not update: + return self.use_bw \ + + kp*self.use_bw*self.pid_error \ + + ki*self.use_bw*self.pid_error_sum \ + + kd*self.use_bw*self.pid_delta + self.prev_error = prev_vote.pid_error # We decay the interval each round to keep it bounded. # This decay is non-standard. We do it to avoid overflow self.pid_error_sum = prev_vote.pid_error_sum*kidecay + self.pid_error - self.pid_bw = self.ns_bw \ - + kp*self.ns_bw*self.pid_error \ - + ki*self.ns_bw*self.integral_error() \ - + kd*self.ns_bw*self.d_error_dt() + self.pid_bw = self.use_bw \ + + kp*self.use_bw*self.pid_error \ + + ki*self.use_bw*self.integral_error() \ + + kd*self.use_bw*self.d_error_dt() return self.pid_bw # Time-weighted sum of error per unit of time (measurement sample) @@ -212,6 +221,7 @@ class ConsensusJunk: self.bwauth_pid_control = False self.use_circ_fails = False self.use_best_ratio = False + self.use_desc_bw = False self.K_p = K_p self.T_i = T_i @@ -224,6 +234,9 @@ class ConsensusJunk: for p in cs_params: if p == "bwauthpid=1": self.bwauth_pid_control = True + elif p == "bwauthdescbw=1": + self.use_desc_bw = True + plog("INFO", "Using descriptor bandwidth") elif p == "bwauthcircs=1": self.use_circ_fails = True plog("INFO", "Counting circuit failures") @@ -472,6 +485,11 @@ def main(argv): n.sbw_ratio = n.strm_bw/true_strm_avg if cs_junk.bwauth_pid_control: + if cs_junk.use_desc_bw: + n.use_bw = n.desc_bw + else: + n.use_bw = n.ns_bw + # Penalize nodes for circ failure rate if cs_junk.use_best_ratio and n.sbw_ratio > n.fbw_ratio: n.pid_error = (n.strm_bw*(1.0-n.circ_fail_rate) - true_strm_avg)/true_strm_avg @@ -496,13 +514,28 @@ def main(argv): cs_junk.K_d, cs_junk.K_i_decay) else: - pid_error = n.pid_error - n.revert_to_vote(prev_votes.vote_map[n.idhex]) # Don't use feedback here, but we might as well use our # new measurement against the previous vote. - n.new_bw = prev_votes.vote_map[n.idhex].pid_bw + \ - cs_junk.K_p*prev_votes.vote_map[n.idhex].pid_bw*pid_error - + n.copy_vote(prev_votes.vote_map[n.idhex]) + + if cs_junk.use_desc_bw: + n.new_bw = n.get_pid_bw(prev_votes.vote_map[n.idhex], + cs_junk.K_p, + cs_junk.K_i, + cs_junk.K_d, + 0.0, False) + else: + # Use previous vote's feedback bw + n.use_bw = prev_votes.vote_map[n.idhex].pid_bw + n.new_bw = n.get_pid_bw(prev_votes.vote_map[n.idhex], + cs_junk.K_p, + 0.0, + 0.0, + 0.0, False) + + # Reset the remaining vote data.. + n.measured_at = prev_votes.vote_map[n.idhex].measured_at + n.pid_error = prev_votes.vote_map[n.idhex].pid_error else: # Everyone else should be pretty instantenous to respond. # Full feedback should be fine for them (we hope), @@ -529,7 +562,7 @@ def main(argv): # Reset values. Don't vote/sample this measurement round. n.revert_to_vote(prev_votes.vote_map[n.idhex]) else: # No prev vote, pure consensus feedback this round - n.new_bw = n.ns_bw + cs_junk.K_p*n.ns_bw*n.pid_error + n.new_bw = n.use_bw + cs_junk.K_p*n.use_bw*n.pid_error n.pid_error_sum = n.pid_error n.pid_bw = n.new_bw plog("INFO", "No prev vote for node "+n.nick+": Consensus feedback") @@ -565,8 +598,9 @@ def main(argv): if n.new_bw >= 0xffffffff*1000: plog("WARN", "Bandwidth of node "+n.nick+"="+n.idhex+" exceeded maxint32: "+str(n.new_bw)) n.new_bw = 0xffffffff*1000 - if cs_junk.T_i > 0 and math.fabs(n.pid_error_sum) > \ - math.fabs(2*cs_junk.T_i*n.pid_error/cs_junk.T_i_decay): + if cs_junk.T_i > 0 and cs_junk.T_i_decay > 0 \ + and math.fabs(n.pid_error_sum) > \ + math.fabs(2*cs_junk.T_i*n.pid_error/cs_junk.T_i_decay): plog("NOTICE", "Large pid_error_sum for node "+n.idhex+"="+n.nick+": "+ str(n.pid_error_sum)+" vs "+str(n.pid_error)) if n.new_bw > tot_net_bw*NODE_CAP:

1 0

[torflow/master] Switch to memory-only sqlalchemy by default.
by mikeperry＠torproject.org 17 Nov '11

17 Nov '11

commit 24927645f5b9fb94ebf92b3294900e64b5e83de2 Author: Mike Perry <mikeperry-git(a)fscked.org> Date: Tue Nov 15 18:43:20 2011 -0800 Switch to memory-only sqlalchemy by default. --- NetworkScanners/BwAuthority/bwauthority_child.py | 7 ++++--- 1 files changed, 4 insertions(+), 3 deletions(-) diff --git a/NetworkScanners/BwAuthority/bwauthority_child.py b/NetworkScanners/BwAuthority/bwauthority_child.py index 65063a9..64a5ca7 100755 --- a/NetworkScanners/BwAuthority/bwauthority_child.py +++ b/NetworkScanners/BwAuthority/bwauthority_child.py @@ -47,7 +47,7 @@ user_agent = "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.37 # Note these urls should be https due to caching considerations. # If you really must make them http, be sure to change exit_ports to [80] # below, or else the scan will not finish. -urls = ["https://38.229.70.2/"] #, "https://38.229.70.19/"] +urls = ["https://38.229.70.2/"]#, "https://38.229.72.16/"] # Do NOT modify this object directly after it is handed to PathBuilder @@ -309,8 +309,9 @@ def main(argv): else: plog("INFO", "db_url not found in config. Defaulting to sqlite") sql_file = os.getcwd()+'/'+out_dir+'/bwauthority.sqlite' - hdlr.attach_sql_listener('sqlite:///'+sql_file) - + #hdlr.attach_sql_listener('sqlite:///'+sql_file) + hdlr.attach_sql_listener('sqlite://') + # set SOCKS proxy socks.setdefaultproxy(socks.PROXY_TYPE_SOCKS5, TorUtil.tor_host, TorUtil.tor_port) socket.socket = socks.socksocket

1 0

[torflow/master] Update spec to include consensus params.
by mikeperry＠torproject.org 17 Nov '11

17 Nov '11

commit 9b088f490baa947fb76063a800fce43c1e1a1a45 Author: Mike Perry <mikeperry-git(a)fscked.org> Date: Thu Nov 17 15:15:18 2011 -0800 Update spec to include consensus params. These are still subject to change, especially in terms of defaults. --- NetworkScanners/BwAuthority/README.spec.txt | 54 ++++++++++++++++++++++++++- 1 files changed, 52 insertions(+), 2 deletions(-) diff --git a/NetworkScanners/BwAuthority/README.spec.txt b/NetworkScanners/BwAuthority/README.spec.txt index 96568c6..5ccf672 100644 --- a/NetworkScanners/BwAuthority/README.spec.txt +++ b/NetworkScanners/BwAuthority/README.spec.txt @@ -364,7 +364,7 @@ should cause convergence to this balanced ideal. See https://en.wikipedia.org/wiki/PID_controller for background, - especially: https://en.wikipedia.org/wiki/PID_controller#Pseudocode + especially https://en.wikipedia.org/wiki/PID_controller#Pseudocode 3.1. Modeling Measurement as PID Control @@ -463,7 +463,7 @@ pid_delta is purely informational, and is not used in feedback. -3.5. Tuning Parameters +3.5. Tuning PID Constants Internally, the source uses the Standard PID Form: https://en.wikipedia.org/wiki/PID_controller#Ideal_versus_standard_PID_form @@ -480,4 +480,54 @@ only gives us useful information for a fraction of a measurement interval, until clients begin to migrate to the new measurements. +3.6. Consensus Parameters + The bandwidth auths listen for several consensus parameters to tweak + behavior: + + "bwauthpid=1" + If present, enables the PID control features in Section 3. + + "bwauthcircs=1" + If present, F_node is multiplied by (1.0 - circ_fail_rate) + as described in Section 3.1. + + "bwauthkp=N" + Sets K_p to N/10000.0 + + "bwauthti=N" + Sets T_i to N/10000.0. For T_i=0, K_i is set to 0. + + "bwauthtd=N" + Sets T_d to N/10000.0. + + "bwauthtidecay=N" + Sets T_i_decay to N/10000.0. T_i_decay is an parameter + used to dampen the pid_error_sum accumulation. If non-zero, + the pid_error_sum integration becomes: + + K_i_decay = (1.0 - T_i_decay/T_i) + pid_control_sum = pid_control_sum*K_i_decay + pid_error + + Intuitively, this means that after T_i sample rounds, + the T_i'th round has experienced a reduction by T_i_decay + for the values of T_i that are relevant to us. + + If T_i is 0, K_i_decay is set to 0. + + "bwauthbestratio=1" + If present, the larger of stream bandwidth vs filtered bandwidth + is used to compute F_node. + + "bwauthdescbw=1" + If present, uses descriptor bandwidth instead of feeding back + PID control values. This may be functionally equivalent to NS + bandwidth so long as T_i is non-zero, because error will get + accumulated in pid_error_sum as opposed to the consensus value + itself. + + It also has the advantage of allowing the PID control code to be + exercised, yet produce identical results to Section 2 with + the following additional constants: + +

1 0

[torflow/master] Let's try turning FetchDirInfo*Early on by default.
by mikeperry＠torproject.org 17 Nov '11

17 Nov '11

commit d9c0f9065d1a7755c79e98d2a5c81ff7ec60a8d8 Author: Mike Perry <mikeperry-git(a)fscked.org> Date: Thu Nov 17 15:42:21 2011 -0800 Let's try turning FetchDirInfo*Early on by default. Memory-only sqlite might make them more bearable. --- NetworkScanners/BwAuthority/data/tor/torrc | 7 ++++--- 1 files changed, 4 insertions(+), 3 deletions(-) diff --git a/NetworkScanners/BwAuthority/data/tor/torrc b/NetworkScanners/BwAuthority/data/tor/torrc index 8f155b5..0c13322 100644 --- a/NetworkScanners/BwAuthority/data/tor/torrc +++ b/NetworkScanners/BwAuthority/data/tor/torrc @@ -8,6 +8,7 @@ PidFile ./data/tor/tor.pid CookieAuthentication 1 FetchUselessDescriptors 1 __LeaveStreamsUnattached 1 -# Bad idea: Too much consensus update activity -#FetchDirInfoExtraEarly 1 -#FetchDirInfoEarly 1 + +# Bad idea? Too much consensus update activity? +FetchDirInfoExtraEarly 1 +FetchDirInfoEarly 1

1 0

[torflow/master] Merge branch 'pid_control-rebased'
by mikeperry＠torproject.org 17 Nov '11

17 Nov '11

commit 021d8cc35bd072fb169fa41d90f5badfe4771522 Merge: 8e94360 d9c0f90 Author: Mike Perry <mikeperry-git(a)fscked.org> Date: Thu Nov 17 15:48:59 2011 -0800 Merge branch 'pid_control-rebased' NetworkScanners/BwAuthority/README.spec.txt | 214 ++++++- NetworkScanners/BwAuthority/aggregate.py | 671 +++++++++++++------- NetworkScanners/BwAuthority/bwauthority_child.py | 54 +- NetworkScanners/BwAuthority/cron.sh | 8 +- .../BwAuthority/data/scanner.1/bwauthority.cfg | 6 +- .../BwAuthority/data/scanner.2/bwauthority.cfg | 8 +- .../BwAuthority/data/scanner.3/bwauthority.cfg | 6 +- .../BwAuthority/data/scanner.4/bwauthority.cfg | 6 +- NetworkScanners/BwAuthority/data/tor/torrc | 7 +- NetworkScanners/BwAuthority/run_scan.sh | 2 +- TorCtl | 2 +- 11 files changed, 695 insertions(+), 289 deletions(-)

1 0

[translation/vidalia_help] Update translations for vidalia_help
by translation＠torproject.org 17 Nov '11

17 Nov '11

commit 564f70a55f5e9b79d78f4c7e4cf755308d41d45e Author: Translation commit bot <translation(a)torproject.org> Date: Thu Nov 17 23:45:21 2011 +0000 Update translations for vidalia_help --- it/bridges.po | 14 +++++++++++- it/log.po | 64 +++++++++++++++++++++++++++++++++++++++++++++++++++----- 2 files changed, 71 insertions(+), 7 deletions(-) diff --git a/it/bridges.po b/it/bridges.po index f6ae381..5991208 100644 --- a/it/bridges.po +++ b/it/bridges.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 16:58+0200\n" -"PO-Revision-Date: 2011-11-17 23:12+0000\n" +"PO-Revision-Date: 2011-11-17 23:17+0000\n" "Last-Translator: n0on3 <a.n0on3(a)gmail.com>\n" "Language-Team: Italian (http://www.transifex.net/projects/p/torproject/team/it/)\n" "MIME-Version: 1.0\n" @@ -110,6 +110,15 @@ msgid "" "attacker to learn lots of bridge addresses, you must send this request from " "a Gmail account." msgstr "" +"E' possibile ottenere una lista di indirizzi di bridges pubblici visitando " +"il sito https://bridges.torproject.org. La risposta ottenuta dalla " +"pagina cambia ogni pochi giorni, pertanto si consiglia di controllare " +"periodicamente la lista disponibile se si ha bisogno di più indirizzi. In " +"alternativa, per ottenere una lista di indirizzi di relay bridges pubblici, " +"si invii una email a bridges(a)torproject.org con la sola linea get " +"bridges nel corpo del messaggio. In ogni caso, per far si che sia " +"difficile per un attaccante accedere alla lista completa di bridges, è " +"necessario inviare questa richiesta da un account Gmail." #. type: Content of: <html><body> #: en/bridges.html:63 @@ -117,5 +126,8 @@ msgid "" "Configuring more than one bridge address will make your Tor connection more " "stable, in case some of the bridges become unreachable." msgstr "" +"Configurare più di un indirizzo di bridge relay renderà la connessione alla " +"rete Tor più stabile, nel caso alcuni dei bridge diventino non " +"raggiungibili." diff --git a/it/log.po b/it/log.po index a1dfcaa..9d28321 100644 --- a/it/log.po +++ b/it/log.po @@ -1,12 +1,13 @@ # # Translators: +# <a.n0on3(a)gmail.com>, 2011. 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: 2011-11-17 23:38+0000\n" +"Last-Translator: n0on3 <a.n0on3(a)gmail.com>\n" "Language-Team: Italian (http://www.transifex.net/projects/p/torproject/team/it/)\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/log.html:16 msgid "Message Log" -msgstr "" +msgstr "Messaggi di Log" #. type: Content of: <html><body> #: en/log.html:19 @@ -28,11 +29,17 @@ msgid "" "See the help section on <a href=\"#severities\">message severities</a> for " "more information. <a name=\"severities\"/>" msgstr "" +"I messaggi di log permettono di visualizzare informazioni relative allo " +"stato di esecuzione di un processo Tor. <a name=\"basic\"/> Ogni messaggio " +"ha un livello di severità associato, che spanna da Errore (il " +"più serio) a Debug (il più prolisso). Si veda la sezione si aiuto " +"sulla <a href=\"#severities\">severità dei messaggi</a>. <a " +"name=\"severities\"/>" #. type: Content of: <html><body><h3> #: en/log.html:28 msgid "Message Severities" -msgstr "" +msgstr "Severità dei messaggi" #. type: Content of: <html><body> #: en/log.html:30 @@ -42,12 +49,19 @@ msgid "" "Lower severity messages appear frequently during normal Tor operations and " "usually do not need to be logged." msgstr "" +"Un livello di severità dei messaggi indica l'importanza dei messaggi che " +"marca. Un maggiore livello di serietà generalmente segnala che qualcosa è " +"andato storto nell'esecuzione di Tor. Livelli più bassi di serietà compaiono" +" più frequentemente durante la normale esecuzione di Tor, e generalmente non" +" necessitano di essere visualizzati." #. type: Content of: <html><body> #: en/log.html:37 msgid "" "The possible message severities, from most severe to least severe, are:" msgstr "" +"Le possibili severità dei messaggi, in ordine dal più severo al meno severo," +" sono:" #. type: Content of: <html><body><ul><li> #: en/log.html:41 @@ -56,6 +70,9 @@ msgid "" "Tor cannot proceed. These messages will be highlighted in red in the " "message log." msgstr "" +" Errore: Messaggi che compaiono quando qualcosa è andato storto al " +"punto tale che Tor non può procedere con l'esecuzione. Questi messaggi sono " +"evidenziati in rosso tra i messaggi di log." #. type: Content of: <html><body><ul><li> #: en/log.html:46 @@ -64,6 +81,9 @@ msgid "" " Tor, but are not fatal and Tor will continue running. These messages will " "be highlighted in yellow." msgstr "" +" Avvertimento: Messaggi che appaiono solo quando qualcosa va storto, " +"ma l'errore riscontrato non è fatale e pertanto Tor può proseguire la " +"propria esecuzione. Questi messaggi sono evidenziati in giallo." #. type: Content of: <html><body><ul><li> #: en/log.html:51 @@ -71,6 +91,9 @@ msgid "" "Notice: Messages that appear infrequently during normal Tor operation" " and are not considered errors, but you still may care about." msgstr "" +" Notifica: Messaggi che non dovrebbero apparire spesso durante la " +"normale esecuzione di Tor e che non sono considerati errori, ma potrebbero " +"comunque riportare informazioni di potenziale interesse." #. type: Content of: <html><body><ul><li> #: en/log.html:55 @@ -78,6 +101,9 @@ msgid "" "Info: Messages that appear frequently during normal Tor operation and" " are not usually of interest to most users." msgstr "" +" Informazioni: Messaggi che appaiono frequentemente durante la " +"normale esecuzione di Tor e generalmente non di interesse per la maggior " +"parte degli utenti." #. type: Content of: <html><body><ul><li> #: en/log.html:59 @@ -86,6 +112,10 @@ msgid "" "developers. You should generally not log debug messages unless you know what" " you are doing." msgstr "" +" Debug: Messaggi estremamente prolissi, che sono principalmente di " +"interesse per gli sviluppatori. Generalmente è sconsigliato loggare i " +"messaggi di debug, a meno di non essere consapevoli di ciò che si sta " +"facendo." #. type: Content of: <html><body> #: en/log.html:66 @@ -93,22 +123,28 @@ msgid "" "Most users should only log Error, Warning, and Notice " "messages." msgstr "" +"La maggior parte degli utenti dovrebbe solo loggare i messaggi con severità " +"Errore, Warning o Notice." #. type: Content of: <html><body> #: en/log.html:71 msgid "" "To select which message severities you would like to see, do the following:" msgstr "" +"Per selezionare quali severità di messaggi visualizzare, si proceda come " +"segue:" #. type: Content of: <html><body><ol><li> #: en/log.html:73 en/log.html:92 msgid "Open the message log from the Vidalia tray menu." msgstr "" +"Aprire i messaggi di log dall'icona di Vidalia sulla barra di sistema." #. type: Content of: <html><body><ol><li> #: en/log.html:74 en/log.html:93 msgid "Click on Settings at the top of the message log window." msgstr "" +"Si faccia click su Settings in cima alla schermata visualizzata." #. type: Content of: <html><body><ol><li> #: en/log.html:76 @@ -116,21 +152,26 @@ msgid "" "Check message severities you would like to see from the Message Filter group" " on the left and uncheck message severities you would like to hide." msgstr "" +"Si spuntino le severità di messaggi che si desidera visualizzare dal gruppo " +"di filtri dei messaggi sulla sinistra e si tolga la spunta alle severità di " +"messaggi che si desidera nascondere." #. type: Content of: <html><body><ol><li> #: en/log.html:79 msgid "Click Save Settings to apply your new message filter." msgstr "" +"Si faccia click su Save Settings per applicare i nuovi filtri " +"definiti per i messaggi." #. type: Content of: <html><body> #: en/log.html:84 msgid "<a name=\"logfile\"/>" -msgstr "" +msgstr "<a name=\"logfile\"/>" #. type: Content of: <html><body><h3> #: en/log.html:85 msgid "Logging to a File" -msgstr "" +msgstr "Salvare i messaggi di log su un file" #. type: Content of: <html><body> #: en/log.html:87 @@ -138,12 +179,17 @@ msgid "" "Vidalia can also write log messages to a file, as well as logging them in " "the message log window. To enable logging to a file, follow these steps:" msgstr "" +"Vidalia è in grado di scrivere i messaggi di log su un file, così come di " +"visualizzarli nella finestra di dialogo. Per abilitare la scrittura dei log " +"su un file, si seguano i successivi passi:" #. type: Content of: <html><body><ol><li> #: en/log.html:94 msgid "" "Check the box labeled Automatically save new log messages to a file." msgstr "" +"Si spunti la casella etichettata con Salvataggio automatico dei nuovi " +"messaggi di log su un file." #. type: Content of: <html><body><ol><li> #: en/log.html:96 @@ -152,10 +198,16 @@ msgid "" "either type the path and filename into the text box, or click Browse " "to navigate to a location for your log file." msgstr "" +"Se si desidera cambiare il file sul quale i messaggi verranno scritti, se ne" +" inserisca il percorso ed il nome del file nel campo di testo, o si faccia " +"click su Sfoglia per navigare fino alla locazione del file di log " +"desiderato." #. type: Content of: <html><body><ol><li> #: en/log.html:100 msgid "Click Save Settings to save your log destination." msgstr "" +"Si faccia click su Salvataggio configurazione per salvare il " +"percorso del nuovo file di log ed uscire."

1 0