|
#1
|
|||
|
|||
Question about FileSystem DeviceDriver
Hello,
I need to write a device driver that hooks up FileSystem activities. if the file was created or deleted, I would be informed by the driver. The problem is that the driver should work in all versions of Windows! Is there anything possible? Does the operating system architecture work effectively in writing the driver? That is, have two separate drivers written for each architecture and windows version? |
#2
|
|||
|
|||
You need a mini-filter driver in this case, consider that writing a well rock-solid and performant FS-minifilter is not an easy task, my primary suggestion is to start learning the basics of FS Filtering and check Microsoft github for already written examples.
Let's discuss about distribution: - One driver per each arch (32 and 64 bits) - You can write a unique driver that works from Windows 7 to Windows 10 including server editions from Win2k8 R2 up to WinServer 2016 To deploy in production on Windows 10 you will also need an EV (Extended Validation) certificate that must be counter-signed by Microsoft. Check this github, you can almost grab a big part of the filter and be sure that it works without BSODs https://github.com/Microsoft/Windows-driver-samples/tree/master/filesys Best Regards, Evilcry |
#3
|
|||
|
|||
Windows has a mature minifilter driver development framework, Linux can hook vfs read and write api.
|
#4
|
|||
|
|||
For anyone needing to refer to the answers for this same question in future, it was asked and answered here as well :
Quote:
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
VS 6 question(s)... | newguy | General Discussion | 9 | 04-22-2004 19:49 |
Question to JMI | Rhodium | General Discussion | 1 | 02-20-2004 06:16 |