3 ms·

> 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 v

by LtWorf 5mo ago

> 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.

tptacek 5mo ago
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?
- LtWorf 5mo ago
  > What Go mmap CVE were you thinking of? Every time you see "segmentation fault", that right there is a CVE.
  - LtWorf 5mo ago
    [flagged]
  - tptacek 5mo ago
    No, obviously.
    - LtWorf 5mo ago
      Because you don't report and open the CVE, not because it isn't a security issue :)
      - tptacek 5mo ago
        No security practitioner agrees with you about this. Please don't troll.
        LtWorf 5mo ago
        I thought DOS was a security problem. Glad to learn differently!
        tptacek 5mo ago
        Now your argument has become that only Go programs ever terminate unexpectedly. You can see why I've lost patience here.