this post was submitted on 01 Nov 2024
72 points (90.0% liked)

Programming

17540 readers
115 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
72
Feds: Critical Software Must Drop C/C++ by 2026 or Face Risk (thenewstack.io)
submitted 4 weeks ago by arendjr@programming.dev to c/programming@programming.dev
32 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] magic_lobster_party@fedia.io 8 points 4 weeks ago

From the original document:

Software manufacturers should build products in a manner that systematically prevents the introduction of memory safety vulnerabilities, such as by using a memory safe language or hardware capabilities that prevent memory safety vulnerabilities. Additionally, software manufacturers should publish a memory safety roadmap by January 1, 2026.

My interpretation is that smart pointers are allowed, as long it’s systematically enforced. Switching to a memory safe language is just one example.