This voluntary guidance provides an overview of product security bad practices that are deemed exceptionally risky, particularly for software manufacturers who produce software used in service of critical infrastructure or national critical functions (NCFs).
their reasoning is that rust (and perhaps others) that can be used in place of c or c++ have stronger compile time memory and thread safety checking which are two major sources of bugs and exploit vectors. So it’s not like they’re infiltrating the language in this case the way they would with crypto.
Right but AI translating of all government code is good. This is what you want, especially if shit goes down. Dont tell your enemy to stop pouring the kool aid.
Am I wrong or is this a strong point in favor of c/c++? I’d generally want to do whatever the opposite is of what the FBI would like me to do.
“critical software” here refers to weapons systems, spying systems, government surveillance systems, cyberwarfare software, etc.
Do you work on critical software
If I did, it wouldn’t 😉
Why would they announce it instead of just memoing to their ghoul coders?
their reasoning is that rust (and perhaps others) that can be used in place of c or c++ have stronger compile time memory and thread safety checking which are two major sources of bugs and exploit vectors. So it’s not like they’re infiltrating the language in this case the way they would with crypto.
Right but AI translating of all government code is good. This is what you want, especially if shit goes down. Dont tell your enemy to stop pouring the kool aid.
Nah, that kind of reasoning is like “nazis think people should get armed, so we shouldn’t.”