Difference between revisions of "Memory Safe"
From MgmtWiki
(Created page with "==Full Title or Meme== Programming languages since C have been known to be hard to create programs that have no memory issues that create a Vulnerability leading to an E...") |
(→Context) |
||
| Line 5: | Line 5: | ||
* [https://www-theregister-com.cdn.ampproject.org/c/s/www.theregister.com/AMP/2023/12/07/memory_correction_five_eyes/ Dump C++ and in Rust you should trust, Five Eyes agencies urge] 2023-12-07 | * [https://www-theregister-com.cdn.ampproject.org/c/s/www.theregister.com/AMP/2023/12/07/memory_correction_five_eyes/ Dump C++ and in Rust you should trust, Five Eyes agencies urge] 2023-12-07 | ||
| + | * [https://www.cisa.gov/resources-tools/resources/case-memory-safe-roadmaps The Case for Memory Safe Roadmaps]] from the CISA (2023-12-06) | ||
==References== | ==References== | ||
[[Category: Vulnerability]] | [[Category: Vulnerability]] | ||
[[Category: Exploit]] | [[Category: Exploit]] | ||
Latest revision as of 14:42, 9 December 2023
Full Title or Meme
Programming languages since C have been known to be hard to create programs that have no memory issues that create a Vulnerability leading to an Exploit.
Context
- Dump C++ and in Rust you should trust, Five Eyes agencies urge 2023-12-07
- The Case for Memory Safe Roadmaps] from the CISA (2023-12-06)
