News for hackers. Stuff that matters.
Re:Dear Flask, Please Fix Your “Secure” Cookies by greghinch on Friday August 10, 2012 @09:46PM (#4369115)
Er, if someone has gotten access to your secret key, aren't they already into your server? Or is this just CYA for developer incompetence?
Re:Dear Flask, Please Fix Your “Secure” Cookies by btilly on Friday August 10, 2012 @09:56PM (#4369134)
Not necessarily. They may have gotten access to an old backup of your server. This misfeature would let them escalate that to a compromise of your live server.

Attacks often involve multiple rounds of escalation as people keep on increasing their level of access. You want that escalation to be as hard as possible. Therefore you really don't want there to be a fact that could be floating around your organization in various ways that can be used to go straight to executing arbitrary code on your production site.

Re:Dear Flask, Please Fix Your “Secure” Cookies by the_mitsuhiko on Friday August 10, 2012 @09:47PM (#4369118)
That was my thinking so far in regards to this issue. I do however understand the concerns so I am probably going to evaluate a few alternatives.
Re:Dear Flask, Please Fix Your “Secure” Cookies by nezza-_- on Friday August 10, 2012 @09:48PM (#4369120)
Local file inclusions are quite often very hard or impossible to exploit. Also, as linked in the blogpost, some may just pushed them online by accident, someone may lost a notebook or whatever. So no, filesystem access is only one way.