| ▲ | slopinthebag 2 hours ago | ||||||||||||||||
yes because the majority are memory safety issues, and it's automatically assumed that a memory safety bug can lead to a vuln one again illustrating the importance of encapsulating unsafe behavior. perhaps c should get a __UNSAFE { } block, where memory access is encapsulated and thus most bugs occurring outside of those blocks do not need to be marked as CVEs. | |||||||||||||||||
| ▲ | akersten 2 hours ago | parent [-] | ||||||||||||||||
> perhaps c should get a __UNSAFE { } block, I think the convention for this is at the filesystem level and most programmers use the `.c` suffix to indicate it | |||||||||||||||||
| |||||||||||||||||