17:01:01 #startmeeting openstack security group 17:01:02 Meeting started Thu Jul 31 17:01:01 2014 UTC and is due to finish in 60 minutes. The chair is hyakuhei. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:01:03 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:01:06 The meeting name has been set to 'openstack_security_group' 17:01:14 Good morning/evening everyone! 17:01:31 hey hey 17:01:33 hi 17:01:35 Yo 17:01:39 :) 17:01:40 howdy 17:01:57 hi... I'm finally getting dug out from being buried with work 17:02:18 hi, all 17:02:19 welcome back to the living bknudson 17:02:30 :) 17:02:42 Ok, lets give people a minute or two longer and then we'll get rolling 17:03:33 sounds good 17:03:38 Righto, what would people like to talk about today ? 17:03:53 maybe status of bug filing for gate test bugs? 17:04:11 Great, what else? 17:04:23 you or nkinder wanted to do some triage for OSSN, right? 17:04:32 I can give some quick book updates 17:04:50 I will give some update on Threat Analysis work 17:04:55 Cool, looks like we might be on for a short meeting :P 17:05:06 nice 17:05:09 Ok well lets dive in. 17:05:17 #topic Bug filing 17:05:20 tmcpeak: go 17:05:26 cool 17:05:39 so, I think we're moving along pretty well on filing bugs 17:05:53 what I was wondering is if we want to tag the ones that we file to indicate they came from gate tests 17:06:01 I mean not gate tests, but the gate test tool 17:06:15 Yes 17:06:27 we should agree some boilerplate, one or two sentances 17:06:43 (This bug was found by the OSSG using X, our beta tool for doing Y etc 17:06:43 I was thinking more along the lines of a tag 17:06:50 Oh i see 17:06:55 is that an appropriate use for a tag? 17:07:03 Not sure that makes sense as in the long term we intend this to be in CI not bugs 17:07:39 I agree with Rob 17:07:40 good point 17:07:49 ok cool 17:08:06 I think thats pretty much all I had to say 17:08:08 Rob +1 17:08:13 is there anybody that wants to take on a bug but doesn't know how to start? 17:08:46 ok cool 17:08:56 So tmcpeak how many bugs are left to file, I know you took a bunch 17:09:10 yeah, I'm actually in a Trove rathole 17:09:24 I started looking at one and found so much stuff that I don't like I think I'll be here for a while 17:09:43 haha good -I think 17:09:48 looks like we have filed about… 7 17:09:55 * bdpayne just remembered one more thing we should talk about ... I'll bring it up at the end 17:09:56 err 9 17:10:03 Ok, maybe I'll see if I can get someone from HP to help, we're a bit thin on the ground atm 17:10:15 sounds good 17:10:19 bdpayne: how exciting :) 17:10:32 yeah, right? 17:10:35 ok bdpayne want to talk about the security guide? 17:10:46 #topic openstack security guide 17:11:11 sure 17:11:23 so we've been chugging along on the bugs filed during the meetup 17:11:41 one key thing worth mentioning is that we have reworked the chapters 17:11:48 before we have something like 55 chapters 17:11:55 Yeah lots of work went into that 17:11:58 now many of those are sections within a larger chapter 17:12:04 the end result is great 17:12:25 big thanks to some guys on the doc team for helping 17:12:29 18 chapters now, looks great 17:12:45 beyond that, I still have it on my todo list to put together a longer term vision on the book 17:12:50 good effort 17:12:54 2 others have expressed interest in helping 17:13:03 so I'll work with them and report back here in a week or two 17:13:16 and that's about all that I have on the book this week :-) 17:13:21 Wonderful 17:13:27 #topic Threat Analysis 17:13:34 shohel02: You're up.... 17:13:36 cool 17:13:53 so we are going through the notes taken in Meetup 17:14:02 some of the action points 17:14:17 one of them was distributing task... 17:14:35 and for that we have created an launchpad ..now anyone can assign themselves 17:14:45 link? 17:14:52 a part of the work 17:14:58 https://launchpad.net/openstack-threat-analysis 17:15:13 #link https://launchpad.net/openstack-threat-analysis 17:15:26 ^ for the minutes ;) 17:15:38 I will send email in the security group so people know the stuff 17:15:49 groovy 17:16:11 shohel02: Great work! 17:16:19 Anything else for today? 17:16:23 nop 17:16:27 some minor editing work 17:16:29 Cool 17:16:31 on the repo 17:16:34 thats it 17:16:39 #topic Summit Talks 17:16:49 Ok kids, time to pimp your talks 17:16:57 how's it done? 17:16:58 what's this summit you guys are talking about? :-) 17:17:10 just provide a link to the talk so we can vote 17:17:16 ha ha...pimping 17:17:16 yes 17:17:20 Just drop a link to your talks in here so people who car can go take a look and decide if it's worth a vote :P 17:17:30 nice to know which ones are coming from the security group 17:17:37 bdpayne: Do you have a talk? 17:17:38 https://www.openstack.org/vote-paris/Presentation/openstack-api-security-testing-automation-in-action 17:17:49 https://www.openstack.org/vote-paris/Presentation/getting-ahead-of-the-game-finding-security-issues-in-openstack-code-at-the-gate 17:17:50 you all want to hear hyakuhei and me talking about makeing sure SSL is everywhere, right? :) https://www.openstack.org/vote-paris/Presentation/ssl-everywhere-with-ephemeral-pki 17:17:51 ^ use #link so it shows up in the minutes 17:17:53 tell your friends! 17:17:54 https://www.openstack.org/vote-paris/Presentation/identifying-security-issues-in-the-cloud-threat-analysis-for-openstack 17:17:57 viraptor: +1 17:17:58 #link https://www.openstack.org/vote-paris/Presentation/getting-ahead-of-the-game-finding-security-issues-in-openstack-code-at-the-gate 17:18:01 #link https://www.openstack.org/vote-paris/Presentation/ssl-everywhere-with-ephemeral-pki 17:18:19 #link https://www.openstack.org/vote-paris/Presentation/identifying-security-issues-in-the-cloud-threat-analysis-for-openstack 17:18:19 #link https://www.openstack.org/vote-paris/Presentation/openstack-public-cloud-the-security-operations-perspective 17:18:39 #link https://www.openstack.org/vote-paris/Presentation/identifying-security-issues-in-the-cloud-threat-analysis-for-openstack 17:18:46 #link https://www.openstack.org/vote-paris/Presentation/trustworthy-geographically-fenced-clouds-tgif-cs 17:18:52 * sicarie_ sneaks in apologizing for being late 17:19:02 #link https://www.openstack.org/vote-paris/Presentation/ossg-delivering-and-improving-on-security-in-openstack 17:19:02 ^^ on this one, it is from IBM Research and I've been chatting with them a bit. Talk sounds interesting. 17:19:11 Oh cool, good job! 17:19:13 Welcome sicarie_ 17:19:14 well, "this one" being the link I provided above 17:19:20 Ok, everyone all done ? 17:19:31 Go take a look and vote if you like peoples :) 17:19:37 hyakuhei: how many do you have, 5? 17:19:47 3 17:19:48 can we create a page to track them? 17:20:16 hyakuhei: nice 17:20:16 #action mixin to create a wiki page to link to the OSSG authored talks at the Paris Sumit 17:20:19 you can use the vote tool to walk through the security talks too 17:20:25 Yeah 17:20:34 might be easier / less appearance of bias ;-) 17:20:39 got it. 17:20:52 So actually, a page listing all the talks by all OSSG members (for all previous summits) might be cool 17:21:01 #topic Any Other Business 17:21:03 =-O#link https://www.openstack.org/vote-paris/Presentation/trusted-bare-metal-what-s-that 17:21:20 So I'd like to talk a bit about Stevedore https://github.com/openstack/stevedore 17:21:32 cool, please do 17:21:32 This came up earlier this week 17:21:47 Bottom line is that several openstack projects are starting to use it (or already do) 17:21:54 And that is is a ripe place for security issues 17:21:59 Not saying it is bad, per se 17:22:08 just that it has the potential for some nasty bugs 17:22:26 keystone has a review in progress for using stevedore 17:22:26 OSSG was asked if we could do a security audit by the Glance PTL 17:22:39 bdpayne: sounds good 17:22:39 I think it is a reasonable request 17:22:48 and I'd like to figure out how we can move ahead on such a thing 17:22:49 how should we chop it up? 17:23:09 not sure if this should fall under threat analysis or if it should be more of a code review or ?? 17:23:11 thoughts? 17:23:11 shohel02: any thoughts ? 17:23:27 probably both 17:23:27 for sure code review 17:23:29 So a 1000ft view would be useful for moving things along I imagine 17:23:31 bdpayne: code review seems the way here 17:23:40 that may be interesting, because it's only an internal library - nothing should pass unsanitized things into it.... code + external usage review? 17:24:05 viraptor malini2 I tend to agree 17:24:06 Doable. viraptor do you have any cycles this week to do a pass througgh 17:24:10 if we are going to do code review, i can work with the people to make the model at the same time 17:24:11 how many lines of codes does it have? 17:24:25 to create threat model 17:24:30 hyakuhei: not really... but later next week should be doable 17:24:36 shohel02: +1 17:25:04 I agree with code review 17:25:33 Yes, Threat Analysis and Code review are good ideas - I'm interested in volunteers.... 17:25:38 readthedocs implies there is some significant code there 17:25:45 I'll take a pass on it 17:25:45 i will also dig in 17:25:48 looks like about 1000 lines of python 17:26:06 mxin: 2.1k in total (comments, empty, ...) 17:26:07 1090, to be exact 17:26:12 cool 17:26:15 That's not too bad. 17:26:31 Ok, so anyone up for mapping the entry/exit points? 17:26:36 I can help too 17:26:59 mxin, will compare notes with you Tuesday? 17:27:09 Great, lets have an update next week 17:27:14 cool, thanks guys 17:27:15 the interface is really nicely defined: see https://github.com/dreamhost/stevedore/blob/master/stevedore/dispatch.py 17:27:22 Cool 17:27:26 malini2: sure. 17:27:27 I encourage everyone working on this to coordinate and work as a team 17:27:48 by using openstack-security irc channel? 17:27:48 congregate in #openstack-security? 17:28:01 makes sense 17:28:13 just want to avoid 5 separate efforts 17:28:15 cool 17:28:17 IRC is ok but not brilliant for timezones, do the best you can :) 17:28:43 Any other business ? 17:29:39 Well I guess we are done then - that's a wrap, thank you everyone! 17:29:44 thanks! 17:29:45 #endmeeting