You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 21, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: