Jump to content
Mr. Green Gaming

Disable people watching over your shoulder when you are on a computer


ikt

Recommended Posts

Physically:

1. Turn around

2. Break their arms

e-method:

1: Open notepad

2: Type in this:

tasklist
@echo off
set /p Input=Enter ID:
taskkill /f /pid %Input%

3: Save the shit as kill.bat

4: Copy it onto a portable medium to transport it to a place where you, for example, can't download/create .bat files, but can open your own files

5: Execute the .bat file

6: Just type in the process ID you want to kill (teamviewer, for example)

7: Hit enter

8: Watch porn on your work without getting caught! (you still need to watch your physical back, though)

Edited by ikt
Link to comment

What... is this for?

What the heck is this anyway?

At some locations, for example, on your work or at school, people tend to monitor their employees/students. At my school, for example, if you go on any sites that do not have to do something with school, you'll get banished as soon as the people watching you press their big red "kill" button. Your account will be suspended and such.

If you kill that monitoring programm, everything will be fine and nobody can touch you, because they can't see you.

Link to comment
  • Greens

Physically:

1. Turn around

2. Break their arms

e-method:

1: Open notepad

2: Type in this:

tasklist
@echo off
set /p Input=Enter ID:
taskkill /f /pid %Input%

3: Save the shit as kill.bat

4: Copy it onto a portable medium to transport it to a place where you, for example, can't download/create .bat files, but can open your own files

5: Execute the .bat file

6: Just type in the process ID you want to kill (teamviewer, for example)

7: Hit enter

8: Watch porn on your work without getting caught! (you still need to watch your physical back, though)

Haha, in my college we can do whatever we want on the PC (or almost), as long as it's outside of the lessons :V

Link to comment

This method doesn't work in my case, cmd.exe is blocked (blocks .bat files before they can execute code) and the monitoring software relaunches itself as soon as it's terminated.

You can prevent relaunching by killing both monitor processes at the same time. Although that's quite impossible through cmd.

Link to comment

This method doesn't work in my case, cmd.exe is blocked (blocks .bat files before they can execute code) and the monitoring software relaunches itself as soon as it's terminated.

You can prevent relaunching by killing both monitor processes at the same time. Although that's quite impossible through cmd.

The main problem is that I can't do anything through CMD. If I could, I might've been able to launch a "dummy" process that has the same name, and pray the relaunching process doesn't check the monitoring .exe's integrity.

Link to comment

This method doesn't work in my case, cmd.exe is blocked (blocks .bat files before they can execute code) and the monitoring software relaunches itself as soon as it's terminated.

You can prevent relaunching by killing both monitor processes at the same time. Although that's quite impossible through cmd.

The main problem is that I can't do anything through CMD. If I could, I might've been able to launch a "dummy" process that has the same name, and pray the relaunching process doesn't check the monitoring .exe's integrity.

True. That's where reverse engineering comes in.

Link to comment

This method doesn't work in my case, cmd.exe is blocked (blocks .bat files before they can execute code) and the monitoring software relaunches itself as soon as it's terminated.

You can prevent relaunching by killing both monitor processes at the same time. Although that's quite impossible through cmd.

The main problem is that I can't do anything through CMD. If I could, I might've been able to launch a "dummy" process that has the same name, and pray the relaunching process doesn't check the monitoring .exe's integrity.

True. That's where reverse engineering comes in.

Blocks .bat files before they can execute code... I might've been able to launch a "dummy" process... Monitoring .exe's integrity... Reverse engineering...

Right. I understood everything.

Might try to use this at school.

Link to comment

This method doesn't work in my case, cmd.exe is blocked (blocks .bat files before they can execute code) and the monitoring software relaunches itself as soon as it's terminated.

You can prevent relaunching by killing both monitor processes at the same time. Although that's quite impossible through cmd.

The main problem is that I can't do anything through CMD. If I could, I might've been able to launch a "dummy" process that has the same name, and pray the relaunching process doesn't check the monitoring .exe's integrity.

True. That's where reverse engineering comes in.

Or just tear the harddrive out if you want to disable the computer so badly.

Link to comment

I don't know how CMD is blocked at your places, but it's blocked here too. Not the process though. If you open up CMD, a message will appear within it "Disabled by administrator", a red light will start blinking and one of the people monitoring the computer place will come visit you and slap you around.

Unless you're awesome in coolfacing.

Link to comment

The newest version of Novell blocks everything. The older version we had at school last year blocked cmd.exe just a tad too late, so it could still execute some quick commands. This allowed people to replace "sethc.exe" (sticky key stuff) with cmd.exe, and that way you could run cmd.exe by pressing shift 5 times before logging in (before login Novell isn't monitoring yet).

It's not possible to replace sethc.exe anymore because of a Windows update. The positive side of Novell is that Windows updates are always installed late because they only update Windows when a new version of Novell comes out.

Ywa, I am in a public school.

Link to comment

I go to a public school and they are fucking IT nazis. Just about everything is blocked even google x4 :o We could use .bat scripts until last year. W managed to copy the teacher desktop because they had access to all user data through desktop short cuts and we distributed some batch pranks but then someone got hold of and spread the shrotcuts the the whole school and it got traced back to me :(

Now we are using .vbs but with practicaly no knowledge of it there isn't much fun to be had. One thing i did find out is that you could make a vbs and save it on a usb with autorun to make it continualy press ctrl+shit+esc at once and because task manager is blocked error messages just keep coming up on screen. But as far as doing anything productive with it i don't know were to begin.

Link to comment

Physically:

1. Turn around

2. Break their arms

e-method:

1: Open notepad

2: Type in this:

tasklist
@echo off
set /p Input=Enter ID:
taskkill /f /pid %Input%

3: Save the shit as kill.bat

4: Copy it onto a portable medium to transport it to a place where you, for example, can't download/create .bat files, but can open your own files

5: Execute the .bat file

6: Just type in the process ID you want to kill (teamviewer, for example)

7: Hit enter

8: Watch porn on your work without getting caught! (you still need to watch your physical back, though)

tCp90.gif

Link to comment
  • 3 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...