News for hackers. Stuff that matters.
Re:Dear Flask, Please Fix Your “Secure” Cookies by the_mitsuhiko on Friday August 10, 2012 @08:19PM (#4368936)
I would love to switch the default to JSON but people store too much stuff in their sessions that does not work on top of JSON (datetime objects and token objects are the most common offender).

In fact the python-openid extension is the most common offender. Also I can't just switch the default because it would invalidate everyone's currently issued sessions.

The issue is not new, changing it without breaking things is the hard part.

Re:Dear Flask, Please Fix Your “Secure” Cookies by seunosewa on Friday August 10, 2012 @08:53PM (#4369003)
It's a security issue. You're allowed to break things (or at least deprecate dangerous features)!
Re:Dear Flask, Please Fix Your “Secure” Cookies by the_mitsuhiko on Friday August 10, 2012 @08:56PM (#4369009)
It's a security issue if people leak their secret key. At that point you have a huge problem anyways. Also breaking things assumes that afterwards you are left with an equally functioning system which I currently don't think I can guarantee.
Re:Dear Flask, Please Fix Your “Secure” Cookies by nezza-_- on Friday August 10, 2012 @09:49PM (#4369125)
No, I don't think "you have a huge problem anyways" is true, as there are a lot of other scenarios.
Re:Dear Flask, Please Fix Your “Secure” Cookies by tptacek on Friday August 10, 2012 @10:36PM (#4369213)
Like what?
Re:Dear Flask, Please Fix Your “Secure” Cookies by moe on Friday August 10, 2012 @09:31PM (#4369090)
One thing that you could and should add is AES-encryption.

It does nothing for the pickle issue but it's quite a shame to send cookies in plain-text in this day and age.

Re:Dear Flask, Please Fix Your “Secure” Cookies by phleet on Friday August 10, 2012 @09:13PM (#4369053)
Why can't a custom JSON encoder be used with support for serializing/deserializing datetime objects?
Re:Dear Flask, Please Fix Your “Secure” Cookies by the_mitsuhiko on Friday August 10, 2012 @09:17PM (#4369060)
It's still inline signalling and might conflict with what people have. Keep in mind that sessions are schemaless. It's not a huge problem changing that and I have a somewhat working implementation but it will break stuff, that's just how it works unfortunately.