ucket only.
Thank you,
Jaseer TK
--
_
The information contained in this communication is intended solely for the
use of the individual or entity to whom it is addressed and others
authorized to receive it. It may contain confidenti
$perm,);
$result = $client->putBucketAcl($args = $arg);
2. I tried creating private buckets as well, using,
s3cmd -c s3cfg_file --acl-private mb s3://Test2
but other users are also able to read/write to the bucket.
Thank you,
Jaseer TK
On Tue, Dec 31, 2013 at 1:20 PM, Ga
=> Array
(
[ID] => test-user
[DisplayName] => Test User
)
[Permission] => READ
)
)
But Still this user is able to delete files from the bucket :(
Am I missing something here ?
utacl.
*--*
*Thank you,*
*Jaseer TK*
On Tue, Jan 7, 2014 at 9:30 PM, Yehuda Sadeh wrote:
> On Tue, Jan 7, 2014 at 2:40 AM, Jaseer Tk wrote:
> >
> > Hi all,
> >
> > I tried to apply custom ACL(only Read) on an s3 bucket created. The rules
> > seems to have g
Moreover, any newly created user is able read/write to existing buckets !!
On Wed, Jan 8, 2014 at 12:46 PM, Jaseer Tk wrote:
>
> Hi Yehuda,
>
> Thanks for response.
>
> my setup is on ubuntu 12.04 servers, ceph pkg's:
>
>
>
>
>
>
>
>
Thanks Yehuda,
But I am seeing only this much in the logs with the log options we set.
I'll try once again and update you.
Do you think any global parameter (like region/zone settings or user's
privileges ) could be causing these buckets to be writable all users ?
Thank you,
Jaseer
. However
this is working with aws s3
Is there a workaround for this, apart from setting
storage-service.disable-live-md5=true in jets3t.properties ?
Dont want to disable md5 checking because it will not ensure
correctness of uploaded data.
Thank you,
Jaseer TK
