Re^4: somethign wrong with the sumbit

well yes iam aware of that, because i didnt knew how to check for the existense of a backwards error.

I mean in the null byte string iam testing against the null string, in the backwards error test what? if the submitted param contains slashes and dots?

Apart from that you didnt point to me whats wrong with the if structure that you say its always false.

Comment on Re^4: somethign wrong with the sumbit

Replies are listed 'Best First'.
Re^5: somethign wrong with the sumbit by shmem (Chancellor) on Dec 29, 2007 at 14:30 UTC
if the submitted param contains slashes and dots? You aren't testing against that. You just say 'else' without a test. So if there's no null byte in the param, you assume there's a "Backwards Directory Traversal". --shmem _($_=" "x(1<<5)."?\n".q·/)Oo. G°\ / /\_¯/(q / ---------------------------- \__(m.====·.(_("always off the crowd"))."· ");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}	[reply]
A reply falls below the community's threshold of quality. You may see it by logging in.
Re^5: somethign wrong with the sumbit by Anonymous Monk on Dec 29, 2007 at 13:27 UTC
You asked why you get backwards error, this is why, because your code is `if ( almost-always-false ) { hey null byte } else { hey backwards error }` [download]	[reply] [d/l]
Re^6: somethign wrong with the sumbit by Nik (Initiate) on Dec 29, 2007 at 15:20 UTC
Yes, but you didnt explain to me why this is almost-always-false as i asked you in response to your first answer How is it possible a selected submitted valid drop down item to pass this if block? Items in the drop down menu doesnt contain null strings only url hack attempts do. Please exlain yourself so i can understand.	[reply]