Reply to thread

Message

<blockquote data-quote="Hacker News" data-source="post: 73916" data-attributes="member: 365">I think AWS and its signature system is making things more complicated than it should be, like this is a normal signing in process to API:1. you request client credentials, which is normal.2. construct request URL, normal.3. add headers, eh, normal.4. signature... fuck.First you need to convert the URL you have from step 2, mash it with headers from step 3, add header keys to signed headers, then sum256 hash the payload and hex encode it.Then you create a sign, add algorithm, request date time that is formatted with ISO8601 but all special characters stripped apart, add credential scopes, hash the canonical request you created at the first step.Then, you calculate this abomination: HMAC(HMAC(HMAC(HMAC(&quot;AWS4&quot; + kSecret,&quot;20150830&quot;),&quot;us-east-1&quot;),&quot;iam&quot;),&quot;aws4_request&quot;)after that you calculate this: signature = HexEncode(HMAC(derived signing key, string to sign))after that you create an authorization header and add signature to it: Authorization: AWS4-HMAC-SHA256 Credential=AKIAIHV6HIXXXXXXX/20201022/us-east-1/execute-api/aws4_request, SignedHeaders=host;user-agent;x-amz-access-token;x-amz-date, Signature=5d672d79c15b13162d9279b0855cfba6789a8edb4c82c400e06b5924aEXAMPLE...I mean what the fuck? I can understand why people choose Azure over AWS for the sake of freaking simplicity just by looking at this sign and request process. It feels overly-complicated. Does anyone feels the same while working with this abomination?<hr />Comments URL: <a href="https://news.ycombinator.com/item?id=33490314" target="_blank">https://news.ycombinator.com/item?id=33490314</a>Points: 14# Comments: 6<a href="https://news.ycombinator.com/item?id=33490314" target="_blank">Continue reading...</a></blockquote>

[QUOTE="Hacker News, post: 73916, member: 365"] I think AWS and its signature system is making things more complicated than it should be, like this is a normal signing in process to API: 1. you request client credentials, which is normal. 2. construct request URL, normal. 3. add headers, eh, normal. 4. signature... fuck. First you need to convert the URL you have from step 2, mash it with headers from step 3, add header keys to signed headers, then sum256 hash the payload and hex encode it. Then you create a sign, add algorithm, request date time that is formatted with ISO8601 but all special characters stripped apart, add credential scopes, hash the canonical request you created at the first step. Then, you calculate this abomination: HMAC(HMAC(HMAC(HMAC("AWS4" + kSecret,"20150830"),"us-east-1"),"iam"),"aws4_request") after that you calculate this: signature = HexEncode(HMAC(derived signing key, string to sign)) after that you create an authorization header and add signature to it: Authorization: AWS4-HMAC-SHA256 Credential=AKIAIHV6HIXXXXXXX/20201022/us-east-1/execute-api/aws4_request, SignedHeaders=host;user-agent;x-amz-access-token;x-amz-date, Signature=5d672d79c15b13162d9279b0855cfba6789a8edb4c82c400e06b5924aEXAMPLE ...I mean what the fuck? I can understand why people choose Azure over AWS for the sake of freaking simplicity just by looking at this sign and request process. It feels overly-complicated. Does anyone feels the same while working with this abomination? [HR][/HR] Comments URL: [URL]https://news.ycombinator.com/item?id=33490314[/URL] Points: 14 # Comments: 6 [url="https://news.ycombinator.com/item?id=33490314"]Continue reading...[/url] [/QUOTE]

Verification