3 ms·
> Memory unsafe? No government contract for you! That's exactly what the GP pointed that isn't on the memo. But if you insist on using unsafe languages, and n
by marcosdumay 3y ago
> Memory unsafe? No government contract for you!
That's exactly what the GP pointed that isn't on the memo.
But if you insist on using unsafe languages, and not using any of the tools and procedures available for making those safer, then yes, no contract money for you, and no insurance if something happens.
- im3w1l 3y agoIt may not be in the memo, but I do think it's coming, at some point.
- marcosdumay 3y ago"At some point" is an awfully vague phrase. Currently people are making very pragmatic changes that doesn't require an impossible retooling of the entire area. The direction is clearly against carefree software, but nobody seems to be moving any fast on that way. We don't even know if people will hold that direction on the long term. This is not the first pro-security cultural change that happened in computing, and it's not even touching the fact that the computers themselves are not secure.
- kbolino 3y agoA lot of contracting is just developing to spec and/or working directly on-site just like regular employees. The government is going to have to dogfood this approach inasmuch as they want this to work.
- pornel 3y agoThat seems to be exactly the point that even the “not my problem” lowest bidder will have to start paying attention to security, and use a safer language, or hardware mitigations, or sandboxing instead of shipping something that could become a potential backdoor.