September 2018 - tor-project - lists.torproject.org

Are there countries where using Tor is illegal?
by Cristian Consonni 11 May '25

11 May '25

Hi, (Sorry if this question has already been asked in the past, feel free to point me to the relevant resources.) I know that the legal FAQs by the EFF state that: «we believe that running a Tor relay — including an exit relay that allows people to anonymously send and receive traffic — is legal under U.S. law.»[1] I also know there is a list of countries for which there is legislation that exclude communication service providers from liability. They are indicated in the Legal of the Tor Exit Guidelines page[2], they are USA, Germany, Netherlands, Austria, France, and Sweden. >From some articles in the press[3a][3b] it may be illegal - depending on how you interpret the wording[*] - to use Tor (and other technologies such as VPNs or proxies) in the UAE, with fines ranging in the millions of dirhams (hundreds of thousand of dollars). A couple of weeks ago it was discussed - on this list as well - that a law was introduced to the state parliament to ban Tor[4a][4b]. This follows a case of some months ago of a Russian Tor exit node operator being arrested for inciting mass riots and terrorism[4c][4d]. The idea of blocking VPNs or Tor seems to have already been considered in the past[4e]. This infographic about pluggable transports[5] suggests access to the Tor network is censored or limited in China, Uzbekistan, Iran, and Kazakhstan. Tor being censored orblocked may be different from it being illegal. What about other countries? Is there a place where I can find more about this topic? Cristian [1]: https://www.torproject.org/eff/tor-legal-faq.html.en [2]: https://trac.torproject.org/projects/tor/wiki/doc/TorExitGuidelines [3a]: http://www.emirates247.com/news/emirates/dh500-000-fine-if-you-use-fraud-ip… [3b]: http://news.softpedia.com/news/people-caught-using-vpns-tor-or-proxies-in-t… [*]: «Whoever uses a fraudulent computer network protocol address (IP address) by using a false address or a third-party address by any other means for the purpose of committing a crime or preventing its discovery» [4a]: https://lists.torproject.org/pipermail/tor-talk/2017-June/043293.html [4b]: https://trac.torproject.org/projects/tor/ticket/22055 [4c]: https://lists.torproject.org/pipermail/tor-talk/2017-April/043109.html [4d]: https://techcrunch.com/2017/04/24/dmitry-bogatov-tor-russia/ [4e]; https://torrentfreak.com/vpn-and-tor-ban-looming-on-the-horizon-for-russia-… [5]: https://www.torproject.org/images/PT/2016-07-how-to-use-PT.png

4 3

Key Signing Party! send your key DEADLINE Sept 29th
by emma peel 01 Oct '18

01 Oct '18

Hello people! So, I will be hosting a Key Signing party in Mexico during the Tor Meeting. Key signing parties should be called certificate verification parties but we are conditioned by the interface, so we call it key signing. Please send me your key on a signed email (unless is another kind of key...), even if it is already in db.torproject.org. before Sept. 29th. ------------------- DEADLINE Sept 29th. ------------------- You also need to be present on the party to get signatures... Lets verify and kill the MitM! ------------------------------------------------------------------ INSTRUCTIONS ------------------------------------------------------------------ Please don't participate of the party if you don't want public signatures... it creates overhead and its very likely that somebody will upload your key to the server with a new signature! Make sure you have a 4096 bit RSA key. If not, generate a new one: http://ekaia.org/blog/2009/05/10/creating-new-gpgkey/ Make sure you follow the OpenPGP Best Practices: https://riseup.net/en/security/message-security/openpgp/best-practices You can get your key on a file called mynickname.asc by doing: gpg --export --armor [your fingerprint] mynickname.asc You can also use this opportunity to add your OTR fingerprints, or other services you may want to certify for the people attending. For the OTR fingerprint, depending on your client: Pidgin: https://otr.cypherpunks.ca/help/fingerprint.php Adium: https://adium.im/help/pgs/AdvancedFeatures-OTREncryption.html BitlBee: otr info irssi: /otr info At the meeting: verify ====================== 0. don't sign anything! 1. i will send the final file the day before, through the list 2. you can come with your laptop, or with a printed version of the file. 3. if you print the file, write the output of this command on the paper: gpg --print-md sha256 fingerprint-verification-unverified.txt 4. read out the checksum and make sure everyone has the same file 5. create a copy of the file to make notes: % cp fingerprint-verification-unverified.txt fingerprint-verification-annotated.txt 6. everyone (silently): verify your fingerprint(s) and user ID(s) in the document are correct 7. everyone (publically): identify yourself and verify that the fingerprint(s) and user ID(s) are correct 8. everyone: fill in the checkboxes in fingerprint-verification-annotated.txt: Fingerprint OK, ID OK 9. when done, sign the document: gpg --detach-sign fingerprint-verification-annotated.txt 10. at home, sign the keys.

