Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Good Day!
New guy here and first post... hope no rules broken.
Installed Linux (Mandrake 9) with paranoid security.
Good stuff but sometimes anoying...
One of the features resets ownership of all files within /var/log to root with permissions "600" read write by owner only.
This appears to be done via cron using "msec".
Does anyone know how to bypass this feature for a given subdirectory?
I searched for config files but could not find an include/exclude list on anything that looke like it. The responsible code appears written in Python and I'm unfamiliar with it.
I'd also be interested in finding decent documentation on this subject.
Distribution: OpenBSD 4.6, OS X 10.6.2, CentOS 4 & 5
Posts: 3,660
Rep:
msec is really nice, but it can be maddening at times(stupid promiscuous mode checks filling the log every minute, arrrg!).
The files are in /usr/share/msec (or was it /usr/share/lib/msec?). I can't remember the exact file that holds the file permission settings, but it's in there. Try # cd /usr/share/msec ; grep "/var/log" *
By the way, /var/log really shouldn't be readable by anyone other than root. Use sudo to view logs as a non-root user.
raybcher, this is some stuff I saved from when I had msec installed
hope its not out of date...
Customizing msec With Overrides
To override any of these defaults, you will need to create the file /etc/security/msec/level.local with your overrides.
To have a better idea of the different commands you can use in the level.local file, read the mseclib manpage (man mseclib). It describes all of the functions you can set in the file and what each function is for.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.