Re:Dear Flask, Please Fix Your “Secure” Cookies
by the_mitsuhiko on Friday August 10, 2012 @09:43PM
(#4369109)
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.
Re:Dear Flask, Please Fix Your “Secure” Cookies
by nezza-_- on Friday August 10, 2012 @09:44PM
(#4369112)
Thank you for the new implementation and your fast reaction!
Re:Dear Flask, Please Fix Your “Secure” Cookies
by lotyrin on Friday August 10, 2012 @10:04PM
(#4369157)
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.
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.