17:03:12 #startmeeting openstack security group 17:03:12 Meeting started Thu Jan 22 17:03:12 2015 UTC and is due to finish in 60 minutes. The chair is hyakuhei. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:03:13 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:03:13 hi 17:03:15 hello! 17:03:15 The meeting name has been set to 'openstack_security_group' 17:03:24 Yay, topic changed this time too 17:03:30 :) 17:03:35 nice 17:03:42 made it finally :) 17:03:51 wassup ljfisher 17:04:12 ljfisher: yo! 17:04:20 so rollcall I guess, any other lurkers? 17:04:34 o/ 17:04:41 o/ 17:04:43 o/ 17:04:53 o/ 17:04:56 o/ 17:04:57 \o\ 17:05:03 o/ 17:05:04 o/ 17:05:12 o/ 17:05:12 woot! 17:05:32 So I can’t believe how quickly a week has gone by, agenda items? 17:05:39 o/ 17:05:50 bandit update 17:05:56 etherpad link 17:06:05 data processing sec guide update 17:06:12 hey redrobot ! 17:06:22 Ok lets crack on then :) 17:06:25 #topic Bandit 17:06:33 maybe Barbican MKEK spec could be interesting to a few? 17:06:50 ok, so I'm still looking into the requirement checking gate job 17:07:01 tkelsey: +1 17:07:02 it's unclear whether the "python-jobs" gate we already have in place is what they are looking for 17:07:12 most in openstack-infra are away this week 17:07:13 yeah tmcpeak, I noticed that was not behaving :( 17:07:20 hyakuhei heya! 17:07:29 anyway, once that's done we can push to requirements, which I double checked, we will need to use in gates 17:07:32 bknudson might be able to help? He seems to know most things about most things 17:07:47 tkelsey: yeah, I'm not sure if it's good enough for what they want 17:07:55 you will need help from -infra 17:08:02 when they're around they seem to get things done quickly 17:08:15 yep, I reached out to them last week and had some discussion around it, just have a few more things to clear up 17:08:22 I'm going to keep working that this week 17:08:31 yeah infra are cool :) good luck tmcpeak 17:08:41 cool 17:08:45 Is there anything we can do to help or any other areas where Bandit needs work? 17:08:54 we were going to write up that spec 17:09:04 I think sarnold was looking at that 17:09:06 i am working on the spec now 17:09:10 cool 17:09:25 on a side note, I went to OWASP bay area last night 17:09:27 * nkinder arrives late 17:09:28 got a bit sidetracked with some other stuff that came down the pike this week 17:09:45 does owasp still put out a top 10? 17:09:46 chatted with one of the sec guys from Netflix, who also was the one to file the first Bandit bug 17:09:49 cool guy 17:10:10 bknudson: I think so… they also have local chapter meetups which are fun. Good place to drink beer and chat security 17:10:13 here's 2013: https://www.owasp.org/index.php/Top_10_2013-Top_10 17:10:27 it's always the same problems. 17:10:36 shocking really 17:10:44 ok cool, any more on Bandit? 17:10:49 nope, that's it for this week 17:10:52 so I got two additions to the blacklist for yaml.load and urlopen. Got through the whole contrib process. 17:10:53 Sweet 17:10:54 hopefully progress by next week 17:10:57 oh yeah 17:10:59 ljfisher 17:11:01 nice ljfisher 17:11:15 Working on fully qualified names in shape for review. 17:11:20 needs some tests still 17:11:27 ok, I’m pretty sure that my kitchen is on fire. Here’s tkelsey to talk to you about MKEKs :) 17:11:35 #topic Barbican KMIP/MKEK 17:11:45 right lol 17:12:17 so i pushed this spec #link https://review.openstack.org/#/c/148948/ 17:12:54 oh cool, will check it out 17:12:59 it details a proposed system for storing encryption keys in the local Barbican database, and so avoiding any scaling problems from HSM storage restrictions 17:13:10 will look also 17:13:25 awesomem thanks bpb_ tmcpeak :) 17:13:42 Nice work tkelsey 17:13:56 I’m hoping to actually get some code written for that :) 17:14:04 Also turns out you can have smoke without fire... 17:14:17 lol, glad your not on fire hyakuhei :P 17:14:26 +1 17:14:51 #topic Data Processing in Sec Guide 17:14:52 yeah, so hyakuhei and myself will be working through the code for an MKEK plugin once the speck lands :) 17:15:00 elmiko ? 17:15:02 #link https://etherpad.openstack.org/p/sahara-security-guide-notes 17:15:05 cool, thanks 17:15:14 so that pad has the current work i've been putting together 17:15:19 always looking for more input =) 17:15:31 * tkelsey looks 17:15:35 That’s a decent amount of content :) 17:15:35 also we have come across a few questions in terms of the boundaries we have for the chapter 17:15:48 i'm giving it my best =) 17:15:49 Anyone want to take an action to review? 17:16:00 o/ 17:16:10 sicarie: thanks! 17:16:19 I'll review 17:16:25 np - already have been glancing through it :) 17:16:33 tmcpeak: cool 17:16:43 2 big questions are coming up from the sahara team though 17:17:08 1. compliance, how does this affect data processing, also what does compliance mean with respect the project? 17:17:26 Many ways, depends which standard you’re looking at though 17:17:36 2. boundaries, because data processing includes things like hadoop, we are having trouble deciding where to draw the line about suggesting advice 17:17:41 Compliance regs in general are horrible to apply to multi-tenant systems 17:18:00 bdpayne had brought up this question on the pad, maybe i need to ping him directly 17:18:07 2 is potetially easier, though might be something better to white-board at the summit 17:18:19 yea, we are kinda scratching our heads about compliance 17:18:41 i'm hoping to get a version of this chapter in for kilo 17:19:11 it's just difficult to draw the line for how much advice we can give an operator who is installing data processing and wants to secure the hadoop side of things. 17:19:17 ok 17:19:29 elmiko: maybe we can setup a google hangout or something for next week? 17:19:31 elmiko: how should I review this? 17:19:35 Anyone else interested in helping out? 17:19:39 just add comments on the right? 17:19:40 hyakuhei: sounds good 17:19:43 elmiko: can you elaborate on compliance ... against any specific one 17:19:51 tmcpeak: yea, inline comments are welcome 17:19:55 ok cool 17:20:16 shohel02: it was something that bdpayne mentioned on the pad but didn't get further than just mentioning compliance 17:20:18 hyakuhei im interested for next week 17:20:25 shohel02: i think i need to ask him a few more questions 17:20:42 sure. 17:20:45 ok, elmiko can you send a mail to the OSSG list after this meeting and we’ll see if we can find a time that works? 17:20:57 hyakuhei: awesome, will do 17:21:15 Ok, we’ve blasted through the agenda :) 17:21:22 #topic any other business 17:21:23 mid-cycle? 17:21:36 #link https://etherpad.openstack.org/p/ossg-kilo-meetup 17:21:45 Most the info should be there 17:21:51 Everyone got their travel sorted? 17:22:24 just ahve to find a place to stay 17:23:28 sorted 17:23:37 is there still room for attendees? 17:23:45 bknudson: for sure! 17:23:49 you coming? 17:23:58 I'll ask and see if I can get approval. 17:24:14 awesome 17:24:34 might be easier with an agenda posted. 17:24:38 looks like we have a good selection of things we want to work on, but in case anybody else has ideas or hasn't indicated interest yet, please do so 17:24:41 It would be great if you could come 17:25:55 Any more for any more ? 17:26:04 I see someone updated me on the pad. Thanks. 17:26:11 o/ 17:26:37 looking forward to meeting everyone in person :) 17:26:42 (my team included heh) 17:26:51 ukbelch: +1 17:26:52 Sweet 17:28:21 #endmeeting