--- On Tue, 2/11/10, Ken Resander <kresan...@yahoo.com> wrote:
From: Ken Resander <kresan...@yahoo.com>
Subject: continued How to use the sign command s3cmd sign STRINGTOSIGN?
To: s3tools-general@lists.sourceforge.net
Date: Tuesday, 2 November, 2010, 6:56 PM
Hi Michal,
Thanks for your super-fast response! I tried the command like this:
$ s3cmd sign $(printf "GET\n\n\nTue, 27 Mar 2007 19:36:42
+0000\n/johnsmith/photos/puppy.jpg")
Signature: UJm2+MfkvdNJFpu71x6T+9+kWuc=
but the signature is different from xXjDGYUmKxnwqr5KXNPGldn5LbA= that I
expected.
I used s3cmd -configure to set accesskey and secretkey to the values used for
the autentication examples in the S3 devguide document. Here is the .s3cfg
contents:
[default]
access_key = 0PN5J17HBGZHT7JJ3X82
acl_public = False
bucket_location = US
cloudfront_host = cloudfront.amazonaws.com
cloudfront_resource = /2008-06-30/distribution
default_mime_type = binary/octet-stream
delete_removed = False
dry_run = False
encoding = UTF-8
encrypt = False
force = False
get_continue = False
gpg_command =
/usr/bin/gpg
gpg_decrypt = %(gpg_command)s -d --verbose --no-use-agent --batch --yes
--passphrase-fd %(passphrase_fd)s -o %(output_file)s %(input_file)s
gpg_encrypt = %(gpg_command)s -c --verbose --no-use-agent --batch --yes
--passphrase-fd %(passphrase_fd)s -o %(output_file)s %(input_file)s
gpg_passphrase =
guess_mime_type = True
host_base = s3.amazonaws.com
host_bucket = %(bucket)s.s3.amazonaws.com
human_readable_sizes = False
list_md5 = False
preserve_attrs = True
progress_meter = True
proxy_host =
proxy_port = 0
recursive = False
recv_chunk = 4096
secret_key = uV3F3YluFJax1cknvbcGwgjvx4QpvB+leU8dUj2o
send_chunk = 4096
simpledb_host = sdb.amazonaws.com
skip_existing = False
urlencoding_mode = normal
use_https = False
verbosity = WARNING
I cannot see what is wrong. Hope you can help.
Regards
Ken
P.S.
I clicked Reply on your response email and got this message
from yahoo:
Your message was not sent
Your account has been temporarily blocked from sending messages. This block can
be caused by sending messages that trigger our spam filters, or by having too
many recipients in one email. We encourage you to review the contents and
recipient list of your message, and try sending it at after an hour or two.
Doing so will usually resolve the matter.
If you are still unable to send messages after a 24-hour period, please read
our FAQ for more information and to request Customer Care assistance.
We apologize for the inconvenience.
Thanks,
The Yahoo! Mail Team
Have been using yahoo.com for more than 10 years and never seen this before, so
I am sending this as a 'fresh' new email instead. Hope it gets through.
------------------------------------------------------------------------------
Nokia and AT&T present the 2010 Calling All Innovators-North America contest
Create new apps & games for the Nokia N8 for consumers in U.S. and Canada
$10 million total in prizes - $4M cash, 500 devices, nearly $6M in marketing
Develop with Nokia Qt SDK, Web Runtime, or Java and Publish to Ovi Store
http://p.sf.net/sfu/nokia-dev2dev
_______________________________________________
S3tools-general mailing list
S3tools-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/s3tools-general
