13:30:02 #startmeeting 13:30:02 Meeting started Wed Aug 12 13:30:02 2015 UTC. The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:30:02 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:30:20 good morning, friends! 13:30:36 Let's start with quick quick status reports and move on to discussion, as is our want. 13:30:38 good 13:30:40 *wont 13:31:25 I've been working on reviewing stuff, getting all of s7r's ed25519 usability issues solved, etc 13:31:54 and I've also been hacking away at the Blob (for blob == "our largest strongly connected component in our call graph") 13:32:37 I hope I can get a lot of writing done, but code is so interesting! 13:32:46 Also we need to talk about freeze for 0.2.7 13:32:55 who's next? 13:33:07 debugging 13:33:22 oh? 13:33:34 stupid ed25519 batch verifyciation code sigsegvs 13:33:39 ah 13:33:48 uh, apart from that, did pt paperwork 13:33:57 now back to my regularly schedule tor fun 13:35:38 I reviewed the SR proposal and some of nickm's patches. 13:36:39 I started work on the fallback directories again, and should be able to have the whitelist code ready really soon 13:37:24 The challenge is then to get the opt-in organised and work out how many fallbacks we need 13:37:25 and the max percentage of clients we want any one fallback to see 13:37:32 #15775 13:37:39 done 13:37:52 finishing off/checkpointing a bunch of dirauth dos filter (#4581) glue and connection-counting hash table i've been on for the last few weeks before leaving for cccamp later tonight - will be testing/debugging after i'm back 13:38:25 sounds good; is it ready for initial review? 13:40:23 athena: ^ 13:40:33 close; still some bits missing but i might get a chunk of them done before i leave later 13:40:42 also, anybody else with an update, or shall we move on to discussion and stuff/ 13:40:43 ? 13:41:38 ok, discussion! 13:41:50 cool 13:42:32 Discussion topics include: deliverables to do for october-ish; how to handle the 0.2.7.x freeze; and... not sure what else 13:43:03 ok 13:43:56 I guess the first topic is more for athena and Yawning 13:43:59 if no other topics, let's talk deliverables 13:44:02 since we dont have all the people here 13:44:21 have you guys seem -> https://docs.google.com/spreadsheets/d/1dTva10mu-FcX8KrxRjgkFvHSyNy7aBpD9xehNuUeZ-4/edit#gid=0 13:44:26 yeah. I'd love to know if others think they can pick up any of the stuff on that list with a super-high chance of getting something done on time. 13:45:38 I ended up without time to add the tickets there but is on my list 13:45:44 (One undesirable outcome is picking it up and then kicking it back to me at the last minute. :) ) 13:45:46 as i indicated earlier, i can definitely take row 6 but i believe it has a dependency on 5 and i'm not current enough on plans for path/guard selection changes to write that spec 13:46:20 I have no idea about the guard stuff 13:46:56 i think asn may be the only person who really does get that and we're short an asn this week 13:47:05 yes 13:47:16 athena: i will putyou on 'who can do' for row 6 13:47:22 for now 13:47:29 Yawning: maybe some of the documentation part? 13:47:30 right, but let's make sure we return to the asn part of it rsn 13:47:31 or testing 13:47:36 ??? 13:47:47 Yawning: just listing other tasks not related to guards 13:47:51 that we need help 13:48:11 the deadline on it would pass before I know enough about the guard thing 13:48:17 nickm: yes, we should do this again next week / i will follow up via email and cc folks this time 13:48:30 I have one thing in my pipeline for more DoS resistances for HSes 13:48:45 which may be 13 13:48:53 but, it's not a propsal, just a code improvement 13:49:17 Yawning: turning it into a proposal -- would that take more than an hour? :) 13:49:30 it's not really a spec change type thing 13:49:38 just "yeah, we drop INTRO2s if the user asks" 13:50:17 asn is currently going to CCC camp 13:50:26 I could go more elaborate and be like 'The HS can use the super special HSOrPort to query the app if it should accept or reject a incoming rdv attempt' 13:50:41 which would be proposal worthy but is a few orders of magnitude more complicated than what I ahd in mind 13:51:02 hm. 13:51:40 well, we can always think of another anti-DoS thing and write a proposal for it 13:51:52 maybe something to handle socket exhaustion on exits or something. 13:52:24 wtffff why is this bullshit segfaulting in crypto_rand 13:52:27 it is still in my August TODO list to write the guard algorithm 13:52:28 *punches wall* 13:52:57 internet in this train is bad. see you later. please send mail if you want careful reply! 13:52:58 Yawning: paste a stack trace? 13:53:24 asn: ok. soon we'll be blocking on it, so getting it together soon will really help 13:53:31 we're not blocking on it quite yet though 13:53:41 nickm: #0 0x0000555555b3c858 in crypto_rand () 13:53:43 #1 0x000055555582779a in ed25519_randombytes_unsafe_donna (len=64, 13:53:45 p=0x7fffffff6ca0) 13:53:48 at ../src/ext/ed25519/donna/ed25519-randombytes-custom.h:16 13:53:55 p is def valid 13:54:04 and has 64 bytes? 13:54:08 yeah 13:54:31 (gdb) p sizeof(batch.r) 13:54:33 $2 = 2064 13:54:42 this is happening from unit tests, or what? 13:54:50 yah unit tests 13:55:08 the code you had in crypto_ed25519.c would have segfaulted later, but I fixed that >.> 13:55:40 err earlier too 13:56:05 hm. let's poke more after meeting 13:56:26 sorry I should focus on the meeting 13:56:36 :) 13:57:02 It might help if I could get somebody to help with all the documentation tasks I have for sponsorU, but I'm not sure whether I .can. delegate those. 13:57:28 like, there are corners of tor's internals that would need serious archeology for somebody else to write about. 13:57:29 nickm: can we do a check on this list every meeting? just so we dont miss anything in this list couple months before deadlines 13:57:29 I can think more about the DoS stuff but my plate is suprisingly full 13:57:34 sounds good 13:57:47 Yawning: yow, thanks 13:57:54 people can pick up stuff later as they have more time too 13:58:05 we just cant ignore this list :) 13:58:10 nickm: yeah, there are definitely significant pieces of tor i don't think anyone but you has ever touched 13:58:27 I bet that team effort on the whitepaper about classifying DoS attacks might be smart. we're all good at those. 13:58:43 we did fix a bunch of gnarly DoS attacks vs HSes 13:59:01 but we just fixed them/added mitigations and not like "wrote propsals" 13:59:35 (hell, even that scalar base mult stuff is a DoS mitigation thing >.>) 14:00:13 I'm better at making DoS attacks via chutney than fixing them 14:00:22 well we wrote the shared randomness proposal. that's anti-DoS right? :) 14:01:21 #prop250 14:03:30 maybe :) 14:03:41 should we move on to the 0.2.7 freeze thoughts? 14:03:56 There's a bunch of stuff I'd love to get into 0.2.7, but I'm also leery of letting anything go to long. 14:03:59 It snowed here in Canberra today 14:04:12 Oops, random association 14:04:18 hm 14:05:28 nickm: maybe we should focus on what has already being selected for august? 14:05:59 makes sense. Try to do the CoreTeam201508 stuff, and then freeze at end-of-aug? 14:06:21 teor: snow in canberra? maybe i should watch the news; sydney felt a bit colder than normal. 14:06:23 https://trac.torproject.org/projects/tor/query?keywords=~TorCoreTeam201508 14:06:33 nickm: yes 14:06:56 we should review to confirm if it makes sense but I think is the way to start 14:08:02 review now, review soon, or review next week? :) 14:08:47 do we have the time to do it now? 20min left for the 1hr meeting 14:08:51 still not sure if we should ship ref10 that will rarely get used 14:08:59 since so far no one has complained 14:09:02 heh 14:09:05 fractalcat: I stayed inside and coded all day 14:10:33 Yawning: I'm a bit indifferent there. 14:11:39 so first thing to do would be to look over isabela's list and see if there's anything assigned to you which you can't do? 14:12:03 myself, I find myself putting off #15055 for a smarter day. 14:12:15 i have both #12595 and #16255. i hope i can do both properly. 14:12:53 i've done most of #16255 already. testing is left. but it's not easy to test. 14:13:09 i've been prioritzing on #16255 so far. but maybe i should swwitch to #12595 since so many people care about it. 14:13:33 I have been trying to help out with testing #16255, but I think there's still a bit of a gap 14:13:40 asn: sounds like a good idea 14:13:50 isabela: ack 14:14:07 Oh, I just realised that #15775 is DoS resistance, too 14:14:41 great 14:15:13 Is there a tag for that? 14:16:18 hm if freeze is in august guess I should focus on the pt stuff I want in :/ 14:16:56 If I want to get fallbacks in, they'll need to be done quick-smart. But my guess is that opt-in will push them to 0.2.7.3 14:17:03 Oops. I mean 0.2.8 14:20:12 if it's dos, use the DoS and the SponsorU tags 14:21:08 Done. Spreading the load using fallback directories makes it harder / less productive to DoS the authorities. 14:22:58 woo 14:23:26 any more for today, or are folks out of energy? :) 14:24:07 i will send an email summarizing 14:24:23 btw dgoulet is on vacation (/me believes) and/or on his way to camp 14:24:36 sounds good 14:24:42 and now it's time for me to say...... 14:24:45 #endmeeting