security - GET vs. POST in Session Validation -


so read this article jeff atwood , wanted make sure understand correctly how applies use case. trying validate session silent login. security purposes should done post right? matter? passing sessionid , username cookie.

when comes csrf (cross-site request forgery), can cause user take action on site logged in provided action requires get. forcing done on post request defeats approach of embedding image, script tag, whatever in page.

even post isn't secure in scenario. there other ways mount csrf attack on site using post. clickjacking/ui-redressing enables site trick user submitting form different website.

basically best way validate add automatically generated, hidden form element. can store inside session data (example: $_session php) need generate token @ start of session. of course, attack try clickjacking (mentioned above) in combination iframe pointing directly site , possibly js hide things little.

for important should re-prompt user password, thereby diminishing value of successful csrf attacks.


Comments

Popular posts from this blog

javascript - RequestAnimationFrame not working when exiting fullscreen switching space on Safari -

Python ctypes access violation with const pointer arguments -