From owner-freebsd-questions@freebsd.org Fri Mar 10 17:12:13 2017 Return-Path: Delivered-To: freebsd-questions@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 C49F5D063A5 for ; Fri, 10 Mar 2017 17:12:13 +0000 (UTC) (envelope-from Lowell@Be-Well.Ilk.Org) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id 9BFFC1679 for ; Fri, 10 Mar 2017 17:12:13 +0000 (UTC) (envelope-from Lowell@Be-Well.Ilk.Org) Received: from lowell-desk.lan (router.lan [172.30.250.2]) by be-well.ilk.org (Postfix) with ESMTP id 02EE833C1E; Fri, 10 Mar 2017 12:12:00 -0500 (EST) Received: by lowell-desk.lan (Postfix, from userid 1147) id 8268A3981A; Fri, 10 Mar 2017 12:11:57 -0500 (EST) From: Lowell Gilbert To: "James B. Byrne via freebsd-questions" Cc: byrnejb@harte-lyne.ca Subject: Re: daily security run output (setuid) References: <0a9bbc9664cdeacc27dacadbd575ea1d.squirrel@webmail.harte-lyne.ca> Date: Fri, 10 Mar 2017 12:11:57 -0500 In-Reply-To: <0a9bbc9664cdeacc27dacadbd575ea1d.squirrel@webmail.harte-lyne.ca> (James B. Byrne via freebsd-questions's message of "Fri, 10 Mar 2017 11:42:42 -0500") Message-ID: <44bmt9jbtu.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Mar 2017 17:12:13 -0000 "James B. Byrne via freebsd-questions" writes: > Following a recent update we began to see this report: > > Checking setuid files and devices: [...] > This was a legitimate update as far as I can see. I can see that the > mtime value has changed but why does the update not account for this > with the security system? Because having "the security system" trust that the the port update was initiated by an appropriately authorized user would make it too easy to hide a security breach.