3 3

Network team meeting notes, 24 Sep 2018
by Nick Mathewson 25 Sep '18

25 Sep '18

Hello! (So you know, we won't be having an online meeting next week.) Our meeting logs are available from http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-09-24-16.59.html The contents of our pad are below. = Network team meeting pad! = Welcome to our meeting! Mondays at 1700 UTC on #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) Want to participate? Awesome! Here's what to do: 1. If you have updates, enter them below, under your name. 2. If you see anything you want to talk about in your updates, put them in boldface! 3. Show up to the IRC meeting and say hi! Note the meeting location: #tor-meeting on OFTC! (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) After each week's meetings, the contents of this pad will be sent to tor-project @ lists.torproject.org. After that is done, the pad can be used for the next week. == Previous notes == (Search the list archive for older notes.) 4 Sep: https://lists.torproject.org/pipermail/tor-project/2018-September/001965.ht… 10 Sep: https://lists.torproject.org/pipermail/tor-project/2018-September/001972.ht… 17 Sep: https://lists.torproject.org/pipermail/tor-project/2018-September/001982.ht… 24 Sep: == Stuff to do every week = * Let's check and update the roadmap. What's done, and what's coming up? url to roadmap: https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Check reviewer assignments at https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Also, let's check for things we need update on our spreadsheet! Are there important documents we should link to? Things we should archive? * Check rotations at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… * Community guides, it's time to hand off to the next guide! * Let's look at proposed tickets! [but see discussion] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… == Reminders == * Remember to "/me status: foo" at least once daily. * Remember that our current code reviews should be done by end-of-week. * Make sure you are in touch with everybody with whom you are doing work for the next releases ------------------------------- ---- 24 September 2018 ------------------------------- == Announcements == Tor 0.3.2 will not be supported past 9 October (2 weeks from now): https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… Here are the Mexico City meeting schedules: https://trac.torproject.org/projects/tor/wiki/org/meetings/2018MexicoCity/D… https://trac.torproject.org/projects/tor/wiki/org/meetings/2018MexicoCity/P… Tor employees, please do timesheets each week, or in the worst case by the end of the month. The new schema (all network team work goes in "Network Team") should make this much faster. == Discussion == * Let's defer non-essential tickets from the 0.3.5.x-final milestone * [dgoulet] asn and I haven't assign needs_review yet. Do we want it considering Tor meeting or not? If yes, only 035 or not? * On the meeting: Are we missing any sessions we need? Are there any sessions we don't need? [isa] what prep work we can do for roadmaping in Mexico? -> https://pad.riseup.net/p/tor-nt-roadmap-prep-keep == Updates == teor (offline): last week: - Travel preparation - Meeting schedules and preparation - Worked on #27288 and children - required protocol error - Review the 0.3.5.1-alpha changelog, make check-changes better (#27761) - make macOS Travis much faster by changing how we install dependencies (#27738) - Code reviews for PrivCount in Tor, protover, macOS i386 time, client auto IPv6 this week: - More travel preparation - Sit on planes and in airports - Take some time off before the meeting - Work out what needs to be done at the meeting, and what can wait until after - I am on the CI rotation, but I'll be offline for at least 3/5 days asn: [Flying to Mexico tomorrow. Will be packing and having dinner with family tonight. Very likely not at the meeting] Last week: - Helped isabela with onion funding proposal - Wrote SponsorV annual report - Review many v3 tickets: #27774, #27410, #27797, #27550. - Re-review #4700. - Review #27709. - Review CF's latest blog post. - Feedback for #27471. This week: - Packing and travelling to Mexico. Nick: Last week: * Revised whitepaper on sidechannels. * Hunted 0.3.5.1-alpha bugs * Released 0.3.5.1-alpha * Diagnosed and fixed #27795 (fd miscouting leading to Tor thinking it was out of FDs) * Made Tor compile happily with -flto * Released 0.3.5.2-alpha to fix #27795 * Patches to split a few modules that were large and/or not where they belonged. * Wrote proposal 297 to suggest a change to protover-based shutdown behavior * Review, merge, etc This week: * PETS reviews * More module splitting * Defer more tickets from 0.3.5 * More Mexico prep * Probably taking short days on Thu/Fri to make up for working over this coming weekend. * See you in Mexico on Saturday morning! dgoulet: Last week: - Worked on annoying HS bugs: #27410, #27550 and #27774 specifically. - Patch for #27549 again in the HS code. - 035 ticket review (See Timeline for this). - Started writing a unit test for #27471 theory so we can test the proposed solution. This week: - Planning to continue the 035 review/patch ticket work. - I'll also tackle some long standing HSv3 bugs which includes #27838 that re-appeared today. #27471 of course to finalize. - I'm on Ticket Triage this week. ahf Last week: Sponsor 8: - More patch work for #25502. - Started an experiment with trying to use Rust's mio for event loop in Tor. Misc: - Reviewed: #27686 - Added some documentation for #4700 and got it landed. - Went over CV's for the sysadmin job opening. - Helped some people trying to understand the #4700 proxy code and the whole CF onion thing. - Read the DeepCorr paper. This week: - Comment on sysadmin CV's/ranking. - Travel to Mexico(!!!) - Some preparation for the Mexico trip. catalyst: last week (2018-W38): - somewhat unwell, hopefully just travel vaccines - bug triage rotation - code reviews - travel prep - troubleshooting for #27484 after seeing it myself this week (2018-W39): - CI+Coverity rotation - more travel prep - Mexico City - people who do Rust, i could use some opinions on "how do we want to do dependency updates anyway?" for #27130 Mike (having IRC shell issues? hrmm..): Last week: - Mexico City travel mails - Vanguard updates - Fixed up #23512 This week: - Travel prep - Vanguards release? - WTF-PAD work Gaba: Last week: - Onboarding with Isa This week: - Reading and preping for mexico

1 0

Job opening - Software Developer for Anti-Censorship Team
by Erin Wyatt 25 Sep '18

25 Sep '18

Hi everyone! We have a new job opening for a software developer on the (new) Anti-Censorship Team! Please help us spread the word. You can forward the job description directly to a person whom you think would be great, you could share it on your social media, and/or you could forward it to a mailing list! Every share helps get us closer to finding the magical person who will fill this position. :) The job description is on our website: https://www.torproject.org/about/jobs-developer-anti-censorship.html.en, pasted below, and attached as a PDF. Thank you, everyone! Have a great week. :) Cheers, Erin Wyatt HR Manager ewyatt(a)torproject.org GPG Fingerprint: 35E7 2A9F 6655 45F9 2CB6 6624 BA0C 9400 F80F 91CE ————————————>8————————————>8————————————>8 Internet Freedom Nonprofit Seeks Software Developer for Anti-Censorship Team The Tor Project, Inc., a 501(c)(3) nonprofit organization advancing human rights and freedoms by creating and deploying free and open source anonymity and privacy technologies, is seeking an experienced Software Developer to take our anti-censorship work to the next level. Tor is for everyone, and we are actively working to build a team that represents people from all over the world — people from diverse ethnic, national, and cultural backgrounds; people from all walks of life. Racial minorities, non-gender-binary people, women, and people from any group that is generally underrepresented in tech are encouraged to apply. This developer will improve the user experience process of finding alternate routes to the Tor network when censorship events are blocking access in their host countries. Experience with Internet security and knowledge of obfuscation technologies would be a big help. Personal commitment to open source and using your advanced programming skills for the greater good is essential. This developer position will be an integral part of our brand new Anti-Censorship Team. Main responsibilities for this position are: • Devise metrics and load balancing mechanisms for our current and future bridge distribution system. • Analyze our current BridgeDB design to determine how it can better leverage other circumvention solutions, such as newer pluggable transports (PTs). • Review our current list of PTs and decide which we should continue to maintain. • Evaluate new Pluggable Transports against our criteria to determine if they should be supported. • Work with other members of the anti-censorship team lead to evaluate, pick and implement censorship-resistant discovery mechanisms for pluggable transport addresses. • Evaluate cryptographic solutions to rate limiting bridge distribution, and if any are feasible, implement them. Required qualifications: • extensive experience writing and evaluating code in Python and Go • experience in designing and documenting software engineering solutions to problems; • self-directed • comfortable and reliable with working remotely Preferred qualifications: • development experience in Rust • understanding of the Tor pluggable transport ecosystem and the censorship circumvention research space • familiarity with developing and scaling distributed systems • previous contributions to other open source projects Experience working with open source communities and/or a dedication to Internet freedom are added pluses. This is a full-time position that can be done remotely/internationally or in our office in Seattle, WA. To apply, send a cover letter that includes a statement about why you want to work at the Tor Project, your CV/resume (including three professional references), and a link to a code sample or some non-trivial software project you have significantly contributed to. The email should go to job-anticensor at torproject dot org with “Anti-Censorship Developer” in the subject line. No phone calls please! The Tor Project's workforce is smart and committed. The Tor Project currently has a paid and contract staff of around 47 developers and operational support staff, plus many thousands of volunteers who contribute to our work. The Tor Project is funded in part by government research and development grants, and in part by individual, foundation and corporate donations. Flexible salary, depending on experience. The Tor Project has a competitive benefits package, including a generous PTO policy; 14 paid holidays per year (including the week between Christmas and New Year's, when the office is closed); health, vision, dental, disability, and life insurance paid in full for employee; and flexible work schedule. The Tor Project, Inc., is an equal opportunity, affirmative action employer.

