AttackVector Linux: the dragon has tails

AttackVector Linux is a new distribution for anonymized penetration and security.
It is based on Parrot, Kali and TAILS, which are all based on Debian.

---

Download Attack Vector Linx Now

Design Philosophy

Yin and Yang

While Kali requires a modified kernel for network drivers to use injection and so forth,
TAILS is designed from the bottom up for encryption, and anonymity. attackVector.org.
The intention of AttackVector Linux is to provide the capability to anonymize attacks
while warning the user when he or she takes actions that may compromize anonymity.
The two projects have different design philosophies that can directly conflict with one another.
In spite of this, the goal of AttackVector Linux is to integrate them complementarily into one OS.

Features

• The anonymity of TAILS
• The privacy of SRWare Iron
• The password recovery of hashkill
• The cryptography of DaKaRand
• The penetration tools of Kali

Build Instructions

[ distro / build / kali_coms.txt ]

1. Install prerequisites in Kali:

   apt-get install git live-build cdebootstrap kali-archive-keyring
   cd /tmp
   git clone git://git.kali.org/live-build-config.git
   apt-get remove libdebian-installer4
   apt-get install libdebian-installer4
   

2. Copy down git repo [ distro / kali / config ]

   git clone git://github.com/ksoona/attackvector.git
   cp attackvector/distro/kali/config /tmp/live-build-config/config
   cd /tmp/live-build-config
   

3. Live build:

   lb clean --purge
   dpkg --add-architecture amd64
   lb config --architecture amd64 --mirror-binary http://http.kali.org/kali --mirror-binary-security http://security.kali.org/kali-security --apt-options "--force-yes --yes"
   lb build
   

(Notice the similarity to Kali Live-Build.)

Download

MD5 (attack_vector_alpha_0.1.1b.iso) = 99243d5f4132116e2e9606d6b0c98e6f
mirror Turing

---

social

IRC #attackvector on Freenode


(Web Mockup)

Docs

• Live Build Manual
• TAILS git branches
• How to build TAILS
• How to customize TAILS
• Rebuilding a Kali Package
• Rebuilding the Kali Kernel
• Live Build a Custom Kali ISO
• How to customize Debian live

Project Status

It seems our best structural approach is customizing the Kali Live Build scripts.
Eventually this Kali derivative should meet the TAILS design specifications.

Git

• Kali git repositories
• TAILS git repository
• GitLab.org for hosting repos cron pull'd from the above (see base-git-subtree.sh)
• GitLab-CI Continuous Intergration system uses Vagrant, just like TAILS build scripts
• Configure build system to generate & test ISOs

Tasks

• Help port TAILS to Wheezy
• Evaluate features of each distro & unify them into a single kernel
• Provide two layers of functionality: dedicated install and live distro
• Add warning messages for anonymity risks
• Full Disk Encryption (FDE) w/ LUKS
• Host on AttackVector.org
• Provide documentation
• HTTPS Everywhere
• Debian repositories

license

Text under Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License. Code under GNU Public License. © Kenneth Soona 1988