On 19 Jun 2014, at 14:59, François Stephany <[email protected]> wrote:
> Hello Sven, > > > You might want to have a look at the code in Zinc-AWS (group AWS in > ConfigurationOfZincHTTPComponents), in particular ZnAWSS3Client and > ZnAWSS3RequestSignatureTool - it is using similar request signing but does > HMAC-SHA1. > > Thanks! I wasn't aware of the existence of ZnAWS. > Actually, i'm currently using the HMAC-SHA256 implementation of the CloudFork. Is that an all Smalltalk implementation ? Because it would be really good to have SHA256 in the image. > From a quick glance at the documentation, it seems you have to use Character > lf (\r) else you'll get the wrong result. > > I'm using withUnixLineEndings to ensure the Character lf line ending. You > meant \n instead of \r, right? Yes, of course, sorry. > Have you tried signing the examples (canonical strings) in the documentation > and comparing with their result ? > > The problem is that they don't tell with which key they've signed the string. > It makes it quite hard to decompose the problem and see where something > breaks. How crazy is that ?? (I am trying to be polite here ;-) > The tests in the Ruby SDK are not really useful neither. I'll the other SDKs, > maybe the tests are more revealing. Good luck. > If you really can't make it work, we can discuss further. > > I'll try a bit more and come back if needed! > > Thanks !
