From: Daniel S. <dan...@gm...> - 2011-03-14 20:43:08
|
I was able to get the desired behavior by adding the following to line 1438 in s3cmd (version 1.0.0): os.chmod(filename, 0644) Probably not an ideal patch for everyone but it works for my purposes. It would probably be good to fix the gpg_decrypt function so that the permissions behave in a manner consistent with how s3cmd behaves if gpg_decrypt is not called. Cheers, Dan On Mon, Mar 14, 2011 at 1:46 PM, Jim Popovitch <ji...@gm...> wrote: > On Mon, Mar 14, 2011 at 04:25, Daniel Stevens <dan...@gm...> > wrote: > > It may also be important to note that I'm using gpg encryption/decryption > on the files. > > Bingo. I just tested this and experienced the same. The reason is > due to the decryption occurring in /tmp. The encrypted file is > fetched from S3, decrypted in /tmp (with 0077 mask) and copied to the > destination location. There is probably no easy way around this > without heavily modifying s3cmd to use a private tmp dir. > > -Jim P. > > > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > _______________________________________________ > S3tools-general mailing list > S3t...@li... > https://lists.sourceforge.net/lists/listinfo/s3tools-general > |