Date: Mon, 28 Jan 2019 08:04:10 -0500 From: Robert Huff <roberthuff@rcn.com> To: Matthew Seaman <matthew@FreeBSD.org> Cc: freebsd-questions@freebsd.org Subject: Re: Wireless interface Message-ID: <23630.64970.365320.231106@jerusalem.litteratus.org> In-Reply-To: <d6244985-8b67-21b3-bf40-884312746035@FreeBSD.org> References: <CAPu-kW-0u=Eoj8NtASnD_WDnsosj_WcTEh=Zhby1DnBV3d2rdg@mail.gmail.com> <MWHPR04MB04954E8E691D98C40B68607780940@MWHPR04MB0495.namprd04.prod.outlook.com> <20190126213957.adfeb61c.freebsd@edvax.de> <5C4CE8B8.4030608@gmail.com> <20190127013705.3e8cd5f3.freebsd@edvax.de> <d6244985-8b67-21b3-bf40-884312746035@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Seaman writes: > Actually, the project is struggling with a lack of information > about its userbase. If you're trying to make decisions about the > lifecycle of support for a particular device it certainly helps to > have an idea about how many people are using it. Are steps being taken to address this? If so, how do I make my information available? > As for whether stock FreeBSD contains backdoors or spyware -- I'm > pretty sure it doesn't, but there are no absolute guarantees. I am told Dennis Ritchie once posed this at a conference: Proove, conclusively, the original C compiler - distributed in binary form - didn't contain an adapting, self-propagating, and self-concealing virus that has infected every executable compiled with that executable, including descendant compilers, /ad infinitum/. Last I heard no one had done so. I'd be happy to be prooved wrong. Respectfully, Robert Huff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?23630.64970.365320.231106>