Re:Return-Oriented Programming without Returns (on the x86)
by ramchip on Saturday February 27, 2010 @09:11PM
(#1156254)
Could you back up that claim? lambdabot on #haskell runs arbitrary Haskell code very safely.
[ Parent
| on HN ]
Re:Return-Oriented Programming without Returns (on the x86)
by jrockway on Saturday February 27, 2010 @11:01PM
(#1156406)
I think he means fail as in allowing you to write a function like:
deleteAllFiles user = if user == Root
then throwError "access denied"
else unsafeDeleteAllFiles
Even if memory access is safe, you can still type in the wrong algorithm.
Re:Return-Oriented Programming without Returns (on the x86)
by ax0n on Saturday February 27, 2010 @11:56PM
(#1156462)
Most certainly. But further, it's possible to write unintentionally exploitable code in any language.
Re:Return-Oriented Programming without Returns (on the x86)
by ax0n on Saturday February 27, 2010 @10:19PM
(#1156353)
No, because I know absolutely nothing about Haskell. I do know that if there was a silver-bullet language that was 100% "secure", everyone would be using it.
This attack is x86 machine-code-native, so Haskell in a VM is not vulnerable to the exact same problems, but to assume it's completely invulnerable is myopic.
Re:Return-Oriented Programming without Returns (on the x86)
by jpr on Sunday February 28, 2010 @02:22AM
(#1156600)
> I do know that if there was a silver-bullet language that was 100% "secure", everyone would be using it.
This is completely false. Almost nobody in the software industry cares about safety. This can be proven trivially just by comparing how much more popular C and C++ are compared to memory-safe languages.