Skip to content

Virtual environments

These steps will help you list all the virtual environment management tools available on your Kali system.

Check System-Wide Package Managers for Installed Tools:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
# Using APT (Default Kali Package Manager)
dpkg --get-selections | grep -E "pyenv|virtualenv|pipenv|conda"

# Using pip to List Installed Python Packages
pip list | grep -E "virtualenv|pipenv|pyenv|conda"


# Verify Installed Tools' Locations
which pyenv
which virtualenv
which pipenv
which conda

Python vs. pyenv

We may have two different Python environments on the system:

  1. System Python (Managed by update-alternatives)

    • Installed globally in /usr/bin/python, /usr/bin/python3.x
    • Used by system packages (like APT, scripts in /usr/bin, or Kali dependencies)
    • Controlled via update-alternatives
    • Can be Python 3.11 (or any other preferred default)

  2. pyenv Python (User-Managed)

    • Installs Python versions under ~/.pyenv/versions/
    • Allows switching between multiple Python versions per project or globally
    • Uses shims (~/.pyenv/shims/) to redirect python to the right version
    • Overrides system Python when active

How They Coexist

  • When pyenv is inactive, the system uses the Python version set by update-alternatives (e.g., /usr/bin/python3.11).
  • When pyenv is active, it intercepts the python command and runs its own managed Python versions from ~/.pyenv/versions/.
  • Pyenv does NOT modify or replace system Python—it just redirects the python command using a shim.

How to Make Them Work Together

1. Set Python 3.11 as System Default (For System-Wide Use)

