Re:On Python security amidst recent Rails/YAML vulnerabilities
by vq on Sunday February 03, 2013 @04:45AM
(#5159219)
This is often the case in Haskell APIs, easily abusable or functions with hard to predict side-effects are usually prefixed with "unsafe", for example unsafeCoerce or unsafePerformIO.
[ Parent
| on HN ]
Re:On Python security amidst recent Rails/YAML vulnerabilities
by tikhonj on Sunday February 03, 2013 @04:26PM
(#5161235)
Another cool thing, from a security perspective, is that there is actually a tool (Safe Haskell[1]) that makes it easy to disallow unsafe behavior and operate a whitelist of trusted modules. So not only is unsafePerformIO well-named, it's also trivial to restrict its usage.
[1]: http://www.haskell.org/ghc/docs/7.4.1/html/users_guide/safe-...