Linux under the file permissions and Windows file permissions compared to the problem, in fact, it is complicated to say, but here, we simplify the story, because, really the two systems are completely contrasted with no meaning; Here is a brief explanation of the file permissions problem, is to let everyone learn Linux in the heart has a more obvious concept of file permissions;
As we all know, each user created directly under Linux will also create that user group, and generate a user home directory, in the user's home directory, the user can create a file with their own permissions, then what is the default permissions? As shown:
As illustrated: Test document permissions are-rw-rw-r--, testfile file permissions are: Drwxrwxr-x, analysis is as follows:
It's not a good picture. But does not affect our judgment, thus may know, in Umask the default is 0002, the ordinary user constructs the document permission is: 664, the file permission is 775; The above number meaning is: 4: reads; 2: Write; 1: Execute; 0: no authority;
In understanding the Linux document permissions, then we do Windows file permissions analysis; Again, let's create a new user remote login to the Windows 2003 server, and then create a new folder, a document, and then we'll look at the default permissions:
As you can see, the new file and document have the same permissions as the same user remote, that is, the remote user has all the permissions to manage the files that he has built; This is different from Linux, Linux under the default umask, users have read and write permission to their own documents without permission to execute , you have read and write permissions to your own folders, and in Windows, users have read and write permissions to any file they build, which is a performance of Linux security in Windows.
Hopefully, this will make it clear that Linux file permissions are more controlled than Windows rights, so Linux is higher than windows at the security level.