generating aws signature

[joejoe]

Hi,

I am following this php code and am trying to reproduce it with nL.

http://webtutsdepot.com/2009/10/13/amaz ... quest-php/

I cannot figure out if this is a two part transaction or just a single query.

Would anyone know if I need an initial aws server response from the get-url command in order to complete the rest of building the url that will make the request with the aws signature?

Like do I need to say 'knock knock', and use part of their 'whos there' response in order to generate my signature?

Thanks for help!

joejoe

[ralph.ronnquist]

I'm no expert on AWS API, but from reading the PHP, it looks like it's a single handshake, but it relies on a prior agreement between you and Amazon about the thingies called "$publicKey" and "$privateKey". Basically it seems to be a matter of scrambling the original request with the private key, then issue the compound request of that scramble together with the public key, for getting the request to be serviced.

[joejoe]

Ok great, that is what I had hoped, thank you very much Ralph!

[joejoe]

And would I be correct to use this module that Lutz has already created?

http://www.newlisp.org/code/modules/cry ... rypto_hmac

or just use the

http://www.newlisp.org/code/modules/cry ... pto_sha256

Thanks again!

[ralph.ronnquist]

[joejoe]

Got it, thanks Ralph! Much appreciated!! :D

[joejoe]

[ralph.ronnquist]

[joejoe]

[ralph.ronnquist]

Maybe you meant to have (string ...) embeddings for the third argument to crypto:hmac calls?

[joejoe]

[joejoe]

[ralph.ronnquist]

An online tool, using a form, would typically digest line ends as \r\j, whereas a *nix system would prefer using \j only, and a mac system would rather favour \r for line endings. The AWS tool you pointed at some posts earlier appears to compute the signature using \j line endings. And it also scrambles the hmac output by both base64 encoding then url-encoding.

[joejoe]