Re: [Openstack] [Blueprint automatic-secure-key-generation] Automatic SECURE_KEY generation

2012-06-20 Thread Sascha Peilicke
Hi guys, according from your answers, I believe we're still trying to tackle slightly different issues, so I'd like step back a bit and try to sum up our discussion. Please correct me where I am wrong. I think we all agree that the SECRET_KEY should be protected as much as possible, via sensible

Re: [Openstack] [Blueprint automatic-secure-key-generation] Automatic SECURE_KEY generation

2012-06-20 Thread Gabriel Hurley
...@suse.de] Sent: Wednesday, June 20, 2012 9:05 AM To: Gabriel Hurley; openstack@lists.launchpad.net Cc: Paul McMillan Subject: Re: [Openstack] [Blueprint automatic-secure-key-generation] Automatic SECURE_KEY generation Hi guys, according from your answers, I believe we're still trying

Re: [Openstack] [Blueprint automatic-secure-key-generation] Automatic SECURE_KEY generation

2012-06-19 Thread Sascha Peilicke
On 06/19/2012 04:55 AM, Paul McMillan wrote: Ah, you're thinking of a setup where there are multiple dashboard VMs behind a load-balancer serving requests. Indeed, there the dashboard instances should either share the SECRET_KEY or the load-balancer has to make sure that all requests of a

Re: [Openstack] [Blueprint automatic-secure-key-generation] Automatic SECURE_KEY generation

2012-06-19 Thread Gabriel Hurley
@lists.launchpad.net Subject: Re: [Openstack] [Blueprint automatic-secure-key-generation] Automatic SECURE_KEY generation On 06/19/2012 04:55 AM, Paul McMillan wrote: Ah, you're thinking of a setup where there are multiple dashboard VMs behind a load-balancer serving requests. Indeed

Re: [Openstack] [Blueprint automatic-secure-key-generation] Automatic SECURE_KEY generation

2012-06-18 Thread Sascha Peilicke
On 06/15/2012 11:08 PM, Gabriel Hurley wrote: To the points Sascha raised, and in particular in response to the code method suggested here (https://github.com/saschpe/horizon/commit/1414d538d65d2d3deb981db0ab9e888a3c96a149) I think we are largely in agreement except for one point: I have

Re: [Openstack] [Blueprint automatic-secure-key-generation] Automatic SECURE_KEY generation

2012-06-15 Thread Sascha Peilicke
Hi Grabriel, let's discuss the blueprint [1] on the list. On 06/14/2012 10:36 PM, Gabriel Hurley wrote: Blueprint changed by Gabriel Hurley: Whiteboard set to: After discussing this with both the Horizon core team and Django's security czar/core committer Paul McMillan, we've decided the

Re: [Openstack] [Blueprint automatic-secure-key-generation] Automatic SECURE_KEY generation

2012-06-15 Thread Gabriel Hurley
To the points Sascha raised, and in particular in response to the code method suggested here (https://github.com/saschpe/horizon/commit/1414d538d65d2d3deb981db0ab9e888a3c96a149) I think we are largely in agreement except for one point: I have no problem with this approach for development, or