16:59:59 <nickm> #startmeeting hi all!
16:59:59 <MeetBot> Meeting started Mon Jan  9 16:59:59 2017 UTC.  The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:59:59 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:00:03 <nickm> it's another network team meeting!
17:00:07 <nickm> happy new year!
17:00:17 <nickm> I'm still in NYC for hacs; I travel back home tomorrow
17:00:30 <dgoulet> hello!
17:00:54 <nickm> so I think we have about 2 weeks left of being open to feature patches in 0.3.0...
17:01:07 <nickm> and a whole bunch of stuff to review
17:01:13 <nickm> that's going to be an adventure!
17:01:47 <nickm> let's see.  I was at RWC this past week, and now I
17:02:09 <nickm> m at HACS.  I've been learning more about fuzzing, about SAW (https://saw.galois.com/downloads.html), and other fun stuff
17:02:26 <Yawning> hi or something
17:02:56 <asn> hello!
17:03:09 <isis> hey hey
17:03:49 <isis> i'm also in NYC because i was at RWC
17:04:11 <nickm> not getting much hacking done this past week though
17:04:13 <nickm> how are others?
17:04:25 <asn> i can go next
17:04:26 <nickm> (hi dgoulet , isis, Yawning !)
17:04:29 <nickm> woo
17:04:32 <asn> I'm now back in Europe! Past week was spent relaxing and recovering from
17:04:32 <asn> various stacked colds and doing some Tor stuff. During Christmas I found three
17:04:32 <asn> potential bugs on the guard code: #21142, #21128, #21129. I also updated the
17:04:32 <asn> HSDir code to conform to the latest prop224 (#20852), and did some review on
17:04:33 <asn> #20029 and #21059.
17:04:51 <isis> me neither, for hacking, but i think talking to people at RWC fixed a couple of my crypto problems
17:04:56 <isis> woah, damn, asn
17:05:34 <isis> so i have a nice generalised way to deal with the curve cofactor now, so my proof will come out nicely
17:06:16 <Yawning> I spent the last week praying for armageddon and being terrible at bloodborne. Need to figure out what I want to do next.
17:06:29 <isis> and the issue with elligator2 is more understood, but i'd still like to write an exploit for current code, just to see how bad the issue is
17:06:38 <nickm> yawning: what kind of stuff are you looking in to?
17:07:21 <Yawning> uh
17:07:30 <Yawning> dunno yet
17:08:02 <nickm> asn: cool! what's next for you?
17:08:53 <nickm> there are some MIT students who have a curve25519 implementation that's only 25% slower than donna64, but it's provably correct. (for some values of provably)
17:09:21 <asn> more guard algo testing (i have a branch which does more logging), more prop224 (probs working on the foloowup tasks of #20852), and i need to get the vanguard design starting again (i dont expect this to happen this week)
17:09:31 <Yawning> if we had profiler output
17:09:36 <dgoulet> quick update on me also, I came back to life officially doing Tor dev. today, so no work for me last week, I did recover from the travelling :). I've been answering bugs this morning and review and code as well
17:09:38 <Yawning> we could kno if that is a big deal or not
17:09:43 <Yawning> but we dont
17:11:29 <asn> (i have some iptables rules that block connections to my primary guards. interesting things happen when you can only connect to non-primary guards.
17:11:45 <asn> not sure how interesting. some pages definitely fail to load on tor browser. trying to understand if it's a guard problem or not.)
17:12:51 <isis> interesting
17:13:02 <nickm> odd
17:13:18 <nickm> there's a bug that's got me concerned, btw: it's the one where moria in't listing some nodes
17:13:45 <nickm> #21107
17:14:06 <nickm> armadev: I am poking you about my open questions on #21107
17:14:32 <nickm> dgoulet: maybe you can investigate which servers it is that moria1 omits?
17:16:14 <nickm> any more folks wih updates?
17:16:17 <nickm> *with
17:16:20 <mikeperry> I am also coming back to life
17:16:23 <nickm> hi mikeperry
17:16:41 <mikeperry> I need to dig my way out of email, and then I'll work on cleaning up the netflow branch
17:16:50 <dgoulet> nickm: yeah I can extract what moria1 is voting for but what I would be looking at?
17:17:10 <nickm> I want to know if there are any versions of tor that it is systematically omitting.
17:17:15 <mikeperry> I'm going to take that easy, thoughm I think, since we're going to defer it to 0.3.1
17:17:21 <nickm> or whether there is any have-an-ed-id or no-ed-id pattern
17:17:23 <dgoulet> nickm: ok sure easy to check
17:17:30 <mikeperry> I might do a bit of other padding stuff in the interim
17:17:40 <nickm> mikeperry: as long as it's early-031, that would be ok
17:18:11 <mikeperry> when will 0.3.1 open?
17:18:29 * isabela is here
17:19:35 <nickm> mikeperry: it used t be on the network team wiki page, but now I can't find it...
17:19:38 <dgoulet> https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTorReleases
17:19:38 <nickm> isis: hi!
17:19:38 <nickm> err
17:19:42 <dgoulet> mikeperry: ^
17:19:51 <dgoulet> Jan 31st is the opening of the merge window in theory :)
17:20:12 <dgoulet> also I updated that page the other day: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRotations
17:20:21 <isabela> dgoulet: thanks
17:20:56 * isabela is back from vacation and is catching up on some follow up with OTF related to our contract that ended last year and plan on sync with nick to organize things for the new one
17:21:20 <isabela> i will also review pending team discussions/organizing stuff for us to catch up
17:23:19 <mikeperry> thanks dgoulet (I'm also done, btw)
17:23:43 <nickm> any other updates today?
17:26:08 <nickm> ok.  Discussion stuff? It would be cool to get us all signed up for rotations.  ANd we have a code-review backlog in whatever our latest review-group is.
17:26:34 <asn> ok wrt rotations
17:26:36 * nickm grabs two weeks of ticket triage
17:26:40 <asn> i will add my name
17:26:56 <nickm> thanks, asn!
17:27:23 <asn> btw nickm it occured to me that if you are interested in setting up a dirauth or relay on the testnet, we can definitely get you started. it's much less responsibility than a real relay/dirauth, and maybe you can use it for testing stuff in the future.
17:27:55 <asn> (also we should get started on the "proposal review" meetings idea. people seem to be interested in them. i will try to do something on that front)
17:29:11 <asn> added my name to this week, and the first week of february
17:29:29 <nickm> appreciated!  I don't think this is the week for me to do that, but it could be clever.
17:29:58 <dgoulet> nickm: 028 aren't voted by moria1 as Running :)
17:30:01 <asn> yep. for the future.
17:30:04 <dgoulet> nickm: nor 029
17:30:27 <dgoulet> nickm: https://share.riseup.net/#stPw1GXC6sYdpZ9H6FJTZA
17:30:59 <nickm> dgoulet: okay, wow.  That sounds like a bad bug.
17:31:25 <dgoulet> could have been in 027 also, this is fishy: Tor 0.2.7.1-alpha: 1
17:31:33 <dgoulet> (but there is probably not many 027 out there)
17:32:28 <nickm> I've added a note to this ticket
17:32:44 <nickm> how will we reduce the review backlog?
17:33:26 <nickm> https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~review-group-14
17:33:58 <dgoulet> hrm some of them could be in merge ready I believe
17:34:02 <nickm> we have 12 with no reviewer there.  17 total
17:34:27 <dgoulet> many of them already have back and forth with reviewer/implementer
17:34:32 <dgoulet> but no Reviewer field
17:34:59 <nickm> I've grabbed a couple more
17:37:27 <nickm> is #20029 raiting for an asn review, or should I be looking at it now?
17:37:58 <dgoulet> oh hrm that one should probably be in merge_ready actually
17:38:05 <asn> i think we can put it on merge_ready eys
17:38:11 <asn> *yes
17:38:12 <nickm> great; thanks!
17:38:34 <asn> i plan to look at #21054 tomorrow. it's likely merge_ready as well.
17:38:45 <asn> (there was update on that ticket)
17:38:51 <nickm> great
17:39:04 <dgoulet> so #18319 and #20996 are in this discussion mode with teor so maybe putting him as the reviewer is wise but I don,t want to do that without his consent :P
17:39:05 <nickm> ok. this is looking much more filled-in to me.
17:40:29 <nickm> I'll try to make progress today and tomorrow on all my reviews
17:43:49 <dgoulet> nickm: there are 1092 relays 0.2.7.* that moria1 sees and 1 is Running so also fishy
17:44:53 <nickm> could you add a note about that to the tickets
17:45:03 <dgoulet> nickm: yes, I'll summarize the findings
17:45:15 <nickm> thanks!
17:45:18 <nickm> any more stuff for today?
17:46:57 <nickm> okay then.  Thanks, all!
17:47:00 <nickm> I'll be lurking...
17:47:02 <nickm> #endmeeting