On Monday, Sep 1, 2003, at 22:55 America/Chicago, Jack Coates wrote:
On Mon, 2003-09-01 at 20:11, Avi Schwartz wrote:Then there is something else going on since I also did the changes manually but the next time that cron ran msec is restored it to the default without taking into account my changes.Hi,
This question started actually in the newbie mailing list but it may be
more appropriate for the expert list.
I setup my machine with security level 4 but I am interested in relaxing some of the permission settings. I made changes to /etc/security/msec/perm.local and then executed msec. I found that msec does not make the requested changes unless I pass it the security level parameter as in
msec 4
If I don't pass this parameter, the local changes are not executed. Even if I do pass this parameter, on the hour, cron executes /etc/cron.hourly/msec which again resets my local changes and reverts to the default.
The reason for this is that in the following line in msec:
/usr/share/msec/Perms.py $CHANGE $OPT /usr/share/msec/perm.$PERM_LEVEL $LOCAL
$CHANGE is not set and therefore the local changes do not get saved. For now I hard coded in the msec script CHANGE=-c so that the changes will be saved.
Is this a bug in msec or am I missing some setting which will force msec to use my local changes?
Thanks, Avi
puzzling. Seems like a bug -- I can only assume that I've made my
changes manually and then altered perm.local so they'll stick, otherwise
I should have seen this too.
If you look at your /etc/cron.hourly/msec is it a link to the msec executable?
Avi
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
