Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 03 Jul 2014 13:02:01 +0200
From:      Rolf Nielsen <rmg1970swe@gmail.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: Security Warning
Message-ID:  <53B53829.3010403@gmail.com>
In-Reply-To: <20140703064754.78407425@scorpio>
References:  <20140703055740.0f94e5e1@scorpio>	<53B53096.3070600@freebsd.org> <20140703064754.78407425@scorpio>

next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2014-07-03 12:47, Jerry wrote:
> On Thu, 03 Jul 2014 11:29:42 +0100, Matthew Seaman stated:
> 
>> On 07/03/14 10:57, Jerry wrote:
>>> Thu, 3 Jul 2014 05:55:05 -0400
>>> 
>>> FreeBSD-10 / amd64
>>> 
>>> Every morning I receive a security email with the following
>>> notations:
>>> 
>>> Checking setuid files and devices: find:
>>> /usr/share/groff_font/devX100/CI: Bad file descriptor find:
>>> /usr/share/groff_font/devX100/S: Bad file descriptor
>>> 
>>> Checking negative group permissions: find:
>>> /usr/share/groff_font/devX100/CI: Bad file descriptor find:
>>> /usr/share/groff_font/devX100/S: Bad file descriptor
>>> 
>>> Is there something seriously wrong here, or can I safely ignore
>>> it?
>>> 
>> 
>> What do you see if you try and read the contents of those files?
>> Smells like a filesystem problem to me, in which case you should
>> unmount that partition (given it's /usr that implies taking the
>> system down to single user mode) and run fsck against it
>> repeatedly until fsck tells you the filesystem is clean.
>> 
>> I'm assuming this is a UFS system -- if it's ZFS then none of the
>> above applies, but also, you probably wouldn't see an error like
>> that either.
>> 
>> Cheers,
>> 
>> Matthew
> 
> If I try to read them, I just get: "Bad file descriptor"
> 
> Okay, do I restart the system in single user mode and then run:
> "fsck-f" until I don't receive any errors,  or do I begin with:
> "umount -af" first? I am assuming I do not umount "root" (use the
> -A flag).
> 

In single user, only / is mounted, and it is mounted read only. You
shouldn't need to run umount. I'd run fsck -fyt ufs /usr (provided
/usr is a separate filesystem, otherwise substitute the fs where /usr
resides for /usr). The -t ufs may not be needed, but it won't hurt.

Rolf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJTtTgpAAoJEB1OKfQ0M8TgdX0P/ipeh51nB1SI35fLiOmPed/D
HTy4t23y8NQnWUxD/Q+byTJL+ozQ008j1VuHa7V/Y+p5TDuQaC1UCR/ohKl3o7HH
eTKv6JfOOYXnrDiegl0o0IXqhSfY2YXZhEYuTYTjGoVcn2sVYpvWwhIbA/zfDYgb
qAZOtArChgN+VvSi/lfaXMM7piKeWxy9H7IYEq0H3cdltO+Trp7oj28Mho/e5OwD
yHsb0mnPqY3GZ0M1gHk0idov3lsXCwP9/pZ81Kd8IwiKuwoPiZ95MBtMGY9LplwR
39NRAouSs5zF7pxNgLWfHbct5tL6WiIqRPkOd5oMlD5dBm++/0XZufQMwiSOPNs3
jfJfFMGOxPiQpOifcLgm4DErd669uxqEytc7fkmrC3jgZ2C94VEZRV2S3mpMjy70
Do9h6l6m+InIxE5HCIbK3Yw3hXhRs7wcHHER4lFOkRx+9z2yNpNYDVIJzToxckNX
izIFdXFbL+F3tjgZrl1s0t/jKZxFO2FozO9+MZ/01whLlw2a1BjkEF6Eh2llWAGn
X2OamJhIQ23iJlYZ0LSK6BrIr5wqvoVABXSVAXxe7AykYt4UQp1r668nWMMgWilz
1APC1zsDbY4m76MyLejerRx3mfMdneeBWarfD/pNRsU73oXMqIjfmcEGmaceKGxL
IHJNbaGMEMe1bj9GZctH
=QhRO
-----END PGP SIGNATURE-----



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53B53829.3010403>