3 ms·
Do you realize that the thing does not process any attacker controlled input and thus all the hardening is completely pointless exercise?
by dfox 8y ago
Do you realize that the thing does not process any attacker controlled input and thus all the hardening is completely pointless exercise?
- joh6nn 8y agoThe number of times in my life that I have seen "this should never happen" scroll by on STDOUT suggests that it's time well spent.
- dfox 8y agoIf you cannot trust that 725 line program without any mention of recv() nor read() will never call recv() or read() on network socket then you have much larger reliability (not security, because whether something that is broken to the point of being unusable is secure or not is completely irrelevant) issue in your system that is not going to go away by applying random hardening options to said program.
- LinuxBender 8y agoIf it opens a socket, it gets hardening. It's just a best practice I follow. Code can change. Subtle changes can lead to gaps, so I wrap that rascal regardless.