15:07:12 #startmeeting SponsorR 15:07:12 Meeting started Tue Jun 9 15:07:12 2015 UTC. The chair is dgoulet. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:07:12 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:07:18 hi everyone! 15:07:22 hi! 15:07:29 hi! 15:07:39 so please go ahead with status report while I press send for this email :) 15:07:46 * syverson can go 15:07:55 please do 15:08:18 ohmygodel, Rob Jansen and I met w/ Richard Barnes of Mozilla and Let's Encrypt. 15:08:37 I sent an email about it to tor-internal this AM. 15:08:56 Also finally got around to putting a few entries into the terminology wiki. 15:09:07 (arma: that draft blog post thingy is waiting on your signoff I think) 15:09:29 Otherwise been busy with separate presentation for today and other stuff mostly. 15:09:31 Done. 15:09:54 syverson: interesting email btw! ok thanks 15:10:07 * karsten can go next and will be very quick 15:10:11 go 15:10:42 mostly/entirely distracted by other things this week. only relevant piece was an email to dgoulet where I asked him about details about his HS health tool. 15:10:49 done. 15:11:19 karsten: for which you should have the answer in your inbox :) 15:11:28 I'll go I guess 15:11:38 dgoulet: I do! :) 15:12:47 so analysis script of the hs health csv logs, I got some good feedback from asn on better analysis that could help us directly now, little-t tor SponsorR related, there is still #4862 in pending review but that fixes lots of open tickets and not a trivial change 15:13:40 been helping isabela and asn about the deliverables, that's about it 15:13:50 oh right, I saw that. 15:13:59 (/me is here and can do a status as needed) 15:14:00 do you need any more help there, or is that done? 15:14:07 karsten: seems all under control for now 15:14:12 yay! 15:14:21 oh ah also one more things 15:14:50 this ticket is also relevant to R that might need more eyes on #16260 15:14:56 * dgoulet done 15:15:01 * armadev can go 15:15:05 go 15:15:08 I had a great chat with Patrick Gray about Ricochet and other novel onion servi 15:15:09 ce ideas. 15:15:16 He went partway to convincing me that Ricochet is going to be a better plan than a Tor Messenger, chatzilla style. 15:15:26 Also he argues that 1-to-1 communication is harder to attack, PR-wise, from the 'what about bad people' angle. 15:15:39 It's likely that I did other things for SponsorR recently (e.g. helping on the HSDir flag tickets) but I do not currently remember them. 15:15:55 There's also the Sybil discussion, where there's a huge uptick in people running relays in order to attack the hsdir subsystem. 15:15:58 done. 15:16:17 * nickm ? 15:16:21 thanks! 15:16:22 nickm: go 15:17:20 I reviewed patches, talked about design stuff, wrote up a proposal to stop using RSA in hidden services entirely (see prop 245, needs review and thought) 15:17:47 There's a neat paper that wendy circulated about this RAPPOR thing that google uses to aggregate usage stats; maybe it would work for us. 15:18:12 Roger mentioned to me it might be possible to frame prop-224 work as sponsorR, maybe. If that's the case, we could really tighten stuff up. 15:18:23 I hope to be more responsive this week than last, given my lack of doom-meeting. 15:18:26 Can you say a few words, maybe for it vs. privex? 15:18:39 not yet; wendy just sent it around this morning :) 15:18:54 Yeah I didn't look and was hoping you somehow had. 15:19:24 diddid everybody get that email though? 15:19:27 hrm where is that RAPPOR thing ? 15:19:36 https://static.googleusercontent.com/media/research.google.com/en/us/pubs/archive/42852.pdf 15:19:39 * isabela is around 15:19:40 https://github.com/google/rappor 15:19:46 not sure if it 15:19:58 is at all suitable for our use, but it couldn't hurt to mine it for ideas. 15:20:05 I got it. 15:20:26 we should make sure that aaron/rob got it also 15:21:01 nickm: all done? (status-report) 15:21:05 They should be on tor-assistants, but I'll forward a reminder. We've got an intern working on pointing privex at onion services. 15:21:34 syverson: just that I don,t see that email on tor-assistants :S 15:21:55 ah! nvm... I'm stupid 15:22:00 syverson: is it safe to specify which intern? 15:22:17 dgoulet: yes, all done. Also, my apologies but I need to run to the bank soon. 15:22:26 We only have one. He's from USNA. 15:22:54 An undergrad student of Adam Aviv's. 15:22:55 nickm: np, thanks! 15:23:15 isabela: hi! if you want to do a status report, go ahead else we are at the discussion phase mostly 15:23:19 ok. will be here another 15 min or so lurking 15:23:53 dgoulet: thanks, just watching :) 15:24:25 ok so I think everyone spoke, anything we should discuss ? 15:24:44 Beer? (Sorry) 15:25:05 syverson: no funding for that :( :P 15:25:22 what about this idea of squeezing 224 in R ? 15:25:56 it is a poorly formed idea. basically it seems like we're wasting a lot of time putting bandaids on the old design, 15:26:09 and we should explore whether we could be a lot more efficient if we use a bigger bandaid 15:26:46 that is, all the folks doing hsdir attacks right now are soaking up our time. can we make those attacks stop working? how much work would it be? 15:27:28 yeah #8244 on the old design or 224 :) 15:28:15 armadev: so should we then try an inception in July to our PM ? :) 15:28:43 can we do 224 piece by piece? or does it have to all go out at once? and if piece by piece, what's the most important / most efficient piece to do first? 15:29:05 armadev: as of the next release it will be slightly harder 15:29:10 hrm I do think we can go incrementely on some part if I recall correctly 15:29:19 and yes, we should totally find out, in july, what our new program manager thinks of all this direction. maybe he likes it, who knows. 15:29:22 Since HSDir will require Stable ('Fast' pending) 15:29:25 but that should be something we can start working on, a transition plan short/mid/long term 15:29:26 also also, it could be a great focus for the july hs hackfest 15:29:37 but that is indeed another bandaid 15:30:01 (weasel suggests 'Guard|Exit' fir HSDirs, but that would need a ton of analysis) 15:30:10 yawning: yea, i want to change the fact that you can generate a particular relay key, then wait sufficiently, then you're in the right spot to do the attack. 15:30:17 yeah 15:30:36 (I need to find the time to expand on the no-HSDirs idea soon. So many things to do.) 15:30:43 raising the bar with voting hax not that effective 15:30:55 yeah bandaid solution :) 15:31:07 also, the 224 design will require changes based on the tor-internal thread that currently mike/I are having 15:31:10 special: speaking of you, speaking of the hs hack fest, is that under control, or is everybody hoping somebody else is dealing with organizing it? 15:31:15 about that pre-print 15:31:48 rather, some of the fixes I want would make the most sense to do as we transition to 224 if we are ready 15:31:51 armadev: I only need a reply to my travel@ email :) 15:32:01 yeah, ugh, good point. 15:32:04 armadev: I was thinking of pinging people later today to figure out what logistics need to be logisticized 15:32:26 (I do want more than mike involved in discussing that, but hard since it's a preprint ;_;) 15:33:13 and there's a bunch of design work/analysis needed I think 15:33:28 (sorry, guess this isn't that R-ish) 15:33:32 yawning: ok. i have no idea what you're talking about. it's likely others here don't either. 15:33:49 there's a pre-print paper about more HS attacks 15:33:50 discussion on the Usenix paper thread 15:34:01 Ah! 15:34:20 when does it turn from a pre-print to a final version? that should be real soon now right? 15:34:27 yeah I think so 15:34:31 it's a good paper 15:34:42 well great. is it an attack paper or a fix paper? 15:34:51 attack with mnitigations suggested 15:34:51 they are suppose to send me the final version when they have it 15:34:56 but, the mitigations are.... hard 15:35:10 and I can extend their attack for a few more things that their mitigations don't cover 15:35:17 oops 15:35:51 though the mitigations are good if we can figure out how to implement their suggestions correctly 15:36:22 mike had some ideas, that I'm not sure/scared about 15:37:19 can you take point on making sure we tell the world about it, as soon as we can? 15:37:35 what, the attack? 15:37:36 rather than waiting and hoping nobody notices and then some journalist writes it up poorly 15:37:41 ok 15:37:46 i dunno, the paper and everything from it 15:37:50 yah 15:38:10 also, the attack isn't a 224 will fix it thing for once 15:38:28 we should look at our 224 design and see if we can change this situation 15:39:07 great 15:39:09 ok 15:39:22 *cough dgoulet cough* 15:39:25 :P 15:39:32 :) 15:39:37 yawning: please rope in as many people as you can for this. it sounds like it totally falls inside sponsorr scope. 15:40:16 mmk 15:40:32 ok so I propose we start, even before the hackfest, some work on the transition plan, patch 224, basically start the ground work 15:40:43 mostly want dgoulet/asn to read the paper so I can talk about it 15:40:44 else it will keep piling up I feel like 15:40:45 :P 15:40:48 yeah 15:41:14 and in July we'll work on an inception operation :) 15:41:49 ok do we have more topics to discuss? 15:42:00 we got the Stable requirement in 026, thanks Yawning's pressure! :) 15:42:24 ^_^ 15:43:06 ok so I guess we can end our meeting unless someone screams? 15:43:27 AAGAAAAAAAAAAAA 15:43:28 ? 15:43:33 See you next week. Same bat-time same bat-channel. 15:43:38 i think we should think of the recent sybil issues as in-scope too 15:43:47 since they seem to keep being about hsdirs 15:43:57 which leads to the whole process of cutting out malicious relays 15:44:04 which leads to the interaction with the research community 15:44:07 all in-scope 15:44:11 armadev: what do you mean by in-scope too ? 15:44:14 in-scope of R ? 15:44:15 yes 15:44:51 Hmm. So developing guidelines is in scope. Makes sense but I hadn't thought about it that way before. 15:45:06 and assessing guidelines 15:45:16 which means testing them. and applying them to test them. :) 15:46:39 is there someone writing them or thinking of writing them? (can't remember the latest on the thread) 15:48:10 i'm not sure. phw knows, but the last mail from phw said he is done with this topic. 15:48:48 ok so let's keep that in our eyesight for R 15:49:09 so, someone else should take point there yes? 15:49:16 ideally the dir auth people? 15:49:37 ideally. but i bet they're all full. 15:49:40 (dunno, someone else?) 15:49:42 yeah 15:50:24 Crap said bye to wrong channel. Here we go: Bye for now. 15:50:28 dgoulet: would you be around after the meeting to work a bit more on the HS health questions? 15:50:41 karsten: sure!, I just need to get food and after that I'm here 15:50:44 ok so let's close this meeting 15:50:51 thanks all! 15:50:55 #endmeeting