Re:Amazon Web Services signature version 1 is insecure
by tptacek on Thursday December 18, 2008 @01:48PM
(#402441)
First, you're talking about a nonce, not a salt. You'd be a happier person if you took the word "salt" out of your CS vocabulary.
Second, the vulnerability here isn't password cracking; it's that AMZN verifies the signature on canonicalized data, but operates on non-canonicalized data.
Re:Amazon Web Services signature version 1 is insecure
by kirse on Thursday December 18, 2008 @02:08PM
(#402471)
Thanks! I understand the Amazon vulnerability fully, I was just referring to my own web-app development.
It's not an issue though because I don't do the key/value pair splitting as they do.
Re:Amazon Web Services signature version 1 is insecure
by tptacek on Thursday December 18, 2008 @02:09PM
(#402473)
Why are you "signing" your data at all? You're doing it wrong. Use SSL to secure the whole transport; use form or HTTP auth to make sure you know who you're talking to.
Re:Amazon Web Services signature version 1 is insecure
by cperciva on Thursday December 18, 2008 @03:32PM
(#402607)
Signing requests with an HMAC provides end-to-end authentication, which is vastly superior to transport-level authentication such as HTTP auth.
Re:Amazon Web Services signature version 1 is insecure
by tptacek on Thursday December 18, 2008 @04:47PM
(#402681)
You skipped the HTTPS part of my recommendation, which is vastly superior to homebrewed HMAC.
Re:Amazon Web Services signature version 1 is insecure
by cperciva on Thursday December 18, 2008 @04:51PM
(#402686)
HTTPS is irrelevant to what I said. End-to-end authentication is better than transport-level authentication. Using an HMAC to sign requests and then sending those signed requests over HTTPS is better than using HTTP auth over HTTPS.
Even if null data is submitted and someone sniffs the salt, it's still 30-chars long and last I checked rainbow tables don't work too well on SHA-256 hashes of that length.
I ask because I use a system similar to this to just do a basic check to ensure that a form POST is coming from a user clicking an action and not just some random spammers' form just posting the needed vars. It's nothing particularly secure (I think), just a nuisance to any spammer.