BlackArch / blackarch

An ArchLinux based distribution for penetration testers and security researchers.
https://www.blackarch.org
Other
2.83k stars 571 forks source link

hundred of tools blackarch don't have #3461

Closed hassan-salloum closed 2 years ago

hassan-salloum commented 2 years ago

Hi, i have over 100 hundred tools that i found blackrach don't have them installed

so please, this is a safe excel table no malicious things and inside it you will find in the first sheet, a column mention that tools that blackarch don't have Weapons4Pentesters.xlsx

i hope in your next upg to add these tools

/|\Vraihack

noraj commented 2 years ago

Hi, thanks for the idea

  1. It seems that 95%+ of the tools that are not included on BA are not included in Kali neither so those are tools which are maybe unfamous or of low quality
  2. Many tools in your list seems not relevant or you didn't looked carefully, examples:
    • Covenant: it's a C# webapp tool so it can only be installed on Windows, it will probably never run on any linux system with mono
    • Octopus is a web app, BA includes mostly CLI tools but very few webapps because there are often very complex with complex deployment and lot of dependencies, in many case upstream offer a docker image. Putting them as a system package makes little sense in most cases.
    • heartbeat no a security tool so it's not the purpose of a pentest/infosec distro to include every utility on earth
    • CobaltStrike: another web app, and https://github.com/trewisscotch/CobaltStr4.4 is an illegal and unoficial repository
    • DNSExplorer: low quality tool, there a dozens of better alternatives already packaged on BA
    • SubEvil: low quality OSINT tool, there a dozens of better alternatives already packaged on BA
    • DOME does not look bad at first glance but there a hundreds of people redoing their own sub-domaine enum tool or OSINT tool so we can't package them all and better, more stable, more featurful and famous alternatives are already packaged
    • linpeas and winpeas: you say they are not included but say peass is included, actually yeah peass is included and peass is the master project that includes both linpeas and winpeas, linpeas is included in /usr/share/peass so you can copy n deploy on a target, winpeas should be included in /usr/share/windows/peass/ but it seems there is a bug
    • privoxy is included in AL so by extension in BA too
    • squid is included in AL so by extension in BA too
    • wifite: wifite is included in BA
    • OpenVAS: it's in AUR https://wiki.archlinux.org/title/OpenVAS
    • etc.

I as far as I look and pick random tools in your list it's either already included in BA or not relevant.

Please can you open a PR per tools that could be included BUT only those who follow the rules edited here https://github.com/BlackArch/blackarch/issues/2842 and also check they are not already included.

I'll close this issue, even if the list was only including relevant tools a xlsx containing hundreds of tools is not actionable and trackable. So please open individual requests for each relevant tool not already included.

hassan-salloum commented 2 years ago

Hi @noraj thanks for the reply:

On what metrics you base on to check if a tools is low quality or not ? thank you again

noraj commented 2 years ago

Covenant is a C2 framework and i am using it actually on kali linux

Kali packages covenant-kbx using kaboxer so they had to package it in a container rather than a proper .deb because the tool is just impossible to package and maintain correctly otherwise. yet they had to a tons of extra stuff and patches.

On what metrics you base on to check if a tools is low quality or not ?

Quick and dirty PoCs or all-in-one scripts, wrapper scripts that are just calling other tools and slightly modifying the output, generally those are shorts (~100-200 LoC in one file), the repository are either a few day young with nearly no stars or old and unmaintained with very few commits. There are ton of "I did a nmap-like myself" that are either pure crap or wrapper calling nmap. We already saw hundreds or sub-domain enum scripts that are doing 5% of what amat or findomains (to name a few) are doing but doing it in a less reliable and efficient way.