17:00:36 #startmeeting security 17:00:38 Meeting started Thu Dec 17 17:00:36 2015 UTC and is due to finish in 60 minutes. The chair is hyakuhei. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:39 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:42 The meeting name has been set to 'security' 17:00:48 hi 17:00:58 hi 17:01:04 #chair elmiko 17:01:04 Current chairs: elmiko hyakuhei 17:01:15 hola 17:01:16 ^ My internet is terrible today so adding elmiko as chair 17:01:24 ack 17:01:38 bknudson: lol, don't you start... ;) 17:01:46 o/ 17:02:28 tmcpeak sends his appologies 17:02:33 hyakuhei: did you have an agenda set up? 17:02:34 tkelsey: you around? 17:02:41 hey yeah 17:02:42 ¿Cómo está todo el mundo? 17:02:54 #link http://eavesdrop.openstack.org/meetings/security/2015/security.2015-12-10-17.00.html agenda 17:02:57 elmiko: ^ 17:03:01 sigmavirus24: shades of #openstack-security 17:03:04 hyakuhei: thanks! 17:03:09 elmiko: only for you 17:03:32 cool so it's time for people to start booking travel etc for the mid-cycle! 17:03:37 #topic midcycpe 17:03:41 sigh... 17:03:52 i'm booked 17:03:55 I haven't gotten formal approval yet, but managers haven't said no either. 17:03:59 I'm booked for the midcycpe too 17:04:08 So yes, book your travel for the midcycpe... you'll see that I've added more detail to the etherpad 17:04:13 i'm in a similar state as bknudson 17:04:20 I'm intending on being there for the Barbican stuff too. 17:04:29 also I'm trying to advertise it so that maybe we can get more from IBM to attend 17:04:36 neat 17:04:57 I'm hoping to get 1 or 2 more to attend at least 17:05:01 #link https://etherpad.openstack.org/p/security-mitaka-midcycle 17:05:05 bknudson: excellent 17:05:14 bknudson: get some of those IBM austiners 17:05:15 actually, more like 2-3... forgot someone 17:06:00 So if everyone who's intending to attend take a look at the topics on the etherpad and add your name by things you care about / want to lead. 17:06:19 You can suggest things even if you don't want to lead them 17:06:53 I invited Major for the meeting 17:07:19 excellent, I was happy to see his name by a few things :D 17:07:23 all rooms have been booked. 17:07:31 We should be good to go. 17:07:33 The Barbican guys have a good list of local hotels etc 17:07:34 cool 17:07:39 #link https://wiki.openstack.org/wiki/Sprints/BarbicanMitakaSprint 17:07:59 I will add my contact info to the page 17:08:17 and direction to the castle and check in procedure. 17:08:28 i went with a-loft. hopefully shuttle is good enough so i don't need to rent a car 17:08:29 We should be ready! 17:09:26 the midcycle agenda has left out Anchor. was that on purpose? 17:09:34 michaelxin: How do refreshments / caffination facilities work at this location, should we arrange to buy something in? 17:09:55 hyakuhei: no worry. 17:10:00 browne: Not particularly, I'll add somethign 17:10:03 We will provide them 17:10:08 * hyakuhei can't seem to type today. 17:10:28 There are free soda, water, coffee in the castle 17:10:40 woot! 17:10:46 food trucks 17:10:49 score 17:10:52 We will provide some refreshments, or better coffee. 17:10:53 wow 17:11:06 michaelxin: You guys should do this more often :P 17:11:07 We will provide breakfast and lunch 17:11:11 and since its a castle, i assume there will be swords 17:11:16 lol 17:11:43 ok any more midcycle-things? 17:12:02 We will have budget for one happy hour dinner. 17:12:10 oooh 17:12:24 Excellent, I'll talk to HPE about getting some budget to either throw in with you or take everyone out another night 17:12:34 hyakuhei: +1 17:12:39 cool 17:12:46 Let me know which would be more appropriate 17:12:46 I need to run 17:12:58 another night will be great 17:13:02 :-) 17:13:11 what do you all think? 17:13:23 yea, definitely another night ;) 17:13:30 +1 17:13:57 sorry, need to take off. 17:13:59 bye 17:14:01 thanks michaelxin 17:14:04 take care michaelxin 17:14:47 ok, next topic 17:15:00 #topic Embargo Privacy 17:15:19 From time to time some of you might be asked to help out with a private OSSA or OSSN 17:15:58 It's important that on these occasions you keep any information in those discussions private 17:16:11 including the title of the issue, the service that might be affected etc. 17:16:17 it would be handy to have a doc to point people to. 17:16:25 bknudson: +1 17:16:39 TBH most of the time it's core-sec so that's 3-4 people 17:16:39 (if there isn't one already) 17:17:15 One issue we had was that when a bug was assigned to the OSSN queue, everyone in OSSP could see it, even if the bug was a private one. That's changed now so that only the core-sec people will have visibility of such things 17:17:25 bknudson: elmiko I'm happy to consider writing up a doc 17:17:39 but other than saying "keep private things private" - I'm not sure what I'd put it in 17:17:42 *in it 17:17:54 hyakuhei: i think it would be useful, but given what you said about the audience maybe it doesn't need to be huge 17:17:55 This is just a general reminder really, it doesn't apply to most of you 17:18:26 elmiko: Righto, I'll put something on the wiki, we should probably document a little more about core-sec anyway 17:18:37 There was some documentation about it in the past 17:18:38 hyakuhei: i don't think it hurt 17:18:43 *it will hurt 17:18:45 * sigmavirus24 shrugs 17:19:09 the common mistake is posting a review to gerrit 17:19:26 bknudson: Yup, developers accidentally disclose this stuff all the time 17:19:34 but we want to be better than them ;) 17:19:39 so maybe include some things to remind people not to do it. 17:20:59 Sure 17:21:18 though private OSSNs generally get written and reviewed in a private GitLab account 17:21:28 ok, that's all I had on this - I don't really want to labor the point 17:21:32 that would be a good suggestion 17:21:47 I haven't seen that done for code patches. 17:22:13 bknudson: So the context is really just writing OSSN/OSSA - A document for how to handle private bugs in general would be the responsibility of the VMT - whom I believe have already done great work in this area 17:23:32 ok, so looking at the standing agenda I can't see anything that's had a lot of movement this week 17:23:48 #topic PR 17:23:51 sicarie: you around? 17:23:55 yep 17:24:09 I heard you gave a good talk involving the security project yesterday or the day before 17:24:14 can you breif us on it ? 17:24:16 Sure 17:24:34 I presented the OSSP deck at the Seattle OpenStack meetup on Tuesday 17:24:42 Overall it was well received 17:24:46 a few good questions 17:24:57 two follow-ups on people who may be interested 17:25:04 (that I know of) 17:25:11 nice one sicarie :) anything we should add into the deck ? 17:25:14 how big was the attendance? 17:25:34 tkelsey: I definitely changed up that deck 17:26:00 The deck is here 17:26:03 #link https://docs.google.com/presentation/d/13GG47EdoQCBEGqMe7ji_UzfO9okMTLgbnK5_UpoaXYA/edit?usp=sharing 17:26:05 could you share out your revised version some place? we should iterate on stuff as we present it 17:26:09 ah :D awesome 17:26:54 elmiko: 20-30? 17:27:08 I’m bad at estimating crowd size 17:27:09 nice 17:27:18 I'm all for iterating on the live deck :) 17:27:24 they had chairs in the front, but poeple were walking around back by the food 17:27:33 probably more the food than listening to me jabber 17:27:56 hehe 17:28:03 hyakuhei: I gave the caveat it would be a living doc, so those in attendance are prepared for it to change 17:28:50 Excellent 17:29:09 I'm sure if you wanted something to distribute you could use the export-as-PDF and then put it in the cloud somewhere :P 17:29:30 Azure or maybe AWS ... just to be safe 17:29:36 lol 17:29:42 real nice... 17:29:48 I was going to take the flyers Rackspace posted, but didn’t end up taking a bag with me 17:29:58 They were good 17:30:00 In hindsight those would have been good to leave by the food 17:30:12 +1 17:30:16 OSSG napkins 17:30:20 hahaha 17:30:34 I guess it's too late for us to try and get some clothing made up 17:30:45 but I'll try to get something lined up for the next summit 17:30:48 well, i’m interested to see how the other ones go 17:32:13 We don't have an nkinder here today. 17:32:15 #topic OSSN 17:32:21 We had a couple of OSSNs issued 17:32:29 \o/ 17:32:50 #link https://wiki.openstack.org/wiki/Security_Notes 17:33:36 62 and 61 are the new ones 17:33:41 That's all I have on OSSN 17:33:56 The queue only has a couple 17:34:05 #link https://bugs.launchpad.net/ossn 17:34:36 It'd be good to have that cleared by the midcycle 17:34:49 and a nice place to be in comparison to the last midcycle ;) 17:35:03 totally 17:35:08 Is there anything interesting going on with Bandit? tkelsey ? 17:35:13 i thought there was some issue with that blacklist one? 17:35:37 there are a few patches in review, we are pushing on with the plan to remove the config file 17:35:50 please take a look if people are interested/have cycles 17:36:14 I have put some words down in the either pad around topics for the midcycle bandit session 17:36:22 please leave feedback there as well :) 17:36:25 tkelsey: will the migration to config-less be an issue for projects currently using bandit? 17:36:26 excellent 17:36:43 elmiko: no it shouldnt be, the old config will still work 17:36:51 got it, thanks 17:36:56 its being deprecated and made optional 17:37:16 cool, that should make it easy =) 17:37:23 yeah :) thats the plan 17:37:41 thats all I have for now 17:38:12 for specifics around the config file stuff, please see the spec 17:38:30 Great 17:38:46 So I'm going to move along to AOB :) 17:38:47 #link https://blueprints.launchpad.net/bandit/+spec/config-change 17:39:12 #topic Any Other Business 17:39:39 no AOB from me, other than to say im looking forward to the midcycle :) 17:40:27 meeting next week? 17:40:41 I think we can give everyone christmas-eve off 17:40:50 So long as they write one OSSN each :) 17:40:56 lol, nice 17:41:26 haha 17:41:31 ok, lets call it there then! 17:41:33 #endmeeting