Re: [S3tools-general] s3cmd -e gives "decrypt_message failed: eof"

[Michal L. <mi...@lo...>]

Hi Thomer,

that's a very interesting behaviour. I can't reproduce it though.

You're not running out of space on your disk (or in /tmp) by chance, are
you?

What if you run s3cmd --configure, it should test GPG as well:

==========
~$ s3cmd --configure
[...]
Encryption password [1234567890]:
Path to GPG program [/usr/bin/gpg]:
[...]
New settings:
  [...]
  Encryption password: 1234567890
  Path to GPG program: /usr/bin/gpg

Test access with supplied credentials? [Y/n]
Please wait...
Success. Your access key and secret key worked fine :-)

Now verifying that encryption works...
Success. Encryption and decryption worked fine :-)
==========

Does this run or does it fail as well?

Michal

Thomer M. Gil wrote:
> Hi Michal,
> 
> 
> I've tried debugging this s3cmd problem myself, but I'm not suport
> comfortable with Python (I am intimately familiar with Ruby and Perl,
> though).
> 
> When I run with the Encrypt option and I fetch a file, I get:
> 
> DEBUG: command ['/usr/bin/gpg', '-d', '--verbose', '--no-use-agent', '--batch', '--yes', '--passphrase-fd', '0', '-o', 'abc.txtQ8zGOm79FKAvBX9Hq38U', 'abc.txt']
> INFO: gpg: decrypt_message failed: eof
> DEBUG: gpg exit code: 512
> 
> (And I'm left with the encrypted version of abc.txt and a zero-length
> file abc.txtQ8zGOm79FKAvBX9Hq38U.)
> 
> However, when I run the gpg command on the command line, it works fine.
> In fact, if I copy the relevant code from the function gpg_command to
> a small .py file and run it, it also works.  (Attached is the .py file
> that works for me.)
> 
> Why, then, does it not work with s3cmd?  I have this problem with both
> 0.9.8.1 and 0.9.8.3.  gpg is version 1.4.9.
> 
> Let me know if I can provide more info.
> 
> Thanks.
> 
> Thomer
> 
>