News for hackers. Stuff that matters.
Re:Langsec explained in a few slogans by munin on Sunday November 22, 2015 @01:22AM (#10609268)
neither necessary nor sufficient. you can have a "turing complete" input with no exploitable bugs (or really, no bugs at all) and you can have a very simple recognizable and computationally limited input that has all kinds of crazy buffer overflows.

the story is about abstractions and security boundaries. what is it that allows an application to write a value of type A to a location expecting type B? why is this expressible? the langsec focus on inputs and parsers is missing the forest for the trees.

Re:Langsec explained in a few slogans by ared38 on Sunday November 22, 2015 @02:19AM (#10609344)
All Turing complete inputs can be attacked by sending an non-terminating program. You could limit the amount of time an input is allowed to run, but then it's no longer Turing complete.
Re:Langsec explained in a few slogans by munin on Sunday November 22, 2015 @10:04AM (#10610228)
it turns out that every system we've ever devised has had a limit on the amount of time the input is allowed to run, so this really seems more like a matter of degrees. this is also only an "attack" if the availability of the system is an invariant that is relevant from a security perspective. usually, we care much more about confidentiality and integrity and absent termination sensitive noninterference (which is a different problem that langsec wholly ignores and has nothing to do with the complexity of the input), i'm not sure how the termination of a program will have any impact on its confidentiality or integrity...
Re:Langsec explained in a few slogans by ared38 on Sunday November 22, 2015 @08:04PM (#10612279)
DoS isn't an attack? I agree it's less severe than leaking credit card numbers, but availability is a big deal in many applications.
Re:Langsec explained in a few slogans by munin on Sunday November 29, 2015 @04:36AM (#10644240)
if DoS was the only problem we had to worry about, we would have won.