Author Topic: chown root.wheel then chmod 600 - WHY???  (Read 2773 times)

grey_moon

  • Full Member
  • ***
  • Posts: 100
    • View Profile
chown root.wheel then chmod 600 - WHY???
« on: March 15, 2004, 12:25:07 pm »
Don\'t now if I should be posting this here, but i\'ve been on linux irc chans, trawled google and could\'nt find an answer.
The question is, lots of linux security howtos and apps say to set ownership of certain files to root.wheel and then chmod it to 600.  So why set the group to wheel if u are going to set its permissions to 0?
I\'ve always done this, but I want to know why
An example is logcheck\'s install doc says to do this to /var/log/messages

Cheers
Moon
PS before anyone says u set the permissions to 600 so that no one but root can access the file, I know that part! Its setting group to wheel and then giving it no rights that puzzles me
Only thing i can think of is some legacy good practice or some pam module would need it, but if it did should wheel be already set!
SL_5600 with Sharp ROM 1.32 - Windows XP Pro
AmbiCom 802.11b CF WL1100C, Pretec CompactBT Bluetooth CF, Hagiwara 256MB SD Card
Expansys Black Chairmans Case, ShirtPocket Battery Extender, ShirtPocket Retractable USB Sync/Charger