search

Abacus-Group-RTO / legion

Legion is an open source, easy-to-use, super-extensible and semi-automated network penetration testing tool that aids in discovery, reconnaissance and exploitation of information systems.
GNU General Public License v3.0
1.03k stars 170 forks source link

Everything in the gui except for the log is blank. #259

Open GuysHowDoIUseLegion opened 2 months ago

GuysHowDoIUseLegion commented 2 months ago

I've tried running legion through the terminal and just opening it from the linux "start menu", I don't know what it's actually called, and both times, no matter what I put in, the gui just won't show anything. The terminal and log are showing everything Legion is doing like normal, but the rest of the gui just looks how it does when it was just opened. My system is completely up to date. I used These instructions to update nmap to what I think is the newest version. I'm not really sure what's going on, any help would be appreciated.

kerboom4826 commented 1 month ago

Im having the exact same problem.

sscottgvit commented 1 month ago

@GuysHowDoIUseLegion @kerboom4826 Can you post a screenshot and the log?

kerboom4826 commented 1 month ago

I fixed it by reinstalling

On Wed, Oct 23, 2024, 10:37 AM S. Scott @.***> wrote:

@GuysHowDoIUseLegion https://github.com/GuysHowDoIUseLegion @kerboom4826 https://github.com/kerboom4826 Can you post a screenshot and the log?

— Reply to this email directly, view it on GitHub https://github.com/GoVanguard/legion/issues/259#issuecomment-2432660615, or unsubscribe https://github.com/notifications/unsubscribe-auth/BL5GNGRDNGN5SAPL4OXLL2DZ467BZAVCNFSM6AAAAABOTWRX5OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZSGY3DANRRGU . You are receiving this because you were mentioned.Message ID: @.***>

GuysHowDoIUseLegion commented 1 month ago

Ok, to preface, I ran it with a 172 address because I was hot spotting off of my phone when I ran the scan, but this is exactly how it looks when I run scans on anything else.

(Edit): The scan I ran was just 172.20.10.0/24

Here is a screenshot of what legion looks like after a completed scan: Blank_Legion_Problem Here is what the terminal looks like (this is how it normally looks to me): Legion_Terminal And here is what was in the log: Creating temporary project at application start... Established SQLite connection on file '/root/.local/share/legion/tmp/legion-u5bn53lk.legion' Wordlist was created/opened: /root/.local/share/legion/tmp/legion-qw5avx70-tool-output/legion-usernames.txt Wordlist was created/opened: /root/.local/share/legion/tmp/legion-qw5avx70-tool-output/legion-passwords.txt Loading settings file.. Legion started successfully. runStagedNmap called for stage 1 Adding process: <db.entities.process.process object at 0x7ffb2aaeebd0> Queuing: nmap -T4 -sV -sSU -O -p T:80,81,443,4443,8080,8081,8082 -vvvv 172.20.10.0/24 -oA /root/.local/share/legion/tmp/legion-0f4hxfw0-running/nmap/20241024020206262421-nmapstage1 Running: nmap -T4 -sV -sSU -O -p T:80,81,443,4443,8080,8081,8082 -vvvv 172.20.10.0/24 -oA /root/.local/share/legion/tmp/legion-0f4hxfw0-running/nmap/20241024020206262421-nmapstage1 runCommand called for stage 1 runCommand connected for stage 1 Process 1 is done! Storing process output into db: <db.entities.processOutput.process_output object at 0x7ffb2ab30950> Halting process panel update timer as all processes are finished. runStagedNmap called for stage 2 Adding process: <db.entities.process.process object at 0x7ffb2ab30530> Queuing: nmap -T4 -sV -sSU -O -p T:25,135,137,139,445,1433,3306,5432,U:137,161,162,1434 -vvvv 172.20.10.0/24 -oA /root/.local/share/legion/tmp/legion-0f4hxfw0-running/nmap/20241024020206790095-nmapstage2 Running: nmap -T4 -sV -sSU -O -p T:25,135,137,139,445,1433,3306,5432,U:137,161,162,1434 -vvvv 172.20.10.0/24 -oA /root/.local/share/legion/tmp/legion-0f4hxfw0-running/nmap/20241024020206790095-nmapstage2 runCommand called for stage 2 runCommand connected for stage 2 Process 2 is done! Storing process output into db: <db.entities.processOutput.process_output object at 0x7ffb2ab32540> Halting process panel update timer as all processes are finished. runStagedNmap called for stage 3 Adding process: <db.entities.process.process object at 0x7ffb2ab03ce0> Queuing: nmap -sV --script=vulners -vvvv 172.20.10.0/24 -oA /root/.local/share/legion/tmp/legion-0f4hxfw0-running/nmap/20241024020207107398-nmapstage3 Running: nmap -sV --script=vulners -vvvv 172.20.10.0/24 -oA /root/.local/share/legion/tmp/legion-0f4hxfw0-running/nmap/20241024020207107398-nmapstage3 runCommand called for stage 3 runCommand connected for stage 3 Process 3 is done! Storing process output into db: <db.entities.processOutput.process_output object at 0x7ffb2ab32ab0> Halting process panel update timer as all processes are finished. runStagedNmap called for stage 4 Adding process: <db.entities.process.process object at 0x7ffb2ab03ce0> Queuing: nmap -T4 -sV -sSU -O -p T:23,21,22,110,111,2049,3389,8080,U:500,5060 -vvvv 172.20.10.0/24 -oA /root/.local/share/legion/tmp/legion-0f4hxfw0-running/nmap/20241024020207326171-nmapstage4 Running: nmap -T4 -sV -sSU -O -p T:23,21,22,110,111,2049,3389,8080,U:500,5060 -vvvv 172.20.10.0/24 -oA /root/.local/share/legion/tmp/legion-0f4hxfw0-running/nmap/20241024020207326171-nmapstage4 runCommand called for stage 4 runCommand connected for stage 4 Process 4 is done! Storing process output into db: <db.entities.processOutput.process_output object at 0x7ffb2ab33710> Halting process panel update timer as all processes are finished. runStagedNmap called for stage 5 Adding process: <db.entities.process.process object at 0x7ffb2ab022a0> Queuing: nmap -T4 -sV -sSU -O -p T:0-20,24,26-79,81-109,112-134,136,138,140-442,444,446-1432,1434-2048,2050-3305,3307-3388,3390-5431,5433-8079,8081-29999 -vvvv 172.20.10.0/24 -oA /root/.local/share/legion/tmp/legion-0f4hxfw0-running/nmap/20241024020207650827-nmapstage5 Running: nmap -T4 -sV -sSU -O -p T:0-20,24,26-79,81-109,112-134,136,138,140-442,444,446-1432,1434-2048,2050-3305,3307-3388,3390-5431,5433-8079,8081-29999 -vvvv 172.20.10.0/24 -oA /root/.local/share/legion/tmp/legion-0f4hxfw0-running/nmap/20241024020207650827-nmapstage5 runCommand called for stage 5 runCommand connected for stage 5 Process 5 is done! Storing process output into db: <db.entities.processOutput.process_output object at 0x7ffb2ab59460> Halting process panel update timer as all processes are finished. runStagedNmap called for stage 6 Adding process: <db.entities.process.process object at 0x7ffb2ab33710> Queuing: nmap -T4 -sV -sSU -O -p T:30000-65535 -vvvv 172.20.10.0/24 -oA /root/.local/share/legion/tmp/legion-0f4hxfw0-running/nmap/20241024020208002924-nmapstage6 Running: nmap -T4 -sV -sSU -O -p T:30000-65535 -vvvv 172.20.10.0/24 -oA /root/.local/share/legion/tmp/legion-0f4hxfw0-running/nmap/20241024020208002924-nmapstage6 runCommand called for stage 6 Process 6 is done! Storing process output into db: <db.entities.processOutput.process_output object at 0x7ffb2ab5a570> Halting process panel update timer as all processes are finished.