18:00:18 #startmeeting OpenStack Security Group 18:00:19 Meeting started Thu Jul 18 18:00:18 2013 UTC. The chair is bdpayne. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:00:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 18:00:22 The meeting name has been set to 'openstack_security_group' 18:00:36 good morning / afternoon / evening everyone 18:00:41 hi 18:00:51 who do we have for the security meeting today? 18:01:02 me, first time 18:01:08 Nate - APL 18:01:15 welcome thomasbiege 18:01:39 Joel from APL 18:01:53 APL is here in force :-) 18:02:21 #topic Previous Action Items 18:02:36 Morning all. 18:02:39 So last week we had a few things that people were going to work on 18:02:50 those people aren't here atm 18:03:01 but I did have one 18:03:20 I was supposed to work on taking action on the security issues identified in the book sprint 18:03:29 unfortunately, my report is that I have not yet done that 18:03:34 so I'll push it back to next week 18:03:49 bdpayne: I can do that tomorrow 18:03:52 bdpayne: is there already a list of security issues? 18:04:08 hyakuhei that would be amazing, thanks! 18:04:14 There are some gaps/bugs/wishes that were identified during the booksprint 18:04:26 hyakuhei note that I passed the list off to joel-coffman too, perhaps he could help 18:04:44 ok cool, I'll reach out 18:04:53 thomasbiege this is a list that came out of the recent book sprint effort 18:05:00 some stuff is bugs, and needs bug reports, others need blueprints... 18:05:12 just random things that the book authors wanted to see addressed 18:05:36 hyakuhei: yep, I converted bdpayne's picture of the whiteboard into text earlier today 18:05:48 I've held the list somewhat close b/c there may be embargoed issued on there… once hyakihei flushes that out we can make the rest public 18:06:11 s/hyakihei/hyakuhei/ 18:06:21 bdpayne: ok. if the list is long we could split it of course 18:06:40 not too long, I think hyakuhei and joel-coffman can handle that one 18:06:56 ok 18:06:58 #action joel-coffman and hyakuhei to work on security issues from book sprint 18:07:08 #topic Book Update 18:07:27 The HTML and PDF versions of the book are now available http://docs.openstack.org/sec/ 18:07:39 You can also purchase the book from Lulu 18:07:50 Yeah, teh PDF is looking good. I've printed that off and have a bunch of on-paper edits. 18:07:52 details, links, etc on the page ref'd above 18:07:58 nice 18:08:05 Hi, joining a bit late, sorry 18:08:12 hi! 18:08:16 Do we create bugs for things we're going to change ourselves or can we branch,fix,commit and review? 18:08:17 the security guide is a big step ahead for openstack security 18:08:25 One great area for contributions is to help improve the book 18:08:36 +1 18:08:47 We have a good starting place, but there lots of room for additional content, editing, etc. 18:09:20 The book is in github, and PR's are welcome! https://github.com/openstack/openstack-manuals/tree/master/doc/src/docbkx/openstack-security 18:09:31 any other thoughts / questions on the book? 18:09:35 on my todo list is reviewing the book and applying the mentioned steps to SUSE Cloud as far as possible 18:09:44 excellent 18:10:01 maybe some things will pop up then 18:10:16 sure, makes sense 18:10:28 The language in the etworking section needs some helping along, I'm hoping to find some time for that tomorrow too. 18:10:45 yeah, there's plenty of edits that would be useful 18:11:01 perhaps just submit PR's one chapter at a time 18:11:21 Yeah that makes sense 18:11:35 #topic Reviewing open security issues 18:11:50 How's the volume encryption reviews coming along? 18:11:55 Getting the feedback you guys need? 18:12:25 Specifically asking rellerreller and joel-coffman here 18:12:36 We had the key manager interface approved today. 18:12:45 Sorry, I thought I would let Joel share the good news 18:13:07 ah, nice! 18:13:25 any other pieces that you guys still need eyes on? 18:13:41 Yes, we still have two more commits yet 18:14:04 https://review.openstack.org/#/c/30974/ 18:14:06 Any reviews on those would be helpful 18:14:09 https://review.openstack.org/#/c/30976/ 18:14:18 Looks like those are the places still open 18:14:30 Sorry, my computer thought it was a good time to starting thrashing 18:14:51 np 18:15:02 Thanks for posting the links. 18:15:05 Both of those reviews are still marked work in progress as we finish some plumbing issues between them 18:15:05 anything to add joel-coffman? 18:15:18 oh, that's good to know 18:15:29 however, the vast majority of the code is finished 18:15:42 looks like the reviews are generally positive at this time 18:15:45 which is great, of course 18:16:40 I also wanted to mention https://review.openstack.org/#/c/33532/ 18:16:52 this is related to masking the keystone tokens in the log feeds 18:17:02 for some reason, this has become contriversial 18:17:25 probably worth having some security eyes on it 18:17:39 Why is that controversial? 18:17:51 although, both hyakuhei and myself have already commented 18:18:13 rellerreller see the comment on that review from McCabe at 6:12a 18:18:35 and then my reply ;-) 18:18:55 any other security reviews we should be mindful of right now? 18:19:09 of course, please do track the mailing list for notifications of other security reviews 18:20:01 #topic Open Discussion 18:20:18 What else would people like to discuss today? 18:20:29 is there automatic testing and/or code scanning planned for the code? 18:20:45 there's a lot of automatic testing that happens 18:20:53 security-wise? 18:20:54 are you talking general testing or security specific testing? 18:21:02 security testing 18:21:06 ahh 18:21:09 :) 18:21:21 nothing that I'm aware of, but this would be a great area for us to work on 18:21:30 is that something you could help with? 18:21:41 bdpayne: at the book sprint we identified that there might be some benefit to having some eyes on the live-migration code... 18:21:49 we currently try to use autom. sec. testing of the web-ui 18:22:02 if it will ever be done I will post it here 18:22:07 bdpayne: I might like to add the 'evacuate' feature to that, perhaps out of ignorance -- I'm not sure what it does, and it scares me a bit 18:23:09 only a bit related to openstack is crowbar, which is scanned now by brakeman, http://ci.opensuse.org/view/Crowbar/job/crowbar-pebbles-travis_ci-trackupstream/ 18:23:15 ewindisch_ ok… perhaps hyakuhei and/or joel-coffman can include those items in the other things they are reviewing from the book sprint 18:23:41 also, I looked at the keystone token expiration issue and I've determined it is NOT possible for users to set arbitrary token expirations as I had suspected 18:24:00 thomasbiege I would really love to see more automated security centric testing in place 18:24:27 thomasbiege perhaps as a first step, you could help us document the current state of affairs and some potential goals? 18:24:27 bdpayne: we currently try to hammer a OWASP test-suite into jenkins too... let's see 18:24:53 ewindisch_ good to know Re keystone tokens 18:26:26 thomasbiege would you be willing to help with that? 18:26:28 bdpayne: state of affairs and goals for my company? here in the chat? 18:26:54 sorry, I meant state of affairs for openstack in general with automated security testing 18:27:02 for example, gating on commits and such 18:27:22 bdpayne: Yes I am willing to help you of course. I can write up something. 18:28:04 great, thanks 18:28:26 you are welcome 18:28:27 #action thomasbiege to writeup information on the current state of security testing in openstack and make some suggestions for how we can improve 18:28:41 ok, anything else for today? 18:29:34 ok, thanks everyone… 18:29:38 see you next week! 18:29:43 #endmeeting