16:00:42 #startmeeting tor anti-censorship meeting 16:00:42 Meeting started Thu Jan 9 16:00:42 2025 UTC. The chair is onyinyang. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:00:42 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:00:43 hello everyone! 16:00:43 here is our meeting pad: [https://pad.riseup.net/p/r.9574e996bb9c0266213d38b91b56c469](https://pad.riseup.net/p/r.9574e996bb9c0266213d38b91b56c469) 16:00:54 hi! 16:01:04 Hi ^^ Happy New year! 16:01:05 hello 16:01:19 :) 16:01:40 hi~hi~ 16:01:46 happy new year! 16:02:44 hehe, we've survived another year 16:04:31 so far lol 16:04:52 oh no, I guess we finished surviving 2024 >.< 16:05:43 :D 16:10:25 and a few percent of 2025 16:10:28 as of now... 16:10:37 It doesn't seem like there is much new to discuss this week except the discussion point just added 16:10:45 Supporting WebTunnel Early Data 16:11:40 I think we left a bunch of topics open in the last meeting before the break, not sure if any need some discussion, I reseted my brain 16:11:49 but we can look into them after the webtunnel topic 16:12:21 sounds good 16:13:29 who did add the webtunnel early data? 16:14:00 Me! 16:14:47 so the thing is that httpupgrade, the transport protocol we used in webtunnel 16:15:35 can support early data: combining the first chunk of client data with the http 1.1 upgrade handshake 16:15:57 to reduce rtt required for creating connection 16:16:23 do we wish to add it to webtunnel 16:17:02 for the context, V2Ray added support it recently so I think maybe we could port it to webtunnel version as well 16:17:32 this is done by encoding the initial data into http header 16:18:10 so that it will be send alongside http1.1 upgrade request 16:18:55 https://github.com/v2fly/v2ray-core/blob/master/transport/internet/httpupgrade/dialer.go 16:19:04 that would be really nice, will it take a lot of effort? 16:19:08 This will make code more complex... 16:20:16 the time required should be manageable, as it is already supported in V2Ray, I just need to port the code 16:21:05 I see, you know better the code, if you think it makes sense, go for it, might not be a big loss if we don't do it as anyway tor's bootstrap is not that fast :S 16:21:43 yes... I think we could wait a while until it is clearly necessary 16:22:34 since V2Ray's version did use its own common library to support the new functionality 16:22:53 we will need to either inline or copy them to use it in webtunnel 16:22:53 over 16:22:58 does it make sense to keep an issue in the "roadmap::future" to keep this idea round? 16:24:17 yes, we could create an issue so that we know where to look at when it is necessary 16:24:38 +1 16:25:20 BTW, we already have over 300 webtunnel bridges, thanks to the bridge campaign 16:25:21 eof 16:25:27 oh! nice! 16:25:32 and is the default transport in russia in circumvention settings 16:25:57 I forgot this early data update would require an update on both client and server 16:26:26 so it won't be instant in webtunnel's case 16:26:37 I see 16:27:32 going over the topics from pre-break 16:27:43 I think Azure changes were done and nothing to update there, isn't it? 16:27:58 that's right, afaik 16:28:19 on the alternative domain fronts we are waiting for the vantage points to be able to test fronts 16:28:39 shelikhoo:this is on your hands, I guess nothing to update for now 16:30:22 what is the status of the covert-tls tests? 16:30:28 I did test the proxy and looks good 16:30:33 do we have something for the client? 16:31:16 i think it is partially blocked on me, i started some tor browser builds 16:32:05 yes... I understand we wants to test domain fronts on vantage points, I will work on that once the snowflake circumvention settings auto update is done 16:32:09 i forgot to check them over break and they failed because of some missing perl dependencies on my machine 16:32:22 i'm looking into it now and will update on the issue 16:32:57 For the how to test part, I haven't written anything. I will test a bit my self and write something when the binaries have been compiled 16:33:06 shelikhoo: nice, let's talk back about it once that work is done 16:33:13 yes! 16:34:14 cool, thanks for looking into it 16:34:24 cohosh: thanks! Also no worries, I have been taking a full offline vacation, so no blocking my work pipeline :) 16:34:27 no problem! 16:36:03 I think that covers all of the pre-break topics 16:36:14 BTW, for my tests of the proxy I added per-country prometheus stadistics to the proxy, is that something we want to integrate in main? I could clean up the code to send a merge request 16:37:14 sure 16:37:54 I'll do that then 16:38:05 yes, now I'm done with pre-break topics 16:38:29 heh 16:38:35 the interesting links are also from pre-break I think 16:39:12 no, I think they are new 16:39:22 oh, ok, my bad 16:39:23 at least I added IRGFW 16:39:25 and the report is from 2 days ago 16:39:47 I mean the daily operations is from 2 days go 16:40:19 I haven't readed the IRGFW report yet, not sure how good it is, but I saw it circulating around 16:42:54 cool 16:43:45 anything else on this or any other topic? 16:44:22 just a reminder, next week we have reading group 16:44:25 if not, just a reminder of the reading group next week 16:44:30 yep 16:44:33 !!! 16:44:41 we will be discussing: Discovering and Measuring CDNs Prone to Domain Fronting 16:45:09 yes! 16:45:28 :) 16:46:13 that's it for this week then :) thanks everyone! 16:46:14 #endmeeting