1 0

Notes from September 20 2018 Vegas team meeting
by Karsten Loesing 21 Sep '18

21 Sep '18

Notes for September 20 2018 meeting: Shari: 1) Pulling together little things for audit. 2) Pulling together bigger things for board meeting in Mexico. 3) Helping with some last minute things re: Mexico meeting. 4) Must finish Sida budget revision today. 5) Pushing along some stuff that has been stuck. Sue: 1) Audit moving along - still working to complete all selections with auditors 2) Onboarding two new employees - trying to delegate as much as I can while doing the audit 3) Working on Mexico City items to discuss at employee/contractor meetings - time sheets, expense reports, etc. Nick: 1) Alpha came out; expecting new alphas every so often 2) About to release whitepaper about UDP and sidechannel research that it needs. I'd like to pull Roger and Mike into a discussion. Alison: 1) woooooooooooooooooo getting all the things done before the meeting!!!!!!! 2) SOTO stuff ready? Please let me know ASAP if you're using slides. Mike: 1) Wrapped up my things for Tor release 2) karsten: I have a question about metrics' use of CIRC_BW events for you (offline/after) 3) Wrote on Mexico safety+security mail Arturo: 1) The OONI Probe mobile app illustrations are done and they look great! 2) Collecting feedback and iterating on OONI Explorer mockups 3) Improving based on feedback the OONI Probe mobile app Android prototype 4) Infrastructure housekeeping and data migration 5) A lot of progress with the OONI Probe desktop app and CLI: https://github.com/ooni/probe-cli/pull/16, https://github.com/ooni/probe-desktop/pull/17 6) Updated test lists: https://github.com/citizenlab/test-lists/pull/392, https://github.com/citizenlab/test-lists/pull/389, https://github.com/citizenlab/test-lists/pull/390, https://github.com/citizenlab/test-lists/pull/391 7) Established new partnership with Paraguay's TEDIC: https://twitter.com/OpenObservatory/status/1042760192197373952 Sarah: 1) Creating a calendar and list of deliverables for YE campaign. Will be looping others into the planning document later today. 2) Updating Tor's Guidestar profile which donors often reference before giving. The info there is also utilized by donation tools like AmazonSmile. 3) Gathering materials for Tor's state registrations for fundraising. 4) Arranging meetings in Mexico. Steph: 1) answered press inquiries about the cloudflare onions, drafted a statement 2) drafted a Tor stories blog post and survey, now in review 3) promoting Toronto library event and TB pilot program 4) prepped with isa for a podcast 5) getting tweets translated with help from emma & antonela Karsten: 1) Released ExoneraTor 4.0.0 that reduces the overall database from 243G to 63G and mean response time from 18.9 to 2.3 seconds. 2) Started a survey to get input on our Tor Metrics 2018/19 roadmap. If you have suggestions what we should take into account, please participate in this survey: https://survey.torproject.org/index.php/987123 ! It runs until next Wednesday. Georg: 1) Release fun++ (we were ready to release 8.0.1/8.5a2 but need to pick up additional Firefox patches) 2) Shari: I want to offer someone a contract for fixing one of our bugs (#27503) as we can't do it ourselves well and reached out to someone to give me an estimate about cost/time. It should be about 2-3 days of work. How can we proceed here? [how much will it cost? If it's not too much, we could just offer that person a contract - Shari]

