October 2015 - tor-commits - lists.torproject.org

[translation/https_everywhere] Update translations for https_everywhere
by translation＠torproject.org 24 Oct '15

24 Oct '15

commit d2adc31182766ccc2dd951eb314e74c06488e076 Author: Translation commit bot <translation(a)torproject.org> Date: Sat Oct 24 14:15:15 2015 +0000 Update translations for https_everywhere --- ja/ssl-observatory.dtd | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ja/ssl-observatory.dtd b/ja/ssl-observatory.dtd index 466c02a..87156a8 100644 --- a/ja/ssl-observatory.dtd +++ b/ja/ssl-observatory.dtd @@ -18,7 +18,7 @@ to turn it on?">-->  <!ENTITY ssl-observatory.prefs.adv_priv_opts1 -"非常に監視が厳しい企業ネットワークを使用する場合は、これを有効にした方が安全です:"> +"非常に監視が厳しい企業ネットワークを使用していなければ、これを有効にした方が安全です:"> <!ENTITY ssl-observatory.prefs.adv_priv_opts2 "次の秘密イントラネットのサーバー名で企業ネットワークを使用しなければ、安全です:">

1 0

[translation/tor-messenger-privproperties_completed] Update translations for tor-messenger-privproperties_completed
by translation＠torproject.org 24 Oct '15

24 Oct '15

commit 9954f4f92441a5970604c0f815128ca7721d2bd7 Author: Translation commit bot <translation(a)torproject.org> Date: Sat Oct 24 10:16:33 2015 +0000 Update translations for tor-messenger-privproperties_completed --- nl_BE/priv.properties | 1 + 1 file changed, 1 insertion(+) diff --git a/nl_BE/priv.properties b/nl_BE/priv.properties new file mode 100644 index 0000000..a6cf57f --- /dev/null +++ b/nl_BE/priv.properties @@ -0,0 +1 @@ +priv.account=Genereert een private sleutel voor %S (%S) ..

1 0

[translation/tor-messenger-otrproperties_completed] Update translations for tor-messenger-otrproperties_completed
by translation＠torproject.org 23 Oct '15

23 Oct '15

commit 879ea953a5ef55c75e8e94cb0d569e2d1379fe27 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Oct 23 19:46:34 2015 +0000 Update translations for tor-messenger-otrproperties_completed --- tr/otr.properties | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tr/otr.properties b/tr/otr.properties index 361d821..9f3346f 100644 --- a/tr/otr.properties +++ b/tr/otr.properties @@ -11,7 +11,7 @@ msgevent.rcvdmsg_malformed=%S kullanıcısından hatalı biçimlendirilmiş bir msgevent.log_heartbeat_rcvd=%S kullanıcısından kalp atışı alındı. msgevent.log_heartbeat_sent=%S kullanıcısına kalp atışı gönderildi. msgevent.rcvdmsg_general_err=Bir kayıt dışı görüşme hatası oluştu. -msgevent.rcvdmsg_unecrypted=%S kullanıcısından şifrelenmemiş bir ileti alındı. +msgevent.rcvdmsg_unecrypted=%S tarafından alınan şu ileti şifrelenmemiş: %S msgevent.rcvdmsg_unrecognized=%S kullanıcısından anlaşılamayan bir kayıt dışı iletisi alındı. msgevent.rcvdmsg_for_other_instance=%S kullanıcısı farklı bir oturuma yönelik bir ileti gönderdi. Birden çok kez oturum açtıysanız, ileti başka bir oturuma gönderilmiş olabilir. context.gone_secure_private=%S kullanıcısı ile özel görüşme başladı.

1 0

[translation/tor-messenger-otrproperties] Update translations for tor-messenger-otrproperties
by translation＠torproject.org 23 Oct '15

23 Oct '15

