News for hackers. Stuff that matters.
Re:FreeBSD – A Lesson in Poor Defaults by ogogmad on Thursday August 18, 2022 @08:47AM (#32508859)
Software's an area where fail-fast/fail-hard is commonplace advice. People often compile their code with -Wall. Secure defaults are like -Wall.

Security's a thankless area since you have no way of knowing which exploits were prevented by security measures. It's like precautions against fires: You have no way of knowing how many thousands of deaths were prevented by measures taken to prevent fires from starting - and you never will. It even affects our politics: We don't know how many deaths were prevented by the measures taken to save lives from the present pandemic, and as a result some people complain.

Re:FreeBSD – A Lesson in Poor Defaults by AlexanderDhoore on Thursday August 18, 2022 @09:17AM (#32509159)
It's funny that you chose -Wall as an example because it is the exact opposite of what you are trying to say. -Wall is effectively frozen and new warnings are never added to it, in the name of backward compatibility.
Re:FreeBSD – A Lesson in Poor Defaults by bombcar on Thursday August 18, 2022 @09:52AM (#32509577)
The best kind of backwards compatibility- designed to forever trip up the newbies who dare to assume all means all.
Re:FreeBSD – A Lesson in Poor Defaults by tedunangst on Thursday August 18, 2022 @11:16AM (#32510851)
New warnings appear in -Wall with just about every compiler upgrade. That's why standard advice is to never ship with -Werror because the next guy's compiler may fail to build it.
Re:FreeBSD – A Lesson in Poor Defaults by blahgeek on Thursday August 18, 2022 @10:37AM (#32510268)
> -Wall is effectively frozen and new warnings are never added to it, in the name of backward compatibility.

Any reference on this? Thanks!