search

leejo / AWS-S3

Lightweight interface to Amazon S3 (Simple Storage Service)
5 stars 6 forks source link

V4 signatures should be used. #13

Open galenhuntington opened 5 years ago

galenhuntington commented 5 years ago

From the code here https://github.com/leejo/AWS-S3/blob/54a608d1ed3c833300e1ed28f10faf92d1c3af22/lib/AWS/S3/Signer.pm#L165 it looks as though AWS V2 signatures are being used for authentication. Amazon's documentation says that these will not be accepted after June 24, 2019. At that point, this module will cease to function.

leejo commented 5 years ago

Thanks! I'll look into this shortly.

leejo commented 5 years ago

(self note) I'm almost certainly going to delegate this to one of the existing solutions on CPAN:

https://metacpan.org/pod/Signer::AWSv4::S3 https://metacpan.org/pod/Net::Amazon::Signature::V4 https://metacpan.org/pod/Net::Amazon::S3::Signature::V4Implementation

leejo commented 5 years ago

@galenhuntington - I've had absolutely no time to look into this and may not do before the deadline. Any chance you could have a go?

galenhuntington commented 5 years ago

Sorry, I can't take this on right now either. I'm not a good choice anyway, since I've never used this module. I was looking for Perl S3 support, and came upon this, but when I noticed it lacked V4 support I just created this issue and kept looking.

FWIW, the June 24 deadline no longer appears in the AWS documentation, just vague references to planned removal. This is a common pattern with Amazon; they want to deprecate some feature, but doing so would break thousands of customers' working stacks, so they announce and then relent. So there's a good chance V2 signatures will get a long reprieve.

leejo commented 5 years ago

@galenhuntington - thanks. I suspected this would be the case as I read about the planned bucket name changes as well (hostname vs path) being deprecated and then not deprecated. Anyway, I'll try to get to this soon but I'm not too worried about it.