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
There appears to be an issue when trying to kill a job by it's ID. I can reliably reproduce it but only for auxiliary modules (sock4a and socks5) while others like exploit/multi/handler can be killed by it's ID.
To reproduce it:
Start msfconsole
Start an auxiliary server module
Find it's job ID with the output of jobs
Try to kill the specific job using either jobs -k <ID> or kill <ID>, both are exhibiting the same behavior
I should have noted that killing all jobs with jobs -K does not exhibit the same issue. Also verified that the auxiliary/server/capture/vnc module is having the same issue.
Steps to reproduce
There appears to be an issue when trying to kill a job by it's ID. I can reliably reproduce it but only for auxiliary modules (sock4a and socks5) while others like exploit/multi/handler can be killed by it's ID.
To reproduce it:
msfconsole
jobs
jobs -k <ID>
orkill <ID>
, both are exhibiting the same behaviorRC Script
Expected behavior
The job whose ID is specified should be killed.
Current behavior
Metasploit is throwing a stack trace and not killing the job.
System stuff
Metasploit version
fa496b939550a5b04dbe19df9f47d16eebc08d40 (HEAD -> master, upstream/master) automatic module_metadata_base.json update
gI installed Metasploit with:
OS
Fedora 32 x64
The text was updated successfully, but these errors were encountered: