News for hackers. Stuff that matters.
Re:Achilles Heel of OAuth or Why Facebook Adds #_=_ by homakov on Friday March 15, 2013 @01:42AM (#5379361)
what provider? Facebook never sends it in query string. It can also be available for Man In The Middle, in server side logs etc. Hash is supposed to be more secure.
Re:Achilles Heel of OAuth or Why Facebook Adds #_=_ by johns on Friday March 15, 2013 @02:55AM (#5379489)
FB definitely sends access token via URL param for the server side flow: https://developers.facebook.com/docs/howtos/login/server-sid...

If there were a mitm they could get it even if it's in the hash. It has to travel to the client at some point.

Re:Achilles Heel of OAuth or Why Facebook Adds #_=_ by homakov on Friday March 15, 2013 @03:05AM (#5379509)
if it's in hash it can be seen only from FB response (https). redirect_uri can be http so hash is not transferred

of course it's visible in server-2-server, but not client-server