Date: Sun, 03 Jun 2007 09:15:22 +0300 From: Manolis Kiagias <sonicy@otenet.gr> To: freebsd-questions@freebsd.org Subject: Re: BSD derivatives Message-ID: <46625C7A.2060604@otenet.gr> In-Reply-To: <20070603055243.GB63366@demeter.hydra> References: <4661FAC9.9010806@transpacific.net> <20070602201740.202e768a.wmoran@potentialtech.com> <46621503.5030303@freebsd.org> <20070603043301.28d9bef2@localhost> <20070603055243.GB63366@demeter.hydra>
next in thread | previous in thread | raw e-mail | index | archive | help
Chad Perrin wrote: > I'm not saying that's what the OpenBSD project does. I'm just saying > that, for instance, the availability of the ath driver contradicts a > claim that security is a top priority of the FreeBSD project. Only if > it was installed and operational by default would that really be the > case. > > Obviously, I'm assuming it's not installed by default. From what I've > read so far, it's not -- please correct me if I'm wrong. > > Actually to set the record straight, the ath driver is installed by default in 6.2 RELEASE. Installed by default meaning the card is recognized during FreeBSD setup and the user is able to configure it immediately from sysinstall. The ath driver was also present in 6.1 RELEASE (and maybe earlier?) although it had to be manually activated as a kernel module and it was not immediately obvious it was supported since it was not present in sysinstall during setup. Although the whole security issue is of course highly debatable, don't forget how much more secure FreeBSD (or other open source OSes) are compared to proprietary systems. I've been (and still am) a competent Windows 200X server admin for years and have seen oh so many holes. Mind you, most of them actually get exploited. It is nowhere near this in FreeBSD.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46625C7A.2060604>