News for hackers. Stuff that matters.
Re:Writing secure Go code by yawaramin on Tuesday November 05, 2024 @06:09PM (#42056001)
Crashing the whole program is actually memory safety. Because then the program can't get into an undefined state where parts of the program have access to memory they shouldn't.
Re:Writing secure Go code by kccqzy on Tuesday November 05, 2024 @09:25PM (#42056849)
Crashing via SIGSEGV is not memory safety.
Re:Writing secure Go code by consteval on Wednesday November 06, 2024 @10:47AM (#42064085)
Crashing with SIGSEGV can be perfectly memory safe. For example, writing to a NULL address is defined behavior on almost all platforms and typically causes the OS to send SIGSEGV.