The problem is that msec doesn't seem to be setting the directory/file permissions unless it is called with the security level passed to it as a parameter as in:
msec 4
Only in this case the script is setting the -c parameter on the call to Perms.py. Without the -c parameter, the file permissions are not set.
Is there a better way to call msec to set the permissions? Shouldn't the file permissions checked and set on each invocation of msec by default?
Avi
On Monday, Sep 1, 2003, at 18:28 America/Chicago, Björn Olsson wrote:
On Monday 1 Sep 2003 Avi Schwartz <[EMAIL PROTECTED]> wrote:
My machine currently uses level 4 security which sets the permissions on /var/tmp to 1773, however I need to make it possible for "other" to be able to read their files from this directory (i.e. mode 1777. so I added to perm.local the following line /var/tmp root.adm 1777 and then went ahead and modified the permissions on the directory manually to see what msec does: chmod g+r /var/tmp Unfortunately when I run msec it changes the permissions back to 1773. Isn't perm.local supposed to allow me to override the default settings? How do I achieve this?
Thanks, Avi
I have gone some rounds against msec too... It seems that level.local has to begin with the line from mseclib import * or else it won't save any changes. Take a look at http://www.mandrakeuser.org/docs/secure/smsec2.html for starters.
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
