15:00:38 #startmeeting security 15:00:38 Meeting started Thu Mar 22 15:00:38 2018 UTC and is due to finish in 60 minutes. The chair is lhinds. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:39 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:43 The meeting name has been set to 'security' 15:00:47 anyone else around (security folks?) 15:00:54 o/ 15:00:55 me 15:01:05 cool! we have some life. 15:01:05 i am here though also have tc office hour starting now 15:01:16 ack fungi 15:01:37 ping me if you need me and i'll catch up 15:02:42 nickthetait: just approved your membership 15:02:55 #topic agenda 15:03:04 #link https://etherpad.openstack.org/p/security-agenda 15:03:28 anything interesting last week gagehugo we need to continue on? 15:03:57 lhinds not really, ttx followed up on some of the spectre/meltdown 15:04:08 ok cool 15:04:28 how about the LCOO, do they have plans to seed some stuff in the SIG? 15:04:54 eeiden o/ 15:05:02 o/ 15:05:36 thanks lhinds 15:06:00 lhinds decided to wait until this week to discuss LCOO 15:06:14 last week was pretty light 15:06:28 gagehugo: ack, eeiden will ping you when the topic is on 15:06:40 perfect 15:06:48 #topic Docs 15:07:21 nothing new here, just a patch to remove `os`, I don't think we need that for spinx / tox stuff, but will double check 15:07:30 #link https://review.openstack.org/#/c/553421/ 15:08:00 #topic Keystone Threat Analysis 15:08:17 probably something that used to be used in there and leftover 15:08:24 re: import os 15:08:44 gagehugo: I think so too. 15:08:49 I added the pycrypto findings into the KSM vmt doc 15:09:03 https://review.openstack.org/#/c/447139/ 15:09:25 thanks gagehugo 15:09:39 lhinds was there anything else that you think should be added to the review findings? 15:09:44 #action look into new central store for TA 15:09:56 gagehugo: nope, that should be it now.. 15:10:09 I just need to look at the above and find a better more easily searched home for them. 15:10:27 and fungi we need to look at bringing the above into VMT's loving care 15:10:39 (keystone-middlewareclient) 15:11:18 ok 15:11:44 cool. next step i suppose is for the keystone team to propose the addition of the vulnerability:managed tag to that deliverable in the governance repo's reference/projects.yaml file? 15:12:05 and make sure to refer to any threat analysis artifacts in the commit message 15:12:10 gagehugo: I guess you would be a good candidate for the above. 15:12:16 sure 15:12:30 lbragstad ^ 15:12:33 I don't mean to keep piling actions onto you bud, but being a keystone core that would work 15:12:42 hey lbragstad 15:12:42 yeah that's fine :) 15:12:58 great, so nice to have that one in the bag 15:13:03 yeah, it's just best when tag additions like that come from the team responsible for the project in question (and get acknowledged by the ptl for it) 15:13:17 raises fewer questions at the tc level 15:13:31 fungi sounds good 15:13:31 What does tc stand for? 15:13:35 technical committee 15:13:38 thx 15:14:10 lbragstad: gagehugo there are some other keystone siblings that were going to be proposed for TA iirc? 15:14:15 #link https://governance.openstack.org/tc/ OpenStack Technical Committee 15:14:45 lhinds yes 15:15:09 pycadf, keystoneauth, oslo.policy 15:15:21 s/policy/cache 15:15:35 o/ 15:16:11 great, I addded those to the pad, so we can look at kicking those off perhaps next meeting or two. 15:16:23 sure 15:16:25 #topic Spectre/Meltdown mitigation 15:16:37 anything else here, ttx ? 15:16:50 I guess he might be busy in the other meeting. 15:17:50 nope 15:17:52 yeah, tc office hours 15:17:53 heh 15:18:18 Don't have much to add to what I said on the topic last week :) 15:18:28 no worries..I think we can skip POlicy Roadmap too, I need to contact some patrole folks and find out where we are 15:18:53 #topic LCOO 15:19:02 eeiden, floor is yours :) 15:19:25 Thanks lhinds! 15:20:36 I'm the current chair for LCOO [stands for Large Contributing OpenStack Operators -- essentially a group of larger companies working to promote and address operator-specific concerns within the community] 15:21:07 which company do you work for eeiden ? 15:21:12 No solid plans from my end at the moment, but was hoping to sync up on priorities so that we can learn about/promote important security initiatives as a working group 15:21:13 AT&T! 15:22:41 eeiden: sounds good. so we moved to a sig in the hope of getting more users involved, so this fits us well. 15:23:05 have you found any topics have come up around sec yet, and what the 'in demand' features are for ops? 15:23:45 things that are making it a challenge to go to production for example (compliance maybe)? 15:24:20 I know policy is a big one 15:25:25 I'm relatively new to the group, so haven't heard much from others. We'll be having a meeting shortly to discuss current priorities, so that's something I'll queue up for discussion. 15:25:48 But ghugo -- definitely policy 15:26:09 please do eeiden , I am happy to join...could you email the sig mailing list and with a date / agenda when set? 15:26:17 Absolutely! 15:26:22 others will likely jump on to then 15:26:32 would love to have you guys there 15:26:55 we will keep LCOO as an agenda item (ongoing), even if nothing new, its a touchstone 15:27:55 ok. lets skip thorugh the other items, as close to the 30 min mark 15:28:17 does not look like ebrown is here, regaring bandit migration to python QA tools 15:28:31 I also don't think Mr Tatu is here. 15:28:36 is bandit being abandoned? 15:28:45 nickthetait: no, far from it. 15:29:02 nickthetait: its going to move to being part of the main python test tools 15:29:08 oh neat :) 15:29:17 so will live alongside tools like pep8 lint etc. 15:29:33 so relocating it's perceived association out of openstack and into the python testing community 15:29:37 er, its 15:30:31 gagehugo: just noticed some new patches from ebrown, we could review those 15:30:50 lhinds one is pretty simple, the other looks like still wip 15:30:53 oh sorry, you already have :) 15:31:11 that yaml typo is on its way in. 15:31:21 so last but not least. 15:31:27 #topic OSSN and OSSA 15:31:43 raises guilty hand, I need to work on clearing the OSSN back log 15:32:06 in the mean time if anyone is interested in writing some security notes, I will support you lots on your first one. 15:32:16 you and your company get a credit in the note. 15:32:30 best to read this if you're interested ... 15:32:51 #link https://openstack-security.github.io/security-notes/2017/09/08/openstack-security-notes.html 15:33:13 check it out nickthetait / eeiden see if its something you would like to get involved in. 15:33:40 fungi: anything big in OSSA that's public and needs some more eyes / views? 15:33:42 oh awesome, will do 15:34:08 sounds like a good fit for me right now. invovles research and documentation right lhinds? 15:34:33 nickthetait: yes, very much. its a very good intro to working in openstack sec. 15:34:39 its how I started out 15:34:44 nice 15:35:04 have a read, and you can email me or ping in irc 15:35:09 the current list is: 15:35:17 https://bugs.launchpad.net/ossn 15:35:32 ok, we are over time. 15:35:37 thanks all 15:35:44 o/ 15:35:56 nice to see some new names, you're very welcome here, please do come back again :) 15:36:01 #endmeeting