commit ce16228719d8f049b99d05caa99be6ba0b204788 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Oct 23 19:46:30 2015 +0000 Update translations for tor-messenger-otrproperties --- tr/otr.properties | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tr/otr.properties b/tr/otr.properties index 34ca421..9f3346f 100644 --- a/tr/otr.properties +++ b/tr/otr.properties @@ -11,7 +11,7 @@ msgevent.rcvdmsg_malformed=%S kullanıcısından hatalı biçimlendirilmiş bir msgevent.log_heartbeat_rcvd=%S kullanıcısından kalp atışı alındı. msgevent.log_heartbeat_sent=%S kullanıcısına kalp atışı gönderildi. msgevent.rcvdmsg_general_err=Bir kayıt dışı görüşme hatası oluştu. -msgevent.rcvdmsg_unecrypted=The following message received from %S was not encrypted: %S +msgevent.rcvdmsg_unecrypted=%S tarafından alınan şu ileti şifrelenmemiş: %S msgevent.rcvdmsg_unrecognized=%S kullanıcısından anlaşılamayan bir kayıt dışı iletisi alındı. msgevent.rcvdmsg_for_other_instance=%S kullanıcısı farklı bir oturuma yönelik bir ileti gönderdi. Birden çok kez oturum açtıysanız, ileti başka bir oturuma gönderilmiş olabilir. context.gone_secure_private=%S kullanıcısı ile özel görüşme başladı.

1 0

[translation/tor-messenger-ircproperties] Update translations for tor-messenger-ircproperties
by translation＠torproject.org 23 Oct '15

23 Oct '15

commit 3485a2a0974d57d9c4ca72f751aa9295e8d468e5 Author: Translation commit bot <translation(a)torproject.org> Date: Fri Oct 23 19:46:25 2015 +0000 Update translations for tor-messenger-ircproperties --- el/irc.properties | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/el/irc.properties b/el/irc.properties index 14b27c7..b96eb23 100644 --- a/el/irc.properties +++ b/el/irc.properties @@ -6,7 +6,7 @@ # This is displayed inside the accountUsernameInfoWithDescription # string defined in imAccounts.properties when the user is # configuring an IRC account. -irc.usernameHint=ψευδόνυμο +irc.usernameHint=ψευδώνυμο # LOCALIZATION NOTE (connection.error.*): # These will show in the account manager if the account is

1 0

[tor-messenger-build/master] README: mention mercurial and git
by boklm＠torproject.org 23 Oct '15

23 Oct '15

commit 87b47d1d805194b1042b160880f69b12b8237803 Author: Nicolas Vigier <boklm(a)torproject.org> Date: Fri Oct 23 21:39:11 2015 +0200 README: mention mercurial and git --- README | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/README b/README index acea749..cc09732 100644 --- a/README +++ b/README @@ -13,6 +13,9 @@ Your user account should have access to the docker command without using sudo, so it should be in the docker group. The docker daemon should also be running. +The sources are downloaded using git and mercurial which need to be +installed. + You also need a few perl modules installed: - YAML::XS - File::Basename @@ -50,11 +53,11 @@ If you want to build only one architecture, you can run something like The resulting builds are stored in the out/tor-messenger directory. -Updating git sources --------------------- +Updating git and hg sources +--------------------------- -You can run "make fetch" to fetch the latest sources from git for all -components included in Tor Messenger. +You can run "make fetch" to fetch the latest sources from git and +mercurial for all components included in Tor Messenger. Cleaning obsolete files and containers images

1 0

[tor-messenger-build/master] rbm: Fix an error when a project's output dir does not exist
by boklm＠torproject.org 23 Oct '15

23 Oct '15

commit 05864d5a11075c094f61b8ef5263db6db7add439 Author: Nicolas Vigier <boklm(a)torproject.org> Date: Fri Oct 23 21:26:52 2015 +0200 rbm: Fix an error when a project's output dir does not exist --- rbm | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rbm b/rbm index 2bb0827..4bb0e17 160000 --- a/rbm +++ b/rbm @@ -1 +1 @@ -Subproject commit 2bb082714f48da9609b700a73875e6a3fadd0b69 +Subproject commit 4bb0e17d467694cfd463a1991e8bf7fc9e6704e6

1 0

[tor-messenger-build/master] Use the bundleclone hg extension to clone mozilla repos
by boklm＠torproject.org 23 Oct '15

23 Oct '15

