From owner-freebsd-security@freebsd.org Wed Oct 5 19:15:03 2016 Return-Path: Delivered-To: freebsd-security@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9052BAF6058 for ; Wed, 5 Oct 2016 19:15:03 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6E882905 for ; Wed, 5 Oct 2016 19:15:03 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from julian-mbp3.pixel8networks.com (50-196-156-133-static.hfc.comcastbusiness.net [50.196.156.133]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u95JF0bg050697 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Wed, 5 Oct 2016 12:15:01 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: isn't this the worst possible report?? To: freebsd-security@freebsd.org References: <1410500115.6001690.1475677275963.ref@mail.yahoo.com> <1410500115.6001690.1475677275963@mail.yahoo.com> From: Julian Elischer Message-ID: Date: Wed, 5 Oct 2016 12:14:55 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 MIME-Version: 1.0 In-Reply-To: <1410500115.6001690.1475677275963@mail.yahoo.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Oct 2016 19:15:03 -0000 On 5/10/2016 7:21 AM, Jules Gilbert via freebsd-security wrote: > Well maybe worse, that the deal with AT&T for the BSD franchise has fallen apart... > Okay, so I have a FreeBSD 10.1 CD-ROM, believed to be a true copy and authentic copy. > And I loaded it on a computer. I did this entirely offline. I also supplied passwords. > > Then I went online to get packages. > Nothing unusual happened UNTIL the machine seized and when I rebooted I discovered it would hang and reboot. A loop. > I had done nothing to cause this. I had not opened an X session nor done anything other than load packages such as maxima, cproto. Nothing involved in the area of security. > > I had thought this was pretty much impossible... Remember, this machine was brand new, I'd loaded FBSD-10.1 on it no more than an hour prior and had not messed with any of the internals. > _______________________________________________ > freebsd-security@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org" > > depending on where it rebooted, it really sounds like an infant mortality problem.. (failure in computer or drive). (brand new machines have a much higher chance of failure than middle aged machines, as all the components burn in.) why is this in 'security'?