13:26:49 #startmeeting 13:26:49 Meeting started Wed Sep 3 13:26:49 2014 UTC. The chair is nickm. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:26:49 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:27:17 I'm around, and I see Yawning is too, and asn told me he'd be away. Who else is around for this? 13:27:30 hi meeting 13:27:41 I'm here too 13:28:03 very jetlag dgoulet here also :) 13:28:10 mostly lurking 13:28:10 hi all 13:28:13 hai 13:29:12 So, I've been stomping warnings from analyzer tools, writing patches, and hacking crypto code. 13:29:21 one challenge: how can we know this crypto code is right? 13:29:34 is this the ed25519 stuff? 13:29:39 Yeah, that's the hard bit. 13:30:22 The scrypt/pbkdf stuff and the encrypted-stored-file stuff is easy enough that I'm confident that I can do it 13:30:38 for the ed25519 stuff, I've tested it all the ways I can think of, but still... 13:30:44 i've figured out what causes #12160; haven't finished coding the fix yet, but don't think it's too difficult 13:30:55 athena: excellent. It's a regression in 0.2.4? 13:30:59 yeah 13:31:00 nickm: I assume you tried asking rransom 13:31:01 whoa 13:31:21 Yawning: I'm kinda hoping to get it as polished as I can before I show it to him, because I don't want to try his patience 13:31:39 the 'accessible from outside' bit gets set in onionskin_answer() when the connection is not local and originated elsewhere 13:31:54 nickm: ahh *nods* 13:31:56 but testing whether it's local depends on the address of the remote end 13:32:07 * nickm nods 13:32:20 have you changed much in the branch since I looked over it? 13:32:21 and that was getting cached as a channel mark right in channel_tls_handle_incoming() 13:32:36 Yawning: let me check... 13:33:05 Yawning: I added more tests and documentation 13:33:12 but in the case of a reverse-proxied connection like that, it gets updated based on the canonical address for the authe nticated digest of the remote end later in the handshake 13:33:38 and the channel marks aren't gettig recalculated after that update happens 13:33:44 ahh 13:33:51 ok, that seems straightforward 13:34:23 yeah, easy fix, and my initial suspicion that it was basically a channeltls.c bug was correct - just one that only manifests under rare circumstances 13:35:34 cool. Fix today, you think? 13:35:39 think so 13:35:42 great 13:37:47 Should we get together after this meeting as well to finish triage? 13:38:06 and maybe allocate a dozen tickets or so for early-026 stuff? 13:38:17 sure 13:40:49 great 13:40:54 let's see, what else.... 13:41:04 I have a new online-ness schedule. 13:41:20 It's approximately 8.30 to 4.10 my time, which is UTC-4. 13:42:01 *tries to convert* 13:42:04 *fails* 13:43:23 is that going to be persistent for a while (and what happens when the clocks change) 13:43:25 ? 13:43:47 It's going to be 8.30 through 4.10 M-Thu most days, local time, probably until about this time next year, with some weeks varying. 13:44:02 and on friday it's 8.30 to 12.30. 13:44:05 (local) 13:44:31 so that's 1230 to 2030 UTC M-Thu and 1230 to 1430 UTC on Fri. 13:44:49 When the clocks change (in Nov), it hops by an hour. 13:45:46 it's back an hour so, everything's later right? 13:45:58 yeah 13:46:00 for someone living in a place 2 kewl 4 dst 13:46:25 it seemed like a good idea back when we were mostly farmers using candles and oil 13:47:37 ok. anything else to do at this meeting? 13:48:30 There, that was a quick one. :) 13:48:32 #endmeeting