commit 513e0f017c55b97bbf0ff717ddaa7f8d50199855 Author: Nicolas Vigier <boklm(a)torproject.org> Date: Fri Oct 23 20:36:10 2015 +0200 Use the bundleclone hg extension to clone mozilla repos This extension makes initial cloning of the mozilla hg repository faster using pre-generated bundles. https://mozilla-version-control-tools.readthedocs.org/en/latest/hgmo/bundle… --- .gitmodules | 3 +++ rbm | 2 +- rbm.conf | 1 + tools/version-control-tools | 1 + 4 files changed, 6 insertions(+), 1 deletion(-) diff --git a/.gitmodules b/.gitmodules index f85be07..4e8e7eb 100644 --- a/.gitmodules +++ b/.gitmodules @@ -1,3 +1,6 @@ [submodule "rbm"] path = rbm url = https://github.com/boklm/rbm +[submodule "tools/version-control-tools"] + path = tools/version-control-tools + url = https://github.com/mozilla/version-control-tools diff --git a/rbm b/rbm index eb70180..2bb0827 160000 --- a/rbm +++ b/rbm @@ -1 +1 @@ -Subproject commit eb70180f710a749d294a16c73223220699e806aa +Subproject commit 2bb082714f48da9609b700a73875e6a3fadd0b69 diff --git a/rbm.conf b/rbm.conf index 4c93634..48a3ddf 100644 --- a/rbm.conf +++ b/rbm.conf @@ -81,3 +81,4 @@ targets: docker_image: '[% pc("docker-image", "docker_save_image") %]' +hg_opt: '--config extensions.bundleclone=[% shell_quote(c("basedir") _ "/tools/version-control-tools/hgext/bundleclone/__init__.py") %]' diff --git a/tools/version-control-tools b/tools/version-control-tools new file mode 160000 index 0000000..fd2903b --- /dev/null +++ b/tools/version-control-tools @@ -0,0 +1 @@ +Subproject commit fd2903b7e3692a3915213390863768b2ae904e2f

1 0

[torspec/master] Document our current guard selection algorithm in path-spec.txt.
by nickm＠torproject.org 23 Oct '15

23 Oct '15

