- tor-dev - lists.torproject.org

Orbot 16.0.3-BETA-2 (tor-0.3.4.8) release for testing
by Nathan Freitas 12 Oct '18

12 Oct '18

Highlights - Tor 0.3.4.8 / OpenSSL 1.0.2p with dirauth module disabled (not used for client devices) - Updated Obfs4/Meek pluggable transport support and built-in bridges - Simplified (less memory, network & battery intensive) notification with "New Identity" button APKs up here: https://github.com/n8fr8/orbot/releases/tag/16.0.3-BETA-2 https://guardianproject.info/releases/Orbot-16.0.3-BETA-2-tor-0.3.4.8-fullp… (.asc) **** @n8fr8 n8fr8 released this just now Assets 6 Orbot-16.0.3-BETA-2-tor-0.3.4.8-fullperm-armeabi-release.apk 8.77 MB Orbot-16.0.3-BETA-2-tor-0.3.4.8-fullperm-armeabi-release.apk.asc 862 Bytes Orbot-16.0.3-BETA-2-tor-0.3.4.8-fullperm-universal-release.apk 17.8 MB Orbot-16.0.3-BETA-2-tor-0.3.4.8-fullperm-universal-release.apk.asc 862 Bytes Source code (zip) Source code (tar.gz) f06939b (HEAD -> master, tag: 16.0.3-BETA-2-tor-0.3.4.8, public/master, origin/master, origin/HEAD, dev/master) update build 16030020 9d3bd82 udpate default bridges c207a1e update new simpler notification with "new identity" button bcae003 add permission to service manifest a7130ab update to latest tor android 0.3.4.8 a5d1978 update default bridges ffda769 update NDK build script 3349454 update to latest Pluto obfs4proxy builds 048ed9f Merge branch 'master' of github.com:n8fr8/orbot 84e0433 (tag: 16.0.3-BETA-1-tor-0.3.4.8) update version to 16.0.3-BETA-1-tor-0.3.4.8 and build to 16030010 66cc8ad improve service checking for running Tor instance 6bc161b update to Tor 0.3.4.8 0ff8d7c Merge pull request #173 from haghighi-ahmad/patch-1 772e0db Improve Persian translation and fix grammar. 129b55a Merge branch 'master' of github.com:n8fr8/orbot 1bef963 Merge branch 'Unpublished-deprecated_torrc' b2bf3d9 Merge branch 'deprecated_torrc' of https://github.com/Unpublished/orbot into Unpublished-deprecated_torrc 06c343c update launcher web graphic 3433112 update launcher graphics bd61739 update version and constrains library 9a866aa update gradle tooling 31238af update tor to 0.3.4.7 RC

1 0

deb.tpo 0.3.5 repos intentionally empty?
by nusenu 08 Oct '18

08 Oct '18

Hi, the tor 0.3.5.x repos (example [1]) exist since some time but are empty since then, is that intentional? kind regards, nusenu [1] https://deb.torproject.org/torproject.org/dists/tor-experimental-0.3.5.x-st… -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu

2 2

Network team meeting postponed to Tuesday
by Nick Mathewson 07 Oct '18

07 Oct '18

Hi! A lot of people are off on Monday, so we'll try to have our weekly meeting on Tuesday Oct 9, at the regular time. best wishes, -- Nick

1 0

txtorcon 18.3.0
by meejah 05 Oct '18

05 Oct '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hot on the heels of 18.2.0 comes 18.3.0 because I forgot to add the "single_hop=" feature to endpoint-strings: * add `singleHop={true,false}` for endpoint-strings as well You can download the release from PyPI or GitHub (or of course "pip install txtorcon"): https://pypi.python.org/pypi/txtorcon/18.3.0 https://github.com/meejah/txtorcon/releases/tag/v18.3.0 Releases are also available from the hidden service: http://timaq4ygg2iegci7.onion/txtorcon-18.3.0.tar.gz http://timaq4ygg2iegci7.onion/txtorcon-18.3.0.tar.gz.asc Or via a "version 3" service: http://fjblvrw2jrxnhtg67qpbzi45r7ofojaoo3orzykesly2j3c2m3htapid.onion/txtor… http://fjblvrw2jrxnhtg67qpbzi45r7ofojaoo3orzykesly2j3c2m3htapid.onion/txtor… You can verify the sha256sum of both by running the following 4 lines in a shell wherever you have the files downloaded: cat <<EOF | sha256sum --check 5601956b3a2452526cd1ea31662696a51ddbf8ed6452633ee464fc1ff275f8b0 dist/txtorcon-18.3.0.tar.gz 8edac3b6d9c633b9182b4e5a2ed3ac86953ed44b9ea230aac3e0708c30b73861 dist/txtorcon-18.3.0-py2.py3-none-any.whl EOF thanks, meejah -----BEGIN PGP SIGNATURE----- iQFFBAEBCAAvFiEEnVor1WiOy4id680/wmAoAxKAaacFAlu37ycRHG1lZWphaEBt ZWVqYWguY2EACgkQwmAoAxKAaafaFAf/e4pVR7bL+gDMq2sJVaFVFzsQqPTV2RLi 9e5A7RRfCPfDSPMyJg71I5qnXXY7aXMP5kBOmK1WF7hN06NRrYGuVifWzijogosP l/2KIGp1I6nK77JTNdjPqnSfQ9N+/ZXaXK3ILzlmSiyI3PMaLgPjB0x2JM6NhcfQ pPPKuL9K0bw94slGSTJa29py4yBV4VhAG0qwHEigw3Zwie2iAejk1GwSW9UEhJnp GBDECiaBdgDZZozn43Q9WXoVIcTnsjTBIN9Km3gNgIcn+ZbwH461HKDXvW7yDfsV oZ7thGr5xD9ENErOzWgU52kMOOuo/pM50vAlzJC518iV39deCD1GQA== =6d14 -----END PGP SIGNATURE-----