1
sudo update-alternatives --install /usr/bin/python python /usr/bin/python3.11 4 sudo update-alternatives --install /usr/bin/python3 python3 /usr/bin/python3.11 4 sudo update-alternatives --config python sudo update-alternatives --config python3`

This makes sure that, when pyenv is NOT active, Python 3.11 is used.

2. Make Sure Pyenv Works Properly

Make sure pyenv is correctly installed in your shell:

1
2
3
4
export PYENV_ROOT="$HOME/.pyenv"
export PATH="$PYENV_ROOT/bin:$PATH"
eval "$(pyenv init --path)"
eval "$(pyenv init -)"

To persist these settings, add them to ~/.zshrc or ~/.bashrc:

1
2
3
4
echo 'export PYENV_ROOT="$HOME/.pyenv"' >> ~/.zshrc 
echo 'export PATH="$PYENV_ROOT/bin:$PATH"' >> ~/.zshrc 
echo 'eval "$(pyenv init --path)"' >> ~/.zshrc 
echo 'eval "$(pyenv init -)"' >> ~/.zshrc source ~/.zshrc

Now, when you activate pyenv, it will take control over Python.

3. Switching Between System Python and Pyenv

Use System Python (Python 3.11 from update-alternatives). To temporarily disable pyenv and use system Python:

1
2
pyenv global system
python -V  # Should return Python 3.11

Use a Pyenv-Managed Python Version To switch to a specific pyenv-managed Python version:

1
2
3
pyenv install 3.10.6
pyenv global 3.10.6
python -V  # Should return Python 3.10.6

4. To use a project-specific version:

1
2
3
cd my_project
pyenv local 3.9.0
python -V  # Should return Python 3.9.0

virtualenvwrapper

Installation

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
# Make sure you have pip installed.
sudo apt-get install python3-pip

# Installing virtualenvwrapper 
sudo pip3 install virtualenvwrapper

# Open bashrc by –
sudo gedit ~/.bashrc

# After opening it, add the following  lines to it :

export WORKON_HOME=$HOME/.virtualenvs
export PROJECT_HOME=$HOME/Projects
source /usr/share/virtualenvwrapper/virtualenvwrapper.sh

Basic usage

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
# Creating a virtual environment with mkvirtualenv
mkvirtualenv nameOfEnvironment

# List exisiting environment in your 
lsvirtualenv -b

# Work on an environment
workon nameOfEnvironment

# Close current environment
deactivate

# Delete virtual environment
rmvirtualenv nameOfEnvironment

# To work on another version of python:
mkvirtualenv -p python3.x venv_name
# You will see something like this: (venv_name)

Backing up virtual environment before removing it:

1
pip freeze > requirements.txt

venv

1
2
python3 -m venv <DIR>
source <DIR>/bin/activate

Now you can activate or deactivate the virtual environment with:

1
<DIR>\Scripts\activate

pyenv

Install prerequisites: Ensure you have the required dependencies for pyenv installation.

1
sudo apt update sudo apt install -y build-essential libssl-dev zlib1g-dev libbz2-dev \ libreadline-dev libsqlite3-dev wget curl llvm libncurses5-dev libncursesw5-dev \ xz-utils tk-dev libffi-dev liblzma-dev python3-openssl git

Install pyenv: Use the following commands to install pyenv:

1
curl https://pyenv.run | bash

Update .bashrc to set up pyenv: Add the following to your .bashrc (or .zshrc if using zsh):

1
2
3
4
export PATH="$HOME/.pyenv/bin:$PATH"
eval "$(pyenv init --path)"
eval "$(pyenv init -)"
eval "$(pyenv virtualenv-init -)"

Then, reload your shell configuration:

1
pyenv install 2.7.18

This command installs Python 2.7.18, or you can choose another Python 2.7 version if needed.

Create a Python 2.7 virtual environment: Once Python 2.7 is installed, you can create a virtual environment with:

1
pyenv virtualenv 2.7.18 env_name

Activate the virtual environment: To activate the environment, run:

1
pyenv activate env_name

Or deactivate:

1
deactivate

1. Install and Configure pyenv

Ensure pyenv is installed and properly configured.

1.1 Install pyenv (If Not Already Installed)

1
curl https://pyenv.run | bash

1.2 Add pyenv to Shell Configuration

For Zsh (~/.zshrc):

1
2
3
4
5
6
echo 'export PYENV_ROOT="$HOME/.pyenv"' >> ~/.zshrc
echo '[[ -d $PYENV_ROOT/bin ]] && export PATH="$PYENV_ROOT/bin:$PATH"' >> ~/.zshrc
echo 'eval "$(pyenv init --path)"' >> ~/.zshrc
echo 'eval "$(pyenv init - zsh)"' >> ~/.zshrc
echo 'eval "$(pyenv virtualenv-init -)"' >> ~/.zshrc
source ~/.zshrc

For Bash (~/.bashrc):

1
2
3
4
5
6
echo 'export PYENV_ROOT="$HOME/.pyenv"' >> ~/.bashrc
echo '[[ -d $PYENV_ROOT/bin ]] && export PATH="$PYENV_ROOT/bin:$PATH"' >> ~/.bashrc
echo 'eval "$(pyenv init --path)"' >> ~/.bashrc
echo 'eval "$(pyenv init - bash)"' >> ~/.bashrc
echo 'eval "$(pyenv virtualenv-init -)"' >> ~/.bashrc
source ~/.bashrc

1.3 Install Required Python Versions

1
2
3
pyenv install 3.11.6
pyenv install 3.9.18
pyenv install 3.8.18

2. Create Virtual Environments

We will create one virtual environment per Python version, grouping compatible tools together.

1
2
3
4
pyenv virtualenv 3.11.6 py311-env
pyenv virtualenv 3.9.18 py39-env
pyenv virtualenv 3.8.18 py38-env
pyenv virtualenv 2.7.18 py27-env

3. Assign Tools to Virtual Environments

Each environment will host tools that require a compatible Python version.

3.1 Python 3.11 Environment (**py311-env**)

1
2
pyenv activate py311-env
pip install crackmapexec bloodhound.py jwt_tool

Tools in Python 3.11:

  • CrackMapExec

  • BloodHound.py

  • jwt_tool

Auto-Activation:

1
2
3
echo "py311-env" > CrackMapExec/.python-version
echo "py311-env" > BloodHound.py/.python-version
echo "py311-env" > jwt_tool/.python-version

3.2 Python 3.9 Environment (**py39-env**)

1
2
pyenv activate py39-env
pip install impacket LaZagne kerbrute

Tools in Python 3.9:

  • impacket

  • LaZagne

  • kerbrute

Auto-Activation:

1
2
3
echo "py39-env" > impacket/.python-version
echo "py39-env" > LaZagne/.python-version
echo "py39-env" > kerbrute/.python-version

3.3 Python 3.8 Environment (**py38-env**)

1
2
pyenv activate py38-env
pip install BloodHound.py

Tools in Python 3.8:

  • BloodHound.py (Older Version if needed)

Auto-Activation:

1
echo "py38-env" > BloodHound.py/.python-version

4. Managing Ruby-based Tools

For tools requiring Ruby, use rbenv instead of pyenv.

4.1 Install rbenv

1
sudo apt install rbenv -y

4.2 Install Ruby Versions

1
2
rbenv install 2.7.4
rbenv install 3.0.2

4.3 Assign Ruby-based Tools

Ruby 2.7.4:

1
echo "2.7.4" > ActiveDirectory/.ruby-version

Ruby 3.0.2:

1
echo "3.0.2" > Metasploit/.ruby-version

5. Managing Docker-based Tools

Some tools have complex dependencies and are best run in Docker.

5.1 Install Docker

1
2
sudo apt install docker.io -y
sudo systemctl enable --now docker

5.2 Run Docker Tools

1
2
docker run --rm -it ghostpack
docker run --rm -it splunk

Docker-based Tools:

  • GhostPack

  • Splunk

6. Verify the Setup

To check installed pyenv versions:

1
pyenv versions

To check the active environment:

1
pyenv version

To list installed tools inside an environment:

1
2
pyenv activate py311-env
pip list

7. Summary of Environment Assignments

Environment Python Version Tools
py311-env Python 3.11 CrackMapExec, BloodHound.py, jwt_tool
py39-env Python 3.9 impacket, LaZagne, kerbrute
py38-env Python 3.8 BloodHound.py (Older Version)
Docker No Python GhostPack, Splunk
rbenv (Ruby) Ruby 2.7.4, 3.0.2 Metasploit, ActiveDirectory, PowerSploit
Last update: 2025-04-13
Created: February 29, 2024 15:15:09