commit 38d9df22ace881f0907c6cdd3ccd38dc95538aad Author: Isis Lovecruft <isis(a)torproject.org> Date: Fri Oct 23 16:29:17 2015 +0000 Document our current guard selection algorithm in path-spec.txt. * ADDS new section, "§5.1. Guard selection algorithm", to path-spec.txt. * FIXES #17261: https://bugs.torproject.org/17261 --- path-spec.txt | 99 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 99 insertions(+) diff --git a/path-spec.txt b/path-spec.txt index 896195a..47dae3b 100644 --- a/path-spec.txt +++ b/path-spec.txt @@ -602,6 +602,105 @@ of their choices. Tor does not add a guard persistently to the list until the first time we have connected to it successfully. +5.1. Guard selection algorithm + + If configured to use entry guards, and the circuit's purpose is not marked + for testing, then a random entry guard from the persisted state (as + mentioned earlier in §5) will be chosen (provided there is already some + persisted state storing previously chosen guard nodes). + + Otherwise, if any the above conditions are not satisfied, then a new entry + guard node will be chosen for that circuit. The algorithm is as follows: + + - EXCLUDED_NODES is a list of nodes which, for some reason, are not + acceptable for use as an entry guard. + + 1. If an exit node has been chosen for the circuit: + + 1.a. Then that exit is added to EXCLUDED_NODES (and thus will not be + used as the entry guard). + + 2. If running behind a fascist firewall (e.g. outgoing connections are + only permitted to ports 80 and/or 443): + + 2.a. For all known routers in the network (as given in the + networkstatus document), a router is added to the list of + EXCLUDED_NODES iff it does not advertise the ability to be reached + via the ports allowed through the fascist firewall. + + 3. Add any entry guards currently in volatile storage, as well as all + nodes within their families, to EXCLUDED_NODES. + + 4. Determine which of the following flags should apply to the selection of + an entry guard: + + * CRN_NEED_UPTIME: the router can only be chosen as an entry guard + iff has been available for at least some minimum uptime. + * CRN_NEED_CAPACITY: potentially suitable routers are weighted by + their advertised bandwidth capacity. + * CRN_ALLOW_INVALID: also consider using routers which have been + marked as invalid. + * CRN_NEED_GUARD: only consider routers which have the Guard flag. + * CRN_NEED_DESC: only consider routers for which we have enough + information to be used to build a circuit. + + Additionally, if configured to allow nodes marked as invalid AND to + specifically allow entry guards which have been marked as invalid, then + the CRN_ALLOW_INVALID flag will be set. Lastly, the CRN_NEED_GUARD and + CRN_NEED_DESC flags are always applied, regardless of configuration. + + 5. If configured to exclude routers which allow single-hop circuits, then + the list of known routers is traversed, and all routers which permit + single-hop circuits are added to EXCLUDED_NODES. + + 6. If we are an OR, add ourselves (and our family) to EXCLUDED_NODES. + + 7. The list of potential routers is weighted according to the bandwidth + weights from the consensus (cf. §5.1.1), and then a random selection is + chosen with respect to those weights. + + 7.a. If we've made a choice now, the algorithm finishes. + 7.b. Otherwise, continue to step #8. + + 8. We couldn't find a suitable guard, so now we try much harder by + discarding the CRN_NEED_UPTIME, CRN_NEED_CAPACITY, and CRN_NEED_GUARD + selection flags. This effectively means we'll use nearly any router, + except for ones already in EXCLUDED_LIST. + + [XXX Does this mean we even include BadExits and other misbehaving + nodes? This sounds bad. —isis] + +5.1.1. How consensus bandwidth weights factor into entry guard selection + + When weighting a list of routers for choosing an entry guard, the following + consensus parameters (from the "bandwidth-weights" line) apply: + + Wgg - Weight for Guard-flagged nodes in the guard position + Wgm - Weight for non-flagged nodes in the guard Position + Wgd - Weight for Guard+Exit-flagged nodes in the guard Position + Wgb - Weight for BEGIN_DIR-supporting Guard-flagged nodes + Wmb - Weight for BEGIN_DIR-supporting non-flagged nodes + Web - Weight for BEGIN_DIR-supporting Exit-flagged nodes + Wdb - Weight for BEGIN_DIR-supporting Guard+Exit-flagged nodes + + Please see "bandwidth-weights" in §3.4.1 of dir-spec.txt for more in depth + descriptions of these parameters. + + If a router has been marked as both an entry guard and an exit, then we + prefer to use it more, with our preference for doing so (roughly) linearly + increasing w.r.t. the router's non-guard bandwidth and bandwidth weight + (calculated without taking the guard flag into account). From proposal + #236: + | + | Let Wpf denote the weight from the 'bandwidth-weights' line a + | client would apply to N for position p if it had the guard + | flag, Wpn the weight if it did not have the guard flag, and B the + | measured bandwidth of N in the consensus. Then instead of choosing + | N for position p proportionally to Wpf*B or Wpn*B, clients should + | choose N proportionally to F*Wpf*B + (1-F)*Wpn*B. + + where F is the weight as calculated using the above parameters. + 6. Server descriptor purposes There are currently three "purposes" supported for server descriptors:

1 0

[metrics-lib/master] Include library version numbers.
by karsten＠torproject.org 23 Oct '15

23 Oct '15

commit 4bfe5417225a4aa1acf36d5e43610604b4479e5a Author: Karsten Loesing <karsten.loesing(a)gmx.net> Date: Fri Oct 23 19:00:08 2015 +0200 Include library version numbers. Suggested by iwakeh on #13166. --- CONTRIB.md | 4 ++-- build.xml | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/CONTRIB.md b/CONTRIB.md index b306dd5..30f8680 100644 --- a/CONTRIB.md +++ b/CONTRIB.md @@ -27,10 +27,10 @@ We tried to keep the number of dependencies as small as possible, and we tried t metrics-lib currently has the following dependencies to compile: - - Apache Commons Compression + - Apache Commons Compression 1.4.1 https://commons.apache.org/proper/commons-compress/download_compress.cgi - - JUnit + - JUnit 4.10 https://github.com/junit-team/junit/wiki/Download-and-Install diff --git a/build.xml b/build.xml index 433a21a..4aaf8f7 100644 --- a/build.xml +++ b/build.xml @@ -8,8 +8,8 @@ <path id="classpath"> <pathelement path="${classes}"/> <fileset dir="/usr/share/java"> - <include name="commons-compress.jar"/> - <include name="junit4.jar"/> + <include name="commons-compress-1.4.1.jar"/> + <include name="junit4-4.10.jar"/> </fileset> </path>

1 0