You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,12 +13,13 @@ A Windows named pipe monitoring GUI. Requires administrator priviledges to run.
13
13
14
14
## Known issues
15
15
16
-
Since Windows doesn't keep timestamps of pipe creation, the creation timestamp is determined by the time the named pipe is first seen.
16
+
- The NPFS driver doesn't keep timestamps of pipe creation, so the creation timestamp is determined by the time the named pipe is first seen.
17
+
- The named pipes that get quickly created and deleted (or deleted and re-created) between scans won't be noticed about at all.
18
+
- The ACLs could not be extracted from pipes without a free server end. Also, for the same reason reading of ACLs may disrupt processes trying to connect to the same ACL.
17
19
18
-
The named pipes that get quickly created and deleted (or deleted and re-created) between scans won't be noticed about at all.
20
+
All of those could be fixed by installing a filesystem filter driver which will gather and export this information. Unfortunately, somebody needs to write such driver first.
19
21
20
22
## TODO
21
23
22
-
- Extraction of ACLs for pipes which only SYSTEM has access to.
23
24
- More/better hints (see the GetHintFor() function in Models/PipeModel.cs).
24
25
- Keep selected line in view when many named pipes gets created or deleted.
0 commit comments