disable task manager when called....
-
You can't capture the key combination alt+control+delete. It's handled by the system and never reaches your application.
Despite everything, the person most likely to be fooling you next is yourself.
hey you pple out threre.... i am not a hacker of some kind u think.... i am making a client program for the lab monitoring system where the student is given with a login screen and if the task manager is avaliable he would end my application so i was asking....and i have found way for disabling the task manager by capturing or by global hooking .... thans...
-
This question has been asked *several* times, and I can't see any reason for disabling the task manager. I don't think the end-user would be too pleased if their task manager got disabled. Why would you wanna do this?
Kristian Sixhoej
hey you pple out threre.... i am not a hacker of some kind u think.... i am making a client program for the lab monitoring system where the student is given with a login screen and if the task manager is avaliable he would end my application so i was asking....and i have found way for disabling the task manager by capturing or by global hooking .... thans...
-
hey you pple out threre.... i am not a hacker of some kind u think.... i am making a client program for the lab monitoring system where the student is given with a login screen and if the task manager is avaliable he would end my application so i was asking....and i have found way for disabling the task manager by capturing or by global hooking .... thans...
As we keep saying, disabling the task manager is done by group policy, if the lab doesn't want students to have access, they need to set this up, your code can't do it.
Christian Graus Driven to the arms of OSX by Vista.
-
As we keep saying, disabling the task manager is done by group policy, if the lab doesn't want students to have access, they need to set this up, your code can't do it.
Christian Graus Driven to the arms of OSX by Vista.
-
hey you pple out threre.... i am not a hacker of some kind u think.... i am making a client program for the lab monitoring system where the student is given with a login screen and if the task manager is avaliable he would end my application so i was asking....and i have found way for disabling the task manager by capturing or by global hooking .... thans...
I didn't say anything at all about what I think that you are or not are. I only pointed out that it's impossible to capture the alt+control+delete key combination. What ever you are or not are, doesn't change this fact.
Despite everything, the person most likely to be fooling you next is yourself.
-
I didn't say anything at all about what I think that you are or not are. I only pointed out that it's impossible to capture the alt+control+delete key combination. What ever you are or not are, doesn't change this fact.
Despite everything, the person most likely to be fooling you next is yourself.
how about using this for disabling the taskman..... impossible is nothin System.IO.File.Open("taskmgr.exe", FileMode.Open, FileAccess.ReadWrite, FileShare.None);
-
A policy can also ban access to the command line, can't it ?
Christian Graus Driven to the arms of OSX by Vista.
-
how about using this for disabling the taskman..... impossible is nothin System.IO.File.Open("taskmgr.exe", FileMode.Open, FileAccess.ReadWrite, FileShare.None);
How does opening it disable it ?
Christian Graus Driven to the arms of OSX by Vista.
-
How does opening it disable it ?
Christian Graus Driven to the arms of OSX by Vista.
modify the fileshare to grant total acess,,,
-
A policy can also ban access to the command line, can't it ?
Christian Graus Driven to the arms of OSX by Vista.
-
modify the fileshare to grant total acess,,,
It seems to me that you're kind of dense. As has been said, the ONLY way to totally block access, is with group policies. I can think of lots of other things you could try, but none of them are fool proof. So long as the student is not locked down on the PC, they will find a way around what you're trying to do. Such as, writing a program that finds the process and kills it, or using the command line to kill it ( as someone else said ). If this is homework, then stop going in circles, your teacher should know that what you're trying to do won't work. If it's a paid job, then tell the people you are robbing that they are just stupid enough to deserve to be working with you.
Christian Graus Driven to the arms of OSX by Vista.
-
how about using this for disabling the taskman..... impossible is nothin System.IO.File.Open("taskmgr.exe", FileMode.Open, FileAccess.ReadWrite, FileShare.None);
If you have ReadWrite access to taskmgr.exe, you're logged in as administrator. Administrators can do what they want with the system. You're just trying to make 'harmful' UI unavailable, but there's always a way around it. I've seen kiosk mode web browsers that tried to take the same approach. Usually all it takes to get around them is to browse to a PDF document, click Adobe's "Save" button, and in the Save As dialog, browse to "C:\windows\system32\cmd.exe" and right-click>Run. You'll never find ALL 'harmful' UI elements! What you really should do is disable harmful ACTIONS, not UI. Use group policy and disable task manager, the command line, etc. And don't log in as administrator: Administrators can do everything !
-
It seems to me that you're kind of dense. As has been said, the ONLY way to totally block access, is with group policies. I can think of lots of other things you could try, but none of them are fool proof. So long as the student is not locked down on the PC, they will find a way around what you're trying to do. Such as, writing a program that finds the process and kills it, or using the command line to kill it ( as someone else said ). If this is homework, then stop going in circles, your teacher should know that what you're trying to do won't work. If it's a paid job, then tell the people you are robbing that they are just stupid enough to deserve to be working with you.
Christian Graus Driven to the arms of OSX by Vista.
i am dosing this work as a graduation project.... and i do have knowkedge that task manaver can be accessed sinply by renaming the System.IO.File.Open("renamed_taskmagr.exe".... but i should try some thing to help me in not ending my program by the task man at the start up by the student who should login and provide his information...
-
If you have ReadWrite access to taskmgr.exe, you're logged in as administrator. Administrators can do what they want with the system. You're just trying to make 'harmful' UI unavailable, but there's always a way around it. I've seen kiosk mode web browsers that tried to take the same approach. Usually all it takes to get around them is to browse to a PDF document, click Adobe's "Save" button, and in the Save As dialog, browse to "C:\windows\system32\cmd.exe" and right-click>Run. You'll never find ALL 'harmful' UI elements! What you really should do is disable harmful ACTIONS, not UI. Use group policy and disable task manager, the command line, etc. And don't log in as administrator: Administrators can do everything !
thans but u are telling to block harmful actions not the programs... but i think it is easy to block the taskman rather than allowing it to open and then block it from ending my applications process..... if such code exists or if i could hide my applications process from the taskman like virus do then also it would be more complex code generation... so the KISS way.... block the taskmgr.exe....
-
thans but u are telling to block harmful actions not the programs... but i think it is easy to block the taskman rather than allowing it to open and then block it from ending my applications process..... if such code exists or if i could hide my applications process from the taskman like virus do then also it would be more complex code generation... so the KISS way.... block the taskmgr.exe....
The KISS way is to open the group policy options and click on 'disable task manager'.
-
The KISS way is to open the group policy options and click on 'disable task manager'.
nice what does the KISS way tel about doing the same gpedit.msc way from c# code.. hope its simple....!
-
thans but u are telling to block harmful actions not the programs... but i think it is easy to block the taskman rather than allowing it to open and then block it from ending my applications process..... if such code exists or if i could hide my applications process from the taskman like virus do then also it would be more complex code generation... so the KISS way.... block the taskmgr.exe....
All right. If you're so bloody clever figure out the code for yourself. You've been told by several experts that the way to do this is to use policies to cope with it, and yet you persist in arguing. Fine - write the code, post it up and then see how long it is before somebody finds a way to work round it (btw - somebody could rename tastmanager.exe and launch that so any approach you had to block it by name would fail).
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
-
i am dosing this work as a graduation project.... and i do have knowkedge that task manaver can be accessed sinply by renaming the System.IO.File.Open("renamed_taskmagr.exe".... but i should try some thing to help me in not ending my program by the task man at the start up by the student who should login and provide his information...
max.4u wrote:
but i should try some thing to help me in not ending my program by the task man at the start up by the student who should login and provide his information...
If you want to do *something*, write a service that checks if the application has closed, and re-opens it. That might make your teacher happy, but if he's not a moron, he'll know that whatever you do, was a waste of time, it's not the place to try to enforce what you want. Overall, you are wasting a lot of time on something really stupid. If your teacher did not ask you to do this, then stop wasting your time, as you've been told over and over, you can't do it this way, not in a foolproof way.
Christian Graus Driven to the arms of OSX by Vista.
-
All right. If you're so bloody clever figure out the code for yourself. You've been told by several experts that the way to do this is to use policies to cope with it, and yet you persist in arguing. Fine - write the code, post it up and then see how long it is before somebody finds a way to work round it (btw - somebody could rename tastmanager.exe and launch that so any approach you had to block it by name would fail).
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
hey man you are on fire... why dont you just help by telling how to call the policy manager from the code and disable the taskmanager.....
-
All right. If you're so bloody clever figure out the code for yourself. You've been told by several experts that the way to do this is to use policies to cope with it, and yet you persist in arguing. Fine - write the code, post it up and then see how long it is before somebody finds a way to work round it (btw - somebody could rename tastmanager.exe and launch that so any approach you had to block it by name would fail).
"WPF has many lovers. It's a veritable porn star!" - Josh Smith
hello.. am extreamly sorry for whats happening here... i was only making new ways of doing the thing.... sorry if i have hurted any one.... once more...