Skip to content
This repository has been archived by the owner on Oct 21, 2024. It is now read-only.

Remcom services left behind #30

Open
rustyscottweber opened this issue Apr 1, 2014 · 0 comments
Open

Remcom services left behind #30

rustyscottweber opened this issue Apr 1, 2014 · 0 comments

Comments

@rustyscottweber
Copy link

Currently, there is a problem with remcom service. If you run the service and then something happens where you are unable to remove the service, for example: a reboot, the service is leaked and tends to clutter up the service console and registry. Since certain tools like impacket python module will spawn lots of remcom services all with a randomly generated name for each service this tends to be a problem. It sounds like it would be a good idea to have just one service which can spawn multiple processes and letting this service start with the machine, but I am not sure how feasible this idea is.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant