Skip to content
This repository has been archived by the owner on May 7, 2022. It is now read-only.

Implement CSRF #57

Open
ericecook opened this issue Jul 3, 2013 · 6 comments
Open

Implement CSRF #57

ericecook opened this issue Jul 3, 2013 · 6 comments
Milestone

Comments

@ericecook
Copy link
Collaborator

No description provided.

@icook
Copy link
Owner

icook commented Jul 3, 2013

Just as a side note we probably want to figure out how to handle Django csrf since it's by default enabled. I had to disable it in the Django example to make it work. Although perhaps it would be good to split that task off into another issue.

@icook
Copy link
Owner

icook commented Jul 19, 2013

This has been pushed back since it requires a server-side persistense layer, or session connectivity. A cross-framework compatibility layer will need to be written to facilitate this, so it will likely come with the release of 0.3.

@prologic
Copy link

prologic commented Sep 6, 2013

To be honest. I think this should NOT be yota's responsibility.
Otherwise it becomes very hard to remain framework agnostic.

@ericecook
Copy link
Collaborator Author

Agreed. What Isaac and I have discussed is a separate library (currently calling it pysistor) to handle framework agnostic persistence. Persistence is actually extremely useful to a form library, notably for things like csrf and captchas. Getting that allows for setting up captchas very rapidly, something which currently is a pretty big pain for most form libraries.

Pysistor itself is designed to be framework and backend agnostic, and is basically done, mostly just ironing out implementation details. Isaac can tell you more about it if you want, I don't think its on github yet.

@icook
Copy link
Owner

icook commented Sep 6, 2013

It actually is on github, it's just really green. I have a big update that I'll push in a few mins, gotta fix the broken tests first.

https://github.com/icook/pysistor

And yeah if I wasn't already making this for captchas I agree it would be of questionable time/value tradeoff.

@prologic
Copy link

prologic commented Sep 6, 2013

Sounds great. I'll check it out :)

James Mills / prologic

E: [email protected]
W: prologic.shortcircuit.net.au

On Sat, Sep 7, 2013 at 5:19 AM, Isaac Cook [email protected] wrote:

It actually is on github, it's just really green. I have a big update that
I'll push in a few mins, gotta fix the broken tests first.

https://github.com/icook/pysistor

And yeah if I wasn't already making this for captchas I agree it would be
of questionable time/value tradeoff.


Reply to this email directly or view it on GitHubhttps://github.com//issues/57#issuecomment-23963041
.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants