-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-09-13 at 07:59 +0200, Jon Clausen wrote:
(It checks file ownership/privs agains /etc/permissions and friends, and corrects anything out of 'sync')
Not really for everything, only those that have a sequrity consequence. For instance, /usr/share/doc is not touched.
True. But the files with a security consequence *are* the most important to fix 'real quick'.
Er... yes, right.
The OP wasn't clear about *which* files were affected, so...
I thought at first he meant those in /root, maybe more.
But in any case the rpm idea presented in another branch of this thread is probably a better solution, overall.
Probably both, rpm first, then suseconfig: rpm -a --setugids rpm -a --setperms SuSEconfig -module permissions I don't knwow why Jon Nelson says that --setugids should always be done before --setperms :-? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFB9wdtTMYHG2NR9URAlUSAJ9uGR13LuDKZ0LlRewYXMRPAfHJBACfWUCs dGvcbD/CciOfJvRbvHlOpgs= =JWrN -----END PGP SIGNATURE-----