Hi all, I probably will be able to download the trunk as well... Haven't done it yet, so will need to read into it (might need a few days for that as I am travelling right now).
The central region (e.g. Frankfurt) is only supporting the V4 authentication: https://stackoverflow.com/questions/26533245/the-authorization-mechanism-you-have-provided-is-not-supported-please-use-aws4
I checked the links you send Ed, one solution was to upgrade boto. The python boto package I am using is 2.20.1. Regarding the links, boto then should be able to use V4 authentication. So it could be a misconfiguration, but after reading it, I did not spot anything obvious and will have to fiddle a bit with it later on.
Here the duplicity command generated by duply: TMPDIR='/tmp' PASSPHRASE='<you_wish>' AWS_ACCESS_KEY_ID='<you_wish>' AWS_SECRET_ACCESS_KEY='<you_wish>' duplicity --name 'duply_Christian-ThinkPad' --encrypt-key <key_id> --sign-key <key_id> --verbosity '9' --include-globbing-filelist ~/.duply/Christian-ThinkPad/filelist.txt --s3-use-new-style --s3-european-buckets --full-if-older-than 1M --volsize 50 --exclude-globbing-filelist '/home/christian/.duply/Christian-ThinkPad/exclude' '/' 's3://s3.eu-central-1.amazonaws.com/<some_bucket_name>'
Regards Christian
Am Montag, den 02.02.2015, 07:04 -0600 schrieb Kenneth Loafman:
Looking back at ede's comments and reading some more I think:
@Christian: please upgrade boto to the latest version via: $ sudo pip install --upgrade boto
That should give us the upgraded login since it's boto's job to log in to S3.
[Need more coffee]
...Ken
On Mon, Feb 2, 2015 at 6:33 AM, <address@hidden> wrote:
maybe he doesn't need V4 for now? the links i sent say it might be the result of misconfiguration.
i checked out http://docs.aws.amazon.com/general/latest/gr/sigv4-signed-request-examples.html and yes, "what the heck!" ;).
..ede
On 02.02.2015 13:27, Kenneth Loafman wrote: > Keeping up with S3 is becoming a PITA! > > That said, does anyone know if the new auth protocol can be used as the > default protocol? I just want to check. > > I found a Python code sample to use, so I'm going to target this bug for > 0.7.02. > > @Christian, are you capable of downloading from the trunk to test it prior > to release? That would help. > > > On Mon, Feb 2, 2015 at 5:08 AM, <address@hidden> wrote: > >> On 02.02.2015 12:07, address@hidden wrote: >>> On 01.02.2015 23:35, Christian Saga wrote: >>>> Hi there, >>>> I am getting the error "The authorization mechanism you have provided is >>>> not supported. Please use AWS4-HMAC-SHA256 duplicity" on a duplicity >>>> backup to Amazon S3. >>>> >>>> This seems to be related to the Frankfurt bucket of Amazon S3, as this >>>> only supports V4 of the authorisation. >>>> A bug was opened for this under: >>>> https://bugs.launchpad.net/duplicity/+bug/1407966 >>>> >>>> Is there a perspective on this bug on if/when it will be solved? >>>> I wanted to start a new backup which is quite time consuming. If I know >>>> this takes a while I would do the backup on one of the other EU buckets, >>>> otherwise I would wait. >>>> >>> >>> maybe switching AWS_DEFAULT_REGION helps? >>> https://github.com/aws/aws-cli/issues/1011 >>> >> >> and did you see this? >> >> http://stackoverflow.com/questions/26562763/signed-cloudfront-url-for-a-s3-bucket >> >> ..ede >> >> _______________________________________________ >> Duplicity-talk mailing list >> address@hidden >> https://lists.nongnu.org/mailman/listinfo/duplicity-talk >> > > > > _______________________________________________ > Duplicity-talk mailing list > address@hidden > https://lists.nongnu.org/mailman/listinfo/duplicity-talk >
_______________________________________________ Duplicity-talk mailing list address@hidden https://lists.nongnu.org/mailman/listinfo/duplicity-talk
_______________________________________________
Duplicity-talk mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/duplicity-talk
|