Date: Tue, 31 Mar 1998 15:22:37 +0930 From: Greg Lehey <grog@lemis.com> To: "John S. Dyson" <toor@dyson.iquest.net> Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: Corruption in security check output Message-ID: <19980331152237.25396@freebie.lemis.com> In-Reply-To: <199803310547.AAA01709@dyson.iquest.net>; from John S. Dyson on Tue, Mar 31, 1998 at 12:47:04AM -0500 References: <19980331085819.11996@freebie.lemis.com> <199803310547.AAA01709@dyson.iquest.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 31 March 1998 at 0:47:04 -0500, John S. Dyson wrote: >> Is anybody else seeing things like this in their security check >> output? I've been haing it for about 3 weeks now, since the build of >> 11 March. >> >> ----- Forwarded message from Charlie Root <root> ----- >>> Date: Tue, 31 Mar 1998 03:00:55 +0930 (CST) >>> To: undisclosed-recipients:; >> >>> checking setuid files and devices: >>> freebie setuid/device diffs: >>> 164a141,144 >>>> -rwsr--r-- 1 grog wheel 0 Feb 7 11:02:59 1998 /home/grog/filth >>>> -rwsr-sr-x 1 grog bin 7780 Aug 13 22:12:28 1995 /home/grog/src/setuid >>>> -rwsr-sr-x 1 grog bin 37643 Aug 13 21:50:44 1995 /home/grog/src/setuid.bsd >>>> -r-sr-s--- 1 grog wheel 17408 Apr 5 04:16:40 1993 /home/grog/vgaset.grog/X386/bin/vgaset >>> 181,436c161,272 >>> < < 4D8E9CA85A8533422D642D7C9A811C349BE2000A97BB7823D92F2190F679B60A >>> < 6243D21CADABBBF1C9942AD2F310F8540E15F25C116818A23458853E338CA388 >>> < A3A17D6C4A73D9DDC2B96253AAC6E7CF7828BE640B45265584EA986747BB1308 >>> < 008C0DC55E4146B646F1CD3C40EFBF3DBE305010878E9D800AABDAB3ED816436 >>> < 2AD34424A40322F5A64DEFCEBE471C0DDB42372DE0708CD6F7295D6C1D5CAF08 >>> < E4BEA40FC1F6302DF9B3C73D34077A762D44D82F309A245443406C544C803DBC >>> < EF2381769EDC098A6AE508312A2AE9A5905715353EBF18BA5F2C8D1DA4E426E6 >>> < ACF611065E05CCBF35F30B9E92412DD28A9B73F0E7C1959A6822C8E94A33FD2C >>> < 015E192BB4654DD86746E4724873E952B69DC8923A9834C57309622FF6E46B37 >>> < 26B43BF80E2A0FD5BF94EA13F8F7BCE84FD7251F8D333DF34C2926A4A7955AD7 >> >> (etc) >> >> I've remade world a couple of times, but the problem has remained. > > Warning: do not enable vfs.ioopt!!! If that isn't the problem, then > that is a new one for me. vfs.ioopt's a new one for me. What is it? In any case, I haven't changed anything for months. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980331152237.25396>