in reply to Re: Re: Re: Why does this crash? (Error 500)
in thread Why does this crash? (Error 500)

You should be aware that using mode 777 means that anybody on the system can read and write that file or directory. If you're on a shared system, anybody else on the system can edit or delete files in a mode 777 directory. Even if you have a system to yourself, giving permissions to everybody to write someplace can make a minor security problem (like disk access as user nobody) into a big one.

If you really don't care about the files or directories with mode 777 being changed by random users, those permissions are fine. Sometimes that's true, as in /tmp. Mostly, though, it's not true, and you should find a more restrictive set of permissions that allows your script to write to that directory, without allowing the rest of the world as well.

  • Comment on Re: Re: Re: Re: Why does this crash? (Error 500)

Replies are listed 'Best First'.
Re: Re: Re: Re: Re: Why does this crash? (Error 500)
by Anonymous Monk on Jan 02, 2004 at 18:03 UTC
    Thanks for the advice - I am only using this as a back up so it will be a question of chmod in the script to 777 then back again after the file is created.
Re: Re: Re: Re: Re: Why does this crash? (Error 500)
by tachyon (Chancellor) on Jan 03, 2004 at 04:35 UTC

    I totally agree that 777 is generally bad which is why I went on to suggest the chown user:nobody and chmod 775 or 770.

    cheers

    tachyon

      I know you suggested it, tachyon. I was concerned the OP had skipped over that part of your post, since he seemed to just try mode 777 and be happy with it. But it sounds like he's taking some precautions, so hopefully all will be well. :-)