Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

For what it's worth, I implemented JSON based sessions for testing purposes: https://github.com/mitsuhiko/flask/commit/4df3bf2058954624f9...

They are currently on a separate branch and they are known to break python-openid (and with that Flask-OpenID). I don't have a solution for that yet. If someone is really concerned regarding security you can copy/paste the code into your own project. The session interface in Flask is pluggable for a while already.



Is there a reason why session storage isn't local, with clients only given the index into that storage?

Allows for any size/types of data but the worst case scenario-without code execution is that an attacker hijacks an existing but valid session.


I should add that this will not be at all the final implementation for Flask 0.10 in case I want to change that. If the change of the implementation will happen I will make itsdangerous (separate Python module) have a way to serialize the custom objects properly and then add this as a dependency.


Thank you for the new implementation and your fast reaction!




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: