Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> the Go runtime which is written with deep expertise of Unix software

Go has no mmap(), import a 3rd party dependency for that and you'll get a segfault the very second you do a mistake.

Python has an mmap module which will catch many memory errors and present them as exception rather than causing a CVE.



I don't agree with the parent comment, but mmap is exposed (low-level) in the standard library and there's a high-level wrapper in x/exp. You need to be careful with mmap no matter where you're using it.

What Go mmap CVE were you thinking of?


> What Go mmap CVE were you thinking of?

Every time you see "segmentation fault", that right there is a CVE.


No, obviously.


Because you don't report and open the CVE, not because it isn't a security issue :)


No security practitioner agrees with you about this. Please don't troll.


I thought DOS was a security problem. Glad to learn differently!


Now your argument has become that only Go programs ever terminate unexpectedly. You can see why I've lost patience here.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: