One of the programming challenges at SPOJ involves writing code in.bf, where input validation is practically infeasible. While there wasn't a chance for arbitrary code, an unexpected value could still disrupt the program. With other esoteric programming languages, input validation would be a luxury, and it's no surprise that something theoretical would come out.
When I followed a few links, I came across a sample exploit [github.io], but I don't see why it's an exploit, nor do I understand what said machine is trying t
Or creating an input subroutine rather than doing input directly. It's not like I was required to use.bf, there was also the choice of Intercal which gets close to implementing that feature.
Late April Fools (Score:2)
One of the programming challenges at SPOJ involves writing code in .bf, where input validation is practically infeasible. While there wasn't a chance for arbitrary code, an unexpected value could still disrupt the program. With other esoteric programming languages, input validation would be a luxury, and it's no surprise that something theoretical would come out.
When I followed a few links, I came across a sample exploit [github.io], but I don't see why it's an exploit, nor do I understand what said machine is trying t
Re: (Score:2)
writing code in .bf, where input validation is practically infeasible.,
You just need a halfway decent macro processor, and the language is fine.
Re:Late April Fools (Score:2)
Or creating an input subroutine rather than doing input directly. It's not like I was required to use .bf, there was also the choice of Intercal which gets close to implementing that feature.