Redditors cope and seethe when stockfish chads refuse to address esoteric buffer overflow exploit

[Deleted by author.]
27
Jump in the discussion.

No email address required.

I don't get what any of this means :marseyretardchad:

Jump in the discussion.

No email address required.

If Stockfish runs from an illegal position, it can crash from a buffer overflow. This is potentially unsafe, but it would be extremely difficult, and practically impossible to find an illegal position that it would crash in a way that would be exploitable.

If anyone really cares about this they can just validate the input before running stockfish and problem solved.

The stockfish devs don't want to fix it because they only care about legal chess. Patching all the ways it could crash from illegal positions for security reasons would harm performance and bloat the software.

Redditors in /r/programming aren't professional codecels so they only see it as Buffer Overflow -> Insecure Application -> :marseyrave:.

Jump in the discussion.

No email address required.

Thanks kind stranger, have this reddit gold :marseygold:

Jump in the discussion.

No email address required.

They can just do those checks inside #ifdefs and add a -oUnsafe option to the compilation where you throw all safety guarantees out the window.

This dude has a point. However, at the end of the day, it's the maintainer's call and their time going into supporting the software. Devs just don't like being politely told to frick off because their over-engineering might not be worth the time or effort.

Edit: The maintainer's responses were also pretty spergtastic.

Jump in the discussion.

No email address required.

also what is stockfish

Jump in the discussion.

No email address required.

Link copied to clipboard
Action successful!
Error, please refresh the page and try again.