4.6 File Attributes Are Always Honored

Figure 4-4 File attributes affect functionality in home folders

Letter	Details
	User Blue is granted all rights to an NSS-based home folder.
	Using a file browser, such as Windows Explorer, Blue applies the Read-only attribute to one of the files in the home folder to ensure that it doesn’t get modified by mistake.
	A few weeks later, Blue opens the file through Filr and having forgotten about the Read-only attribute, tries to change it. The file system doesn’t allow this because of the file’s Read-only attribute. Of course, Blue could remove the attribute using a file browser and then modify the file. Filr always honors the file system. As long as the file is Read-only, it cannot be modified through Filr.

Letter

Details

User Blue is granted all rights to an NSS-based home folder.

Using a file browser, such as Windows Explorer, Blue applies the Read-only attribute to one of the files in the home folder to ensure that it doesn’t get modified by mistake.

A few weeks later, Blue opens the file through Filr and having forgotten about the Read-only attribute, tries to change it.

The file system doesn’t allow this because of the file’s Read-only attribute.

Of course, Blue could remove the attribute using a file browser and then modify the file.

Filr always honors the file system. As long as the file is Read-only, it cannot be modified through Filr.

Figure 4-5 File attributes also affect functionality in Net Folders

Letter	Details
	As shown in Figure 4-2, Blue doesn’t have Erase rights on the projects folder.
	Therefore, Blue only qualifies for the Filr Editor role.
	The project leader maintains strict control of the scope.txt file by using the Read-only attribute.
	This means that, even though Blue is an Editor in the projects folder, the scope.txt file is off-limits for making any changes.