1 0

txtorcon 18.2.0
by meejah 05 Oct '18

05 Oct '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I'm glad to announce txtorcon 18.2.0. This adds or fixes the following: * add `privateKeyFile=` option to endpoint parser (ticket 313) * use `privateKey=` option properly in endpoint parser * support `NonAnonymous` mode for `ADD_ONION` via `single_hop=` kwarg You can download the release from PyPI or GitHub (or of course "pip install txtorcon"): https://pypi.python.org/pypi/txtorcon/18.2.0 https://github.com/meejah/txtorcon/releases/tag/v18.2.0 Releases are also available from the hidden service: http://timaq4ygg2iegci7.onion/txtorcon-18.2.0.tar.gz http://timaq4ygg2iegci7.onion/txtorcon-18.2.0.tar.gz.asc Or via a "version 3" service: http://fjblvrw2jrxnhtg67qpbzi45r7ofojaoo3orzykesly2j3c2m3htapid.onion/txtor… http://fjblvrw2jrxnhtg67qpbzi45r7ofojaoo3orzykesly2j3c2m3htapid.onion/txtor… You can verify the sha256sum of both by running the following 4 lines in a shell wherever you have the files downloaded: cat <<EOF | sha256sum --check b1714dfa633cb4097c9ea649c8c49657d9d22a990cc465bb904620428c5e684e dist/txtorcon-18.2.0.tar.gz 9d05f2b1144dfbc63844e78fbc51a195e3b39a79f280db50a81b346476c47e7b dist/txtorcon-18.2.0-py2.py3-none-any.whl EOF thanks, meejah -----BEGIN PGP SIGNATURE----- iQFFBAEBCAAvFiEEnVor1WiOy4id680/wmAoAxKAaacFAlu2qS0RHG1lZWphaEBt ZWVqYWguY2EACgkQwmAoAxKAaafvxAgAxsqlJ7LcnX2SxU89NHXJZ/og9ZkcKF89 RCAdYm/G1R4cJpqX9wjd0Kt38NJJyt/SuT95wGtYInLjrrTs3lzg7ToLoRxIodaF rXdlnUKaNJBStpIW62oJ1WRq8AFsjtjnxFv9iuIyUCA7BMh/nkKwCMoEOqtQ/KbO V43DjZpTr9cQmn62c1b6H+x+TVXhyZxiTK0d7WTHrrKbMOIpSKIJTezZvOfDV7MC dQdmLlhE1qxW8X5UjlNeWApuGWtY6U9aSVJcglN6Ecp8bZcvvS9LSWxn+KHkbzFX uLOgTyfp9/mQsAeVosp9HQ7iB+6BD27blJlMIBFPNLoBaFNjX91H7A== =v2ac -----END PGP SIGNATURE-----

1 0

Information on the handling of relays churn
by Adrien Luxey 28 Sep '18

28 Sep '18

Dear Tor developers, As a PhD student in distributed systems, I am studying onion routing. We would like to investigate an onion routing system that would run on users devices, i.e. a lot of nodes with crappy bandwidth and intermittent connection. To compare against Tor, I have been looking for information about how you currently handle the disconnection of relays, but I found no "digest" on the Web. Your code seems to point to the direction of core/or/circuit*, that I need to investigate further. I still would love some first-hand high-level description from you guys. I have the following questions: * When an OR disconnects while supporting active circuits, how is the failure detected? * How are the paths subsequently rebuilt? * To which extent would you say that Tor is resilient to churn? What would be the effects of a massive churn of relays? Where would be the bottleneck? If you have any questions on my work, I will be pleased to answer (though a little ashamed, because I know our system will never hold your security properties so tight)! With much respect for your work and philosophy, Adrien Luxey

