Package Details: airgeddon-git r1895.e9775f8-1

Git Clone URL: https://aur.archlinux.org/airgeddon-git.git (read-only, click to copy)
Package Base: airgeddon-git
Description: Multi-use bash script for Linux systems to audit wireless networks
Upstream URL: https://github.com/v1s1t0r1sh3r3/airgeddon
Keywords: airgeddon bash hacking penetration pentesting testing wifi wireless
Licenses: GPL3
Conflicts: airgeddon-git
Provides: airgeddon-git
Submitter: xtonousou
Maintainer: xtonousou (OscarAkaElvis)
Last Packager: OscarAkaElvis
Votes: 5
Popularity: 0.010702
First Submitted: 2017-04-19 23:12
Last Updated: 2019-11-03 19:27

Dependencies (44)

Required by (0)

Sources (1)

Latest Comments

1 2 Next › Last »

OscarAkaElvis commented on 2019-06-05 10:37

By the way... maybe someone could add hostapd-wpe to the repos. That could be awesome. :)

OscarAkaElvis commented on 2019-06-05 10:35

Not exactly... the option of the menu can be launched using hashcat 3.0 for example without needing hashcat-utils. That's the reason it is not added as an optional dependency. It is checked internally before launching the attack once the option is selected and only depending of your hashcat version. The message is pretty clear as you can see and it should be enough for any user to handle what to do. Thanks anyway for the suggestions.

I'm glad mdk4 was added to the repos. nice! thanks.

pizzaman commented on 2019-06-05 09:35

community/hashcat-utils is also a dependency, I got this notification

The hashcat version you have installed (5.1.0) is greater or equal than 3.40 so you need to convert the capture files to "hccapx" format, airgeddon will do this automatically. To do this you need a converter that is not present on your system (hashcat-utils package), install it to be able to perform this attack

pizzaman commented on 2019-06-05 09:31

mdk4 package is now in AUR

OscarAkaElvis commented on 2019-05-26 19:23

Probably I have mdk4 package available due using of some nice repositories like ArchStrike and that caused the confusion for me.

Anyway, mdk3 is not what we want... and mdk not sure what is. Bear in mind that it is an optional dependency. It is not a serious problem. I'll prefer to wait till see if finally mdk4 package is packaged.

Thank you for reporting this to us and to the mdk package maintainer. Keep me updated about this please.

nac commented on 2019-05-26 19:15

I have notified the mdk3 maintainer that mdk4 is available: https://www.archlinux.org/packages/community/x86_64/mdk3/

nac commented on 2019-05-26 19:03

OscarAkaElvis the mdk4 package does not exist in the repositories. The dependency you have called out for airgeddon is broken. So I think it is a problem with this pacakge's PKGBUILD ( aka your package's problem )

I see the mdk3 package is available in the official repositories. And I see an mdk package available in the AUR.

I think you need to fix your PKGBUILD so that it correctly requires one of those two packages ( I'm not sure which one though ).

So to summarize, I think this is a problem with your package's PKGBUILD, because it requires a dependency that doesn't exist.

OscarAkaElvis commented on 2019-05-26 18:57

Not sure if there is something that I can do. If mdk4 package exist on the repositories to be installed by pacman I think everything is done on my side. Maybe you want to notify it to Arch staff or to somebody in charge. :S

nac commented on 2019-05-26 18:47

Hey OscarAkaElvis, the mdk(4) dependency of this package is still broken. Can you please check why?

nac commented on 2019-05-19 01:23

@OscarAkaElvis, from what I understand, it's read because it is not a package.

pacman -Ss mdk4 returns 0 results.

https://www.archlinux.org/packages/?sort=&q=mdk4&maintainer=&flagged=

also shows 0 results.

Maybe the mdk package used to be called mdk4 and was changed recently? Not sure, but this seems like airgeddon is not set up to handle the arch linux mdk package dependency correctly.