Ability to run as a windows service about reverse_ssh HOT 13 CLOSED

Existing state of this shamblesdelightful example of a project:

from reverse_ssh.

The project already uses what you describe to determine if its in a windows service.

from reverse_ssh.

Whats missing seems to be the start command

from reverse_ssh.

Oh. Alright ill tweak that and test it

from reverse_ssh.

For some additional info, rssh can install itself as a service, and I have used it there. So Im not sure what the issue is here.

from reverse_ssh.

The issue is described in the original comment, where you are hijacking an existing service to assume its identity. That is, for example, you have write access over a binary or a binary's location used by a service that isn't presently running or you can stop and start. You replace the binary then start the service - at present this will fail with the message in the prior screenshot.

from reverse_ssh.

Hm, thanks.

I think it may be due to this: golang/go#44921

As I cant spot anything that would make rssh unable to communicate as a service otherwise

from reverse_ssh.

Hmm okay. Ill do some testing - see if it functions properly with a low privilege service

from reverse_ssh.

Please try with the unstable branch, I've just bumped the modules

from reverse_ssh.

Just tried and it starts fine now, ta. Working well with nt authority\system coming through for a service run as LocalSystem. However, it won't stop properly:

Somewhat debatable if this is an issue - a service that won't stop is possibly suspicious, but stopping a rssh client is not really what you want anyway

from reverse_ssh.

It can still be stopped by killing the client from the rssh catcher interface. I'm fine to close this issue, ta.

from reverse_ssh.

Ah yes, actually thats a bug funny enough. The break statement is breaking the switch rather than the outer for loop

from reverse_ssh.

This change is now on unstable

from reverse_ssh.