Advertisement:

Author Topic: Why chmod 777 is NOT a security risk  (Read 359146 times)

Offline Arantor

  • Resident Overthinker
  • SMF Friend
  • SMF Legend
  • *
  • Posts: 68,032
    • Arantor on GitHub
Re: Why chmod 777 is NOT a security risk
« Reply #100 on: August 17, 2009, 07:43:58 AM »
philesq: please open a new topic in the support boards.

For reference SMF should be able to set its own permissions if given FTP username/password.
To assume is to hope that those who came before had the presence of mind and capacity to implement the dreams of those who would come after.

You either die a hero or live long enough to see yourself become the villain. It seems you have chosen which, and now I must do the same.

Offline GravuTrad

  • Senior Translator
  • SMF Hero
  • *
  • Posts: 8,582
  • Gender: Male
  • One of the french SMF translators
Re: Why chmod 777 is NOT a security risk
« Reply #101 on: August 17, 2009, 07:45:31 AM »
For reference SMF should be able to set its own permissions if given FTP username/password.

Not all servers configurations permit this...
On a toujours besoin d'un plus petit que soi! (Petit!Petit!)


Think about Search function before posting.
Pensez à la fonction Recherche avant de poster.

Offline Arantor

  • Resident Overthinker
  • SMF Friend
  • SMF Legend
  • *
  • Posts: 68,032
    • Arantor on GitHub
Re: Why chmod 777 is NOT a security risk
« Reply #102 on: August 17, 2009, 08:55:43 AM »
Not all servers configurations permit this...

True enough - as the support topics testify. However this should be used in the first instance and as ever any problems should get their own support topic.
To assume is to hope that those who came before had the presence of mind and capacity to implement the dreams of those who would come after.

You either die a hero or live long enough to see yourself become the villain. It seems you have chosen which, and now I must do the same.