The user mode functions could already have been subverted, maybe that’s why
the OP wants to terminate the process in kernel mode.
But then so could the kernel functions of course…
If he’s checking the behaviour of a process after it’s been run, it’s kind
of like cutting off the branch you’re sitting on.
He’s also assuming that he can analyse this processes behaviours without it
realising that it is being tampered with, and reacting to that tampering.
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of
xxxxx@arcor.de
Sent: 05 February 2010 03:13
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Terminate a process from kernel-mode with the help of
usermode
Hi,
i personally do not see any sense to terminate a process in kernel mode when
there are the stubs in user mode that transist into kernel mode and call the
functions. Using a approach like that (as said before) is a great security
problem and not really recommended.
But one thing that everybody forget here is the fact that many of the
commercial security solutions would (possibly) flag such a product as a
security thread/risk, especially when it comes to calls like
Nt/ZwTerminateProcess and functions acting in that space (everything that
hooks something)! Am i right or wrong!
The best termination method is by far using
TerminateProcess(…)/ExitProcess(…) or possibly FatalAppExit(…)
(depending on the goal) from Usermode when the main application runs there
as this one seems to be one of this kind.
Regards
Kerem
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4837 (20100205) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4837 (20100205) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com