Giters

mgeeky / Penetration-Testing-Tools

A collection of more than 170+ tools, scripts, cheatsheets and other loots that I've developed over years for Red Teaming/Pentesting/IT Security audits purposes.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Install prepare-kali.sh errors

scaery opened this issue · comments

commented

Ohai, tried this on a vanilla kali 2019.4 and encountered some prequisites missing.

  1. Docker debian keyring required else docker-ce cannot be installed trough apt
    apt install -y debian-keyring

  2. lanmaster53 recon-ng repo is no more on bitbucket, it is on github instead line 266
    https://github.com/lanmaster53/recon-ng

  3. mitmproxy 5.0.0.dev0 has requirement certifi 2017.7.27.1 + ldap3 2.5.1 which is incompatible.
    apt install -y tox
    pip3 install -U pip
    pip3 install mitmproxy
    or
    apt install -y mitmproxy

  4. ruby mysql error Gem::Ext::BuildError: ERROR: Failed to build gem native extension.
    apt install -y libmariadb-dev

  5. screenshot util in ~/tools/web/httpscreenshot - Failed building wheel for m2crypto with pip
    apt install -y python-m2crypt

  6. s3 has a bunch of depency errors

Everything else is straight forward. Thanks for sharing your pentest arsenal. Highly appreciated :)

commented

Hi @scaery! Thanks for your bug report. I've added some fixes and changed docker installation strategy entirely to accommodate later additions to Kali packages repository.

Hope the script will work more stable now :)

commented

Awesome. Thanks

You copied a typo from my post in line 67: python-m2crypt to python-m2crypto
And debian-keyring is no more needed with your modified install routine of docker.

just tox libmariadb-dev python-m2crypto
mitmproxy is installed by default (no need to overhead)
and pip2 or pip3 install -U pip will break things on kali, dont do it, do it right or remove lines 69+70

fix either for the latest and greatest:
python -m pip install --user --upgrade pip
python3 -m pip install --user --upgrade pip
remove the distribution pips and link to the newest (quick`n dirty):
rm /usr/bin/pip*
ln -s ~/.local/bin/pip* /usr/bin/

read further on the topic here:
https://stackoverflow.com/questions/49836676/error-after-upgrading-pip-cannot-import-name-main

commented

You're totally right, I've just took the shortcut and copied-pasted your solution. Fixed the typo now in e3fc9a5e. I'd rather stay away from mangling with pip as long as it works fine on my Kali instance provisioned with this script.

If you forsee any further issues with that pip installation - could you please do some tests first, pointing out where it may come short and what do we do about that in a stable manner?

Best regards,
M.

commented

(closed the issue by mistake :< )

commented

Now it works like a charm ;)

[Closed]