-Original Message-
From: Sean Dague [mailto:s...@dague.net]
Sent: 02 February 2015 16:19
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Product] [all][log] Openstack HTTP error codes
On 02/01/2015 06:20 PM, Morgan Fainberg wrote:
Putting on my sorry
this discussion, here)
-Original Message-
From: Sean Dague [mailto:s...@dague.net]
Sent: Monday, February 02, 2015 8:19 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Product] [all][log] Openstack HTTP error codes
On 02/01/2015 06:20 PM, Morgan Fainberg wrote:
Putting
, 2015 8:19 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Product] [all][log] Openstack HTTP error codes
On 02/01/2015 06:20 PM, Morgan Fainberg wrote:
Putting on my sorry-but-it-is-my-job-to-get-in-your-way hat (aka security),
let's be careful how generous we
On 02/02/2015 12:54 AM, Christopher Yeoh wrote:
On Sun, Feb 1, 2015 at 2:57 AM, Sean Dague s...@dague.net
mailto:s...@dague.net wrote:
On 01/31/2015 05:24 AM, Duncan Thomas wrote:
Hi
This discussion came up at the cinder mid-cycle last week too,
specifically in
On 02/01/2015 06:20 PM, Morgan Fainberg wrote:
Putting on my sorry-but-it-is-my-job-to-get-in-your-way hat (aka security),
let's be careful how generous we are with the user and data we hand back. It
should give enough information to be useful but no more. I don't want to see
us opened to
Putting on my sorry-but-it-is-my-job-to-get-in-your-way hat (aka security),
let's be careful how generous we are with the user and data we hand back. It
should give enough information to be useful but no more. I don't want to see us
opened to weird attack vectors because we're exposing internal
On Sun, Feb 1, 2015 at 2:57 AM, Sean Dague s...@dague.net wrote:
On 01/31/2015 05:24 AM, Duncan Thomas wrote:
Hi
This discussion came up at the cinder mid-cycle last week too,
specifically in the context of 'Can we change the details text in an
existing error, or is that an
On 01/31/2015 05:24 AM, Duncan Thomas wrote:
Hi
This discussion came up at the cinder mid-cycle last week too,
specifically in the context of 'Can we change the details text in an
existing error, or is that an unacceptable API change'.
I have to second security / operational concerns
Sean Dague s...@dague.net writes:
On 01/31/2015 05:24 AM, Duncan Thomas wrote:
What I would rather not see is leakage of information when something
internal to the cloud goes wrong, that the tenant can do nothing
against. We certainly shouldn't be leaking internal implementation
details like
Hi
This discussion came up at the cinder mid-cycle last week too, specifically
in the context of 'Can we change the details text in an existing error, or
is that an unacceptable API change'.
I have to second security / operational concerns about exposing too much
granularity of failure in these
10 matches
Mail list logo
