tor-commits December 2014

tor-commits@lists.torproject.org

20 participants
797 discussions

[tor/master] Missing semicolon; my bad
by nickm＠torproject.org 30 Dec '14

30 Dec '14

commit 9765ae44479b35ed96e1f9ff88e10cd07b86c5d4 Author: Nick Mathewson <nickm(a)torproject.org> Date: Tue Dec 30 10:00:11 2014 -0500 Missing semicolon; my bad --- src/or/circuituse.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/or/circuituse.c b/src/or/circuituse.c index 015270c..3322d31 100644 --- a/src/or/circuituse.c +++ b/src/or/circuituse.c @@ -1659,7 +1659,7 @@ have_enough_path_info(int need_exit) if (need_exit) return router_have_consensus_path() == CONSENSUS_PATH_EXIT; else - return router_have_consensus_path() != CONSENSUS_PATH_UNKNOWN + return router_have_consensus_path() != CONSENSUS_PATH_UNKNOWN; } /** Launch a new circuit with purpose <b>purpose</b> and exit node

1 0

[chutney/master] Speed up tor bootstrap phase (chutney portion)
by nickm＠torproject.org 30 Dec '14

30 Dec '14

commit 05d9d63548dff686f66b2f1322a7f80e452462a1 Author: teor <teor2345(a)gmail.com> Date: Sat Dec 20 11:35:00 2014 +1100 Speed up tor bootstrap phase (chutney portion) Speed up the tor bootstrap by modifying both tor and chutney. Comprehensive bootstrap: (30s) Reduce the consensus interval to 10 seconds Depends on corresponding tor changes Don't require any bandwith for an exit flag Depends on corresponding tor changes Fast Bootstrap: (10s) Assume that everything is reachable and an exit Start building paths once the minimum number of descriptors are available Reduce consensus validity to 2 intervals Also make other minor config fixes Resolves bug 13823. Tests resolution of (tor) bug 13718 and children. --- torrc_templates/authority.tmpl | 33 +++++++++++++++++++++++++++------ torrc_templates/bridge-v6.tmpl | 2 +- torrc_templates/bridge.tmpl | 7 ++----- torrc_templates/bridgeauthority.tmpl | 2 +- torrc_templates/bridgeclient.tmpl | 13 ++++++++++++- torrc_templates/client.tmpl | 8 +++++++- torrc_templates/common.i | 27 +++++++++++++++++++++++++++ torrc_templates/exit-v4.i | 16 +++++++++++++++- torrc_templates/exit-v6.i | 16 +++++++++++++++- torrc_templates/relay-non-exit.tmpl | 8 +++++++- 10 files changed, 114 insertions(+), 18 deletions(-) diff --git a/torrc_templates/authority.tmpl b/torrc_templates/authority.tmpl index eda123c..108e1cf 100644 --- a/torrc_templates/authority.tmpl +++ b/torrc_templates/authority.tmpl @@ -1,19 +1,40 @@ -${include:relay.tmpl} +${include:relay-non-exit.tmpl} + AuthoritativeDirectory 1 V3AuthoritativeDirectory 1 ContactInfo auth${nodenum}(a)test.test ExitPolicy reject *:* -TestingV3AuthInitialVotingInterval 300 + +# Speed up the consensus cycle as fast as it will go +# Voting Interval can be: +# 10, 12, 15, 18, 20, 24, 25, 30, 36, 40, 45, 50, 60, ... +# Testing Initial Voting Interval can be: +# 5, 6, 8, 9, or any of the possible values for Voting Interval, +# as they both need to evenly divide 30 minutes. +# If clock desynchronisation is an issue, use an interval of at least: +# 18 * drift in seconds, to allow for a clock slop factor +TestingV3AuthInitialVotingInterval 5 +V3AuthVotingInterval 10 +# VoteDelay + DistDelay must be less than VotingInterval TestingV3AuthInitialVoteDelay 2 +V3AuthVoteDelay 2 TestingV3AuthInitialDistDelay 2 -TestingV3AuthVotingStartOffset 0 +V3AuthDistDelay 2 +# This is autoconfigured by chutney, so you probably don't want to use it +#TestingV3AuthVotingStartOffset 0 # Work around situations where the Exit and Guard flags aren't being set # These flags are set eventually, but it takes ~30 minutes # We could be more precise here, but it's easiest just to vote everything -# Clients are sensible enough to filter out Exits without any exit ports, +# Clients are sensible enough to filter out Exits without any exit ports, # and Guards without ORPorts # If your tor doesn't recognise TestingDirAuthVoteExit, update your chutney # to a version that includes the issue-13161-check-torrc-options features -TestingDirAuthVoteExit * -TestingDirAuthVoteGuard * + +# These are all set in common.i in the Comprehensive/Rapid sections +# Work around Exit requirements +#TestingDirAuthVoteExit * +# Work around bandwidth thresholds for exits +#TestingMinExitFlagThreshold 0 +# Work around Guard uptime requirements +#TestingDirAuthVoteGuard * diff --git a/torrc_templates/bridge-v6.tmpl b/torrc_templates/bridge-v6.tmpl index c9ba1e3..7e4ff91 100644 --- a/torrc_templates/bridge-v6.tmpl +++ b/torrc_templates/bridge-v6.tmpl @@ -1,3 +1,3 @@ ${include:bridge.tmpl} -OrPort ${ipv6_addr}:${orport} IPv6Only +OrPort ${ipv6_addr}:${orport} IPv6Only diff --git a/torrc_templates/bridge.tmpl b/torrc_templates/bridge.tmpl index 0c1a622..34c7f14 100644 --- a/torrc_templates/bridge.tmpl +++ b/torrc_templates/bridge.tmpl @@ -1,7 +1,4 @@ -${include:common.i} -SocksPort 0 -OrPort $orport -Address $ip +${include:relay-non-exit.tmpl} + BridgeRelay 1 ExitPolicy reject *:* - diff --git a/torrc_templates/bridgeauthority.tmpl b/torrc_templates/bridgeauthority.tmpl index 5598069..04fd2b5 100644 --- a/torrc_templates/bridgeauthority.tmpl +++ b/torrc_templates/bridgeauthority.tmpl @@ -1,4 +1,4 @@ -${include:relay.tmpl} +${include:relay-non-exit.tmpl} AuthoritativeDirectory 1 ContactInfo bridgeauth${nodenum}(a)test.test ExitPolicy reject *:* diff --git a/torrc_templates/bridgeclient.tmpl b/torrc_templates/bridgeclient.tmpl index f414718..4c10c54 100644 --- a/torrc_templates/bridgeclient.tmpl +++ b/torrc_templates/bridgeclient.tmpl @@ -1,5 +1,16 @@ ${include:client.tmpl} + UseBridges 1 -UseMicrodescriptors 0 # Microdescriptors don't work well with bridge clients + +# In some tor versions, Microdescriptors don't work well with bridge clients +# But the latest git sources appear to be fine +#UseMicrodescriptors 0 + ${bridges} +# Like TestingClientDownloadSchedule, but for bridge clients +# Try to download after: +# the minimum initial consensus time to start with, +# a few eager fetches, +# then half the minimum testing consensus interval +TestingBridgeDownloadSchedule 0, 5 diff --git a/torrc_templates/client.tmpl b/torrc_templates/client.tmpl index 1eb1d99..3aff6cb 100644 --- a/torrc_templates/client.tmpl +++ b/torrc_templates/client.tmpl @@ -1,6 +1,12 @@ ${include:common.i} SocksPort $socksport + #NOTE: Setting TestingClientConsensusDownloadSchedule doesn't # help -- dl_stats.schedule is not DL_SCHED_CONSENSUS # at boostrap time. -TestingClientDownloadSchedule 10, 2, 2, 4, 4, 8, 13, 18, 25, 40, 60 +# Try to download after: +# the minimum initial consensus time to start with, +# a few eager fetches, +# then half the minimum testing consensus interval +TestingClientDownloadSchedule 0, 5 +TestingClientConsensusDownloadSchedule 0, 5 diff --git a/torrc_templates/common.i b/torrc_templates/common.i index 42eebc4..16f2944 100644 --- a/torrc_templates/common.i +++ b/torrc_templates/common.i @@ -1,4 +1,29 @@ TestingTorNetwork 1 + +## Comprehensive Bootstrap Testing Options ## +# These typically launch a working minimal Tor network in 25s-30s +# See authority.tmpl for a partial explanation +#AssumeReachable 0 +#Default PathsNeededToBuildCircuits 0.6 +#Disable TestingDirAuthVoteExit +#Default V3AuthNIntervalsValid 3 + +## Rapid Bootstrap Testing Options ## +# These typically launch a working minimal Tor network in 6s-10s +# These parameters make tor networks bootstrap fast, +# but can cause consensus instability and network unreliability +# (Some are also bad for security.) +AssumeReachable 1 +PathsNeededToBuildCircuits 0.25 +TestingDirAuthVoteExit * +V3AuthNIntervalsValid 2 + +## Always On Testing Options ## +# We enable TestingDirAuthVoteGuard to avoid Guard stability requirements +TestingDirAuthVoteGuard * +# We set TestingMinExitFlagThreshold to 0 to avoid Exit bandwidth requirements +TestingMinExitFlagThreshold 0 + DataDirectory $dir RunAsDaemon 1 ConnLimit $connlimit @@ -7,6 +32,8 @@ ShutdownWaitLength 0 PidFile ${dir}/pid Log notice file ${dir}/notice.log Log info file ${dir}/info.log +# Turn this off to save space +#Log debug file ${dir}/debug.log ProtocolWarnings 1 SafeLogging 0 DisableDebuggerAttachment 0 diff --git a/torrc_templates/exit-v4.i b/torrc_templates/exit-v4.i index eca35e0..375164b 100644 --- a/torrc_templates/exit-v4.i +++ b/torrc_templates/exit-v4.i @@ -1,3 +1,17 @@ # An exit policy that allows exiting to IPv4 localhost -ExitPolicy accept 127.0.0.0/8:* +#ExitPolicy accept 127.0.0.0/8:* + +# An exit policy that allows exiting to the entire internet on HTTP(S) +# This may be required to work around #11264 with microdescriptors enabled +# "The core of this issue appears to be that the Exit flag code is +# optimistic (just needs a /8 and 2 ports), but the microdescriptor +# exit policy summary code is pessimistic (needs the entire internet)." +# An alternative is to disable microdescriptors and use regular +# descriptors, as they do not suffer from this issue. +#ExitPolicy accept *:80 +#ExitPolicy accept *:443 + +#ExitPolicy reject *:* +# OR +ExitPolicy accept *:* diff --git a/torrc_templates/exit-v6.i b/torrc_templates/exit-v6.i index 74232a5..5200f3e 100644 --- a/torrc_templates/exit-v6.i +++ b/torrc_templates/exit-v6.i @@ -1,4 +1,18 @@ # An exit policy that allows exiting to IPv6 localhost -ExitPolicy accept [::1]:* +#ExitPolicy accept6 [::1]:* IPv6Exit 1 + +# An exit policy that allows exiting to the entire internet on HTTP(S) +# This may be required to work around #11264 with microdescriptors enabled +# "The core of this issue appears to be that the Exit flag code is +# optimistic (just needs a /8 [IP6?] and 2 ports), but the microdescriptor +# exit policy summary code is pessimistic (needs the entire internet)." +# An alternative is to disable microdescriptors and use regular +# descriptors, as they do not suffer from this issue. +#ExitPolicy accept6 *:80 +#ExitPolicy accept6 *:443 + +#ExitPolicy reject6 *:* +# OR +ExitPolicy accept6 *:* diff --git a/torrc_templates/relay-non-exit.tmpl b/torrc_templates/relay-non-exit.tmpl index 2f4b7f1..bf870a6 100644 --- a/torrc_templates/relay-non-exit.tmpl +++ b/torrc_templates/relay-non-exit.tmpl @@ -3,7 +3,13 @@ SocksPort 0 OrPort $orport Address $ip DirPort $dirport + #NOTE: Setting TestingServerConsensusDownloadSchedule doesn't # help -- dl_stats.schedule is not DL_SCHED_CONSENSUS # at boostrap time. -TestingServerDownloadSchedule 10, 2, 2, 4, 4, 8, 13, 18, 25, 40, 60 +# Try to download after: +# the minimum initial consensus time to start with, +# a few eager fetches, +# then half the minimum testing consensus interval +TestingServerDownloadSchedule 0, 5 +TestingServerConsensusDownloadSchedule 0, 5

1 0

[chutney/master] Merge commit '05d9d63548dff686f66b2f1322a7f80e452462a1'
by nickm＠torproject.org 30 Dec '14

30 Dec '14

commit 0a2e018bc8822701b5218c83852a81bdcf85f58e Merge: de810e6 05d9d63 Author: Nick Mathewson <nickm(a)torproject.org> Date: Tue Dec 30 09:57:52 2014 -0500 Merge commit '05d9d63548dff686f66b2f1322a7f80e452462a1' torrc_templates/authority.tmpl | 33 +++++++++++++++++++++++++++------ torrc_templates/bridge-v6.tmpl | 2 +- torrc_templates/bridge.tmpl | 7 ++----- torrc_templates/bridgeauthority.tmpl | 2 +- torrc_templates/bridgeclient.tmpl | 13 ++++++++++++- torrc_templates/client.tmpl | 8 +++++++- torrc_templates/common.i | 27 +++++++++++++++++++++++++++ torrc_templates/exit-v4.i | 16 +++++++++++++++- torrc_templates/exit-v6.i | 16 +++++++++++++++- torrc_templates/relay-non-exit.tmpl | 8 +++++++- 10 files changed, 114 insertions(+), 18 deletions(-)

1 0

[torspec/master] If the consensus doesn't contain exits, don't build exit paths
by nickm＠torproject.org 30 Dec '14

30 Dec '14

commit 96f068af4430a1965cdd792fa318be82b2da37e6 Author: teor <teor2345(a)gmail.com> Date: Sat Dec 20 11:29:47 2014 +1100 If the consensus doesn't contain exits, don't build exit paths If the consensus doesn't contain exits, we only build internal paths. This is enough to allow reachability tests (which can enable exits to bootstrap), and hidden services. If we subsequently receive a consensus with exits, start building exit paths. Update dir-spec and path-spec to document this. Update control-spec to document changes in controller bootstrap messages. Based on changes made in tor to resolve bug #13814. --- control-spec.txt | 110 +++++++++++++++++++++++++++++++++++++++++++----------- dir-spec.txt | 18 ++++++++- path-spec.txt | 23 +++++++++--- 3 files changed, 124 insertions(+), 27 deletions(-) diff --git a/control-spec.txt b/control-spec.txt index 1ac6bfd..04fa34e 100644 --- a/control-spec.txt +++ b/control-spec.txt @@ -1873,6 +1873,10 @@ ENOUGH_DIR_INFO Tor now knows enough network-status documents and enough server descriptors that it's going to start trying to build circuits now. + [Newer versions of Tor (0.2.6.1-alpha and later): + If the consensus contains Exits (the typical case), Tor will build + both exit and internal circuits. If not, Tor will only build internal + circuits.] {Controllers may want to use this event to decide when to indicate progress to their users, but should not interrupt the user's browsing @@ -2615,6 +2619,21 @@ Current Tor versions enter these phases in order, monotonically. Future Tors MAY revisit earlier stages. + [XXXX: do we revisit earlier stages if the network fails?] + + [Newer versions of Tor (0.2.6.1-alpha and later): + If the consensus contains Exits (the typical case), Tor will build both + exit and internal circuits. When bootstrap completes, Tor will be ready + to handle an application requesting an exit circuit to services like the + World Wide Web. + + If the consensus does not contain Exits, Tor will only build internal + circuits. In this case, earlier statuses will have included "internal" + as indicated above. When bootstrap completes, Tor will be ready to handle + an application requesting an internal circuit to hidden services at + ".onion" addresses. + + If a future consensus contains Exits, exit circuits may become available.] Phase 0: tag=starting summary="Starting" @@ -2622,31 +2641,32 @@ Tor starts out in this phase. Phase 5: - tag=conn_dir summary="Connecting to directory mirror" + tag=conn_dir summary="Connecting to directory server" - Tor sends this event as soon as Tor has chosen a directory mirror -- + Tor sends this event as soon as Tor has chosen a directory server -- e.g. one of the authorities if bootstrapping for the first time or after a long downtime, or one of the relays listed in its cached directory information otherwise. Tor will stay at this phase until it has successfully established - a TCP connection with some directory mirror. Problems in this phase + a TCP connection with some directory server. Problems in this phase generally happen because Tor doesn't have a network connection, or because the local firewall is dropping SYN packets. Phase 10: - tag=handshake_dir summary="Finishing handshake with directory mirror" + tag=handshake_dir summary="Finishing handshake with directory server" - This event occurs when Tor establishes a TCP connection with a relay used - as a directory mirror (or its https proxy if it's using one). Tor remains - in this phase until the TLS handshake with the relay is finished. + This event occurs when Tor establishes a TCP connection with a relay or + authority used as a directory server (or its https proxy if it's using + one). Tor remains in this phase until the TLS handshake with the relay + or authority is finished. Problems in this phase generally happen because Tor's firewall is doing more sophisticated MITM attacks on it, or doing packet-level keyword recognition of Tor's handshake. Phase 15: - tag=onehop_create summary="Establishing one-hop circuit for dir info" + tag=onehop_create summary="Establishing an encrypted directory connection" Once TLS is finished with a relay, Tor will send a CREATE_FAST cell to establish a one-hop circuit for retrieving directory information. @@ -2669,7 +2689,7 @@ phase is a good opportunity for using the "progress" keyword to indicate partial progress. - This phase could stall if the directory mirror we picked doesn't + This phase could stall if the directory server we picked doesn't have a copy of the networkstatus consensus so we have to ask another, or it does give us a copy but we don't find it valid. @@ -2682,51 +2702,99 @@ fetched on hold and fetch the keys so we can verify the signatures. Phase 45 - tag=requesting_descriptors summary="Asking for relay descriptors" + tag=requesting_descriptors summary="Asking for relay descriptors + [ for internal paths]" Once we have a valid networkstatus consensus and we've checked all its signatures, we start asking for relay descriptors. We stay in this phase until we have received a 'connected' relay cell in response to a request for descriptors. + [Newer versions of Tor (0.2.6.1-alpha and later): + If the consensus contains Exits (the typical case), Tor will ask for + descriptors for both exit and internal paths. If not, Tor will only ask + for descriptors for internal paths. In this case, this status will + include "internal" as indicated above.] + Phase 50: - tag=loading_descriptors summary="Loading relay descriptors" + tag=loading_descriptors summary="Loading relay descriptors[ for internal + paths]" We will ask for relay descriptors from several different locations, so this step will probably make up the bulk of the bootstrapping, especially for users with slow connections. We stay in this phase until - we have descriptors for at least 1/4 of the usable relays listed in - the networkstatus consensus. This phase is also a good opportunity to - use the "progress" keyword to indicate partial steps. + we have descriptors for a significant fraction of the usable relays + listed in the networkstatus consensus (this can be between 25% and 95% + depending on Tor's configuration and network consensus parameters). + This phase is also a good opportunity to use the "progress" keyword to + indicate partial steps. + + [Newer versions of Tor (0.2.6.1-alpha and later): + If the consensus contains Exits (the typical case), Tor will download + descriptors for both exit and internal paths. If not, Tor will only + download descriptors for internal paths. In this case, this status will + include "internal" as indicated above.] Phase 80: - tag=conn_or summary="Connecting to entry guard" + tag=conn_or summary="Connecting to the Tor network[ internally]" Once we have a valid consensus and enough relay descriptors, we choose - some entry guards and start trying to build some circuits. This step + entry guard(s) and start trying to build some circuits. This step is similar to the "conn_dir" phase above; the only difference is the context. If a Tor starts with enough recent cached directory information, its first bootstrap status event will be for the conn_or phase. + [Newer versions of Tor (0.2.6.1-alpha and later): + If the consensus contains Exits (the typical case), Tor will build both + exit and internal circuits. If not, Tor will only build internal circuits. + In this case, this status will include "internal(ly)" as indicated above.] + Phase 85: - tag=handshake_or summary="Finishing handshake with entry guard" + tag=handshake_or summary="Finishing handshake with first hop[ of internal + circuit]" This phase is similar to the "handshake_dir" phase, but it gets reached if we finish a TCP connection to a Tor relay and we have already reached the "conn_or" phase. We'll stay in this phase until we complete a TLS handshake with a Tor relay. + [Newer versions of Tor (0.2.6.1-alpha and later): + If the consensus contains Exits (the typical case), Tor may be finishing + a handshake with the first hop if either an exit or internal circuit. In + this case, it won't specify which type. If the consensus contains no Exits, + Tor will only build internal circuits. In this case, this status will + include "internal" as indicated above.] + Phase 90: - tag=circuit_create summary="Establishing circuits" + tag=circuit_create summary="Establishing a[n internal] Tor circuit" + + Once we've finished our TLS handshake with the first hop of a circuit, + we will set about trying to make some 3-hop circuits in case we need them + soon. - Once we've finished our TLS handshake with an entry guard, we will - set about trying to make some 3-hop circuits in case we need them soon. + [Newer versions of Tor (0.2.6.1-alpha and later): + If the consensus contains Exits (the typical case), Tor will build both + exit and internal circuits. If not, Tor will only build internal circuits. + In this case, this status will include "internal" as indicated above.] Phase 100: tag=done summary="Done" - A full 3-hop exit circuit has been established. Tor is ready to handle + A full 3-hop circuit has been established. Tor is ready to handle application connections now. + [Newer versions of Tor (0.2.6.1-alpha and later): + If the consensus contains Exits (the typical case), Tor will build both + exit and internal circuits. At this stage, Tor will be ready to handle + an application requesting an exit circuit to services like the World + Wide Web. + + If the consensus does not contain Exits, Tor will only build internal + circuits. In this case, earlier statuses will have included "internal" + as indicated above. At this stage, Tor will be ready to handle an + application requesting an internal circuit to hidden services at ".onion" + addresses. + + If a future consensus contains Exits, exit circuits may become available.] diff --git a/dir-spec.txt b/dir-spec.txt index 54a0437..9049c35 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -2689,7 +2689,23 @@ On failure, the client waits briefly, then tries that network-status document again from another cache. The client does not build circuits until it has a live network-status consensus document, and it has - descriptors for more than 1/4 of the routers that it believes are running. + descriptors for a significant proportion of the routers that it believes + are running (this is configurable using torrc options and consensus + parameters). + + [Newer versions of Tor (0.2.6.1-alpha and later): + If the consensus contains Exits (the typical case), Tor will build both + exit and internal circuits. When bootstrap completes, Tor will be ready + to handle an application requesting an exit circuit to services like the + World Wide Web. + + If the consensus does not contain Exits, Tor will only build internal + circuits. In this case, earlier statuses will have included "internal" + as indicated above. When bootstrap completes, Tor will be ready to handle + an application requesting an internal circuit to hidden services at + ".onion" addresses. + + If a future consensus contains Exits, exit circuits may become available.] (Note: clients can and should pick caches based on the network-status information they have: once they have first fetched network-status info diff --git a/path-spec.txt b/path-spec.txt index f3c7c9f..192bbc7 100644 --- a/path-spec.txt +++ b/path-spec.txt @@ -28,6 +28,20 @@ of their choices. that no current circuit can handle, for testing the network or our reachability, and so on). + [Newer versions of Tor (0.2.6.1-alpha and later): + If the consensus contains Exits (the typical case), Tor will build both + exit and internal circuits. When bootstrap completes, Tor will be ready + to handle an application requesting an exit circuit to services like the + World Wide Web. + + If the consensus does not contain Exits, Tor will only build internal + circuits. In this case, earlier statuses will have included "internal" + as indicated above. When bootstrap completes, Tor will be ready to handle + an application requesting an internal circuit to hidden services at + ".onion" addresses. + + If a future consensus contains Exits, exit circuits may become available.] + When a client application creates a new stream (by opening a SOCKS connection or launching a resolve request), we attach it to an appropriate open circuit if one exists, or wait if an appropriate circuit is @@ -659,12 +673,12 @@ of their choices. Clients maintain two usage counts for each of their guards: a count of the number of usage attempts, and a count of the number of successful usages. - + A usage attempt means any attempt to attach a stream to a circuit. Usage success status is temporarily recorded by state flags on circuits. Guard usage success counts are not incremented until circuit close. A - circuit is marked as successfully used if we receive a properly + circuit is marked as successfully used if we receive a properly recognized RELAY cell on that circuit that was expected for the current circuit purpose. @@ -733,7 +747,7 @@ of their choices. Min: 0 Max: 100 Effect: If the circuit success rate falls below this percentage, - we emit a more alarmist warning log message. If + we emit a more alarmist warning log message. If pb_dropguard is set to 1, we also disable the use of the guard. @@ -791,7 +805,7 @@ of their choices. version of the defense is unlikely to be deployed until the ntor circuit handshake is enabled, or the nature of CPU overload induced failure is better understood. - + X. Old notes @@ -844,4 +858,3 @@ X.3. Some stuff that worries me about entry guards. 2006 Jun, Nickm. [Do we do any of this now? If not, this should move into 099-misc or 098-todo. -NM] -

1 0

[torspec/master] Actually, this patch is going into 0.2.6.2-alpha, not 0.2.6.1-alpha
by nickm＠torproject.org 30 Dec '14

30 Dec '14

commit 9098fab087224611617a4cf076716c67f25eeed4 Author: Nick Mathewson <nickm(a)torproject.org> Date: Tue Dec 30 09:56:14 2014 -0500 Actually, this patch is going into 0.2.6.2-alpha, not 0.2.6.1-alpha --- control-spec.txt | 16 ++++++++-------- dir-spec.txt | 2 +- path-spec.txt | 2 +- 3 files changed, 10 insertions(+), 10 deletions(-) diff --git a/control-spec.txt b/control-spec.txt index 04fa34e..88319ff 100644 --- a/control-spec.txt +++ b/control-spec.txt @@ -1873,7 +1873,7 @@ ENOUGH_DIR_INFO Tor now knows enough network-status documents and enough server descriptors that it's going to start trying to build circuits now. - [Newer versions of Tor (0.2.6.1-alpha and later): + [Newer versions of Tor (0.2.6.2-alpha and later): If the consensus contains Exits (the typical case), Tor will build both exit and internal circuits. If not, Tor will only build internal circuits.] @@ -2621,7 +2621,7 @@ Future Tors MAY revisit earlier stages. [XXXX: do we revisit earlier stages if the network fails?] - [Newer versions of Tor (0.2.6.1-alpha and later): + [Newer versions of Tor (0.2.6.2-alpha and later): If the consensus contains Exits (the typical case), Tor will build both exit and internal circuits. When bootstrap completes, Tor will be ready to handle an application requesting an exit circuit to services like the @@ -2710,7 +2710,7 @@ phase until we have received a 'connected' relay cell in response to a request for descriptors. - [Newer versions of Tor (0.2.6.1-alpha and later): + [Newer versions of Tor (0.2.6.2-alpha and later): If the consensus contains Exits (the typical case), Tor will ask for descriptors for both exit and internal paths. If not, Tor will only ask for descriptors for internal paths. In this case, this status will @@ -2729,7 +2729,7 @@ This phase is also a good opportunity to use the "progress" keyword to indicate partial steps. - [Newer versions of Tor (0.2.6.1-alpha and later): + [Newer versions of Tor (0.2.6.2-alpha and later): If the consensus contains Exits (the typical case), Tor will download descriptors for both exit and internal paths. If not, Tor will only download descriptors for internal paths. In this case, this status will @@ -2746,7 +2746,7 @@ If a Tor starts with enough recent cached directory information, its first bootstrap status event will be for the conn_or phase. - [Newer versions of Tor (0.2.6.1-alpha and later): + [Newer versions of Tor (0.2.6.2-alpha and later): If the consensus contains Exits (the typical case), Tor will build both exit and internal circuits. If not, Tor will only build internal circuits. In this case, this status will include "internal(ly)" as indicated above.] @@ -2760,7 +2760,7 @@ the "conn_or" phase. We'll stay in this phase until we complete a TLS handshake with a Tor relay. - [Newer versions of Tor (0.2.6.1-alpha and later): + [Newer versions of Tor (0.2.6.2-alpha and later): If the consensus contains Exits (the typical case), Tor may be finishing a handshake with the first hop if either an exit or internal circuit. In this case, it won't specify which type. If the consensus contains no Exits, @@ -2774,7 +2774,7 @@ we will set about trying to make some 3-hop circuits in case we need them soon. - [Newer versions of Tor (0.2.6.1-alpha and later): + [Newer versions of Tor (0.2.6.2-alpha and later): If the consensus contains Exits (the typical case), Tor will build both exit and internal circuits. If not, Tor will only build internal circuits. In this case, this status will include "internal" as indicated above.] @@ -2785,7 +2785,7 @@ A full 3-hop circuit has been established. Tor is ready to handle application connections now. - [Newer versions of Tor (0.2.6.1-alpha and later): + [Newer versions of Tor (0.2.6.2-alpha and later): If the consensus contains Exits (the typical case), Tor will build both exit and internal circuits. At this stage, Tor will be ready to handle an application requesting an exit circuit to services like the World diff --git a/dir-spec.txt b/dir-spec.txt index 9049c35..1fdafbd 100644 --- a/dir-spec.txt +++ b/dir-spec.txt @@ -2693,7 +2693,7 @@ are running (this is configurable using torrc options and consensus parameters). - [Newer versions of Tor (0.2.6.1-alpha and later): + [Newer versions of Tor (0.2.6.2-alpha and later): If the consensus contains Exits (the typical case), Tor will build both exit and internal circuits. When bootstrap completes, Tor will be ready to handle an application requesting an exit circuit to services like the diff --git a/path-spec.txt b/path-spec.txt index 192bbc7..64886dc 100644 --- a/path-spec.txt +++ b/path-spec.txt @@ -28,7 +28,7 @@ of their choices. that no current circuit can handle, for testing the network or our reachability, and so on). - [Newer versions of Tor (0.2.6.1-alpha and later): + [Newer versions of Tor (0.2.6.2-alpha and later): If the consensus contains Exits (the typical case), Tor will build both exit and internal circuits. When bootstrap completes, Tor will be ready to handle an application requesting an exit circuit to services like the

1 0

[tor/master] Lintchanges some more.
by nickm＠torproject.org 30 Dec '14

30 Dec '14

commit b32e10253cb3698245aab632b43e98165f09c186 Author: Nick Mathewson <nickm(a)torproject.org> Date: Tue Dec 30 09:39:12 2014 -0500 Lintchanges some more. --- changes/bug13718-add-internal-bootstrap-statuses | 4 +-- changes/bug13718-avoid-excluding-guards | 4 +-- changes/bug13718-check-consensus-exits | 6 ---- changes/bug13718-make-nodelist-args-readable | 8 ------ changes/bug13814-avoid-exit-paths-no-exits | 31 +++++---------------- changes/bug13814-reachability-without-exits | 14 +++------- changes/bug13823-decrease-consensus-interval | 2 +- changes/bug13839-fix-TestingMinExitFlagThreshold | 5 ++-- changes/bug13924-fix-testing-reachability | 4 +-- changes/bug13963-decrease-if-modified-since-delay | 1 + 10 files changed, 21 insertions(+), 58 deletions(-) diff --git a/changes/bug13718-add-internal-bootstrap-statuses b/changes/bug13718-add-internal-bootstrap-statuses index d3e9a77..add2e8e 100644 --- a/changes/bug13718-add-internal-bootstrap-statuses +++ b/changes/bug13718-add-internal-bootstrap-statuses @@ -1,4 +1,4 @@ - o Minor bugfixes: + o Minor bugfixes (Testing networks): - Add "internal" to some bootstrap statuses when no exits are available. If the consensus does not contain Exits, Tor will only build internal circuits. In this case, relevant statuses will contain the word @@ -6,4 +6,4 @@ completes, Tor will be ready to handle an application requesting an internal circuit to hidden services at ".onion" addresses. If a future consensus contains Exits, exit circuits may become available. - Consequential change from #13718. + Fixes part of bug 13718; bugfix on 0.2.4.10-alpha. Patch by "teor". diff --git a/changes/bug13718-avoid-excluding-guards b/changes/bug13718-avoid-excluding-guards index bf80d2a..8bb4fa3 100644 --- a/changes/bug13718-avoid-excluding-guards +++ b/changes/bug13718-avoid-excluding-guards @@ -1,8 +1,8 @@ - o Minor bugfixes: + o Minor bugfixes (Test networks): - Avoid excluding guards from path building in minimal test networks, when we're in a test network, and excluding guards would exclude all nodes. This typically occurs in incredibly small tor networks, and those using TestingAuthVoteGuard * This fix only applies to minimal, testing tor networks, so it's no less secure. - Discovered as part of #13718. + Fixes part of bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor". diff --git a/changes/bug13718-check-consensus-exits b/changes/bug13718-check-consensus-exits deleted file mode 100644 index 5ca4b11..0000000 --- a/changes/bug13718-check-consensus-exits +++ /dev/null @@ -1,6 +0,0 @@ - o Minor enhancement: - - Check if there are exits in the consensus. - Add router_have_consensus_path() which reports whether - the consensus has exit paths, internal paths, or whether it - just doesn't know. - Used by #13718 and #13814. diff --git a/changes/bug13718-make-nodelist-args-readable b/changes/bug13718-make-nodelist-args-readable deleted file mode 100644 index 7377a81..0000000 --- a/changes/bug13718-make-nodelist-args-readable +++ /dev/null @@ -1,8 +0,0 @@ - o Minor refactoring: - - Refactor count_usable_descriptors to use named enums for exit_only. - count_usable_descriptors now uses named exit_only values: - * USABLE_DESCRIPTOR_ALL - * USABLE_DESCRIPTOR_EXIT_ONLY - - Add debug logging code for descriptor counts. - This resolves nickm's request in bug 13718 to improve argument - readability. diff --git a/changes/bug13814-avoid-exit-paths-no-exits b/changes/bug13814-avoid-exit-paths-no-exits index 8b0446f..8276121 100644 --- a/changes/bug13814-avoid-exit-paths-no-exits +++ b/changes/bug13814-avoid-exit-paths-no-exits @@ -1,25 +1,8 @@ - o Minor bugfixes: - - Avoid building exit circuits from a consensus with no exits - Tor can now build circuits from a consensus with no exits. - But if it tries to build exit circuits, they fail and flood the logs. - The circuit types in the Exit Circuits list below will only be - built if the current consensus has exits. If it doesn't, - only the Internal Circuits will be built. (This can change - with each new consensus.) - Fixes bug #13814, causes fewer path failures due to #13817. + o Minor features (Testing networks): + - Avoid building exit circuits from a consensus with no exits. + Now thanks to our fix for 13718, + we accept a no-exit network as not wholly lost, but + we need to remember not to try to build exit circuits on it. + Closes ticket 13814; + patch by "teor". - Exit Circuits: - Predicted Exit Circuits - User Traffic Circuits - Most AP Streams - Circuits Marked Exit - Build Timeout Circuits (with exits) - - Internal Circuits: - Hidden Service Server Circuits - Hidden Service Client Circuits - Hidden Service AP Streams - Hidden Service Intro Point Streams - Circuits Marked Internal - Build Timeout Circuits (with no exits) - Other Circuits? diff --git a/changes/bug13814-reachability-without-exits b/changes/bug13814-reachability-without-exits index 43a326b..07f2d8a 100644 --- a/changes/bug13814-reachability-without-exits +++ b/changes/bug13814-reachability-without-exits @@ -1,15 +1,9 @@ - o Minor bugfixes: - - Allow tor to build circuits using a consensus with + o Minor bugfixes (Testing networks): + - Allow Tor to build circuits using a consensus with no exits. If the consensus has no exits (typical of - a bootstrapping test network), allow tor to build + a bootstrapping test network), allow Tor to build circuits once enough descriptors have been downloaded. - When there are no exits, we always have "enough" - exit descriptors. (We treat the proportion of - available exit descriptors as 100%.) This assists in bootstrapping a testing Tor network. - Fixes bug 13718. - Makes bug 13161's TestingDirAuthVoteExit - non-essential. - (But still useful for speeding up a bootstrap.) + Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch by "teor". diff --git a/changes/bug13823-decrease-consensus-interval b/changes/bug13823-decrease-consensus-interval index 67f0b9f..cc0e6c7 100644 --- a/changes/bug13823-decrease-consensus-interval +++ b/changes/bug13823-decrease-consensus-interval @@ -6,4 +6,4 @@ This assists in quickly bootstrapping a testing Tor network. Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. - + Patch by "teor". diff --git a/changes/bug13839-fix-TestingMinExitFlagThreshold b/changes/bug13839-fix-TestingMinExitFlagThreshold index e0fa270..86315de 100644 --- a/changes/bug13839-fix-TestingMinExitFlagThreshold +++ b/changes/bug13839-fix-TestingMinExitFlagThreshold @@ -3,6 +3,5 @@ TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0, ignore exit bandwidthcapacity. This assists in bootstrapping a testing Tor network. - Fixes bugs parts of bugs 13718 and 13839; - Makes bug 13161's TestingDirAuthVoteExit non-essential. - Bugfix on 0.2.0.3-alpha. + Fixes parts of bugs 13718 and 13839; + bugfix on 0.2.0.3-alpha. Patch by "teor". diff --git a/changes/bug13924-fix-testing-reachability b/changes/bug13924-fix-testing-reachability index 914a159..e10dda8 100644 --- a/changes/bug13924-fix-testing-reachability +++ b/changes/bug13924-fix-testing-reachability @@ -1,7 +1,7 @@ - o Minor bugfixes: + o Minor bugfixes (Testing networks) - Stop assuming that private addresses are local when checking reachability in a TestingTorNetwork. Instead, when testing, assume all OR connections are remote. (This is necessary due to many test scenarios running all nodes on localhost.) This assists in bootstrapping a testing Tor network. - Fixes bugs 13718 & 13924. + Fixes bug 13924; bugfix on 0.1.0.1-rc. Patch by "teor". diff --git a/changes/bug13963-decrease-if-modified-since-delay b/changes/bug13963-decrease-if-modified-since-delay index d4bbc1b..26bda82 100644 --- a/changes/bug13963-decrease-if-modified-since-delay +++ b/changes/bug13963-decrease-if-modified-since-delay @@ -5,3 +5,4 @@ interval is very short. This assists in bootstrapping a testing Tor network. Fixes parts of bugs 13718 and 13963; bugfix on 0.2.0.3-alpha. + Patch by "teor". \ No newline at end of file

1 0

[tor/master] Fold more things into the 0.2.6.2-alpha changelog
by nickm＠torproject.org 30 Dec '14

30 Dec '14

commit 03e9aa094185e55e120f2fffa01da62b5a7b44df Author: Nick Mathewson <nickm(a)torproject.org> Date: Tue Dec 30 09:53:13 2014 -0500 Fold more things into the 0.2.6.2-alpha changelog --- ChangeLog | 106 +++++++++++++++++++-- changes/bug13667 | 6 -- changes/bug13718-add-internal-bootstrap-statuses | 9 -- changes/bug13718-avoid-excluding-guards | 8 -- changes/bug13808 | 9 -- changes/bug13811 | 6 -- changes/bug13814-avoid-exit-paths-no-exits | 8 -- changes/bug13814-reachability-without-exits | 9 -- changes/bug13823-decrease-consensus-interval | 9 -- changes/bug13839-fix-TestingMinExitFlagThreshold | 7 -- changes/bug13913 | 7 -- changes/bug13924-fix-testing-reachability | 7 -- changes/bug13963-decrease-if-modified-since-delay | 8 -- changes/bug14013 | 6 -- changes/bug14041 | 5 - changes/resolvemyaddr-tests | 3 - changes/ticket11016 | 6 -- 17 files changed, 99 insertions(+), 120 deletions(-) diff --git a/ChangeLog b/ChangeLog index d7c9430..18bd536 100644 --- a/ChangeLog +++ b/ChangeLog @@ -18,6 +18,10 @@ Changes in version 0.2.6.2-alpha - 2014-12-?? implements ticket 9262. o Major features (hidden services): + - Make HS port scanning more difficult by sending back REASON_DONE + if the exit policy didn't match. Furthermore, immediately close + the circuit to slow down port scanning attempts. Closes + ticket 13667. - Add a HiddenServiceStatistics option that allows Tor relays to gather and publish statistics the overall size and volume of hidden service usage. Specifically, when this option is turned on, @@ -30,6 +34,13 @@ Changes in version 0.2.6.2-alpha - 2014-12-?? proposal 238, "Better hidden service stats from Tor relays". This feature is currently disabled by default. Implements feature 13192. + o Major bugfixes (client, automap): + - Repair automapping with IPv6 addresses; this automapping should + have worked previously, but one piece of debugging code that we + inserted to detect a regression actually caused the regression to + manifest itself again. Fixes bug 13811; bugfix on 0.2.4.7-alpha. + Diagnosed and fixed by Francisco Blas Izquierdo Riera. + o Major bugfixes (hidden services): - When closing an introduction circuit that was opened in parallel with others, don't mark the introduction point as unreachable. @@ -37,6 +48,12 @@ Changes in version 0.2.6.2-alpha - 2014-12-?? point would make the other introduction points get marked as having timed out. Fixes bug 13698; bugfix on 0.0.6rc2. + o Major removed features: + - Tor clients no longer support connecting to hidden services + running on Tor 0.2.2.x and earlier; the Support022HiddenServices + option has been removed. (There shouldn't be any hidden services + running these versions on the network.) Closes ticket 7803. + o Minor features (client): - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks is enabled, reject requests with IP addresses as hostnames. @@ -63,9 +80,29 @@ Changes in version 0.2.6.2-alpha - 2014-12-?? directories and hostname files to be created group-readable. Patch from "anon", David Stainton, and "meejah". Closes ticket 11291. - o Minor features (transparent firewall): + o Minor features (systemd): + - Where supported, when running with systemd, report successful + startup to systemd. Part of ticket 11016. Patch by Michael Scherer. + - When running with systemd, support systemd watchdog messages. Part + of ticket 11016. Patch by Michael Scherer. + + o Minor features (transparent proxy): - Update the transparent proxy option checks to allow for both ipfw and pf on OS X. Closes ticket 14002. + - Use the correct option when using IPv6 with transparent proxy + support on Linux. Resolves 13808. Patch by Francisco Blas + Izquierdo Riera. + + o Minor bugfixes (preventative security, C safety): + - When reading a hexadecimal, base-32, or base-64 encoded value from + a string, always overwrite the complete output buffer. This + prevents some bugs where we would look at (but fortunately, not + reveal) uninitialized memory on the stack. Fixes bug 14013; bugfix + on all versions of Tor. + - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not + just the part that's used. This makes it harder for data leak bugs + to occur in the event of other programming failures. Resolves + ticket 14041. o Minor bugfixes (client, micordescriptors): - Use a full 256 bits of the SHA256 digest of a microdescriptor when @@ -103,6 +140,11 @@ Changes in version 0.2.6.2-alpha - 2014-12-?? directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported by "special". + o Minor bugfixes (Linux seccomp2 sandbox): + - Make transparent proxy support work along with the seccomp2 + sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch + by Francisco Blas Izquierdo Riera. + o Minor bugfixes (logging): - Downgrade warnings about RSA signature failures to info log level. Emit a warning when extra info document is found incompatible with @@ -118,6 +160,56 @@ Changes in version 0.2.6.2-alpha - 2014-12-?? our address-range parsing code. Fixes bug 7484; bugfix on 0.0.2pre14. + o Minor bugfixes (testing networks): + - Allow Tor to build circuits using a consensus with no exits. If + the consensus has no exits (typical of a bootstrapping test + network), allow Tor to build circuits once enough descriptors have + been downloaded. This assists in bootstrapping a testing Tor + network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch + by "teor". + - When V3AuthVotingInterval is low, give a lower If-Modified-Since + header to directory servers. This allows us to obtain consensuses + promptly when the consensus interval is very short. This assists + in bootstrapping a testing Tor network. Fixes parts of bugs 13718 + and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor". + - Stop assuming that private addresses are local when checking + reachability in a TestingTorNetwork. Instead, when testing, assume + all OR connections are remote. (This is necessary due to many test + scenarios running all nodes on localhost.) This assists in + bootstrapping a testing Tor network. Fixes bug 13924; bugfix on + 0.1.0.1-rc. Patch by "teor". + - Avoid building exit circuits from a consensus with no exits. Now + thanks to our fix for 13718, we accept a no-exit network as not + wholly lost, but we need to remember not to try to build exit + circuits on it. Closes ticket 13814; patch by "teor". + - Stop requiring exits to have non-zero bandwithcapacity in a + TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0, + ignore exit bandwidthcapacity. This assists in bootstrapping a + testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix + on 0.2.0.3-alpha. Patch by "teor". + - Add "internal" to some bootstrap statuses when no exits are + available. If the consensus does not contain Exits, Tor will only + build internal circuits. In this case, relevant statuses will + contain the word "internal" as indicated in the Tor control- + spec.txt. When bootstrap completes, Tor will be ready to handle an + application requesting an internal circuit to hidden services at + ".onion" addresses. If a future consensus contains Exits, exit + circuits may become available. Fixes part of bug 13718; bugfix on + 0.2.4.10-alpha. Patch by "teor". + - Decrease minimum consensus interval to 10 seconds when + TestingTorNetwork is set, or 5 seconds for the first consensus. + Fix assumptions throughout the code that assume larger interval + values. This assists in quickly bootstrapping a testing Tor + network. Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. + Patch by "teor". + - Avoid excluding guards from path building in minimal test + networks, when we're in a test network, and excluding guards would + exclude all nodes. This typically occurs in incredibly small tor + networks, and those using TestingAuthVoteGuard * This fix only + applies to minimal, testing tor networks, so it's no less secure. + Fixes part of bug 13718; bugfix on 0.1.1.11-alpha. Patch + by "teor". + o Code simplification and refactoring: - Stop using can_complete_circuits as a global variable; access it with a function instead. @@ -153,12 +245,10 @@ Changes in version 0.2.6.2-alpha - 2014-12-?? good idea. Also, properly cross-reference how to specify nodes in all parts of the manual for options that take a list of nodes. Closes ticket 13381. - - o Major removed features: - - Tor clients no longer support connecting to hidden services - running on Tor 0.2.2.x and earlier; the Support022HiddenServices - option has been removed. (There shouldn't be any hidden services - running these versions on the network.) Closes ticket 7803. + - Clarify HiddenServiceDir option description in manpage to make it + clear that relative paths are taken with respect to the current + working directory of Tor instance. Also clarify that this behavior + is not guaranteed to remain indefinitely. Fixes issue 13913. o Testing: - New tests for many parts of channel, relay, and circuit mux @@ -168,6 +258,8 @@ Changes in version 0.2.6.2-alpha - 2014-12-?? test temporary directory to the current user, so that the sticky bit doesn't interfere with tests that check directory groups. Closes 13678. + - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch + by 'rl1987'. Changes in version 0.2.6.1-alpha - 2014-10-30 diff --git a/changes/bug13667 b/changes/bug13667 deleted file mode 100644 index 852e61f..0000000 --- a/changes/bug13667 +++ /dev/null @@ -1,6 +0,0 @@ - o Major features (security, hidden services): - - Make HS port scanning more difficult by sending back REASON_DONE if the - exit policy didn't match. Furthermore, immediately close the circuit to - avoid other connection attempts on it from the possible attacker trying - multiple ports on that same circuits. Closes ticket 13667. - diff --git a/changes/bug13718-add-internal-bootstrap-statuses b/changes/bug13718-add-internal-bootstrap-statuses deleted file mode 100644 index add2e8e..0000000 --- a/changes/bug13718-add-internal-bootstrap-statuses +++ /dev/null @@ -1,9 +0,0 @@ - o Minor bugfixes (Testing networks): - - Add "internal" to some bootstrap statuses when no exits are available. - If the consensus does not contain Exits, Tor will only build internal - circuits. In this case, relevant statuses will contain the word - "internal" as indicated in the Tor control-spec.txt. When bootstrap - completes, Tor will be ready to handle an application requesting an - internal circuit to hidden services at ".onion" addresses. - If a future consensus contains Exits, exit circuits may become available. - Fixes part of bug 13718; bugfix on 0.2.4.10-alpha. Patch by "teor". diff --git a/changes/bug13718-avoid-excluding-guards b/changes/bug13718-avoid-excluding-guards deleted file mode 100644 index 8bb4fa3..0000000 --- a/changes/bug13718-avoid-excluding-guards +++ /dev/null @@ -1,8 +0,0 @@ - o Minor bugfixes (Test networks): - - Avoid excluding guards from path building in minimal test networks, - when we're in a test network, and excluding guards would exclude - all nodes. This typically occurs in incredibly small tor networks, - and those using TestingAuthVoteGuard * - This fix only applies to minimal, testing tor networks, - so it's no less secure. - Fixes part of bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor". diff --git a/changes/bug13808 b/changes/bug13808 deleted file mode 100644 index b24a01c..0000000 --- a/changes/bug13808 +++ /dev/null @@ -1,9 +0,0 @@ - o Minor features (transparent proxy): - - Use the correct option when using IPv6 with transparent proxy - support on Linux. Resolves 13808. Patch by Francisco Blas - Izquierdo Riera. - - o Minor bugfixes (sandbox): - - Make transparent proxy support work along with the seccomp2 - sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. - Patch by Francisco Blas Izquierdo Riera. diff --git a/changes/bug13811 b/changes/bug13811 deleted file mode 100644 index 1b9bd9c..0000000 --- a/changes/bug13811 +++ /dev/null @@ -1,6 +0,0 @@ - o Major bugfixes (client, automap): - - Repair automapping with IPv6 addresses; this automapping should - have worked previously, but one piece of debugging code that we - inserted to detect a regression actually caused the regression - to manifest itself again. Fixes bug 13811; bugfix on - 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas Izquierdo Riera. \ No newline at end of file diff --git a/changes/bug13814-avoid-exit-paths-no-exits b/changes/bug13814-avoid-exit-paths-no-exits deleted file mode 100644 index 8276121..0000000 --- a/changes/bug13814-avoid-exit-paths-no-exits +++ /dev/null @@ -1,8 +0,0 @@ - o Minor features (Testing networks): - - Avoid building exit circuits from a consensus with no exits. - Now thanks to our fix for 13718, - we accept a no-exit network as not wholly lost, but - we need to remember not to try to build exit circuits on it. - Closes ticket 13814; - patch by "teor". - diff --git a/changes/bug13814-reachability-without-exits b/changes/bug13814-reachability-without-exits deleted file mode 100644 index 07f2d8a..0000000 --- a/changes/bug13814-reachability-without-exits +++ /dev/null @@ -1,9 +0,0 @@ - o Minor bugfixes (Testing networks): - - Allow Tor to build circuits using a consensus with - no exits. If the consensus has no exits (typical of - a bootstrapping test network), allow Tor to build - circuits once enough descriptors have been - downloaded. - This assists in bootstrapping a testing Tor - network. - Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch by "teor". diff --git a/changes/bug13823-decrease-consensus-interval b/changes/bug13823-decrease-consensus-interval deleted file mode 100644 index cc0e6c7..0000000 --- a/changes/bug13823-decrease-consensus-interval +++ /dev/null @@ -1,9 +0,0 @@ - o Minor bugfixes (Testing networks): - - Decrease minimum consensus interval to 10 seconds - when TestingTorNetwork is set, or 5 seconds for - the first consensus. - Fix assumptions throughout the code that assume larger interval values. - This assists in quickly bootstrapping a testing - Tor network. - Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. - Patch by "teor". diff --git a/changes/bug13839-fix-TestingMinExitFlagThreshold b/changes/bug13839-fix-TestingMinExitFlagThreshold deleted file mode 100644 index 86315de..0000000 --- a/changes/bug13839-fix-TestingMinExitFlagThreshold +++ /dev/null @@ -1,7 +0,0 @@ - o Minor bugfixes (Testing networks) - - Stop requiring exits to have non-zero bandwithcapacity in a - TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0, - ignore exit bandwidthcapacity. - This assists in bootstrapping a testing Tor network. - Fixes parts of bugs 13718 and 13839; - bugfix on 0.2.0.3-alpha. Patch by "teor". diff --git a/changes/bug13913 b/changes/bug13913 deleted file mode 100644 index 9a23180..0000000 --- a/changes/bug13913 +++ /dev/null @@ -1,7 +0,0 @@ - o Documentation: - - Clarify HiddenServiceDir option description in manpage to make it - clear that relative paths are taken with respect to the current - working - directory of Tor instance. Also clarify that this behavior is - not guaranteed to remain indefinitely. Fixes - issue 13913. diff --git a/changes/bug13924-fix-testing-reachability b/changes/bug13924-fix-testing-reachability deleted file mode 100644 index e10dda8..0000000 --- a/changes/bug13924-fix-testing-reachability +++ /dev/null @@ -1,7 +0,0 @@ - o Minor bugfixes (Testing networks) - - Stop assuming that private addresses are local when checking - reachability in a TestingTorNetwork. Instead, when testing, assume - all OR connections are remote. (This is necessary due to many test - scenarios running all nodes on localhost.) - This assists in bootstrapping a testing Tor network. - Fixes bug 13924; bugfix on 0.1.0.1-rc. Patch by "teor". diff --git a/changes/bug13963-decrease-if-modified-since-delay b/changes/bug13963-decrease-if-modified-since-delay deleted file mode 100644 index 26bda82..0000000 --- a/changes/bug13963-decrease-if-modified-since-delay +++ /dev/null @@ -1,8 +0,0 @@ - o Minor bugfixes: - - When V3AuthVotingInterval is low, decrease the delay on the - If-Modified-Since header passed to directory servers. - This allows us to obtain consensuses promptly when the consensus - interval is very short. - This assists in bootstrapping a testing Tor network. - Fixes parts of bugs 13718 and 13963; bugfix on 0.2.0.3-alpha. - Patch by "teor". \ No newline at end of file diff --git a/changes/bug14013 b/changes/bug14013 deleted file mode 100644 index 640cf85..0000000 --- a/changes/bug14013 +++ /dev/null @@ -1,6 +0,0 @@ - o Major bugfixes: - - When reading a hexadecimal, base-32, or base-64 encoded value - from a string, always overwrite the complete output buffer. This - prevents some bugs where we would look at (but fortunately, not - reveal) uninitialized memory on the stack. Fixes bug 14013; - bugfix on all versions of Tor. diff --git a/changes/bug14041 b/changes/bug14041 deleted file mode 100644 index d3d6538..0000000 --- a/changes/bug14041 +++ /dev/null @@ -1,5 +0,0 @@ - o Minor features (security): - - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), - not just the part that's used. This makes it harder for data leak - bugs to occur in the event of other programming failures. - Resolves ticket 14041. diff --git a/changes/resolvemyaddr-tests b/changes/resolvemyaddr-tests deleted file mode 100644 index c019bb8..0000000 --- a/changes/resolvemyaddr-tests +++ /dev/null @@ -1,3 +0,0 @@ - o Testing: - - Add unit tests for resolve_my_addr(). Part of ticket 12376; - patch by 'rl1987'. diff --git a/changes/ticket11016 b/changes/ticket11016 deleted file mode 100644 index 98d5d49..0000000 --- a/changes/ticket11016 +++ /dev/null @@ -1,6 +0,0 @@ - o Minor features (systemd): - - Where supported, when running with systemd, report successful - startup to systemd. Part of ticket 11016. Patch by Michael - Scherer. - - When running with systemd, support systemd watchdog messages. - Part of ticket 11016. Patch by Michael Scherer.

1 0

[translation/tails-misc] Update translations for tails-misc
by translation＠torproject.org 30 Dec '14

30 Dec '14

commit b87d59d7e285f26049b5c3c4c615735c2783560b Author: Translation commit bot <translation(a)torproject.org> Date: Tue Dec 30 14:45:47 2014 +0000 Update translations for tails-misc --- az.po | 53 +++++++++++++++++++++++++++-------------------------- 1 file changed, 27 insertions(+), 26 deletions(-) diff --git a/az.po b/az.po index 76ea08f..8e8f3d5 100644 --- a/az.po +++ b/az.po @@ -3,13 +3,14 @@ # This file is distributed under the same license as the PACKAGE package. # # Translators: +# E <ehuseynzade(a)gmail.com>, 2014 msgid "" msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2014-12-02 11:29+0100\n" -"PO-Revision-Date: 2014-12-21 15:51+0000\n" -"Last-Translator: runasand <runa.sandvik(a)gmail.com>\n" +"PO-Revision-Date: 2014-12-30 14:41+0000\n" +"Last-Translator: E <ehuseynzade(a)gmail.com>\n" "Language-Team: Azerbaijani (http://www.transifex.com/projects/p/torproject/language/az/)\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" @@ -19,11 +20,11 @@ msgstr "" #: config/chroot_local-includes/etc/NetworkManager/dispatcher.d/60-tor-ready-notification.sh:42 msgid "Tor is ready" -msgstr "" +msgstr "Tor hazırdır" #: config/chroot_local-includes/etc/NetworkManager/dispatcher.d/60-tor-ready-notification.sh:43 msgid "You can now access the Internet." -msgstr "" +msgstr "İndi internetə qoşula bilərsən." #: config/chroot_local-includes/etc/whisperback/config.py:64 #, python-format @@ -41,11 +42,11 @@ msgid "" "<p>Anyone who can see this reply will probably infer you are\n" "a Tails user. Time to wonder how much you trust your\n" "Internet and mailbox providers?</p>\n" -msgstr "" +msgstr "<h1>Problemini həll etmək üçün bizə kömək et!</h1>\n<p><a href=\"%s\">Bizim problem haqqında xəbər qaydalarımızı</a> oxu.</p>\n<p><strong>Lazım olandan artıq məlumat daxil\netmə!</strong></p>\n<h2>Bizə təqdim edilən email ünvan</h2>\n<p>Şəxsi məlumatlarının çox kiçik hissəsini Tails-ə\ndemək sənin üçün problem deyilsə, problemini daha\nyaxşı həll etməyimiz üçün email ünvanını bizə yaza bilərsən.\nİctimai PGP-in daxil edilməsi əlavə olaraq gələcək \nkommunikasiyamızı şifrələməyə imkan verir.</p>\n<p>Bu cavabı görə bilən hər kəs sənin Tails istifadəçisi\nolduğun nəticəsinə gələcək. \nİnternet və ya email təminatçılarına nə qədər inandığınla\nmaraqlanmaq vaxtıdır?</p>\n" #: config/chroot_local-includes/usr/local/bin/gpgApplet:136 msgid "OpenPGP encryption applet" -msgstr "" +msgstr "OpenPGP şifrələnmə apleti" #: config/chroot_local-includes/usr/local/bin/gpgApplet:139 msgid "Exit" @@ -57,41 +58,41 @@ msgstr "Haqqında" #: config/chroot_local-includes/usr/local/bin/gpgApplet:192 msgid "Encrypt Clipboard with _Passphrase" -msgstr "" +msgstr "Mübadilə Buferini _Şifrə İfadəsi ilə şifrələ" #: config/chroot_local-includes/usr/local/bin/gpgApplet:195 msgid "Sign/Encrypt Clipboard with Public _Keys" -msgstr "" +msgstr "İctimai _Açarlarla Mübadilə Buferinə/i Daxil Ol/Şifrələ" #: config/chroot_local-includes/usr/local/bin/gpgApplet:200 msgid "_Decrypt/Verify Clipboard" -msgstr "" +msgstr "Mübadilə Buferin/i _Şifrəsini Aç/Təsdiqlə" #: config/chroot_local-includes/usr/local/bin/gpgApplet:204 msgid "_Manage Keys" -msgstr "" +msgstr "Açarları _İdarə et" #: config/chroot_local-includes/usr/local/bin/gpgApplet:244 msgid "The clipboard does not contain valid input data." -msgstr "" +msgstr "Mübadilə buferində düzgün giriş məlumatı yoxdur." #: config/chroot_local-includes/usr/local/bin/gpgApplet:295 #: config/chroot_local-includes/usr/local/bin/gpgApplet:297 #: config/chroot_local-includes/usr/local/bin/gpgApplet:299 msgid "Unknown Trust" -msgstr "" +msgstr "Bilinməyən İnam" #: config/chroot_local-includes/usr/local/bin/gpgApplet:301 msgid "Marginal Trust" -msgstr "" +msgstr "Son İnam" #: config/chroot_local-includes/usr/local/bin/gpgApplet:303 msgid "Full Trust" -msgstr "" +msgstr "Tam İnam" #: config/chroot_local-includes/usr/local/bin/gpgApplet:305 msgid "Ultimate Trust" -msgstr "" +msgstr "Başlıca İnam" #: config/chroot_local-includes/usr/local/bin/gpgApplet:358 msgid "Name" @@ -99,15 +100,15 @@ msgstr "Name" #: config/chroot_local-includes/usr/local/bin/gpgApplet:359 msgid "Key ID" -msgstr "" +msgstr "Açar ID-si" #: config/chroot_local-includes/usr/local/bin/gpgApplet:360 msgid "Status" -msgstr "" +msgstr "Status" #: config/chroot_local-includes/usr/local/bin/gpgApplet:392 msgid "Fingerprint:" -msgstr "" +msgstr "Barmaq izi:" #: config/chroot_local-includes/usr/local/bin/gpgApplet:395 msgid "User ID:" @@ -117,33 +118,33 @@ msgstr[1] "" #: config/chroot_local-includes/usr/local/bin/gpgApplet:425 msgid "None (Don't sign)" -msgstr "" +msgstr "Heç biri (Giriş etmə)" #: config/chroot_local-includes/usr/local/bin/gpgApplet:488 msgid "Select recipients:" -msgstr "" +msgstr "Qəbul ediciləri seç:" #: config/chroot_local-includes/usr/local/bin/gpgApplet:496 msgid "Hide recipients" -msgstr "" +msgstr "Qəbul ediciləri gizlə" #: config/chroot_local-includes/usr/local/bin/gpgApplet:499 msgid "" "Hide the user IDs of all recipients of an encrypted message. Otherwise " "anyone that sees the encrypted message can see who the recipients are." -msgstr "" +msgstr "Şifrələnmiş mesajı qəbul edənlərin hamısının istifadəçi ID-ni gizlə. Əks halda, şifrələnmiş mesajı görən hər hansı şəxs onu qəbul edəni də görə bilər." #: config/chroot_local-includes/usr/local/bin/gpgApplet:505 msgid "Sign message as:" -msgstr "" +msgstr "Mesajı belə imzala:" #: config/chroot_local-includes/usr/local/bin/gpgApplet:509 msgid "Choose keys" -msgstr "" +msgstr "Açarları seç" #: config/chroot_local-includes/usr/local/bin/gpgApplet:549 msgid "Do you trust these keys?" -msgstr "" +msgstr "Bu açarlara inanırsan?" #: config/chroot_local-includes/usr/local/bin/gpgApplet:552 msgid "The following selected key is not fully trusted:" @@ -159,7 +160,7 @@ msgstr[1] "" #: config/chroot_local-includes/usr/local/bin/gpgApplet:583 msgid "No keys selected" -msgstr "" +msgstr "Açar seçilməyib" #: config/chroot_local-includes/usr/local/bin/gpgApplet:585 msgid ""

1 0

[translation/mat-gui_completed] Update translations for mat-gui_completed
by translation＠torproject.org 30 Dec '14

30 Dec '14

commit 1a21826617c17b270133596910a2c38a14147c7d Author: Translation commit bot <translation(a)torproject.org> Date: Tue Dec 30 14:45:38 2014 +0000 Update translations for mat-gui_completed --- az.po | 200 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 200 insertions(+) diff --git a/az.po b/az.po new file mode 100644 index 0000000..28a81e9 --- /dev/null +++ b/az.po @@ -0,0 +1,200 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER +# This file is distributed under the same license as the PACKAGE package. +# +# Translators: +# Translators: +# E <ehuseynzade(a)gmail.com>, 2014 +msgid "" +msgstr "" +"Project-Id-Version: The Tor Project\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2014-01-19 14:48+0000\n" +"PO-Revision-Date: 2014-12-30 14:31+0000\n" +"Last-Translator: E <ehuseynzade(a)gmail.com>\n" +"Language-Team: Azerbaijani (http://www.transifex.com/projects/p/torproject/language/az/)\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Language: az\n" +"Plural-Forms: nplurals=2; plural=(n != 1);\n" + +#: mat-gui:61 mat-gui:403 mat-gui:422 +msgid "Ready" +msgstr "Hazır" + +#: mat-gui:128 +msgid "Choose files" +msgstr "Faylları seç" + +#: mat-gui:135 +msgid "All files" +msgstr "Bütün fayllar" + +#: mat-gui:142 +msgid "Supported files" +msgstr "Dəstəklənən fayllar" + +#: mat-gui:157 +msgid "No metadata found" +msgstr "Metadata tapılmadı" + +#: mat-gui:158 mat-gui:398 mat-gui:420 +msgid "Clean" +msgstr "Təmizlə" + +#: mat-gui:160 mat-gui:400 +msgid "Dirty" +msgstr "Çirkli" + +#: mat-gui:165 +#, python-format +msgid "%s's metadata" +msgstr "%s-in metadatası" + +#: mat-gui:176 +msgid "Trash your meta, keep your data" +msgstr "Meta-nı sil, data-nı saxla" + +#: mat-gui:181 +msgid "Website" +msgstr "Veb səhifə" + +#: mat-gui:207 data/mat.ui:107 +msgid "Preferences" +msgstr "Xüsusiyyətlər" + +#: mat-gui:220 +msgid "Reduce PDF quality" +msgstr "PDF keyfiyyətini azalt" + +#: mat-gui:223 +msgid "Reduce the produced PDF size and quality" +msgstr "Hazırlanmış PDF-in ölçü və küyfiyyətini azalt" + +#: mat-gui:226 +msgid "Add unsupported file to archives" +msgstr "Dəstəklənməyən faylı arxivə əlavə et" + +#: mat-gui:229 +msgid "Add non-supported (and so non-anonymised) file to output archive" +msgstr "Dəstəklənməmiş (o cümlədən, qeyri-anonim) faylı çıxış arxivinə əlavə et" + +#: mat-gui:268 +msgid "Unknown" +msgstr "Tanınmayan" + +#: mat-gui:310 +msgid "Not-supported" +msgstr "Dəstəklənmir" + +#: mat-gui:324 +msgid "Harmless fileformat" +msgstr "Zərərli fayl formatı" + +#: mat-gui:326 +msgid "Fileformat not supported" +msgstr "Fayl formatı dəstəklənmir" + +#: mat-gui:329 +msgid "These files can not be processed:" +msgstr "Bu fayllar emal edilə bilmir:" + +#: mat-gui:334 mat-gui:363 data/mat.ui:292 +msgid "Filename" +msgstr "Fayl adı" + +#: mat-gui:336 +msgid "Reason" +msgstr "Səbəb" + +#: mat-gui:348 +msgid "Non-supported files in archive" +msgstr "Arxivdəki dəstəklənməyən fayllar" + +#: mat-gui:349 data/mat.ui:227 +msgid "Scour" +msgstr "Təmizləmə" + +#: mat-gui:362 +msgid "Include" +msgstr "Daxil et" + +#: mat-gui:378 +#, python-format +msgid "MAT is not able to clean the following files, found in the %s archive" +msgstr "%s arxivində tapılmış bu faylları MAT təmizləyə bilmir" + +#: mat-gui:394 +#, python-format +msgid "Checking %s" +msgstr "%s-in yoxlanması" + +#: mat-gui:409 +#, python-format +msgid "Cleaning %s" +msgstr "%s-in təmizlənməsi" + +#: data/mat.ui:63 +msgid "_File" +msgstr "_Fayl" + +#: data/mat.ui:99 +msgid "_Edit" +msgstr "_Dəyişiklik Et" + +#: data/mat.ui:118 data/mat.ui:253 +msgid "Clear" +msgstr "Təmizlə" + +#: data/mat.ui:134 +msgid "_Process" +msgstr "_Proses" + +#: data/mat.ui:168 +msgid "_Help" +msgstr "_Kömək" + +#: data/mat.ui:214 +msgid "Add" +msgstr "Əlavə et" + +#: data/mat.ui:240 +msgid "Check" +msgstr "Yoxla" + +#: data/mat.ui:309 +msgid "State" +msgstr "Vəziyyət" + +#: data/mat.ui:347 data/mat.ui:499 +msgid "Metadata" +msgstr "Metadata" + +#: data/mat.ui:376 +msgid "Name" +msgstr "Name" + +#: data/mat.ui:390 +msgid "Content" +msgstr "Mətn" + +#: data/mat.ui:452 +msgid "Supported formats" +msgstr "Dəstəklənən formatlar" + +#: data/mat.ui:486 +msgid "Support" +msgstr "Dəstək" + +#: data/mat.ui:512 +msgid "Method" +msgstr "Üsul" + +#: data/mat.ui:525 +msgid "Remaining" +msgstr "Yerdə qalanlar" + +#: data/mat.ui:560 +msgid "Fileformat" +msgstr "Fayl formatı"

1 0

[translation/mat-gui] Update translations for mat-gui
by translation＠torproject.org 30 Dec '14

30 Dec '14

commit 221fd06246e1c775219112672705ed7210084977 Author: Translation commit bot <translation(a)torproject.org> Date: Tue Dec 30 14:45:34 2014 +0000 Update translations for mat-gui --- az.po | 44 ++++++++++++++++++++++---------------------- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git a/az.po b/az.po index 216c077..28a81e9 100644 --- a/az.po +++ b/az.po @@ -10,7 +10,7 @@ msgstr "" "Project-Id-Version: The Tor Project\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2014-01-19 14:48+0000\n" -"PO-Revision-Date: 2014-12-30 14:15+0000\n" +"PO-Revision-Date: 2014-12-30 14:31+0000\n" "Last-Translator: E <ehuseynzade(a)gmail.com>\n" "Language-Team: Azerbaijani (http://www.transifex.com/projects/p/torproject/language/az/)\n" "MIME-Version: 1.0\n" @@ -106,58 +106,58 @@ msgstr "Fayl adı" #: mat-gui:336 msgid "Reason" -msgstr "" +msgstr "Səbəb" #: mat-gui:348 msgid "Non-supported files in archive" -msgstr "" +msgstr "Arxivdəki dəstəklənməyən fayllar" #: mat-gui:349 data/mat.ui:227 msgid "Scour" -msgstr "" +msgstr "Təmizləmə" #: mat-gui:362 msgid "Include" -msgstr "" +msgstr "Daxil et" #: mat-gui:378 #, python-format msgid "MAT is not able to clean the following files, found in the %s archive" -msgstr "" +msgstr "%s arxivində tapılmış bu faylları MAT təmizləyə bilmir" #: mat-gui:394 #, python-format msgid "Checking %s" -msgstr "" +msgstr "%s-in yoxlanması" #: mat-gui:409 #, python-format msgid "Cleaning %s" -msgstr "" +msgstr "%s-in təmizlənməsi" #: data/mat.ui:63 msgid "_File" -msgstr "" +msgstr "_Fayl" #: data/mat.ui:99 msgid "_Edit" -msgstr "" +msgstr "_Dəyişiklik Et" #: data/mat.ui:118 data/mat.ui:253 msgid "Clear" -msgstr "" +msgstr "Təmizlə" #: data/mat.ui:134 msgid "_Process" -msgstr "" +msgstr "_Proses" #: data/mat.ui:168 msgid "_Help" -msgstr "" +msgstr "_Kömək" #: data/mat.ui:214 msgid "Add" -msgstr "" +msgstr "Əlavə et" #: data/mat.ui:240 msgid "Check" @@ -165,11 +165,11 @@ msgstr "Yoxla" #: data/mat.ui:309 msgid "State" -msgstr "" +msgstr "Vəziyyət" #: data/mat.ui:347 data/mat.ui:499 msgid "Metadata" -msgstr "" +msgstr "Metadata" #: data/mat.ui:376 msgid "Name" @@ -177,24 +177,24 @@ msgstr "Name" #: data/mat.ui:390 msgid "Content" -msgstr "" +msgstr "Mətn" #: data/mat.ui:452 msgid "Supported formats" -msgstr "" +msgstr "Dəstəklənən formatlar" #: data/mat.ui:486 msgid "Support" -msgstr "" +msgstr "Dəstək" #: data/mat.ui:512 msgid "Method" -msgstr "" +msgstr "Üsul" #: data/mat.ui:525 msgid "Remaining" -msgstr "" +msgstr "Yerdə qalanlar" #: data/mat.ui:560 msgid "Fileformat" -msgstr "" +msgstr "Fayl formatı"

1 0

← Newer
1
2
3
4
5
6
7
8
...
80
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits December 2014