Paging I/O bypasses desired access security checks for local files, so
you can do paging reads/writes with a file object opened without
FILE_READ_DATA/FILE_EXECUTE/FILE_WRITE_DATA. However, the security
checks DO apply for file objects that represent remote files (on the
network), because obviously the remote server is doing the check. In
this case the redirector will bypass the Cache Manager for file objects
opened with write-only access.
ecore wrote:
Is the FileObject used by PagingIO must be CREATED with FILE_READ_DATA or
FILE_EXECUTE or
FILE_WRITE_DATA or FILE_APPEND_DATA???In other words,the FileObject must
not be CREATED with
single ,just,
DELETE,FILE_READ_ATTRIBUTES,FILE_READ_EA,READ_CONTROL,FILE_WRITE_ATTRIBUTES,FILE_WRITE_EA ,WRITE_DAC ,WRITE_OWNER !!!
I think,because the FileObject used by pagingIO will execute
IO(Read,Write),so it must be Created
with these IO flag.And I know,if I have a FileObject,I can roll a IRP to
READ/Write afaid of the Created
flag of the FileObject(Is that?).So,my means is the CacheManager’s real
solution.
I think,because Cc reference the fileobject when the first data IO,the
FileObject used by pagingIO must be CREATED
with data IO flag.
just discuss it.Please…
You are currently subscribed to ntfsd as: xxxxx@nryan.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
–
- Nick Ryan (MVP for DDK)