Re:On Python security amidst recent Rails/YAML vulnerabilities
by patio11 on Sunday February 03, 2013 @04:30AM
(#5159199)
I like that project but have been trying to avoid saying "Use this!" because I haven't personally audited it and am scared that Rails devs might adopt it and think it means it definitively resolves all of their issues for February, which it might not.
[ Parent
| on HN ]
Re:On Python security amidst recent Rails/YAML vulnerabilities
by thibaut_barrere on Sunday February 03, 2013 @04:47AM
(#5159226)
So far, people I've seen using it are "security-aware" developers who know there is always a remaining risk and who are just trying to reduce the surface attack a bit.
For the others, well, we'll have to educate them, or push a safe yaml default quickly into Ruby [1].
This is no holy grail for sure, and there are plenty of other topics to be addressed (eg: secret tokens stored in SCM, pushed to third-party CI services and shared with freelancers and remote employees using non-encrypted disk, shared as well between production and non-regularly updated staging servers etc!)