@Jeremy, your summary is accurate. If you guess a container name, you could confirm it exists.
I tend to tag as a vulnerability when I am not sure, and then hope that someone wiser will make a judgement:) If containers are randomly named then its hard to guess their names. If they are not, and their names are easy to guess, then does that count as disclosing 'content'? I guess it depends on whether you consider the name of your container to be sensitive information.
I noticed that https://bugs.launchpad.net/swift/+bug/1489749 was made public, so perhaps there is precedent to make this public. Bug 1489749 allowed potentially greater disclosure of information. So on those grounds I wouldn't object to this bug being made public.
@Jeremy, your summary is accurate. If you guess a container name, you could confirm it exists.
I tend to tag as a vulnerability when I am not sure, and then hope that someone wiser will make a judgement:) If containers are randomly named then its hard to guess their names. If they are not, and their names are easy to guess, then does that count as disclosing 'content'? I guess it depends on whether you consider the name of your container to be sensitive information.
I noticed that https:/ /bugs.launchpad .net/swift/ +bug/1489749 was made public, so perhaps there is precedent to make this public. Bug 1489749 allowed potentially greater disclosure of information. So on those grounds I wouldn't object to this bug being made public.