Tuesday, 2014-11-18

*** kebray has quit IRC00:05
*** david-lyle is now known as david-lyle_afk00:13
*** atiwari has quit IRC00:18
*** kgriffs|afk is now known as kgriffs00:21
*** ryanpetrello has joined #openstack-barbican00:21
*** kgriffs is now known as kgriffs|afk00:30
*** ryanpetrello has quit IRC00:40
*** zz_dimtruck is now known as dimtruck00:46
*** ryanpetrello has joined #openstack-barbican01:19
*** tdink has joined #openstack-barbican01:20
*** woodster_ has quit IRC01:30
*** tdink has quit IRC01:30
*** dave-mccowan_ has joined #openstack-barbican01:33
*** dave-mccowan has quit IRC01:35
*** dave-mccowan_ is now known as dave-mccowan01:35
*** tkelsey has joined #openstack-barbican01:53
*** bdpayne has quit IRC01:55
*** tkelsey has quit IRC01:59
*** ryanpetrello has quit IRC02:14
*** bubbva has quit IRC02:58
*** kgriffs|afk is now known as kgriffs02:59
*** bdpayne has joined #openstack-barbican03:03
*** rm_you| is now known as rm_you03:07
reaperhulkalee: I tentatively like the idea of using CMC03:51
aleereaperhulk, cool - I was just about to amend the cert api spec to propose that.03:53
reaperhulkcool03:55
openstackgerritJohn Wood proposed openstack/barbican-specs: Remove the tenant-secret association table  https://review.openstack.org/13515803:59
*** dave-mccowan has quit IRC04:01
rm_workwait what, why would we remove that04:10
* rm_work reads04:10
*** dimtruck is now known as zz_dimtruck04:37
*** tkelsey has joined #openstack-barbican05:56
*** tkelsey has quit IRC06:01
*** bdpayne has quit IRC06:32
*** miqui has joined #openstack-barbican07:24
miquinewbie question: can i run barbican standalone?07:25
*** miqui has quit IRC08:11
*** codekobe has quit IRC08:26
*** erw has quit IRC08:27
*** codekobe_ has joined #openstack-barbican08:27
*** erw has joined #openstack-barbican08:27
*** jamielennox is now known as jamielennox|away09:43
openstackgerritTim Kelsey proposed openstack/barbican: Adding client certificates to connection credentials.  https://review.openstack.org/13521710:36
openstackgerritTim Kelsey proposed openstack/barbican: Adding client certificates to connection credentials  https://review.openstack.org/13521711:28
openstackgerritOpenStack Proposal Bot proposed openstack/barbican: Updated from global requirements  https://review.openstack.org/13523411:29
openstackgerritOpenStack Proposal Bot proposed openstack/python-barbicanclient: Updated from global requirements  https://review.openstack.org/13524311:36
*** ayoung-dadmode has quit IRC12:42
*** ryanpetrello has joined #openstack-barbican12:44
*** ryanpetrello has quit IRC12:51
*** ryanpetrello has joined #openstack-barbican12:57
*** woodster_ has joined #openstack-barbican13:26
*** dave-mccowan has joined #openstack-barbican14:00
*** alee has quit IRC14:06
*** ayoung has joined #openstack-barbican14:27
*** david-lyle_afk is now known as david-lyle14:43
*** paul_glass has joined #openstack-barbican14:43
*** ametts has joined #openstack-barbican14:51
*** kgriffs is now known as kgriffs|afk14:53
*** rellerreller has joined #openstack-barbican14:58
*** kgriffs|afk is now known as kgriffs14:58
*** nkinder has joined #openstack-barbican14:59
*** openstackgerrit has quit IRC15:04
*** openstackgerrit has joined #openstack-barbican15:04
*** zz_dimtruck is now known as dimtruck15:05
*** alee_ has joined #openstack-barbican15:11
*** akoneru has joined #openstack-barbican15:22
*** woodster_ has quit IRC15:30
*** bdpayne has joined #openstack-barbican15:32
*** rellerreller has quit IRC15:33
*** bdpayne has quit IRC15:44
*** tdink has joined #openstack-barbican15:53
*** tdink has quit IRC15:54
*** jorge_munoz has quit IRC15:56
*** dave-mccowan has quit IRC15:57
*** kgriffs is now known as kgriffs|afk15:58
*** jorge_munoz has joined #openstack-barbican16:00
*** tdink has joined #openstack-barbican16:03
*** SheenaG1 has joined #openstack-barbican16:04
*** rellerreller has joined #openstack-barbican16:05
*** dave-mccowan has joined #openstack-barbican16:08
*** bdpayne has joined #openstack-barbican16:14
*** kebray has joined #openstack-barbican16:20
*** kebray has quit IRC16:21
openstackgerritDouglas Mendizábal proposed openstack/python-barbicanclient: Add Usage documentation  https://review.openstack.org/13534216:25
*** kebray has joined #openstack-barbican16:25
*** kebray has quit IRC16:31
openstackgerritJohn Wood proposed openstack/barbican-specs: Remove the tenant-secret association table  https://review.openstack.org/13515816:37
openstackgerritJohn Wood proposed openstack/barbican-specs: Remove the tenant-secret association table  https://review.openstack.org/13515816:42
*** atiwari has joined #openstack-barbican16:49
rm_workhttps://letsencrypt.org/16:58
rm_workneat16:58
*** SheenaG1 has quit IRC17:00
*** bdpayne has quit IRC17:03
rm_workhttps://github.com/letsencrypt/acme-spec/blob/master/draft-barnes-acme.md17:04
*** SheenaG1 has joined #openstack-barbican17:06
rm_workreaperhulk / redrobot / alee_ ^^ have you seen that?17:07
alee_rm_work, interesting -- I'll give it a read ..17:11
reaperhulkIt's essentially a JSON API that does what CMC does with the addition of challenge protocols for validation.17:11
reaperhulkplus RFC 7030 I suppose as well since it describes the exact client/server interaction17:12
*** kebray has joined #openstack-barbican17:12
reaperhulkI haven't read it closely enough to have an opinion on its quality.17:12
reaperhulkAlthough I do have an opinion on the client python code they released as part of their preview today. It's shit.17:13
reaperhulk(Although some of its problems are because I need to finish the x509 support in pyca/cryptography...)17:13
*** kebray has quit IRC17:17
*** kebray has joined #openstack-barbican17:19
rm_worklol17:20
*** bdpayne has joined #openstack-barbican17:29
*** SheenaG1 has quit IRC17:32
*** SheenaG1 has joined #openstack-barbican17:43
*** tdink has quit IRC17:45
*** kebray has quit IRC17:49
*** SheenaG1 has quit IRC17:55
*** tdink has joined #openstack-barbican17:58
*** paul_glass has quit IRC18:02
*** jamielennox|away is now known as jamielennox18:04
*** jamielennox is now known as jamielennox|away18:04
*** bdpayne_ has joined #openstack-barbican18:05
*** jamielennox|away is now known as jamielennox18:05
*** bdpayne has quit IRC18:06
*** woodster_ has joined #openstack-barbican18:17
openstackgerritMerged openstack/barbican: Updated from global requirements  https://review.openstack.org/13523418:22
*** gyee has joined #openstack-barbican18:22
*** SheenaG1 has joined #openstack-barbican18:24
openstackgerritThomas Dinkjian proposed openstack/barbican: Moved secret functional tests to data driven tests  https://review.openstack.org/13508918:32
*** tdink has quit IRC18:44
*** paul_glass has joined #openstack-barbican18:44
*** liam__ has joined #openstack-barbican19:03
*** liam__ has quit IRC19:05
*** tdink has joined #openstack-barbican19:05
*** tdink has quit IRC19:09
*** SheenaG1 has quit IRC19:26
*** SheenaG1 has joined #openstack-barbican19:28
*** kfox1111 has joined #openstack-barbican19:35
kfox1111Is there a way to restrict access to secrets within a tenant yet?19:36
kfox1111I want to be able to have some vm's in my tenant get access to their own secrets, but seems like I'm giving it too much access to give them access to all vm's secrets within the same tenant. Read only too. The vm shouldn't need to create/delete secrets.19:37
rellerrellerkfox1111 That feature is not currently supported but on the roadmap for Kilo19:46
redrobothi kfox111119:46
redrobotkfox1111 currently we do support read-only, but it would still apply to all secrets within the tenant19:47
*** darrenmoffat has quit IRC19:55
*** darrenmoffat has joined #openstack-barbican19:56
*** ametts has quit IRC19:57
kfox1111We've been running our own keyserver that has a vendor plugin for nova. We tag vm's with metadata saying what tenant-group(s) they can access, the vendor plugin provides a signed token that the keyserver trusts for giving secrets out, and the keys are associated with tenant-groups.19:59
kfox1111with this arangement, its easy to create an auto scaling group or whatever in heat, and it can download just the keys we said it can.20:00
kfox1111Any plan to support this sort of arangement?20:00
redrobotkfox1111 we're using Keystone for Auth, so VMs would need to have a Keystone token to talk to Barbican.  If all VMs share a tenant, then you could store keys under that tenant, and give the VMs read-only access to the keys.  This is currently supported now.20:03
redrobotkfox1111 what rellerreller was talking about was scoping keys so that you provide access to only an individual key.20:03
alee_redrobot, whats the scoop on the midcycle?20:20
redrobotalee_ nothing official yet.  Still poking at people.  It seems the Keystone folks are still debating between bay area or sa.  I don't think we have a preference either way.20:21
alee_redrobot, last I heard -- keystone was saying sa20:22
redrobotalee_ are they commited to SA now?  Last time I spoke to morganfainberg they were leaning SA, but still up in the air.20:23
alee_redrobot, I just hear rumors20:23
redrobotalee_ :)20:23
alee_redrobot, you're more likely to know than me.20:24
alee_redrobot, but its likely we'll meet wherever keystone does?20:24
morganfainbergwe are committing to SA20:24
morganfainbergJanuary 19, 20, 2120:25
alee_redrobot, ^^ there you go.20:25
redrobotmorganfainberg cool.  Do you have space yet?  I can talk to the Geekdom folks, I'm sure they'll be more than happy to host they mid-cycle again20:25
morganfainbergredrobot, working on geekdom20:25
morganfainbergdolphm is handling that part for us20:25
alee_redrobot, so what does mean for barbican? SA?20:25
morganfainbergredrobot, my expectation is i'll do the legwork *before* the summit for next cycle (or help the new PTL whatever)20:26
morganfainbergso it will be decided 100% by summit time.20:26
morganfainbergrather than "oh uh..... lets not make people scramble"20:26
morganfainbergshould be easier for alternate city/venue that way :)20:26
redrobotalee_ possibly, if there's enough interest from our folks in sharing the space with Keystone again.  I know jaosorio for sure would like to attend both.20:27
redrobotmorganfainberg that's a good plan.  I wasn't even thinking about the mid-cycle until you and Rob started asking about it.  Definitely makes sense to plan in advance.20:28
kfox1111redrobot: but until all openstack projects have sane policy stuff, it really hurts to use keystone in that way. As is, I'd have to go find all the policy files for all services, add some roles that are required to do anything, and then make sure the vm's keystone account does not have any of those roles. Then I'd have to add the roles to all of the users I already have to ensure they can continue to use the services they already have access to.20:33
rellerrelleralee woodster_ You should probably review the patch https://review.openstack.org/#/c/127659/. It deals with all of the content type stuff we had discussed.20:34
kfox1111Otherwise, the "vm's" keystone account can lauch/delete vms, heat stacks, delete storage in swift, mess with cinder, etc.20:34
kfox1111without owning the cloud, but with a regular user hat on, I can't put policy stuff in place to do that either.20:35
kfox1111This is why we have continued to use our own keyserver and haven't been able to use barbican yet. :/20:35
alee_rellerreller, looks like we need your content-type spec ..20:37
rellerrelleralee_ I know I need to get that out soon. I wish I did not have to go through prepub, so I could put out a spec tomorrow.20:37
alee_rellerreller, you have to go through prepub on specs too?20:38
rellerrellerEverything must go through prepub.20:39
alee_code CRs?20:39
rellerrelleralee_ yes20:39
alee_rellerreller, wow .. sorry20:40
kfox1111has any thought gone into how to get the other projects to require some role so that barbican can have users that can't do anything but download a secret?20:50
redrobotkfox1111 I'm not sure I understand the question20:51
redrobotkfox1111 policy checks happen on barbican side20:51
redrobotkfox1111 we do have a role that only allows reading a secret20:52
kfox1111keystone gives you a token for a user bound to a tenant... that token can be used to talk to any openstack api...20:52
redrobotkfox1111 keystone gives you a token for user/tenant/roles combination20:52
kfox1111if I have to create a user and bind it to a tenant to allow it to contact barbican to download a secret, it can do other things without some kind of restriction.20:52
redrobotkfox1111 not necessarily.  You have the option of granting a list of roles when you create the user->tenant association.20:53
kfox1111redrobot: sure, in theory. but in practice, which roles do i use?20:54
kfox1111I don't think there is a role today that lets you do that.20:54
kfox1111it requires allocating a role, and editing policy files of all the openstack projects?20:54
redrobotkfox1111 a lot of those decisions are left to the deployer.  Yes, it does require editing policy files if the default ones don't do what you need.20:55
redrobotour reference policy file for example uses "observer" role for read only. https://github.com/openstack/barbican/blob/master/etc/barbican/policy.json20:56
redrobotbut our real deployment will probably have project scoped roles20:56
kfox1111so, unless you are the one deploying the cloud, and the one writing heat templates to allocate the roles to your keystone users, you can't really use barbican in a very secure way. that was my point. If barbican is going to continue to only support keystone auth, how do we extend the roles provided by stock openstack to allow barbican to be used securely out of the box?20:56
kfox1111In keystone, roles are additive, and if I remember trusts correctly, you can drop roles. So flagging a user read only is not a good idea since they can wiggle out of it. So something like a 'barbican-only-ro' role on the account, then marking all the policy files disallowing access to those wouldn't work.20:58
*** SheenaG11 has joined #openstack-barbican20:58
*** alee_ has quit IRC20:58
kfox1111you kind of need a "regular-openstack-user" role for normal accounts, that is on normal users, and if missing, it can still talk to barbican, but nothing else.20:59
*** SheenaG1 has quit IRC20:59
kfox1111but then you have to get every other project to agree to use it in their default policy file. :/20:59
kfox1111am I misunderstanding something?21:02
*** paul_glass has quit IRC21:03
redrobotI'm still not sure I follow your concerns.  I think that someone deploying Barbican will have to make some choices to determine what a "secure" barbican means to them.21:05
redrobotI think that includes figuring out what the correct policy for a their deployment iw.21:06
redrobot*is.21:06
kfox1111but as a user of barbican, I need to ensure its "secure", but am not in control of some of that. right?21:06
kfox1111it should not be different between clouds, or as a user, I have to be very careful the cloud I run on has done the right thing.21:07
kfox1111For example, I create a heat template to deploy my application. I create a keystone user as part of the app, since I need a user to talk to barbican.21:08
*** atiwari has quit IRC21:08
kfox1111I add some roles to it to be able to talk to barbican.21:08
kfox1111I need to know what role names those are, and they need to have the same behaviors on all the clouds I want to launch that heat stack, or else I have to write a custom template per cloud I'm deploying on.21:09
kfox1111by default, I think if there is any role on a tenant, then the user can do all sorts of bad things in most of the openstack api's. so simply tagging a service user as a barbican:observer means that the vm can do those bad things unless the cloud provider was very careful and rewrote their policy files?21:11
redrobotI don't think that's true, although I must admit I haven't read every single policy file for every project.   If you want to create a VM, then Nova policy _should_ check for some Nova role that allows the user to do that.21:15
kfox1111https://github.com/openstack/nova/blob/master/etc/nova/policy.json21:16
redrobotI think that oslo.policy by being flexible as it is, and letting deployers make policy decisions will make it hard/impossible to make a heat template that works for every deployment.21:16
*** stanzi has joined #openstack-barbican21:17
kfox1111redrobot: Yeah, I agree they should have roles for different services to allow the restriction. Today, that does not look to be the case...21:17
kfox1111yeah. Thats why I think the policy files should for the most part be considered code provided by openstack, and out of the box should be flexable enough to allow roles via keystone to manage stuff and policy is only changed very rarely on oddball clouds.21:18
kfox1111nova's policy file above looks similar to most of the other services policies too. Its usually admin or not, not much else. :/21:19
redrobotkfox1111 I think I understand where you're coming from now.  I agree, there definitely seems to be a need to standardize on sane policy defaults across every project.21:19
kfox1111yeah. :/21:20
kfox1111With as big as some of these policy files are too, I'm worried to have to maintain thousands of lines of changes in order to secure mine. then when kilo comes out, I got to double check everything. :/21:21
kfox1111Thats why we bypassed keystone for this one case to allow vm's to download secrets based on what metadata they were tagged with. since only a tenant user can tag metadata onto the vm, the vm can't give itself privilages. its then fairly safe.21:23
kfox1111In some ways, its really all the other projects problem, not barbican's. but it really messes with the barbican workflow. :/21:24
*** stanzi_ has joined #openstack-barbican21:30
*** alee_ has joined #openstack-barbican21:31
*** stanzi has quit IRC21:33
*** SheenaG11 has quit IRC21:36
*** kfox1111 has quit IRC21:52
*** paul_glass has joined #openstack-barbican21:55
akoneruredrobot, ping21:55
redrobotakoneru pong21:55
akoneruredrobot, Hi. wanted to ask you where exactly during startup is the barbican-api.conf loaded using oslo.config?21:57
akoneruredrobot, i looked up at barbican/common/config.py, And even tried to hard code the path to barbican-api.conf as a dewfault config file, but it didn't work.21:58
redrobotakoneru give me a sec, let me look that up22:01
akoneruredrobot, sure.22:03
*** rtom has joined #openstack-barbican22:07
woodster_akoneru, this call is what processes the config file: https://github.com/openstack/barbican/blob/master/barbican/api/app.py#L10822:09
woodster_...this configures it: https://github.com/openstack/barbican/blob/master/barbican/api/app.py#L10822:09
woodster_are you trying to change where the config file is located?22:09
*** SheenaG1 has joined #openstack-barbican22:13
anteayais douglas mendizabal's irc nick d0ugal ?22:15
d0ugalanteaya: nope :)22:16
anteayaany idea what it is?22:16
*** dave-mccowan has quit IRC22:16
d0ugalNo idea who that is :)22:16
anteayaokay thanks22:16
anteayaanyone else?22:17
dstufftanteaya: redrobot22:17
woodster_kfox1111, so alee has posted a CR to add white/black list functionality for secrets, not sure if that helps: https://review.openstack.org/#/c/127353/22:18
anteayadstufft: thank you22:18
akoneruwoodster_, yeah.22:20
*** stanzi_ has quit IRC22:21
akoneruwoodster_, i installed the barbican-api.conf at /etc/barbican from the rpm and would like to pass this path during startup. As of now i am getting CryptoPluginNotFound exception on starting barbican after installing the rpms22:21
*** stanzi has joined #openstack-barbican22:21
akoneruwoodster_, so i think the file is not being read currently in my setup.22:22
*** SheenaG1 has quit IRC22:25
*** paul_glass has quit IRC22:27
*** paul_glass has joined #openstack-barbican22:31
*** stanzi has quit IRC22:35
*** SheenaG1 has joined #openstack-barbican22:38
*** stanzi has joined #openstack-barbican22:40
*** akoneru is now known as akoneru_afk22:53
*** akoneru_afk has quit IRC22:54
*** paul_glass has quit IRC22:57
*** rellerreller has quit IRC23:07
*** nkinder has quit IRC23:08
woodster_akoneru, the oslo.config logic will naturally look into /etc/barbican...you shouldn't have to modify setup.py for example.23:10
*** liam__ has joined #openstack-barbican23:21
*** liam__ has quit IRC23:21
*** stanzi has quit IRC23:24
*** dimtruck is now known as zz_dimtruck23:36
openstackgerritJohn Wood proposed openstack/barbican-specs: Remove the tenant-secret association table  https://review.openstack.org/13515823:45
*** rtom has quit IRC23:46

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