From owner-freebsd-questions@freebsd.org Tue Jun 11 12:57:02 2019 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A93A15BA3CF for ; Tue, 11 Jun 2019 12:57:02 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0DC498AA7A for ; Tue, 11 Jun 2019 12:57:02 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from smtp.infracaninophile.co.uk (smtp.infracaninophile.co.uk [IPv6:2001:8b0:151:1:c4ea:bd49:619b:6cb3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "smtp.infracaninophile.co.uk", Issuer "Let's Encrypt Authority X3" (verified OK)) (Authenticated sender: matthew/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id D90242119 for ; Tue, 11 Jun 2019 12:57:01 +0000 (UTC) (envelope-from matthew@FreeBSD.org) Received: from leaf.local (unknown [88.212.184.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: m.seaman@infracaninophile.co.uk) by smtp.infracaninophile.co.uk (Postfix) with ESMTPSA id A99A5A036 for ; Tue, 11 Jun 2019 12:57:00 +0000 (UTC) Authentication-Results: smtp.infracaninophile.co.uk/A99A5A036; dkim=none; dkim-atps=neutral Subject: Re: Daily Security is compiling about my backup drive To: freebsd-questions@freebsd.org References: <184B84B0-C4F9-4DC5-9F55-98B26422EE37@kreme.com> From: Matthew Seaman Message-ID: Date: Tue, 11 Jun 2019 13:56:59 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.7.0 MIME-Version: 1.0 In-Reply-To: <184B84B0-C4F9-4DC5-9F55-98B26422EE37@kreme.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-GB Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 0DC498AA7A X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.99 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; NEURAL_HAM_SHORT(-0.99)[-0.985,0]; ASN(0.00)[asn:11403, ipnet:96.47.64.0/20, country:US] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Jun 2019 12:57:02 -0000 On 11/06/2019 13:36, @lbutlr wrote: > On May 31, 2019, at 6:09 AM, @lbutlr wrote: >> The Daily Security update email that FreeBS generates is reporting a lot of error on my /mnt/backup drive (like setuid errors). Is there a way to let the periodic process ignore this mount point? > > I’ve been looking for information on how to do this, and have come up empty. > > It’s about 1000 lines every day. > > /etc/periodic/security/100.chksetuid is the file that runs the check, but I am hesitant to edit the file. > > I can disable the check entirely > > /etc/defaults/periodic.conf:security_status_chksetuid_enable=“YES" > > But I only want to exclude /mnt/backup from the check. It appears the only thing I could do is exclude /usr/local/bin from my backups (which I can’t do as many of those executables are custom local binaries and scripts) or to edit the 100.chksetuid file and set $MP manually. > If you mount your backup drive nosuid then 100.chksetuid will ignore it. IIRC you can still set the suid bit on a file, but mounting the filesystem nosuid means it will have no effect. Cheers, Matthew