Date: Wed, 13 Jul 2016 10:57:25 +0200 From: Dan Lukes <dan@obluda.cz> To: freebsd-security@freebsd.org Subject: Re: FreeBSD - a lesson in poor defaults? Message-ID: <57860275.404@obluda.cz> In-Reply-To: <20160713073859.GA88448@localhost.lu> References: <20160713073859.GA88448@localhost.lu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13.7.2016 9:38, Steve Clement wrote: > https://vez.mrsk.me/freebsd-defaults.txt This document is based on premise I can't agree with. I will not dispute each argument in the document, but there are two main ideas. Features compiled in and features turned on by default. According features compiled in ... I'm administrator responsible for a computer configuration. If OpenSSH devs have publicly said threads are too risky and won't be added, I'm hearing their opinion and taking them seriously, but final decision shall be mine. I wish I will be allowed to decide I wish to use threads, NONE cipher and so on. In short, no features should be removed/disabled at compiled time because if "security" (assuming the "insecure" feature can be disabled by configuration). According features turned on by default ... To say true, I don't care them so much. Performance, backward compatibility and security require trade offs all the time. There are no generic answers. I assume the virgin installed system will be ready to be remotely configured (e.g. sshd running, no firewall). Particular system needs to be tuned according local environment, goal and requirements. Thus I don't care install-time defaults so much. Just $0.02 ... Dan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?57860275.404>