NHacker Next
  • new
  • past
  • show
  • ask
  • show
  • jobs
  • submit
Thirty Years Later: Lessons from the Multics Security Evaluation (2002) [pdf] (acsac.org)
musicale 16 hours ago [-]
> The net result is that a PL/I programmer would have to work very hard to program a buffer overflow error, while a C programmer has to work very hard to avoid programming a buffer overflow error.

;-)

I am in favor of -fbounds-safety, -fsanitize=address, etc. for any C/C++ software where you don't want memory errors.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact
Rendered at 20:57:21 GMT+0000 (Coordinated Universal Time) with Vercel.