Date: Thu, 01 Jun 2006 14:40:50 -0700 From: Jeff <dt@defcon.org> To: freebsd-security@freebsd.org Subject: mac_bsdextended log information Message-ID: <7.0.1.0.2.20060601142921.2284c5b0@wheresmymailserver.com>
next in thread | raw e-mail | index | archive | help
Hey everyone, I'm hoping someone can point me in the right direction. I'm running a 6.1 box with mac_bsdextended compiled. I've created my ugidfw rules, and all seems well in the universe. I've got rules set up so the web process uid 80 and gid 80 can only read uid 1010 and gid 1010 owned files. When the web server tries to do something else, it throws an error such as: <authpriv.emerg> www kernel: mac_bsdextended: 80:80 request 256 on 0:0 failed. So the question is, what file did the www process try to muck with? It is a root owned file, and it is important that it want to act on it. Security problem, or benign problem? Who knows without being able to know what the file is. A look at the source code implies that the "request 256" means that the web process tried to read the vnode numbered 256. Is that accurate? If it is, how do I go about associating vnode numbers to files, so I have a hope of troubleshooting these errors. Searching seems to turn up no tool or easy way to get this vnode -> file information. Help! Jeff
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7.0.1.0.2.20060601142921.2284c5b0>