"It is the responsibility of any application that scans the directory hierarchy and especially the responsibility of applications that make destructive changes recursively through the directory hierarchy to recognize directory junctions and avoid traversing through them, Because directory junctions are implementer using reparse points, applications should see if a directory has the FILE_REPARSE_POINT attribute set before processing that directory. "Directory junctions present a threat to any application that does a recursive traversal of the directory structure." You can create and manage directory junctions using Linkd.exe a tool available in the Windows Resource Kit." This is similar to a UNIX symbolic link that redirects a reference from one directory to another directory on the same machine. "Starting in windows 2000 NFTS supports directory junctions. MS Press Writing Secure Code 2 pages 686-7 includes the following information regarding File System Reparse Point Issues: At the time of failure it was looking for c:\temp\recursive1\recursive2\recursive2\recursive2\recursive2\recursive2\recursive2\recursive2\recursive2\rerecursive2\recursive2\recursive2 After a few recursions you get “System.IO.IOException: The name of the file cannot be resolved by the system.”. When compiling the code and running if you add a reparse point to (c:\temp\recursive1\recursive2 -> c:\temp\recursive1). What is File System Reparse Point issue ? Update: Thanks to Avner's comment I've noticed that the original code I've posted here was vulnerable to File System Reparse Point issue. Well just a quick sample recursive solution. Someone asked me how to loop through all the files in a folder.
0 kommentar(er)
