News for hackers. Stuff that matters.
Re:Secure Your REST API by dllthomas on Wednesday April 17, 2013 @03:24PM (#5566503)
Are you saying the server sees the password in HTTP Digest authentication?
Re:Secure Your REST API by jimktrains2 on Wednesday April 17, 2013 @03:36PM (#5566584)
How else would the server know what to check your response against? If you don't want to give the server a password, try SRP.
Re:Secure Your REST API by tptacek on Wednesday April 17, 2013 @03:48PM (#5566659)
... but please don't use SRP for your API authentication.
Re:Secure Your REST API by dllthomas on Wednesday April 17, 2013 @03:55PM (#5566707)
Well, in this case (having gone back and actually checked the docs rather than relying on recollection roughly a decade old) you could store MD5(username:realm:password) rather than password, though that doesn't buy you all that much in a case like this where making the password a long, random string that's not reused is not only good practice but also easy and so likely to be general practice.
Re:Secure Your REST API by tptacek on Wednesday April 17, 2013 @03:57PM (#5566728)
Stipulating all the other points you've made, exactly what is the purpose of hiding from a server a long random string generated by that server and useful only to that server?
Re:Secure Your REST API by jimktrains2 on Wednesday April 17, 2013 @10:22PM (#5568608)
Preventing someone else from getting that and using it on the server, especially if the service can rack up charges.
Re:Secure Your REST API by dllthomas on Wednesday April 17, 2013 @11:02PM (#5568710)
If you have the hash, you can log into the site (just not using the typical libraries), so it really doesn't add a lot of security. That's why I was wrong :-P
Re:Secure Your REST API by dllthomas on Wednesday April 17, 2013 @04:14PM (#5566864)
Yeah, I got there, just was confused about the digest thing.