Hi Daniel,

> Is this an open and properly standardized authentication scheme?

It is open in the sense that it's well documented by AWS and there's a lot
of existing implementations in many languages. It is not standardized, but
it's useful to a wide range of users (all AWS customers). Users usually use
the CLI or SDKs to call AWS APIs, but there's still need to inspect the raw
HTTP responses from API calls.

I think I can free up a few days to work on an implementation for SigV4 in
curl. If you have any guidance regarding contributing to curl, I appreciate
if you can share it with me.

Thanks,
Haitham

On Tue, Dec 12, 2017 at 11:50 PM, Daniel Stenberg <daniel_at_haxx.se> wrote:

> On Tue, 12 Dec 2017, Haitham Gad via curl-users wrote:
>
> I'm wondering if AWS SigV4 authentication is supported by cURL?
>>
>
> It is not.
>
> If not, what's the reason it's not supported? Is it just the lack of
>> manpower?
>>
>
> Nobody has provided code for it nor offered to implement the functionality.
>
> Is this an open and properly standardized authentication scheme? It seems
> to be custom and Amazon proprietary, which if true makes me less interested.
>
> --
>
> / daniel.haxx.se
>

-----------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-users
Etiquette: https://curl.haxx.se/mail/etiquette.html
Received on 2017-12-13