Skip Menu |

This queue is for tickets about the Net-Amazon-Signature-V4 CPAN distribution.

Report information
The Basics
Id: 100964
Status: resolved
Priority: 0/
Queue: Net-Amazon-Signature-V4

People
Owner: Nobody in particular
Requestors: steven.hartland [...] multiplay.co.uk
Cc: DBOOK [...] cpan.org
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Patch to fix a few issues in Net-Amazon-Signature-V4
Date: Wed, 17 Dec 2014 12:52:35 +0000
To: bug-Net-Amazon-Signature-V4 [...] rt.cpan.org
From: Steven Hartland <steven.hartland [...] multiplay.co.uk>
While trying to use this modules I came across a few issues so I've created the patch (attached) to fix these. The fixes are: * Remove dependency on perl 5.10 features. * Ensure a date is always present, using X-Amz-Date if present. * Remove spaces between Credential, SignedHeaders and Signature in the header as per spec. * Use \x0a line endings as per spec. Hopefully this can be incorporated in the next version. Regards Steve

Message body is not shown because sender requested not to inline it.

Hi Tim, Any chance of getting this patch merged and released? Or, if you're not using the module any more, giving co-maint to someone who is? The X-Amz-Date issue is causing intermittent errors when using Paws, since it sets the Date and X-Amz-Date headers separately, and Amazon prefers the latter, while this module uses the former to sign (see https://github.com/pplu/aws-sdk-perl/pull/58). Thanks, Ilmari
CC: Gonzalo Barco <gbarcouy [...] gmail.com>
Subject: Re: [rt.cpan.org #100964] Patch to fix a few issues in Net-Amazon-Signature-V4
Date: Fri, 11 Sep 2015 14:57:09 +0200
To: bug-Net-Amazon-Signature-V4 [...] rt.cpan.org
From: Tim Nordenfur <tim [...] gurka.se>
Hi Ilmari, Gonzalo Barco (GBARCO) has taken over development of Net::Amazon::Signature::V4. Cheers, Tim On Fri, Sep 11, 2015 at 2:50 PM, Dagfinn Ilmari Mannsaker via RT < bug-Net-Amazon-Signature-V4@rt.cpan.org> wrote: Show quoted text
> Queue: Net-Amazon-Signature-V4 > Ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=100964 > > > Hi Tim, > > Any chance of getting this patch merged and released? Or, if you're not > using the module any more, giving co-maint to someone who is? > > The X-Amz-Date issue is causing intermittent errors when using Paws, since > it sets the Date and X-Amz-Date headers separately, and Amazon prefers the > latter, while this module uses the former to sign (see > https://github.com/pplu/aws-sdk-perl/pull/58). > > Thanks, > > Ilmari >
RT-Send-CC: tim [...] gurka.se, gbarcouy [...] gmail.com
On 2015-09-11 05:57:40, tim@gurka.se wrote: Show quoted text
> Hi Ilmari, > > Gonzalo Barco (GBARCO) has taken over development of > Net::Amazon::Signature::V4.
Awesome! Is there a git repository available? Please let us know how we can help.
On 2015-09-24 15:42:38, ETHER wrote: Show quoted text
> On 2015-09-11 05:57:40, tim@gurka.se wrote:
> > Hi Ilmari, > > > > Gonzalo Barco (GBARCO) has taken over development of > > Net::Amazon::Signature::V4.
> > Awesome! > > Is there a git repository available? > > Please let us know how we can help.
Hi, over a year has passed. I'd still very much like to send you some patches for this distribution. I hope you are still alive! :)
This patch has been applied in the testing release 0.15_01. Please test if it works for you. https://metacpan.org/release/DBOOK/Net-Amazon-Signature-V4-0.15_01
Subject: Re: [rt.cpan.org #100964] Patch to fix a few issues in Net-Amazon-Signature-V4
Date: Fri, 31 Mar 2017 12:08:12 +0100
To: bug-Net-Amazon-Signature-V4 [...] rt.cpan.org
From: Steven Hartland <steven.hartland [...] multiplay.co.uk>
Thank Dan, I've attached an additional patch we're also using here. This does the following: 1. Ensures the Host header is always present, as its required. 2. Sets the X-Amz-Content-Sha256 when we calculate the payload hash, as certain regions require it. 3. Always sets X-Amz-Date to workaround Amazon implementation not abiding by the spec and requiring X-Amz-Date in some regions. Regards Steve On 31/03/2017 03:27, Dan Book via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=100964 > > > This patch has been applied in the testing release 0.15_01. Please test if it works for you. https://metacpan.org/release/DBOOK/Net-Amazon-Signature-V4-0.15_01

Message body is not shown because sender requested not to inline it.

On Fri Mar 31 07:08:31 2017, steveh wrote: Show quoted text
> Thank Dan, I've attached an additional patch we're also using here. > > This does the following: > 1. Ensures the Host header is always present, as its required. > 2. Sets the X-Amz-Content-Sha256 when we calculate the payload hash, > as > certain regions require it. > 3. Always sets X-Amz-Date to workaround Amazon implementation not > abiding by the spec and requiring X-Amz-Date in some regions. > > Regards > Steve
Thanks. I have applied this additional patch in the testing release 0.15_02. https://metacpan.org/release/DBOOK/Net-Amazon-Signature-V4-0.15_02
Subject: Re: [rt.cpan.org #100964] Patch to fix a few issues in Net-Amazon-Signature-V4
Date: Sat, 1 Apr 2017 19:17:13 +0100
To: bug-Net-Amazon-Signature-V4 [...] rt.cpan.org
From: Steven Hartland <steven.hartland [...] multiplay.co.uk>
On 01/04/2017 18:32, Dan Book via RT wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=100964 > > > On Fri Mar 31 07:08:31 2017, steveh wrote:
>> Thank Dan, I've attached an additional patch we're also using here. >> >> This does the following: >> 1. Ensures the Host header is always present, as its required. >> 2. Sets the X-Amz-Content-Sha256 when we calculate the payload hash, >> as >> certain regions require it. >> 3. Always sets X-Amz-Date to workaround Amazon implementation not >> abiding by the spec and requiring X-Amz-Date in some regions. >> >> Regards >> Steve
> Thanks. I have applied this additional patch in the testing release 0.15_02. https://metacpan.org/release/DBOOK/Net-Amazon-Signature-V4-0.15_02
Thanks Dan, I'll get our internal FreeBSD port updated to that and do some testing when we're back in the office next week.
Applied in 0.16