Hacker News new | past | comments | ask | show | jobs | submit login

Maybe I'm having a dumb day here but I'm not following... is the code block there the intended behavior or the exploit? In the case you mention, both conditions are false...



Apologies, == instead of &&.

false == false


Can you link to the code. This seems bizarre to me that someone would write it this way.


Microbugs always look like that. Weird stuff pops out of our brains when transcribing ideas about rules into logic. The overwhelming majority of such thinkos are clearly wrong and don't work, or often even build. And sometimes you get bugs that take a while to find because the case where it would fail is an untested edge case.

And then, once in a while, one of those edge cases...


The longer it takes to find the cause of a bug, the more likely the bug is a thinko.




Consider applying for YC's W25 batch! Applications are open till Nov 12.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: