Selecting any option results in "Is a directory" and consequent exit
Closed this issue · 3 comments
Just pulled the recent updates from 09/25/24 (and thank you for the updates btw), but when I run ./discover, selecting any option result in the following errors - here are some examples:
...
Choice: 1
./discover.sh: line 628: /opt/discover: Is a directory
...
Choice: 3
./discover.sh: line 630: /opt/discover: Is a directory
...
Choice: 8
./discover.sh: line 635: /opt/discover: Is a directory
and the the main script exists... Please advise.
Just pulled the recent updates from 09/25/24 (and thank you for the updates btw), but when I run
./discover, selecting any option result in the following errors - here are some examples:... Choice: 1 ./discover.sh: line 628: /opt/discover: Is a directory... Choice: 3 ./discover.sh: line 630: /opt/discover: Is a directory... Choice: 8 ./discover.sh: line 635: /opt/discover: Is a directoryand the the main script exists... Please advise.
I had this issue this morning. I checked and the code on line 628 looks for discover.sh. I had an old repo that was coming up in the locate database: ie:
/opt/discover
/opt/discover-old
I renamed the /opt/discover-old/discover.sh file to something else (dscvr.sh) and then it worked.
However, now when I run it, it exits without error. I tried a passive and it always exits after it hits the second request.
==================================================================
ARIN
Email (1/46)
Names (2/46)
┌──(rootkali-vm1)-[/opt/discover]
Might be something else going on.
I found the problem, even when the previous discover folder is in Trash the old discover.sh is causing a problem... Looks like there can be no copies of discover.sh even in Trash... I think we can call it closed.
I have had some major updates in the past week. You should be good now.