15:59:00 #startmeeting tor anti-censorship meeting 15:59:00 here is our meeting pad: https://pad.riseup.net/p/tor-anti-censorship-keep 15:59:00 feel free to add what you've been working on and put items on the agenda 15:59:00 Meeting started Thu Jul 21 15:59:00 2022 UTC. The chair is shelikhoo. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:59:00 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:59:07 Hi everyone~ 15:59:48 hi 16:00:35 hello 16:01:27 o/ 16:02:06 I have removed git repo migration and sharing URL for bridges topic, let me know if we wants to discuss it in this meeting 16:02:44 is fine for me 16:03:52 same 16:04:45 while everyone is editing, there is a silent announcement. please discuss this in the private ticket itself: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/issues/40161 (Private) 16:06:35 not sure this is on topic, but i will mention that it seems like ROSKOMNADZOR might have lifted the ban on the torproject.org website, but not on the tor network itself https://gitlab.torproject.org/tpo/community/support/-/issues/40050#note_2823017 16:06:51 \o/ 16:08:08 hahaha, it is interesting... 16:09:22 is kind of funny that they recognize publicly that they block the website, but not that they block the tor network, so we can fight legally for the website but not the network 16:10:03 yeah 16:10:12 i wonder how that works, it's an interesting question 16:10:35 Perhaps it's a different authority/department that blocks the Tor network. 16:12:06 AFAIK both are blocked by ROSKOMNADZOR 16:12:30 meskio: How do you/they know? 16:13:19 actually you are right, I have no idea, is supposed to be the government section that should deal with blocking content, but who knows 16:13:59 For instance in Spain there are multiple authorities that block websites, I recall reading a blockpage with different case statements per blocking authority. 16:14:19 and it 16:14:40 yes, AFAIK in spain there is no single organization for censorship 16:16:18 and it's pretty common practice in Europe, there re public website blocklists, private CSAM blocklists, police, court and blocking of websites from other authorities. And then the ISP itself to block phising domains :) 16:17:41 yes anything more on this topic? 16:18:11 not from me 16:18:25 logcollector redeployment finished, project moved to team space(src shell) 16:18:25 https://gitlab.torproject.org/tpo/anti-censorship/connectivity-measurement 16:18:25 https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/70 16:18:25 https://gitlab.torproject.org/tpo/anti-censorship/connectivity-measurement/logcollector-admin/-/issues/3 16:18:34 another announcement here 16:18:56 the log collector have been moved to team namespace 16:19:26 congrats, is a great step forward 16:19:57 👍 16:19:57 Is there a recommended location to share all the passwords(cloudflare accounts) and other infos with other team members? 16:20:15 great work! 16:20:26 thanks! 16:21:35 shelikhoo: I don't know what other teams do, in other non-tor projects I use a git repo with passwords encrypted to the openpgp keys of the people 16:21:58 there is pass for example that works pretty well for that 16:22:10 yes. I think this should be fine... let me do that 16:22:18 +1 16:22:32 okay, anything more on this topic? 16:22:58 we will now move to the discuss part 16:23:03 the first topic is 16:23:03 What is the status of adjusting snowflake (pion) DTLS signature to avoid blocking in Russia? (Based on offset of supported_groups extension.) 16:23:20 I have then posted the link to browser to forums 16:23:36 https://ntc.party/t/testing-invitation-for-tor-browser-with-supported-groups-patch-countermeasure-in-snowflake-to-evade-censorship-observed-in-russia/2837 16:23:36 (Not working???) 16:23:36 https://forum.torproject.net/t/testing-invitation-for-tor-browser-with-supported-groups-patch-countermeasure-in-snowflake-to-evade-censorship-observed-in-russia/4029 16:23:36 (No reply #~#) 16:23:58 on the ntc forum, some user reported that it is not working 16:24:31 :( 16:24:44 yet it still need more info to find out the root cause of failure 16:25:26 Is this testing invitation only valid to Russian networks or also elsewhere (where Snowflake is blocked)? 16:25:53 the countermeasure patch is specific to a kind of block observed in russia 16:26:41 so it is not targeted at other regions 16:28:13 what should be our next step? 16:29:48 people at ntc.party seems to be fairly tech savy, can we ask them to do any kind of test that will help to figure out why is not working for them? 16:31:08 I could comment and request a packet capture 16:32:43 sounds like a good next step 16:32:50 yes, let's do that 16:33:11 we can discuss again once we have got more info on this 16:33:17 anything more on this topic 16:34:10 the next topic is 16:34:15 Bug fix release for Snowflake necessary(src shell) 16:34:15 Semver? 0.6.1, is cherry-pick necessary? 16:34:15 https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/issues/45 16:34:15 https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-webext/-/merge_requests/40 16:34:49 a bug is discovered in snowflake that will display incorrect number of users helped 16:35:15 we could release bug fix release to fix this 16:36:12 I think cherry-picking is too much work, I think it makes sense to release a new version with the current main 16:36:25 by cherry-pick the fix on to 0.6.0 as 0.6.1 and send WebExtension to markets 16:36:48 but if you prefer to cherry-pick, go ahead 16:37:04 the fix is small enough I think it should be able to just work 16:37:17 without the need to manually merge anything 16:37:43 I will try to cherry-pick and generate a release 16:38:07 and release at main as a fallback 16:38:09 ok, good for me 16:38:17 anything more on this topic? 16:38:39 nop, thanks for taking care of it 16:39:30 yes. anything more to discuss in this meeting? 16:40:40 not from my side 16:41:39 okay, thanks everyone! 16:41:39 #endmeeting