On Sat, 15 Feb 2003, Murray J. Root wrote: > > Msec does not touch devices: > > I don't know what it was touching - dvgrab and kino have permission > problems right from the beginning. I'd ask the kids what they had to > change but they're asleep (my 13 year old knows more about admin in > linux than I do :). My point was and is - it required learning msec > to make MDK useful to my non-computer-geek kids. Fortunately for them > they have a brother who is a geek - we should not depend on that for > average users.
I agree. But remember that linux is many things to many people. Many reasons for people looking at linux are improvied security. Ease of use and security are always a compromise. IMHO, if msec in level 3 could break any software, it is the software that is broken. > The problem was and is - msec changes things root has changed. That is > absolutely always wrong. There is no exception. Then change security levels. It is good that msec does this, why should msec not reset permissions on /etc/ to be write-only for root? Would you want someone to leave /etc/passwd world-writeable by mistake? But I cannot accept that msec is at fault, unless someone provides details. My home desktop and my laptop both run msec 3 and I have never touched msec. Our servers run msec 4 with some customisation, our work desktops run (IIRC) msec 4 with one customisation (no user list). Actually, that is my one issue with msec, it may have been addressed already, but *reduing* permissions/security should not be done IMHO. Buchan -- |----------------Registered Linux User #182071-----------------| Buchan Milne Mechanical Engineer, Network Manager Cellphone * Work +27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
