BlackArch is a complete Linux distribution for penetration testers and security researchers. It Is derived from ArchLinux and users can install BlackArch components individually or in groups directly on top of it. The toolset is distributed as an Arch Linux unofficial user repository so you can install BlackArch on top of an existing Arch Linux installation. Packages may be installed individually or by category. The constantly expanding repository currently includes over 1300 tools. All tools are thoroughly tested before being added to the codebase to maintain the quality of the repository.

This is for who want to try this OS on device, here the guide :

It will show you how to setup the BlackArch repository and install packages. BlackArch supports both, installing from the repository using binary packages as well as compiling and installing from sources. BlackArch is compatible with normal Archinstallations. It acts as an unofficial user repository. If you want an ISO instead, see the Live ISO section.

A.            Instalation

1. Installing on top of ArchLinux

Run as root and follow the instructions. See the following example. curl -O sha1sum # should match: 6f152b79419491db92c1fdde3fad2d445f09aae3 sudo ./

Now download a fresh copy of the master package list and synchronize packages: sudo pacman -Syyu

2. Installing packages

You may now install tools from the blackarch repository.

1. To list all of the available tools, run pacman -Sgg | grep blackarch | cut -d’ ‘ -f2 | sort -u

2. To install all of the tools, run pacman -S blackarch

3. To install a category of tools, run The BlackArch Linux Guide pacman -S blackarch-<category>

4. To see the blackarch categories, run pacman -Sg | grep blackarch

3. Installing packages from source

As part of an alternative method of installation, you can build the BlackArch packages from source. You can find the PKGBUILDs on github. To build the entire repo, you can use the Blackman tool.

• First, you have to install Blackman. If the BlackArch package repository is setup on your machine, you can install Blackman: pacman -S blackman

• You can build and install Blackman from source: mkdir blackman cd blackman wget # Make sure the PKGBUILD has not been maliciously tampered with. makepkg -s

• Or you can install Blackman from the AUR: <whatever AUR helper you use> -S blackman

4. Basic Blackman usage

Blackman is very simple to use, though the flags are different from what you would typically expect from something like pacman. Basic usage has been outlined below. • Download, compile and install packages: sudo blackman -i package

• Download, compile and install whole category: sudo blackman -g group

• Download, compile and install all of the BlackArch tools: sudo blackman -a

• To list the blackarch categories: blackman -l

• To list category tools: blackman -p category The BlackArch Linux Guide

5. Installing from live-, netinstall- ISO or ArchLinux

You can install BlackArch Linux from one of our live- or netinstall-ISOs. See ISO boot up.

• Install blackarch-installer package: sudo pacman -S blackarch-installer

• Run sudo blackarch-install

B.            Arch’s Build System and Repositories

PKGBUILD files are build scripts. Each one tells makepkg(1) how to create a package. PKGBUILD files are written in Bash. For more information, read (or skim through) the following:

• Arch Wiki: Creating Packages

• Arch Wiki: makepkg

• Arch Wiki: PKGBUILD

• Arch Wiki: Arch Packaging Standards

1. Blackarch PKGBUILD standards

For the sake of simplicity, our PKGBUILDs are similar to that of the AUR ones, with a few small differences outlined below. Every package must belong to blackarch at the minimum, there will also be a lot of crossover with multiple packages belonging to multiple groups.

1.1 Groups

To allow users to install a specific range of packages quickly and easily, packages have been separated into groups. Groups allow users to simply go ”pacman -S <group name>” in order to pull a lot of packages.

2.1.1 blackarch

Theblackarchgroupisthebasegroupthatallpackagesmustbelongtoo.Thisallowsuserstoinstall every package with ease. What should be in here: Everything.

2.1.2 blackarch-anti-forensic

Packages that are used for countering forensic activities, including encryption, steganography, and anything that modifies files/file attributes. This all includes tools to work with anything in general that makes changes to a system for the purposes of hiding information. Examples: luks, TrueCrypt, Timestomp, dd, ropeadope, secure-delete

2.1.3 blackarch-automation

Packages that are used for tool or workflow automation. Examples: blueranger, tiger, wiffy

2.1.4 blackarch-backdoor

Packages that exploit or open backdoors on already vulnerable systems. Examples: backdoor-factory, rrs, weevely

2.1.5 blackarch-binary

Packages that operate on binary files in some form. Examples: binwally, packerid

2.1.6 blackarch-bluetooth

Packages that exploit anything concerning the Bluetooth standard (802.15.1). Examples: ubertooth, tbear, redfang

2.1.7 blackarch-code-audit

Packages that audit existing source code for vulnerability analysis. Examples: flawfinder, pscan

2.1.8 blackarch-cracker

Packages used for cracking cryptographic functions, ie hashes. Examples: hashcat, john, crunch

2.1.9 blackarch-crypto

Packages that work with cryptography, with the exception of cracking. Examples: ciphertest, xortool, sbd

