3 ms·
> http://man.openbsd.org/OpenBSD-current/man1/gcc-local.1 http://man.openbsd.org/OpenBSD-current/man1/gcc-local.1 Wait, is it really true that OpenBSD's gcc is
by geofft 10y ago
> http://man.openbsd.org/OpenBSD-current/man1/gcc-local.1 http://man.openbsd.org/OpenBSD-current/man1/gcc-local.1
Wait, is it really true that OpenBSD's gcc is from the 4.x series?
Apart from the general idea that you shouldn't be writing network-facing software in C when good alternatives (Rust, Go, C++11, Haskell, just about anything else) exist, there's a lot of good work happening in upstream GCC. How up-to-date is OpenBSD's -fstack-protector compared to GCC 6's?
> Write portable and secure C.
If you're running on the BCHS stack, why? And how is it possible to reconcile this with the suggestions to use systrace(4), pledge(2), and capsicum(4), which aren't even portable among the vibrant BSDs?