Re: 2 questions: 1. ssh permissions to 777 and 2. recursively change all directories/files to 777

[Simon Valiquette <v.simon@ieee.org>]

Ray Olszewski a écrit :
 >
 > So you want an uploaded file to be mode 777, writable (and executable,
 > if you really mean 777, not 666) by any user on the system? OK. Change
 > the account's umask, in ./.profile, or ./.bashrc, or whatever
 > user-specific file is appropriate to your setup.

   I would also had done something likes that.  Then, if you want those
users to be _forced_ to put all their files world readable, I don't know
how to do it.  The closest I know is with a cron that change back the
permissions with chmod every 5 minutes or a script runned at logout time
(maybe scp also execute .logout).

 >
 > Since the relevant command is "chmod", not "Chmod" (case counts in
 > Linux/Unix commands), I'm surprised you hit *anything* with the command
 > as written.

   It surelly really was chmod.  Typo, or Outlook that automatically
fixed the case (I remember seeing things likes that many years ago when
I was still using Windows).

 >         chmod -R 777 ./*
 >
 > (Even this will not chmod **all** files, because because by convention
 > almost all Linux/Unix commands treat files that begin with a dot
 > character as special, so standard wildcards (*) will not match them. So
 > this command will chmod files with names like filename and filename.txt,
 > but not one with names like .filename . I don't know a general way to
 > include such files.)
 >

          chmod -R 777 .

   Note the "." at the end.  That will do it for the current directory,
and all files/directories that start from the inode represented by "."

Simon Valiquette
http://gulus.USherbrooke.ca



-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs