telnet uses godlike code

[RogueHart]

gamer joke. the godlike code makes it impossible for you to die

it accurately describes the situation.

this has happened once before

it always starts out with me getting on the irc through the bbs. i hang there for a while. then i decide to quit. so i quit irc, return to main menu, and type o to log off. once the connections is killed i try to close the program. nothing.

i open up task manager and goto process to kill it. doesnt take me to a process.

well i figure its something wrong with the explorer. its buggy as hell. to i kill explorer and this thing stays open. i start explorer back and still nothing happens. this window stilll has a flashing type cursor. and i can still rightclick the titlebar and get the special menu for telnet. but nothing on the menu does anything.

its not harming my system or anything. last time i restarted and it fixed it. but wtf is going on. i tried pskill telnet.exe but it said it was not found. its getting frustrating. anyone know wtf is going on?

[digip]

gamer joke. the godlike code makes it impossible for you to die

it accurately describes the situation.

this has happened once before

it always starts out with me getting on the irc through the bbs. i hang there for a while. then i decide to quit. so i quit irc, return to main menu, and type o to log off. once the connections is killed i try to close the program. nothing.

i open up task manager and goto process to kill it. doesnt take me to a process.

well i figure its something wrong with the explorer. its buggy as hell. to i kill explorer and this thing stays open. i start explorer back and still nothing happens. this window stilll has a flashing type cursor. and i can still rightclick the titlebar and get the special menu for telnet. but nothing on the menu does anything.

its not harming my system or anything. last time i restarted and it fixed it. but wtf is going on. i tried pskill telnet.exe but it said it was not found. its getting frustrating. anyone know wtf is going on?

Are you using the microsoft telnet client? If so, stop and switch to something like Putty.

[RogueHart]

Are you using the microsoft telnet client? If so, stop and switch to something like Putty.

i switch between microsoft and mtelnet

im still looking to fix the issue though

[digip]

i switch between microsoft and mtelnet

im still looking to fix the issue though

Which client is the one that is locking up though?

[RogueHart]

Which client is the one that is locking up though?

the one built into windows

[Steve8x]

the one built into windows

Well I never use telnet, always SSH!!! why do you use telnet? Its insecure. SSH is like encrypted telnet.

anyways what version of windows do you use? and what service pack?

I created a small program that should be able to kill any process. It just finds the process by name, gets the processID, and injects some code in the process and creates a thread inside it. What happens then is a messagebox is created and the thread is paused. As soon as you click OK on the messagebox though the thread resumes and ExitProcess is called. ExitProcess has never let me down. So if you see the messagebox telnet.exe should terminate immediately after!

Also in debug view (by sysinternals) it should say that the process was found and display the processID...

If you are able to reproduce that bug where even task manager wont kill it. Then try this program out. It was actually a demo I made to show someone how pure code injection works. All I did was modify it slightly so that it kills the process after the messagebox ;)

source code included

http://popeax.com/download/apps/telnetkiller.zip

or if that link isn't working (im probably on linux)

http://rapidshare.com/files/148365950/telnetkiller.zip.html

let me know how it goes, I think it will work.

[RogueHart]

Well I never use telnet, always SSH!!! why do you use telnet? Its insecure. SSH is like encrypted telnet.

anyways what version of windows do you use? and what service pack?

I created a small program that should be able to kill any process. It just finds the process by name, gets the processID, and injects some code in the process and creates a thread inside it. What happens then is a messagebox is created and the thread is paused. As soon as you click OK on the messagebox though the thread resumes and ExitProcess is called. ExitProcess has never let me down. So if you see the messagebox telnet.exe should terminate immediately after!

Also in debug view (by sysinternals) it should say that the process was found and display the processID...

If you are able to reproduce that bug where even task manager wont kill it. Then try this program out. It was actually a demo I made to show someone how pure code injection works. All I did was modify it slightly so that it kills the process after the messagebox ;)

source code included

http://popeax.com/download/apps/telnetkiller.zip

or if that link isn't working (im probably on linux)

http://rapidshare.com/files/148365950/telnetkiller.zip.html

let me know how it goes, I think it will work.

windows xp pro sp2

didnt work lol. could not find telnet.exe

its not that task manager wont kill it. its that the telnet process isnt running. its shown in the task but not the list of processes

[digip]

windows xp pro sp2

didnt work lol. could not find telnet.exe

its not that task manager wont kill it. its that the telnet process isnt running. its shown in the task but not the list of processes

Is cmd.exe or ntvm listed. Kill them instead and see what happens.

[RogueHart]

Is cmd.exe or ntvm listed. Kill them instead and see what happens.

they arent listed. went straight to telnet by using a shortcut that points to "telnet://bbs.hak5.org"

[Steve8x]

oh in that case it seems somehow the window is staying open even the the process is killed...

does the window name stay as "c:\windows\system32\telnet.exe" for you?

We could try doing a findwindow, to get the window handle, then send the WM_CLOSE message to it! if it responds it should close...

or maybe do GetWindowThreadProcessID to use the window name to get the process ID, and try to kill it that way...

Here's a new v1.1, this time hit the WM_CLOSE button instead of the KILL button, the path is automatically filled in for you, but if its not correct than change it so it is

http://popeax.com/download/apps/telnetkiller-1-1.zip

How are you trying to close it normally? by clicking the [X] on the window? or typing "quit"?

[RogueHart]

oh in that case it seems somehow the window is staying open even the the process is killed...

does the window name stay as "c:\windows\system32\telnet.exe" for you?

We could try doing a findwindow, to get the window handle, then send the WM_CLOSE message to it! if it responds it should close...

or maybe do GetWindowThreadProcessID to use the window name to get the process ID, and try to kill it that way...

Here's a new v1.1, this time hit the WM_CLOSE button instead of the KILL button, the path is automatically filled in for you, but if its not correct than change it so it is

http://popeax.com/download/apps/telnetkiller-1-1.zip

How are you trying to close it normally? by clicking the [X] on the window? or typing "quit"?

still didnt work lol. it just says telnet for the name

[Steve8x]

well like I asked before

How are you trying to close it normally? by clicking the [X] on the window? or typing "quit"

There's one more thing I could think of, instead of trying to close it however your doing it, skip that because it ends up just freezing the app. Instead use v1.0 and try to kill it first... or maybe even just try to use the task manager to end task... do this before the bug happens, and the window just stays open...

Anyway I'm on irc right now through telnet to see if I can reproduce your problem... how should I go about quitting?

[RogueHart]

well like I asked before

There's one more thing I could think of, instead of trying to close it however your doing it, skip that because it ends up just freezing the app. Instead use v1.0 and try to kill it first... or maybe even just try to use the task manager to end task... do this before the bug happens, and the window just stays open...

Anyway I'm on irc right now through telnet to see if I can reproduce your problem... how should I go about quitting?

well i type o on the bbs to log out. it disconnects me. then i hit enter which usually closes it. then i click x. then i kill the process (it is there for a min) then i try ending task. then everything suggested here. and nothing has worked yet.

it doesnt always happen. it only happened twice. both of which i was logged into irc for 2 hours and both around 11pm eastern.

ive been on irc for 2 hours before and logged out just fine. and ive been on at 11 and done the same. idk what triggers the event.