Live data from Hacker News

CVE-2021-32471 – Input validation in Marvin Minsky 1967 Turing Machine

cve.mitre.org

41–43 of 43 posts

Re: CVE-2021-32471 – Input validation in Marvin Minsky 1967 Turing Machine

#41
post #39

Earlier quoted context omitted.

You can't do anything like recursion.

I spent a while trying to parse this, and it doesn't make a lick of sense. Brainfuck is a classical example of a turing complete language that doesn't have a notion of functions. What does "recursion" mean here? Nothing, I think. So you don't need recursion for Turing completeness. Some people work on languages that support functions as first class objects, which don't natively support recursion. This is nice from a…

I'm not that great a programmer, but this one seems easy to me, you write an interpreter in brainfuck that allows function definitions that support recursion, then include your recursive function definitions as an included constant then point your interpreter at the constant and tell it to run it. I assume bf allows constants but like I said I'm not that great a programmer.

Obviously using a recursive descent parser is out but thats probably easy to work around right?

I could be wrong tho so don't base mission critical code on this without rigorous testing!

Re: CVE-2021-32471 – Input validation in Marvin Minsky 1967 Turing Machine

#42
post #39

Earlier quoted context omitted.

I spent a while trying to parse this, and it doesn't make a lick of sense. Brainfuck is a classical example of a turing complete language that doesn't have a notion of functions. What does "recursion" mean here? Nothing, I think. So you don't need recursion for Turing completeness. Some people work on languages that support functions as first class objects, which don't natively support recursion. This is nice from a…

I'm not that great a programmer, but this one seems easy to me, you write an interpreter in brainfuck that allows function definitions that support recursion, then include your recursive function definitions as an included constant then point your interpreter at the constant and tell it to run it. I assume bf allows constants but like I said I'm not that great a programmer. Obviously using a recursive descent parser…

> I assume bf allows constants but like I said I'm not that great a programmer.

Key to being a good programmer: at least read a bit about the language before speculating about it. Not sure what you mean by "allows constants", but you're only given increment and decrement operators, and a promise that fresh tape is zeroed out.

Brainfuck supports iteration. Performing recursion in a higher level language will still look like iteration in Brainfuck.

Re: CVE-2021-32471 – Input validation in Marvin Minsky 1967 Turing Machine

#43
post #42

Earlier quoted context omitted.

I'm not that great a programmer, but this one seems easy to me, you write an interpreter in brainfuck that allows function definitions that support recursion, then include your recursive function definitions as an included constant then point your interpreter at the constant and tell it to run it. I assume bf allows constants but like I said I'm not that great a programmer. Obviously using a recursive descent parser…

> I assume bf allows constants but like I said I'm not that great a programmer. Key to being a good programmer: at least read a bit about the language before speculating about it. Not sure what you mean by "allows constants", but you're only given increment and decrement operators, and a promise that fresh tape is zeroed out. Brainfuck supports iteration. Performing recursion in a higher level language will still loo…

100 percent agree, but honestly I couldn't make sense of the examples I looked at. It was probably just me tho.
Post reply on HN