News for hackers. Stuff that matters.

A comment on FreeBSD – A lesson in poor defaults. Parent comment

Re:FreeBSD – A lesson in poor defaults by CameronNemo on Friday July 05, 2019 @01:44PM (#20364305)
There is no definitive way of knowing how many security issues are present in a piece of software or a collection of software. You can only look at history and attitudes for a project (and perhaps other factors such as language used) and extrapolate from there.
[ Parent | on HN ]
Re:FreeBSD – A lesson in poor defaults by tracker1 on Friday July 05, 2019 @03:38PM (#20365220)
Maybe security issues is overly broad... but poor configuration choices related to security is obviously the context here.
[ Parent | on HN ]
Re:FreeBSD – A lesson in poor defaults by thrwaway6318 on Friday July 05, 2019 @02:48PM (#20364810)
>and perhaps other factors such as language used) and extrapolate from there.

I'm curious about this statement. Which languages do you think indicate greater security, which ones tend to indicate the opposite?

[ Parent | on HN ]
Re:FreeBSD – A lesson in poor defaults by CameronNemo on Friday July 05, 2019 @03:02PM (#20364912)
Languages with a garbage collector will be able to avoid some of the worst memory errors.
[ Parent | on HN ]
Re:FreeBSD – A lesson in poor defaults by asveikau on Friday July 05, 2019 @03:57PM (#20365360)
Usually people say it's bounds checking and preventing use after free rather than GC. It's possible to have both without GC.
[ Parent | on HN ]