Remove unnecessary remote ops check #185
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Impacket checks if remote ops is already running on the target system. If it does it does not "start it again", therefore we can remove the check in nxc.
Besides that, it intruduces a bug where, if we want to use remote ops, but it has been closed without setting the
self.remote_ops
variable to None, nxc thinks remote_ops are running, leading to a crash inside impacket. This happens for example if the target has not rrp running and we do--sam
together with--lsa
(lsa dump will not succeed, because of missing remote ops).