2.1.10 blackarch-database

Packages that involve database exploitations on any level. Examples: metacoretex, blindsql

2.1.11 blackarch-debugger

Packages that allow the user to view what a particular program is ”doing” in realtime. Examples: radare2, shellnoob

2.1.12 blackarch-decompiler

Packages that attempt to reverse a compiled program into source code. Examples: flasm, jd-gui

2.1.13 blackarch-defensive

Packages that are used to protect a user from malware & attacks from other users. Examples: arpon, chkrootkit, sniffjoke

2.1.14 blackarch-disassembler

This is similar to blackarch-decompiler, and there will probably be a lot of programs that fall into both, however these packages produce assembly output rather than the raw source code. Examples: inguma, radare2

2.1.15 blackarch-dos

Packages that use DoS (Denial of Service) attacks. Examples: 42zip, nkiller2

2.1.16 blackarch-drone

Packages that are used for managing physically engineered drones. Examples: meshdeck, skyjack

2.1.17 blackarch-exploitation

Packages that takes advantages of exploits in other programs or services. Examples: armitage, metasploit, zarp

2.1.18 blackarch-fingerprint

Packages that exploit fingerprint biometric equipment. Examples: dns-map, p0f, httprint

2.1.19 blackarch-firmware

Packages that exploit vulnerabilities in firmware Examples: None yet, amend asap.

2.1.20 blackarch-forensic

Packages that are used to find data on physical disks or embedded memory. Examples: aesfix, nfex, wyd

2.1.21 blackarch-fuzzer

Packages that use the fuzz testing principle, ie ”throwing” random inputs at the subject to see what happens. Examples: msf, mdk3, wfuzz

2.1.22 blackarch-hardware

Packages that exploit or manage anything to do with physical hardware. Examples: arduino, smali

2.1.23 blackarch-honeypot

Packages that act as ”honeypots”, ie programs that appear to be vulnerable services used to attract hackers into a trap. Examples: artillery, bluepot, wifi-honey

2.1.24 blackarch-keylogger

Packages that record and retain keystrokes on another system. Examples: None yet, amend asap.

2.1.25 blackarch-malware

Packages that count as any type of malicious software or malware detection. Examples: malwaredetect, peepdf, yara

2.1.26 blackarch-misc

Packages that don’t particularly fit into any categories. Examples: oh-my-zsh-git, winexe, stompy

2.1.27 blackarch-mobile

Packages that manipulate mobile platforms. Examples: android-sdk-platform-tools, android-udev-rules

2.1.28 blackarch-networking

Package that involve IP networking. Examples: Anything pretty much

2.1.29 blackarch-nfc

Packages that use nfc (near-field communications). Examples: nfcutils

2.1.30 blackarch-packer

Packages that operate on or invlove packers. packers are programs that embed malware within other executables. Examples: packerid

2.1.31 blackarch-proxy

Packages that acts as a proxy, ie redirecting traffic through another node on the internet. Examples: burpsuite, ratproxy, sslnuke

2.1.32 blackarch-recon

Packages that actively seeks vulnerable exploits in the wild. More of an umbrella group for similar packages. Examples: canri, dnsrecon, netmask

2.1.33 blackarch-reversing

This is an umbrella group for any decompiler, disassembler or any similar program. Examples: capstone, radare2, zerowine

2.1.34 blackarch-scanner

Packages that scan selected systems for vulnerabilities. Examples: scanssh, tiger, zmap

2.1.35 blackarch-sniffer

Packages that involve analyzing network traffic. Examples: hexinject, pytactle, xspy

2.1.36 blackarch-social

Packages that primarily attack social networking sites. Examples: jigsaw, websploit

2.1.37 blackarch-spoof

Packagesthatattempttospooftheattackersuch,inthattheattackerdoesn’tshowupasanattacker to the victim. Examples: arpoison, lans, netcommander

2.1.38 blackarch-threat-model

Packagesthatwouldbeusedforreporting/recordingthethreatmodeloutlinedinaparticularscenario. Examples: magictree

2.1.39 blackarch-tunnel

Packages that are used to tunnel network traffic on a given network. Examples: ctunnel, iodine, ptunnel

2.1.40 blackarch-unpacker

Packages that are used to extract pre-packed malware from an executable. Examples: js-beautify

2.1.41 blackarch-voip

Packages that operate on voip programs and protocols. Examples: iaxflood, rtp-flood, teardown

2.1.42 blackarch-webapp

Packages that operate on internet-facing applications. Examples: metoscan, whatweb, zaproxy

2.1.43 blackarch-windows

This group is for any native Windows package that runs via wine. Examples: 3proxy-win32, pwdump, winexe

2.1.44 blackarch-wireless

Packages that operates on wireless networks on any level. Examples: airpwn, mdk3, wiffy


Please enter your comment!
Please enter your name here