4 4

txtorcon 18.1.0
by meejah 27 Sep '18

27 Sep '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I'm very pleased to announce txtorcon 18.1.0. This adds or fixes the following: * better error-reporting (include REASON and REMOTE_REASON if available) when circuit-builds fail (thanks David Stainton) * more-robust detection of "do we have Python3" (thanks Balint Reczey) * fix parsing of Unix-sockets for SOCKS * better handling of concurrent Web agent requests before SOCKS ports are known * allow fowarding to ip:port pairs for Onion services when using the "list of 2-tuples" method of specifying the remote vs local connections. You can download the release from PyPI or GitHub (or of course "pip install txtorcon"): https://pypi.python.org/pypi/txtorcon/18.1.0 https://github.com/meejah/txtorcon/releases/tag/v18.1.0 Releases are also available from the hidden service: http://timaq4ygg2iegci7.onion/txtorcon-18.1.0.tar.gz http://timaq4ygg2iegci7.onion/txtorcon-18.1.0.tar.gz.asc Or via a "version 3" service: http://fjblvrw2jrxnhtg67qpbzi45r7ofojaoo3orzykesly2j3c2m3htapid.onion/txtor… http://fjblvrw2jrxnhtg67qpbzi45r7ofojaoo3orzykesly2j3c2m3htapid.onion/txtor… You can verify the sha256sum of both by running the following 4 lines in a shell wherever you have the files downloaded: cat <<EOF | sha256sum --check b61cf175a5f1d4092609caf05d178fcdcabf513928eec98d38125c501afea43c dist/txtorcon-18.1.0.tar.gz 98aba4a96c355c55ee5d8290b67a09380b02e1044fb2e76737f47f5a33659dce dist/txtorcon-18.1.0-py2.py3-none-any.whl EOF thanks, meejah -----BEGIN PGP SIGNATURE----- iQFFBAEBCAAvFiEEnVor1WiOy4id680/wmAoAxKAaacFAlusMDQRHG1lZWphaEBt ZWVqYWguY2EACgkQwmAoAxKAaadz3wgAk+UbYuw0lIwEqQZbhQ6oTk0cTu5GrB5q WkSbqPkj5Ph+y1iYMQoEgAZdD97zjpfGR+/JcyXbPyh4ZDcqkL8Hhay9yF2/PAkd agu1LBuBjVXOFvcw3D8Xi91miFwjmMKznAuR1Jv9gp66emw3qbZRZE9g1S9o1lCX 3Cx6o3kLiq8h7UmOiqFfCFGjNBFsaiDqf35P7FH7Btg4FYIGtI5/uQ3qgDtyqlhD YKA91KxZQoZFGiAhp5h84WXrvtuQ5tDjRNiIfh76xRFiFRnWe9ofELidKqEgnyzF shBqdGpaIT0g0NTQRhCnzBM7m3u0RHxkRblJWBLa6t4KYNFTMJ8Pag== =z+Lo -----END PGP SIGNATURE-----

1 0

[release] Tor Metrics Library 2.5.0 and Tor Metrics Website 1.2.0
by Karsten Loesing 26 Sep '18

26 Sep '18

Hi, we just released new versions of the Tor Metrics Library, metrics-lib 2.5.0, and Tor Metrics Website, metrics-web 1.2.0. The primary reason for these new releases is that libraries contained in the tarball match the ones needed to build current master. Downloads are available at: https://dist.torproject.org/metrics-lib/2.5.0/ https://dist.torproject.org/metrics-web/1.2.0/ Please direct comments and questions to the metrics-team mailing list: https://lists.torproject.org/cgi-bin/mailman/listinfo/metrics-team All the best, Karsten -- on behalf of the Metrics Team.

1 0

I
by john loughlin 24 Sep '18

24 Sep '18

Sent from my iPhone b

1 0

Memory usage on 0.3.4.8
by r1610091651 24 Sep '18

24 Sep '18

Hi devs After upgrade from 3.3.7 -> 3.4.8, I've noticed that memory usage is erratic. Please consult the image below, showing memory available in green and memory used in blue on a tor dedicate system. [image: image.png] The upgrade to 3.4.8 took place on Saturday in week 37. The connection count / load was relativity stable: [image: image.png] (green inbound, blue outbound) I was wondering if there were any changes from 3.3.7 to 3.4.8 which might impact memory behaviour on a middle-relay. I'm also wander what is the "source" of this usage? Potentially relevant config entries (remainder is port/ip, accounting & exit(no)): MaxConsensusAgeForDiffs 4 hours DirCache 0 MaxMemInQueues 64 MB (but "defaulting" to 256mb now) Thanks in advance Seb

2 1