1 0

Survey: Tor Metrics 2018/19 Roadmap
by Karsten Loesing 20 Sep '18

20 Sep '18

Hi, everyone! I just published a new survey to help us, the Tor Metrics Team, get more user input and as a result make better plans for the upcoming 6 months and beyond: https://survey.torproject.org/index.php/987123 This survey has 7 questions and shouldn't take longer than 5 to 10 minutes, depending on the detail of responses. It will be active for 1 week until September 25, 2018, at around 12:00 UTC. If you want your idea to be taken into account for the next Tor Metrics roadmap, this is your chance to share it with us! Thanks in advance! All the best, Karsten

2 3

Tor Browser team meeting notes, 17 Sep 2018
by Georg Koppen 20 Sep '18

20 Sep '18

Hi! On Monday we had our weekly Tor Browser meeting. For the IRC log see: http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-09-17-18.00.log… Notes from our pad are pasted below: Tor Browser Meeting Notes Monday September 17, 2018 Discussion: -state of the onion talks (GeKo: pad for collecting ideas https://pad.riseup.net/p/G6ToSghBgWhG) -sessions for the team meeting day (GeKo: Added a Tor Browser 8 retrospective; two sessions are place holders for stuff popping on on 9/27) -next meeting (GeKo: Will be in Mexico!) mcs and brade: Last week: - Did some testing and created a patch for #26146 (`general.useragent.override` does not spoof the platform part) - Followed up on various desktop onboarding issues: - #27483 (dialog closure is effectively treated as "read", causing screen advancement). - #27484 (unintuitive not-navigation buttons, starting with "Circuit Display" / "See My Path") - #27485 (user not taught *how* to open the security-slider dialog) - Filed #27623 (wrong default pref values in Tor Browser 8.0). - Reviewed #26381 (about:tor page does not load on first start on Windows). - Reviewed several smaller patches. - Commented on #27691 (reset bootstrap progress when enough things change). - Helped with triage of incoming tickets. This week: - We will be away from keyboard on Friday September 21. - Review Richard's revised patch for #26381 (about:tor page does not load on first start on Windows). - Create a patch for #27623 (wrong default pref values in Tor Browser 8.0). - Help with code reviews. - Work on other 8.0 follow up tickets. - Help with triage of new tickets. - Review our notes from #22074 (undocumented bugs since FF52esr) and file additional tickets if necessary. GeKo: Last week: - mainly worked on tbb-8.0.1-can tickets (e.g. #26624, #27264, #27507, #27543, #27546 #27663, #27469, #26556, and #27535) - triaging incoming bug reports for 8.0 - reviews - tjr/sukhe: where are we with respect to https://bugzilla.mozilla.org/show_bug.cgi?id=1470772 (aka #26476)? This week: - reviewing and merging remaining things for 8.0.1 and 8.5a2 - building 8.0.1 and 8.5a2 and signing both - triaging ff60-esr items - back to "paper" work: release doc update and design doc update for 8.0 - Mexico meetings preparation - i will be afk 9/24 and 9/25 igt0: Last week: - Worked on #25764(making the mobile version of the circuit display) - Finished the #26690(padlock for mobile) This Week: - Finish #25764 - Investigate more fingerprint attacks on mobile pospeselr: Last week: - fixed up patch for #26540 (pdf range requests) - updated patch for #26381 (windows sandboxing race condition) - started looking into #3600 (cookie redirects) This week: #3600 in earnest mozilla all-hands travel planning code reviews sysrqb: Last week: Worked on Restarting Gecko during First Run Began evaluating the Tor API This week: Give feedback on Tor's API Finish branch for restarting Gecko Work on patch for TBA only having Private Tabs Note: I'll be away for the beginning of the meeting due to an unexpected conflict (GeKo: That's fine :) ) (not a discussion topic) boklm: Last week: - was afk until Friday - made patch for #27552 (fix Tor Browser 8 on CentOS/RHEL 6) - reviewed the patch for #27546 (Vertical scrollbar is broken on Linux in Tor Browser 8 with Gtk3) - answered comment on binutils issue: https://sourceware.org/bugzilla/show_bug.cgi?id=23466 This week: - look at #27508 (issue with libstdc++ on some systems) - help with building/publishing the new releases - get the testsuite running on nightly builds traumschule: This week: - more testing, create trace for https://bugs.torproject.org/27110 (TBB segfaults on I/O error and silently fails to restart) arthuredelstein: - Last week: - Wrote or revised patches for - https://bugs.torproject.org/26555 (new circuit display shows bridge addresses) - https://bugs.torproject.org/27097 (add "tor news" newsletter signup link) - https://bugs.torproject.org/27427 (Fix no Script IPC for about:blank) - https://bugs.torproject.org/27478 (torbutton dark theme) - https://bugs.torproject.org/27506 (onboarding bubble for rtl locales) - Investigated: - https://bugs.torproject.org/27542 (saving websites locally loses pictures) - https://bugs.torproject.org/27175 (noscript plugin does not save per-site permissions) [what should we do here?] - Opened: - https://bugs.torproject.org/27752 (network settings dialog does not switch to meek smoothly) - https://bugs.torproject.org/27621 (idea: port tb-manual to lektor) - Met with loca lab to discuss Tor Browser locales - Met with Mozilla Tor uplift team - This week: - More tbb-8.0-issues/tbb-8.0.1-can - Finally uplift permissions/FPI patch (if time) - optimistic socks? sisbell: Last week: - Worked on #25164 - Reproducible Tor Browser for Android Builds (pausing for now, moving on to other trac issues). Currently program outputs specific items in dex file that are different between builds. - Source Code: https://github.com/sisbell/dexd - Crate: https://crates.io/crates/dexd This Week: - Integrate and test rust program output (from #27438) with RBM build for android-toolchain - Work on #26696, #26597, #27441 Georg

1 0

Damian's Status Report - August 2018
by Damian Johnson 19 Sep '18

19 Sep '18

Hi lovely onion enthusiasts! Here's my much belated status report for August. I'll probably skip September since this was so late. https://blog.atagar.com/august2018/ Hope folks have fun in Mexico!

1 0

(FWD) Save the Date for RightsCon Tunis (June 11-14, 2019)
by Roger Dingledine 18 Sep '18

18 Sep '18

The next RightsCon has been scheduled. It's right before the summer Mozilla-All-Hands in Canada, which will make the logistics tricky but possible for those who want to do both. --Roger ----- Forwarded message from "Nikki Gladstone, Access Now" <conference(a)accessnow.org> ----- Date: Tue, 18 Sep 2018 15:53:05 -0400 (EDT) From: "Nikki Gladstone, Access Now" <conference(a)accessnow.org> To: arma(a)mit.edu Subject: Save the Date for RightsCon Tunis (June 11-14, 2019) Hi Roger, It???s officially time to mark your calendars for RightsCon Tunis [https://www.e-activist.com/ea-action/enclick?ea.url.id=1510845&ea.campaigne…] We???re thrilled to share with you that the next RightsCon will be held from Tuesday, June 11 to Friday, June 14, 2019. Alongside our team in Tunis, we have found the perfect venue for hosting the growing RightsCon Community. RightsCon Tunis will be a bustling hub, situated at the Laico Hotel and the Palais des Congrès, right next to the city???s Human Rights Square, and just a few minutes walk from the downtown core. RightsCon Tunis will build on the historic success of RightsCon Toronto by continuing to provide a space for a community of civil society organizations, technologists, businesses, startups, public servants, and lawyers to connect, collaborate, build strategies, draft declarations, and move forward real-world change. Whether in provocative plenaries, intimate roundtables, informal meetings, or the lively Community Village, RightsCon Tunis will help shape the future of human rights in the digital age. RightsCon Tunis will be the summit???s eighth iteration, the first hosted in Africa and the Middle East. As an emerging tech center and growing democracy, Tunisia has been a beacon of hope for others across the region and the world ??? yet there is still so much work to do. Next year???s program will tackle current pressing issues and those on the horizon, including: ----------------------------------------------------------------------------- * Election integrity and the erosion of democratic values; ----------------------------------------------------------------------------- * Artificial intelligence and algorithmic accountability; ----------------------------------------------------------------------------- * Our identities online, biometrics, and facial recognition technology; ----------------------------------------------------------------------------- * The convergence of emerging technologies; ----------------------------------------------------------------------------- * Data trust, protection, and user control ??? locally, regionally, and globally; ----------------------------------------------------------------------------- * Misinformation and the future of journalism; ----------------------------------------------------------------------------- * Preventing net discrimination and promoting Net Neutrality; ----------------------------------------------------------------------------- * Privacy, surveillance, and societal control; ----------------------------------------------------------------------------- * Digital inclusion and accessibility; ----------------------------------------------------------------------------- * Technology as a tool for the Sustainable Development Goals; ----------------------------------------------------------------------------- * Strengthening digital security and encryption; ----------------------------------------------------------------------------- * Cybersecurity policy; ----------------------------------------------------------------------------- * Conflict and humanitarian response in the digital age; ----------------------------------------------------------------------------- * And much, much more. ----------------------------------------------------------------------------- It is more important than ever to bring the RightsCon community together. These topics are just a glimpse of what???s to come. Tell your network you???re joining us in Tunis. SHARE ON FACEBOOK: [https://www.e-activist.com/ea-action/enclick?ea.url.id=1510846&ea.campaigne…] SHARE ON TWITTER: [https://www.e-activist.com/ea-action/enclick?ea.url.id=1510847&ea.campaigne…] Soon, we???ll be sharing with you important updates on RightsCon Tunis, including the launch of our new RightsCon community platform in early October, which will host our call for proposals . Make sure to keep an eye out for details on attending the summit including ticket sales, hotel accommodations, travel visas, and more. Mark your calendar, save the date, and get ready for the official RightsCon call for proposals. We can???t wait to see your submissions! Chat soon! Nikki RightsCon Program and Community Manager Stay connected with the RightsCon [https://www.e-activist.com/ea-action/enclick?ea.url.id=1510850&ea.campaigne…] community on social media for all the latest updates. [https://www.e-activist.com/ea-action/enclick?ea.url.id=1510848&ea.campaigne…] [https://www.e-activist.com/ea-action/enclick?ea.url.id=1510849&ea.campaigne…] Follow Access Now [https://www.e-activist.com/ea-action/enclick?ea.url.id=1510854&ea.campaigne…] for more opportunities to join the fight for human rights in the digital age. [https://www.e-activist.com/ea-action/enclick?ea.url.id=1510851&ea.campaigne…] [https://www.e-activist.com/ea-action/enclick?ea.url.id=1510852&ea.campaigne…] [https://www.e-activist.com/ea-action/enclick?ea.url.id=1510853&ea.campaigne…] You are receiving this email because you have registered for updates about RightsCon. If you do not wish to receive these emails, click here to unsubscribe: [https://act.accessnow.org/page/broadcast.message.redirect.do?campaignpageur…] For support on anything related to RightsCon, please contact us at conference(a)accessnow.org. The hyperlinks in this email contain URLs with tracking IDs used to measure clicks, only for the purpose of internal metrics. We do not sell or share this data with third parties. We use this data to improve the quality and relevance of our campaigns, and it is collected and stored in compliance with our Data Usage Policy [https://www.e-activist.com/ea-action/enclick?ea.url.id=1510855&ea.campaigne…] . If you would prefer to receive the RightsCon Rundown without these tracking IDs, you can opt out by clicking here: [https://www.e-activist.com/ea-campaign/action.handleOptOut.do?ea.question.i…] Feel free to contact us at info(a)accessnow.org with any questions or concerns. Access Now defends and extends the digital rights of users at risk around the world. Your support makes a difference. Donate here. [https://www.e-activist.com/ea-action/enclick?ea.url.id=1510856&ea.campaigne…] [https://www.e-activist.com/ea-action/enclick?ea.url.id=1510857&ea.campaigne…] | P.O. Box 20429, Greeley Square Station, 4 East 27th Street, New York, NY 10001-9998 ----- End forwarded message -----

1 0

UX Team Report - August 2018
by Antonela Debiasi 18 Sep '18

18 Sep '18

Hi Tor, Those are the highlights from last month: * Tor Browser Tor Browser 8 got released, and I'm proud of the work we did in collaboration with the Development, Community and Communications teams. We thought about the user experience browsing with Tor Browser 8 as an opportunity to educate users. Educated users empower our product. The new circuit display, the onion padlock, and the new onboarding are just the beginning. https://blog.torproject.org/new-release-tor-browser-80 Tor Browser for Android got it first alpha release, please download it and let us know what do you think! https://blog.torproject.org/new-alpha-release-tor-browser-android * Tor Browser Icon Tor browser got significant visual updates, and we think that our icon should reflect it. Yes, Tor Browser needs a new icon *_* I have been working on some concepts to replace the globe icon. What do you think? Do you have ideas? Dump there at the ticket! https://trac.torproject.org/projects/tor/ticket/25702 * New torproject.org Website After the support portal launch, we continued our Tor Project website redesign focusing on landing pages. We are working with the Communications Team iterating content and layout. You anxious? Feel free to sneak peek the prototype here: https://marvelapp.com/project/2397265/ * Usability Research Helen is traveling through Kenya meeting and interviewing our users. We are using the ticket #27010 for hosting all our usability research efforts. https://trac.torproject.org/projects/tor/ticket/27010 * Academic Research Marshini Chetty and Agnieszka Dutkowska-Żuk from Princeton have been playing with .onions for a while and also they wrote a paper (!). Last month we met to talk about further usability research related with onion services and Tor Browser. Thanks, Marshini and Agnieszka! * Conferences Hiro spoke about onions and different user cases at Fullstackfest in Barcelona. Are you curious about .onions? You can see the slides here: https://slides.com/hiropaw/deck-15-18#/ * S9 - Localization The new Tor Browser 8 got released with 9 nine more language support: Catalan, Irish, Indonesian, Icelandic, Norwegian, Danish, Hebrew, Swedish, and Traditional Chinese. Thanks, emmapeel, arthurdelsdein, ggus and folks around the globe for making it happen! On behalf of the Tor UX team, Antonela

2 3