-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support reloading of custom modules using "reload" #241
Comments
This shouldn't be too difficult to implement. I should be able to simply remove the reference from |
I implemented a first-pass on this in the referenced PR. @DanaEpp if you have the time/interest, I'd appreciate you giving that branch a try. You should be able to either use Thanks for the suggestion. This is a really good feature to have for debugging, and I don't know why it didn't occur to me before! 👍 |
Thanks for such a quick turnaround Caleb! This will be an awesome feature. I am right in the middle of writing a module as we speak, so this is timely. I'll try to test this branch tonight. |
When doing custom module development it is rather tedious to have to restart pwncat and establish a new session just to reload the changes to the module code. It would be nice to do
reload /path/to/modules
, or to otherwise auto-reload when a module file has been altered.Alternatively, having an option during dev to pass a switch to pwncat-cs to have it reload modules from disk on every "run", or offer a new command like
run-dev
that would always fetch the module code would be useful.The text was updated successfully, but these errors were encountered: