Explore targets does'nt work anymore

[venethia]

What is your airgeddon version?

11.30

What is your Linux O.S. and which version?

Kali 6.8.11-1kali2 (2024-05-30) updated

Is your O.S. running in native mode or is a virtualized system? in that case, VMware? VirtualBox? Other?

WMware workstation player 17.5.2 build-23775571 on Windows 11 23H2.

Which is the chipset of your wireless card?

MediaTek MT7612U

Describe the issue and the steps to reproduce it

Never had problem until today.

The wireless adapter Alfa AWUS036ACM has always worked well. The 'secret' was to plug the usb adapter only after the VM was running. It worked perfectly for 1 year. Now the adapter is correctly recognized from Linux (command: lsusb) and from Airgeddon. I can set the monitor mode on without problem. But when I try to explore for targets nothing done. All blocked.

I keep blocked `here:

WPA/WPA2/WPA3 filter enabled in scan. When started, press [Ctrl+C] to stop... Press [Enter] key to continue...

I don't have problems with other wifi tools.

Thanks in advance.

[OscarAkaElvis]

Ok this is a known problem caused by a bug in the modern bash package (in version 5.2.21 as far as I know). But you are not blocked. Everything is working normal. It is just that you can't see it. For some reason, the xterm windows are opened in a collapsed way. This way:

You can just expand it and you'll see that everything is ok. This is a non-related to airgeddon problem. The bug is not ours. Anyway here you are some workarounds until they fix it:

1. Go to your airgeddon dir using cd command (where you cloned it, or on /usr/share/airgeddon if got it by apt), and launch it this way: bash --posix airgeddon.sh . You'll see the windows are opening again as normal.
2. Just use it as it is and expand the windows manually
3. Set tmux instead of xterm on the airgeddon options or setting it manually on the hidden .airgeddonrc file as explained here. I mean, setting AIRGEDDON_WINDOWS_HANDLING=tmux

We should be patient until the problem is fixed. I know that @alexl83 already reported it somewhere. I'll close this because as I said is something out of our hands and our scope.

EDIT Definitely the best solution is the referenced one in the post below until an official fix by Debian: https://github.com/v1s1t0r1sh3r3/airgeddon/issues/612#issuecomment-2313223702

[alexl83]

This is the debian bug entry that tracks this issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078556

[OscarAkaElvis]

I saw you @alexl83 created a patched version of the "broken" bash 5.2.21 package and put it on your GitHub repo. I tested it and it works well. I'd recommend to use this instead of the --posix workaround because the --posix stuff is changing the behaviour of some things inside airgeddon and could cause errors on some things (even if the xterm windows are opening well).

So the best advice I'd give is:

1. Just download the bash fixed package from here: https://github.com/alexl83/alexl83.github.io/raw/main/pool/main/b/bash/bash_5.2.21-2.1+b3_amd64.deb
2. Install it on your debian based system (I tested it on Kali Linux and it worked very well) using this command: dpkg -i bash_5.2.21-2.1+b3_amd64.deb
3. Wait until an official fix come from Debian

Thanks for your work on this @alexl83 . Great contribution! 🤟

[alexl83]

I saw you @alexl83 created a patched version of the "broken" bash 5.2.21 package and put it on your GitHub repo. I tested it and it works well. I'd recommend to use this instead of the --posix workaround because the --posix stuff is changing the behaviour of some things inside airgeddon and could cause errors on some things (even if the xterm windows are opening well).

So the best advice I'd give is:

1. Just download the bash fixed package from here: https://github.com/alexl83/alexl83.github.io/raw/main/pool/main/b/bash/bash_5.2.21-2.1+b3_amd64.deb

2. Install it on your debian based system (I tested it on Kali Linux and it worked very well) using this command: `dpkg -i bash_5.2.21-2.1+b3_amd64.deb`

3. Wait until an official fix come from Debian

Thanks for your work on this @alexl83 . Great contribution! 🤟

Happy to help 🙏🏻

[youthanazia]

Hi,

https://github.com/alexl83/alexl83.github.io/raw/main/pool/main/b/bash/bash_5.2.21-2.1+b3_amd64.deb

Is there a fix for 32bit/i386?

Thanks

[OscarAkaElvis]

Maybe you can use the bash --posix airgeddon.sh for now. Not sure if @alexl83 compiled it for 32bits. At least is not in the repo.

[youthanazia]

Ok, thanks for your help.

[alexl83]

Maybe you can use the bash --posix airgeddon.sh for now. Not sure if @alexl83 compiled it for 32bits. At least is not in the repo.

cross-compiled i386 arch and uploaded to repo I strongly suggest to add repo to sources.list and use version 5.2.32 as it's more up-to date, nevertheless 5.2.21 is available too

Sources can be checked from repo itself Hope it helps :)

Ale

[youthanazia]

5.2.32 i386 works great.

Thank you