Date: Fri, 23 Feb 2018 08:25:11 -0700 From: Warner Losh <imp@bsdimp.com> To: Ben RUBSON <ben.rubson@gmail.com> Cc: Freebsd fs <freebsd-fs@freebsd.org>, FreeBSD-scsi <freebsd-scsi@freebsd.org> Subject: Re: smartmontools and kern.securelevel Message-ID: <CANCZdfo4PZv7ueCZUZ_bnPu26mL12HAUzfoszhXeDkrTShV6zA@mail.gmail.com> In-Reply-To: <0985ABD3-D141-4EE2-B1B3-3016B16E2B68@gmail.com> References: <0985ABD3-D141-4EE2-B1B3-3016B16E2B68@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 23, 2018 at 8:20 AM, Ben RUBSON <ben.rubson@gmail.com> wrote: > Hi, > > I run smartmontools on my storage servers, to launch periodic disk tests > and alert on disk errors. > > Unfortunately, if we set sysctl kern.securelevel >=2, smartmontools does > not work anymore. > Certainly because it needs to write directly to raw devices. > (details of the levels, -1 to 3, in security(7)) > > Any workaround to this ? > > Perhaps we could think about allowing SMART commands to be written to > disks when sysctl kern.securelevel >=2 ? > (I assume smartmontools writes SMART commands) > Sending raw disks commands is inherently insecure. It's hard to create a list of those commands that are OK because of the complexity and diversity of the needed functionality. That complexity also makes it hard to put the commands into a series of ioctls which could be made more secure. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfo4PZv7ueCZUZ_bnPu26mL12HAUzfoszhXeDkrTShV6zA>