Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
hi guys,
writing my first driver that uses "ObRegisterCallbacks" to intercept handle creation attempts to my process.
but when my process is created the creator also "creates" (it did call CreateProcess ) a handle to my process which triggers a false alert.
is there any-way to detect that the handle creation is from the "parent" process so i can make my alerting code ignore it?
thanks in advance
Upcoming OSR Seminars | ||
---|---|---|
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead! | ||
Kernel Debugging | 9-13 Sept 2024 | Live, Online |
Developing Minifilters | 15-19 July 2024 | Live, Online |
Internals & Software Drivers | 11-15 Mar 2024 | Live, Online |
Writing WDF Drivers | 20-24 May 2024 | Live, Online |
Comments
Hi , you can use PsSetCreateProcessNotifyRoutine routine for notify process creation and exit, in this routine you can find the parent and child process id Separately And you do not need to calculate these IDs, These IDs exist in PCREATE_PROCESS_NOTIFY_ROUTINE structure,
https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/ntddk/nf-ntddk-pssetcreateprocessnotifyroutine