--- layout: post title: Logs for the Kovri Dev Meeting Held on 2017-05-07 summary: Brief review of what has been completed since last meeting, Monero HackerOne Bounty, 96boards OpenHours showcase, website discussion, and code & open tickets discussion tags: [dev diaries, i2p, crypto] author: dEBRUYNE / fluffypony --- *May 7th, 2017* # Logs **\** 1. Greetings **\** 2. Brief review of what's been completed since the previous meeting **\** 3. More preparation for [96boards.org OpenHours showcase for Kovri / Monero](https://github.com/monero-project/meta/issues/46) (@fluffypony @danrmiller location status) **\** 4. Status (again) of [Monero HackerOne umbrella and bounty](https://github.com/monero-project/meta/issues/39). [hackerone.com/monero](https://hackerone.com/monero) is online but we need to resolve FFS funding before inviting researchers. VRP status for all projects + bounty status **\** 5. Open forum for https://github.com/monero-project/kovri/issues/630 **\** 6. Website status (@rehrar @bigreddmachine @alvinjoelsantos @danrmiller) **\** 7. @EinMByte ...where is he? Github repo privilege discussion **\** 8. Code + ticket discussion / Q & A **\** 9. Any additional meeting items **\** 10. Confirm next meeting date/time **\** Hello **\** hi **\** hey! **\** o/ **\** Here **\** \o **\ {-fluffypony}** hi! **\** Here for a bit, then gone, then back. **\** Yay, enough people for a party. **\** Hello **\** 2. Brief review of what's been completed since the previous meeting **\** 3...2...1... KOVRI!!! **\** hello **\** For me, see http://forum.getmonero.org/9/work-in-progress/86967/anonimal-s-kovri-full-time-development-funding-thread?page=&noscroll=1#post-90900 **\** moroccanmalinois can fill us in on his work. **\** i've been playing with fuzz testing **\ {-fluffypony}** nice **\** I've looked through the PR's, looks like fun. **\** it's the beginning. More tests to come **\** Any questions/comments on point 2? **\ {-fluffypony}** and guzzi ? **\** guzzi is not here, ...again... **\** He says he's doing work but I haven't seen a commit or question from him in over 7 weeks, AFAICT. **\** I think he's trying to separate the contexts from the singleton. At least that's the end goal. **\ {-fluffypony}** guzzi: when you read this, please make an effort to attend meetings **\ {-fluffypony}** I know you're around at other times, but meetings are important **\** Yes, please. **\** Ok, anything else on 2.? **\ {-fluffypony}** no **\** 3. More preparation for [96boards.org OpenHours showcase for Kovri / Monero](https://github.com/monero-project/meta/issues/46) (@fluffypony @danrmiller location status) **\** Is pigeons still in Africa? This point was moved from last meeting. **\ {-pigeons}** i returned yesterday **\** Are you suggesting pigeons migrate ? **\ {-pigeons}** i saw rock doves **\** fluffypony? How's it going? **\ {-fluffypony}** anonimal: it's a podcast, right? **\** https://www.96boards.org/openhours/, there are videos too. **\ {-fluffypony}** ok well I'm ready whenever **\ {-fluffypony}** I don't really prepare for stuff like this **\** sorry i'm late! **\** Ok well what time/date works for you? **\** fluffypony ^ **\ {-fluffypony}** anonimal: my PA would have to schedule it - probably best to get my PA to schedule myself and pigeons and them **\ {-fluffypony}** she's good at that **\ {-fluffypony}** it's literally her job :-P **\ {-pigeons}** I was thinking ask hyc if he's interested, he's been playing with arm and monero i think **\ {-fluffypony}** cool **\ {-fluffypony}** hyc is a beautiful man **\** +1 Ric's PA. She was great when i wanted to schedule a podcast **\* anonimal** pinged him in #monero-dev **\** Ok well at this point, IMHO, fluffypony I think it would be good for you to touch base / introduce yourself to sdrobertw in #OpenHours on freenode. **\** I think I can only play the middleman for so long. **\ {-fluffypony}** email is better for Shay, I don't think I can teach her IRC :-P **\** Contact info? I have none. **\ {-fluffypony}** for them? **\ {-fluffypony}** didn't we reach out to them via email first? **\ {-fluffypony}** \* can't remember **\** For Shay **\** No, not via email, all IRC. **\ {-fluffypony}** oh lol **\ {-fluffypony}** pa@spagni.net **\** Alright, anything else on this point before moving on? **\** 4. Status (again) of [Monero HackerOne umbrella and bounty](https://github.com/monero-project/meta/issues/39). [hackerone.com/monero](https://hackerone.com/monero) is online but we need to resolve FFS funding before inviting researchers. VRP status for all projects + bounty status **\** I've sent a VRP to monero, it's been merged. I believe we're funded at ~500 XMR, which is great. **\** Any questions? **\** We just need to launch after submitting VRP to the GUI (and site?) **\** Sound good? **\** Is the bounty held in xmr or something else? **\** Yes. Link to FFS in the meta issue. **\** https://forum.getmonero.org/8/funding-required/87597/monero-bounty-for-hackerone It was funded to 500 XMR and then increased to 1000 XMR for further funding **\** ty **\** I think we can start now before funding is at 1000. **\** (it won't mean we'll find researchers immediately anyway) **\** Any questions/comments before moving onto next point? **\ {-fluffypony}** yrah **\ {-fluffypony}** agreed **\ {-fluffypony}** we can continue to increase it as necessary **\** Ok. Moving on, **\** 5. Open forum for https://github.com/monero-project/kovri/issues/630 **\** Comments needed before we move on this. **\ {-fluffypony}** I agree with MoroccanMalinois, but I think it's manageable if we set a severity **\ {-fluffypony}** and some caveats **\** Maybe a strict validity domain definition would do good (ie, "we only accept vulns in the following categories"). **\** And then expand the list as stuff matures. **\** moneromooo - why would we restrict? **\** To prevent known problems from being reported, or problems in stuff that is known to be unfinished. **\ {-pigeons}** because the code has a bunch of legacy mess and is early state with low hanging fruit that is just later on the to fix when that section gets refactored **\** Yes. So, with that said, I don't know what categories we could even have. **\** *at this stage* **\** moneromooo: did you have any ideas on categories for this stage? **\** No. I've not really looked at kovri yet, despite saying I would (sorry). **\ {-pigeons}** i2p consensus related issues **\ {-pigeons}** if we implement like X we might cause incompatibility **\ {-pigeons}** maybe those but again maybe those are known and will be fixed when those sections are given love **\** Anything which can leak keymat. Good starting point. **\** Ideally you'd start giving bounties when you know you've done what you could, and the bounty to find bugs is less than what your time is worth looking at it :) **\** pigeons: Well, then I think that's java I2P's problem because they would then have to keep up with us. What we could do now though is start with a research-related category for general specifications? **\** So it's a bit subjective. **\** moneromooo: indeed, and this is border-lining on simply hiring a new dev too with the funds available. **\** Well, the draw is that the bounty ensures results for the money. **\** So expert time. **\** What if we opened bounty for non-implementation research? I know this is an MRL area though. **\** Or we could open more categories for implementation but the payout is smaller because code is Alpha? **\** For finding bugs in the theory, definitely worth doing so (for monero anyway, I expect kovri's following established research already). **\** (then they would risk waiting to beta to 0day to get bigger payout?) **\** what up kids? I'm here. **\** I think monero's research is more vetted than I2P's, even though I2P has been around longer. Simply because there are less moving parts. **\** +1 for bounty for non-implementation research **\** Interesting. **\** Just my opinion. I've read the I2P papers available, I'm not blown away but it's better than nothing. **\** And not like I'm in a position to drop everything to do purely research so... **\** We'll add categories for bounty? One obvious one being research. Maybe crypto implementation sooner than later since that's a big one. **\** Sound fair? **\** From a relative outsider, it seems like a sensible start. **\** yes. is "leaked info" too broad of a category? **\** yes for me **\** Yes because a leak would cover too much code that hasn't been vetted. **\** \* could cover **\** Ok, I'll get that going then. **\** Moving on. 6. Website status (@rehrar @bigreddmachine @alvinjoelsantos @danrmiller) **\ {-pigeons}** I need to talk with fluffypony about a potential dns thing **\** aight, so just in case somebody hasn't seen the Kovri web design here it is: http://imgur.com/a/An8K8 **\** it's the top one **\ {-pigeons}** then the demo of ajs' site should be up **\ {-fluffypony}** I got msgs about it **\ {-fluffypony}** will look at it tomorrow **\** it's based on the same framework as the getmonero.org website, so once the custom framework is made for one, it is easy to make pages for the other **\** my update is that we're making the framework even now, and it's coming along well, I should be able to make a few experimental Kovri pages soon **\** The question is content. **\** I think the "It's I2P, but in C++" phrase should go; we should use our standard "A secure, private, untraceable C++ implementation of the [I2P anonymous network](https://getmonero.org/knowledge-base/moneropedia/i2p)" **\** I will work with rehrar to write up some content, but need direction on what should be included. **\** that's fine. Copy is not indicative. :) **\** My past month has been packed getting ready for my phd comprehensive exam (1 step before the defense). So I haven't looked at the site yet, but talked briefly with ajs about it and plan to get more involved now that that's done. **\** Other than that, can we move this item to the website meeting in #monero in 10 minutes? **\** sure, that sounds alright. **\** It looks nice (says the cow who's got no clue about design). **\** K **\** bigreddmachine ajs: will you be around in 10 minutes in #monero? **\** Yes **\** yeah, i'm also editing tonight's podcast episode so i may take a minute to reply **\** rehrar: yes, what moneromooo said, looks nice **\** cool. If people have ideas for content that are not on the demo site **\** Ok, moving on. 7. @EinMByte ...where is he? Github repo privilege discussion **\** let me know **\** I'd like to have a simple website for alpha release :) **\** fluffypony: so... his last commit was from Septemeber 19th, he's not responded to 99% of my pings since then... **\** i haven't seen him since i started getting involved in Jan **\** I speak highly of him and his work, I think he's a great contributor and wish he was around more. **\** could be a legal issue? **\** The problem is he's not around anymore, he has assigned issues of which I've had to assign myself since he's not around to do them. **\** And he has repository push access. If something happened to him and his account is compromised, we could be left in an embarrassing trolling situation where someone deletes the repo. **\** I don't want to send any wrong signals but I also think access privileges should be on an as-needed basis. **\** i think that's fair. can always be re-established if he comes back and he can be verified **\** in that vein, should things like Salti tracking be moved to another place? **\** I don't know, we'll have to bring that up at the next meeting I think since we're running out of time. **\** fluffypony: any thoughts about this? Will you remove EinMByte's github push access privileges? **\** I think it's fair to revoke for inactivity and failure to reply to pings. Reinstate when back. **\** okay, can we add #619 to next meeting's agenda? **\** I'd also want to remove warptangent's key (unlikely to be back to use it) and a few others. **\** bigreddmachine: oh, sure I guess, more research/info needed. **\** k i'll just reply to the issue and talk about it there for now. sorry to jump into other discussion about that. **\** No problem **\** Since we're running out of time, 8. Code + ticket discussion / Q & A **\** last update from me — mozilla work continues with the proxy stuff, but not ready yet. i don't have a good feel for how long **\** Anything pressing? Questions/comments that can't be answered on github or after the meeting? **\** Ok, thanks bigreddmachine **\** not from me, I'll be in contact :( **\** :) **\** 9. Any additional meeting items **\** none. thanks anonimal! **\** Nothing from me, other than I need to AFK rehrar so, bigreddmachine ajs pigeons if you want to talk more about kovri-site then I'll have to read backlog **\** aight, thanks. **\** Now over to monero! **\** K **\** Thank you all if you keep the torch burning for the site, awesome. **\** 10. Confirm next meeting date/time **\** 2 weeks, same time? **\** indeed **\** Ok. Thanks everyone :)