#11 -P (--acl-public) doesn't seem to work for bucket creation

Malfunction
closed-fixed
Michal Ludvig
s3cmd (118)
5
2008-02-11
2007-11-23
Gregory Golberg
No

And I think it's necessary in order to enable reading on particular objects. I have tried to just enable reading on the objects but I got access denied. However, the
following fixed it.

In S3.S3.S3.bucket_create(), I added the following as lines 150 and 151:

if self.config.acl_public:
headers["x-amz-acl"] = "public-read"

And now it's fine.

Discussion

  • Michal Ludvig
    Michal Ludvig
    2008-02-11

    Logged In: YES
    user_id=344740
    Originator: NO

    Fixed in SVN.

    Although uploading public objects to private buckets worked fine for me and I could read them via web browser.

     
  • Michal Ludvig
    Michal Ludvig
    2008-02-11

    • assigned_to: nobody --> ludvigm
    • status: open --> closed-fixed
     
  • Michal Ludvig
    Michal Ludvig
    2008-02-11

    Logged In: YES
    user_id=344740
    Originator: NO

    Apparently the making a Bucket public means that anyone can read its contents, i.e. list the objects contained within. Therefore BEWARE when using -P with bucket creation!

    I have verified that private buckets can have publicly accessible *objects* so there is probably not much need for public *buckets*