Monday, 2015-03-09

*** tmcpeak has quit IRC00:11
*** amrith is now known as _amrith_00:11
*** tmcpeak has joined #openstack-security00:17
*** dave-mccowan has quit IRC02:02
*** Krast has joined #openstack-security02:32
*** tmcpeak has quit IRC02:44
*** browne has joined #openstack-security02:49
*** dave-mccowan has joined #openstack-security03:19
*** dave-mccowan has quit IRC04:07
*** elo2 has joined #openstack-security07:35
*** elo2 has quit IRC07:45
*** elo2 has joined #openstack-security07:57
*** browne has quit IRC08:28
*** tmcpeak has joined #openstack-security10:46
*** hyakuhei has joined #openstack-security10:47
*** hyakuhei_ has joined #openstack-security11:02
*** hyakuhei has quit IRC11:02
*** hyakuhei_ is now known as hyakuhei11:02
*** _amrith_ is now known as amrith11:10
*** markvoelker has joined #openstack-security11:13
*** elo2 has quit IRC11:15
*** hyakuhei has quit IRC11:24
*** hyakuhei has joined #openstack-security11:28
*** markvoelker has quit IRC11:47
*** markvoelker has joined #openstack-security11:48
*** hyakuhei has quit IRC11:49
*** hyakuhei has joined #openstack-security11:49
*** markvoelker has quit IRC11:52
*** hyakuhei has quit IRC12:22
*** hyakuhei has joined #openstack-security12:25
*** amrith is now known as _amrith_12:42
*** hyakuhei has quit IRC12:51
*** hyakuhei has joined #openstack-security13:03
*** bknudson has left #openstack-security13:03
*** bknudson has joined #openstack-security13:24
*** singlethink has joined #openstack-security13:41
openstackgerritDave Belcher proposed stackforge/bandit: Buf fixes in node visitor and sql injection test  https://review.openstack.org/16263613:51
*** _amrith_ is now known as amrith13:52
*** salv-orlando has joined #openstack-security14:05
*** markvoelker has joined #openstack-security14:11
*** markvoelker has quit IRC14:18
*** markvoelker has joined #openstack-security14:19
*** hyakuhei has quit IRC14:19
*** hyakuhei has joined #openstack-security14:21
*** markvoelker has quit IRC14:23
*** voodookid has joined #openstack-security14:23
*** markvoelker has joined #openstack-security14:24
*** rkgudboy has joined #openstack-security14:24
*** voodookid has quit IRC14:28
*** voodookid has joined #openstack-security14:42
*** rkgudboy has quit IRC14:53
*** bpokorny has joined #openstack-security14:56
*** edmondsw has joined #openstack-security15:02
*** dwyde has joined #openstack-security15:04
*** dave-mccowan has joined #openstack-security15:05
*** dave-mccowan has quit IRC15:09
*** dave-mccowan has joined #openstack-security15:09
*** dave-mcc_ has joined #openstack-security15:10
*** dave-mccowan has quit IRC15:13
*** bpokorny_ has joined #openstack-security15:17
*** bpokorny has quit IRC15:20
*** browne has joined #openstack-security15:21
openstackgerritDave Belcher proposed stackforge/bandit: Buf fixes in node visitor and sql injection test  https://review.openstack.org/16263615:29
*** edmondsw has quit IRC15:29
*** markvoelker has quit IRC15:30
*** markvoelker has joined #openstack-security15:31
*** markvoelker has quit IRC15:35
*** edmondsw has joined #openstack-security15:35
*** markvoelker has joined #openstack-security15:38
*** markvoelker has quit IRC15:43
*** markvoelker has joined #openstack-security15:44
*** markvoelker has quit IRC15:49
*** dave-mcc_ has quit IRC15:49
openstackgerritDave Belcher proposed stackforge/bandit: Buf fixes in node visitor and sql injection test  https://review.openstack.org/16263615:54
openstackgerritDave Belcher proposed stackforge/bandit: Buf fixes in node visitor and sql injection test  https://review.openstack.org/16263615:56
*** amrith has left #openstack-security16:00
*** browne has quit IRC16:21
*** salv-orlando has quit IRC16:22
openstackgerritDave Belcher proposed stackforge/bandit: Fixes for node_visitor, sql injection and hardcoded password tests  https://review.openstack.org/16267516:34
openstackgerritDave Belcher proposed stackforge/bandit: Fixes for node_visitor, sql injection and hardcoded password tests  https://review.openstack.org/16267516:40
openstackgerritDave Belcher proposed stackforge/bandit: Fixes for node_visitor, sql and hardcoded password tests  https://review.openstack.org/16267516:41
openstackgerritDave Belcher proposed stackforge/bandit: Fixes for node_visitor, sql and hardcoded password tests  https://review.openstack.org/16267516:46
openstackgerritDave Belcher proposed stackforge/bandit: Fixes for node_visitor, sql and hardcoded password tests  https://review.openstack.org/16267516:48
*** Krast has quit IRC16:55
*** sicarie has joined #openstack-security16:56
*** Krast has joined #openstack-security16:56
*** dwyde has quit IRC16:57
openstackgerritDave Belcher proposed stackforge/bandit: Fixes for node_visitor, sql and hardcoded password tests  https://review.openstack.org/16267516:58
*** pdesai has joined #openstack-security17:00
elmikoi see sicarie and pdesai, are we doing the meeting now or is it affected by DST as well?17:01
sicarieI think bdpayne may have been17:01
pdesainot sure17:02
elmikoit did bring up an item issue though, we should edit https://wiki.openstack.org/wiki/Meetings#Documentation_team_meeting to add out meeting =)17:02
pdesaiany of you have expertise using inkscape?17:02
elmikoi do17:02
*** bdpayne has joined #openstack-security17:03
pdesaiInkscape natively does not support Open Sans fonts, is there any way i can import those fonts ?17:03
*** browne has joined #openstack-security17:03
elmikomine picks up all the fonts i've added to the system17:03
sicarieand bdpayne arrives!17:03
elmikoso, if you add an open sans to the system you should be able to use it in inkscape17:03
bdpaynehey guys17:04
elmikohey17:04
bdpaynesorry I'm a little late :-)17:04
bdpaynewhat did I miss?17:04
elmikono worries17:04
pdesaihey17:04
elmikoi was asking about DST and our meeting time17:04
elmikoalso, we should probably add ourselves to https://wiki.openstack.org/wiki/Meetings#Documentation_team_meeting17:04
elmikoand pdesai had some questions about inkscape17:05
bdpayneoh right... so for DST, I'd vote to adjust the meeting tor DST so that it is still at 10a pacific17:05
bdpaynegive that we are mostly in the US, that is probably the easiest option for everyone17:05
sicarieI just ping'd Doug and he's logging in - was complaining about DST17:06
bdpaynes/give/given/17:06
*** dg_ has joined #openstack-security17:06
dg_hello17:06
sicariewelcome!17:06
bdpayneyeah, figured he'd be the one to object ;-)17:06
elmikobdpayne: make sense for now, but if we grow we should probably adjust to setting out meeting time in UTC, so no DST17:06
bdpayneyeah17:06
sicarie+117:06
bdpaynealso, Re posting the meeting on the wiki... I'd actually advocate for keeping it on the smaller side for the very near term17:07
bdpaynelet us get into a groove a little bit17:07
elmikoi'm ok with that17:07
bdpayneand then we can perhaps switch to a UTC time, posting on the wiki, and perhaps even meeting in a real meeting room17:07
bdpayneso with that, good morning / evening everyone!17:08
elmikoyea, standard time, meeting room, agenda wiki, etc...17:08
dg_sorry Im late, thought this meeting was in an hours time!17:08
*** edmondsw has quit IRC17:08
dg_elmiko minutes...17:08
elmikodg_: no worries, it was a real question =)17:08
bdpayneno worries, we're just gettting started17:08
elmikoexactly...17:08
bdpayneagenda items?17:08
bdpayne1) triage bugs17:09
bdpayne2) planning for L release17:09
bdpaynewhat else?17:09
elmikoi think we covered my question ;)17:09
bdpayneexcellent17:09
bdpaynepdesai you get your questions answered?17:10
sicarieTaking a look at #link https://bugs.launchpad.net/openstack-manuals/+bugs?field.tag=sec-guide17:10
sicarieI think we're good on Triage for this week17:10
bdpayneindeed, we do look good on tirage17:10
bdpaynenice to be caught up :-)17:10
bdpayneok, so let's talk a bit about the L release17:10
pdesaiyup, was struggling with changing fonts using inkscape17:10
bdpayneat the meetup, we decided it would be good to have releases of the book that fall in line with the 6-month openstack release cycle17:11
bdpayneand we decided that doing it for this May would be too fast17:11
bdpayneso we should start with the L release17:11
bdpayneL = Liberty, I believe17:11
bdpayneSo, what do we need to do to get there?17:12
elmikowhen you say "release", are you meaning like a tagged official product?17:12
bdpayneyeah... so the idea would be that the book would be updated to work with the openstack software released with L17:12
bdpayneso if we need to adjust config settings or whatever, we would keep that up to date and in sync17:12
bdpaynestuff like that17:12
elmikogreat idea, +117:12
bdpaynealso, trying to keep up to date with new security features that we should be pointing people at, etc17:13
sicarieSo I still see Computer and Networking as the two largest glaring needs17:13
elmikowe might need to do some outreach to the various project teams to get help17:13
bdpayneright, so let me start recording these ideas17:13
bdpaynea) We need to fill out the core openstack services chapters (e.g., Computing and Networking)17:13
bdpayneb) We need to have a way to reach out to the various teams and/or have them reach back to us to stay informed.17:14
sicarie+1 was just writing something like that17:14
bdpayneOn (b), we should leverage the docimpact field in commits as well... you guys familiar with that?17:14
elmikomaybe, c) review all config examples?17:14
pdesainope17:14
bdpayneagreed on (c)17:15
elmikoas for (b), we might leverage the security liaison list as well17:15
bdpaynefor docimpact, this is a tag that devs can put on their CRs to indicate that the change impacts the documentation17:15
bdpaynesecurity liaison list?17:15
sicarieelmiko: do you have a link to the list?17:15
elmikoyea, sec17:16
pdesai(c) is little tricky and depends on when the config changes are released, may be along with the release17:16
elmikohttps://wiki.openstack.org/wiki/CrossProjectLiaisons#Vulnerability_management17:16
bdpayneah, so that's the VMT17:17
bdpaynethey are a little different17:17
elmikopdesai: yea, i was thinking something along the lines of ensuring that config examples were still valid (e.g. no deprecated values)17:17
bdpaynethey are basically just there for CVE reporting17:17
elmikoah, ok. i thought it might be a starting point for contact17:17
bdpayneon (c), I think we should begin by identifying where in the guide today we have stuff that may be impacted on a per release basis17:17
*** dave-mccowan has joined #openstack-security17:17
bdpaynebuild up a checklist of the things that we'd need to check on every 6 months17:18
elmikothat's a nice first step17:18
pdesaiagree on the first step17:18
bdpaynelonger term, I'd love to see people on the book effort that specialize in certain projects... so we could have one person that does all of Nova and Keystone, another that does Networking, etc.17:19
elmiko+117:19
bdpaynebut there will always be a need for someone to make sure that it is all getting done17:19
bdpayne;-)17:19
sicarie+1 to the specializiation as well17:19
bdpayneok, so I think there are two immediate actions we can take17:20
bdpayneAction 1 -- File tickets for filling out the missing core chapters / pieces... and start writing that stuff.17:20
sicarieThere currently exists tickets for nova, neutron, and one other area Im forgetting off the top of my head17:21
bdpayneAction 2 -- File tickets for identifying what pieces will require updating per release cycles and start identifying that stuff.17:21
bdpaynesicarie, excellent17:21
sicarieLet me stop multitasking and find them :)17:21
bdpayneOn Action 2 -- could we just put comments in the docbook source?17:21
pdesaiAction 2 can be documented in the book itself as an appendix17:21
pdesaiyup17:21
bdpayneI like comments that are easily searchable (perhaps all include a certain keyword)17:22
elmikothat would be nice17:22
bdpaynegrep 'keywork' *.xml17:22
bdpayneor keyword, whatever ;-)17:22
elmikowould be interesting if we could have an appendix that only gets generated for "debug" builds or something17:22
bdpayneAnyone want to take starting one of these action itmes?17:23
bdpayneelmiko, that could be handy17:23
pdesaikeyword could be the release name itself17:23
elmikoi can look into making the index or keywords or w/e17:23
*** salv-orlando has joined #openstack-security17:23
elmikopdesai: good idea17:23
sicariebdpayne: feel free to give me whatever anyone doesn't volunteer for17:23
bdpayneI think keyword should be indpendent of release17:23
bdpaynethe idea being that we need to check all of these places for every release17:24
sicarieit looks like there's no 'over-arching' ticket for the networking chapter, but there are 3-4 smaller tickets on possible gaps17:24
elmikobdpayne: ok, so something along the lines of "dev-update-checklist"?17:24
bdpayneelmiko Ok, let give you Action 2 and sicarie gets Action 117:24
openstackgerritMerged stackforge/bandit: Fixes for node_visitor, sql and hardcoded password tests  https://review.openstack.org/16267517:24
elmikoworks for me17:24
sicarie+117:24
bdpaynepdesai can continue working on her existing massive changes :-)17:25
pdesai:)17:25
sicarieThey're looking really good!17:25
bdpayneanything else to discuss today?17:25
elmikojust to be sure i've got this straight. i will start with a bug, then we can create a patch from there?17:25
bdpayneelmiko yeah, one or more bugs17:25
bdpaynejust a nice way to track the work17:25
elmikoyea17:25
elmikothis almost borders on a blueprint for the doc ;)17:25
bdpayneeh, yeah17:26
bdpaynebut I don't think doc does blueprints17:26
elmikoyea17:26
bdpaynebut specing it out in a bug and getting feedback there first is probably a good plan17:26
elmiko+117:26
pdesai+117:26
bdpayneok, thanks all17:27
elmikothanks!17:27
sicarieCool, thanks!17:27
pdesaithanks !!!17:27
bdpaynethat's a wrap for today then17:27
*** dave-mccowan has quit IRC17:30
*** dave-mccowan has joined #openstack-security17:34
*** salv-orlando has quit IRC17:36
*** hyakuhei has quit IRC17:52
*** dwyde has joined #openstack-security17:54
*** dave-mccowan has quit IRC17:56
*** hyakuhei has joined #openstack-security17:56
*** bpokorny has joined #openstack-security18:03
*** bpokorny_ has quit IRC18:06
*** dave-mccowan has joined #openstack-security18:07
*** hyakuhei has quit IRC18:12
*** dave-mccowan has quit IRC18:15
*** hyakuhei has joined #openstack-security18:38
*** sicarie has left #openstack-security18:38
*** mgagne is now known as mgagne_PHL18:42
*** hyakuhei has quit IRC18:45
*** salv-orlando has joined #openstack-security18:46
*** salv-orlando has quit IRC18:51
*** dave-mccowan has joined #openstack-security18:53
*** dg_ has quit IRC18:54
*** salv-orlando has joined #openstack-security18:55
*** dave-mccowan has quit IRC18:58
*** salv-orlando has quit IRC19:00
*** salv-orlando has joined #openstack-security19:00
*** tkelsey has joined #openstack-security19:30
tmcpeakelmiko: you around?19:33
elmikotmcpeak: hey19:34
*** tkelsey has quit IRC19:50
*** tkelsey has joined #openstack-security19:51
openstackgerritDavid Wyde proposed stackforge/bandit: Add tests for subprocesses and deserialization  https://review.openstack.org/16196719:52
*** hyakuhei has joined #openstack-security20:09
*** hyakuhei has quit IRC20:13
openstackgerritMerged stackforge/anchor: Fixing several issues in Anchor startup  https://review.openstack.org/16130120:16
tmcpeakdwyde: you around?20:18
dwydetmcpeak: am now20:33
tmcpeakcool, so I'm not sure I understand what you're asking on wildcard injection20:34
tmcpeakdespite my response20:34
tmcpeakdwyde: ^20:34
*** bpokorny_ has joined #openstack-security20:34
dwydeso if I have a top-level config named for the plugins20:35
openstackgerritMerged stackforge/anchor: Adding functional testing  https://review.openstack.org/16182120:35
dwydelike subprocess_popen_with_shell_equals_true20:35
dwydethen I can just do @takes_config on that plugin20:35
dwydeand I think that’s what you suggested I do20:35
tmcpeakyeah20:35
dwydebut if i want to share 3 top-level configs with the wildcard_injection plugin, I don’t think that’s possible20:36
*** bpokorny has quit IRC20:37
tmcpeakoh, you're saying the same 3 items used by shell_injection and wildcard_injection?20:37
dwydeyes20:37
tmcpeakyeah, framework isn't set up for sharing config between different plugins20:37
tmcpeakif they really should be shared we can move them into the same plugin20:37
tmcpeakin my mind though wildcard injection and shell injection are separate vulns though20:38
tmcpeakand should be separate plugins20:38
dwydeagreed20:38
tmcpeakand actually, wildcard injection is probably static20:38
tmcpeakI wouldn't even see the use in anybody configuring that plugin20:38
tmcpeakso could just leave them as a list in the plugin itself20:38
tmcpeakfor those that care about wildcard injection they should always check all 4 of those, for those that don't care they should just run a profile that doesn't include it20:39
dwydei’m just confused about how to include all the process-calling functions in the wildcard injection plugin20:40
tmcpeakahh I see20:40
tmcpeakhmmm20:41
tmcpeakgood question20:41
tmcpeakwas going to suggest wildcard injection could become a string check, but the problem is how to detect parameterized wildcard injection vectors20:42
tmcpeakhmmmm20:44
tmcpeakwhat about if you move wildcard injection into shell injection, then it can have access to the full shell injection list20:44
tmcpeakactually this makes sense20:45
tmcpeakwe have a "processes" file, which contains a plugin called something like "called_process"20:45
tmcpeakcalled_process forks out and runs tests for shell injection and wildcard injection20:45
*** dave-mccowan has joined #openstack-security20:45
tmcpeaksince both inherit processes, they have access to the full config of "ways to call processes"20:46
tmcpeakdwyde: ^ does this make sense?20:46
dwydemostly :-)20:47
tmcpeak:( but then we have no good way to disable one or the other20:47
tmcpeakwe lose the granularity of having those as separate plugins20:47
dwyderight20:48
dwydeyou don’t like my solution of just explicitly passing a config section name to each plugin that needs it?20:50
tmcpeakit works?20:50
tmcpeakif so, then yeah.  After this discussion I really like it :)20:50
dwydehaha okay20:50
tmcpeakthanks man20:51
dwydesure, thanks for helping review my changes20:51
tmcpeakyeah, you've done some good stuff20:51
tmcpeakthanks for the work :)20:51
dwyde:-)20:51
*** dave-mccowan has quit IRC20:58
*** tkelsey has quit IRC20:59
openstackgerritMerged stackforge/bandit: Add tests for subprocesses and deserialization  https://review.openstack.org/16196721:09
*** fletcher has joined #openstack-security21:34
*** openstack has joined #openstack-security22:25
*** bknudson has quit IRC22:28
*** dwyde has quit IRC22:33
*** singlethink has quit IRC22:43
*** bpokorny has joined #openstack-security22:47
*** bpokorny_ has quit IRC22:50
*** voodookid has quit IRC23:15
*** openstack has joined #openstack-security23:24
*** pdesai has quit IRC23:26
*** bpokorny_ has joined #openstack-security23:30
*** bpokorny has quit IRC23:33

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!