how best hinder csrf attacks gae app?


so, best proceed hinder an xsrf dispute gae application? suspect following:




  1. anyone user's open object, db.model id used ask figure out vigilant show. antagonistic user id.

  2. malicious user creates possess vigilant checks out mislay form. know mislay an vigilant certain id.

  3. malicious user gets trusting user quarrel mislay ask user's object.



what stairs i supplement hinder #3? note i contend id, i am controlling tangible id biased key. thought i full pivotal value mislay requests, nonetheless hinder antagonistic user being means figure out? distant i know, pivotal multiple denote category type, app id, vigilant instance id, substantially get pivotal id wanted to.



any ideas? jeff wrote , suggested integrate methods - dark form value change any request, cookie value combined around js form. i won't wish bar non-javascript users, cookie fortitude good - dark form value, i have datastore each ask displayed deletable vigilant - an ideal conditions scalable app!



any ideas out there?



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?