r3dy/capsulecorp-pentest

Vagrant VirtualBox environment for conducting an internal network penetration test

Blog        

Twitter:  

Discord:

Book:     

1. Capsulecorp Pentest

The Capsulecorp Pentest is a small virtual network managed by Vagrant and Ansible. It contains five virtual machines, including one Linux attacking system running Xubuntu and 4 Windows 2019 servers configured with various vulnerable services. This project can be used to learn network penetration testing as a stand-alone environment but is ultimatly designed to complement my book The Art of Network Penetration Testing.

Why is this cool?

Setting up a virtual network to learn penetration testing can be tedious as well as time/resource consuming. Everything in the capsulecorp environment is pretty much done for you already. Once you get Vagrant, Ansible and VirtualBox installed on your machine you only need to run a couple of vagrant commands to have a fully functioning Active Directory domain that you can use for hacking/learning/pentesting etc.

1.1. Requirements

In order to use the Capsulecorp Pentest network you must have the following:

• VirtualBox

  • https://www.virtualbox.org/wiki/Downloads

• Vagrant

  • https://www.vagrantup.com/downloads.html

• Ansible

  • https://docs.ansible.com/ansible/latest/installation_guide/index.html

• Quad-core CPU with 16GB RAM is recommended.

  • With 8GB or less you could still use the project but only run 2 or 3 VMs at a time.
  • For All VMs running at once 16GB is required.

1.2. Current Functionality

• Active directory domain with one DC and 3 server members. All windows server have evaluation licenses, which are activated on installation (for 180 days)
  • Domain Controler: goku.capsulecorp.local
  • Server 01: vegeta.capsulecorp.local
  • Server 02: gohan.capsulecorp.local
  • Server 03: trunks.capsulecorp.local
  • Wrkstn 01: tien.capsulecorp.local
• Vulnerable Jenkins server on vegeta
• Vulnerable Apache Tomcat server on trunks
• Vulnerable MSSQL server on gohan
• Vulnerable MS17-010 on tien
• Xubuntu pentest system running XRDP.
  • Metasploit
  • CrackMapExec
  • Nmap
  • Remmina RDP client
  • RVM
  • Python/Pip/Pipenv
  • Impacket

1.3. OSX Configuration

In order to manage Windows hosts you'll have to install pywinrm with pip inside the ansible virtual environment

source ~/ansible/bin/activate
pip install pywinrm
deactivate

2. Installation

YouTube Setup Tutorial

For a detailed installation walkthrough check out

• MacOS Setup Guide

• Windows Setup Guide

2.1. Configure the windows hosts

The first thing you should do is bring up and provision Goku the domain controller. This system will likely take the longest to bring up because the dcpromo stuff just takes a while.

Note: if you are running vagrant with sudo. use sudo -E vagrant option to run vagrant

Bring up the VM

vagrant up goku

Provision the VM

vagrant provision goku

Repeat the above two commands for gohan, vegeta and trunks.

...WARNING...

This section of the provision is expected to take a while because after a dcpromo it takes a long time for the system to reboot.

TASK [promotedc : Set a static address to 172.28.128.100] **********************
changed: [goku]

TASK [promotedc : Change hostname to goku] *************************************
ok: [goku]

TASK [promotedc : Install Active Directory Services] ***************************
ok: [goku]

TASK [promotedc : Promote goku to domain controller] ***************************
changed: [goku]

TASK [promotedc : Reboot after promotion] **************************************

2.2. Configure your pentest platform

Bring up the virtual machines using Vagrant. First cd into the project directory, for example: cd ~/capsulecorp-pentest. Take note of the RDP port that gets forwarded to your localhost.

vagrant up pentest

Provision the pentest machine.

vagrant provision pentest

You can access your pentest machine either using your preferred RDP client to connect to the xrdp listener or via SSH with.

vagrant ssh pentest

capsulecorp-pentest's Issues

Can we get a Linux based installation guide?

I can see that there are Mac and Windows based installation guides for the lab, however there are a lot of us who work on Linux/Ubuntu, and the installation guide is not available.

MSSQL cli

Mr. Royce,
I am not sure but I tried many time and looked at the setting of gohan, SQL server configuration manager, the sa account password, the sql service and the TPC/IP.
I ran these commands

• mssql-cli -S 172.28.128.101 -U sa from pentest
• sqlcmd -S 172.28.128.101\CAPSULECORPDB -U sa on gohan just to check on connectivity to the SQL database
  I am getting these errors:

From pentest:
Error message: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 40 - Could not open a connection to SQL Server)
From gohan:
sqlcmd:Error: Microsoft ODBC Driver 13 for SQL Server : Login failed for user 'sa'..

I can ping the server.
So I am not really sure what I am missing, why these commands are failing?

having problem with pentest machine

when i try to make pentest up this error appears. what can I do ?

Vagrant in WSL unable to access Virtualbox and Windows environment

after following tutorial for windows setup on this git repo and even from vagrant website. even after setting the correct windows path variable and running this command

sudo vagrant up goku

it throws the following error

Vagrant failed to initialize at a very early stage:

Vagrant is unable to use the VirtualBox provider from the Windows Subsystem for
Linux without access to the Windows environment. Enabling this access must be
done with caution and an understanding of the implications. For more information
on enabling Windows access and using VirtualBox from the Windows Subsystem for
Linux, please refer to the Vagrant documentation:

Host OS

Edition: Windows 10 Home Single Language Version: 20H2 OS Build: 19042.870

Ubuntu WSL Description: Ubuntu 20.04 LTS

output of sudo vagrant up goku --debug
vagrant.log.txt

also in log file it shows that vagrant is trying to run this command on powershell

Starting process: ["/usr/local/bin/powershell", "-NoLogo", "-NoProfile", "-NonInteractive", "-ExecutionPolicy", "Bypass", "-Command", "$x = (Get-VMHost).Name; if($x -eq [System.Net.Dns]::GetHostName()){ Write-Output 'true'}"]

Why is this trying to call hyperv when we mention virtualbox provider in Vagrantfile?

How much disk space is required?

Could you please specify how much disk space is needed for each VM and in total ?

Running action: environment_unload #<Vagrant::Action::Builder:0x000055985625ae88>

vagrant up goku
INFO global: Vagrant version: 2.2.14
INFO global: Ruby version: 2.7.4
INFO global: RubyGems version: 3.2.27
INFO global: VAGRANT_LOG="debug"
WARN global: resolv replacement has not been enabled!
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/destroy/plugin.rb
INFO manager: Registered plugin: destroy command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/provision/plugin.rb
INFO manager: Registered plugin: provision command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/push/plugin.rb
INFO manager: Registered plugin: push command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/init/plugin.rb
INFO manager: Registered plugin: init command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/winrm_config/plugin.rb
INFO manager: Registered plugin: winrm-config command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/help/plugin.rb
INFO manager: Registered plugin: help command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/box/plugin.rb
INFO manager: Registered plugin: box command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/validate/plugin.rb
INFO manager: Registered plugin: validate command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/plugin/plugin.rb
INFO manager: Registered plugin: plugin command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/cloud/plugin.rb
INFO manager: Registered plugin: vagrant-cloud
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/ssh_config/plugin.rb
INFO manager: Registered plugin: ssh-config command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/ssh/plugin.rb
INFO manager: Registered plugin: ssh command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/snapshot/plugin.rb
INFO manager: Registered plugin: snapshot command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/port/plugin.rb
INFO manager: Registered plugin: port command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/winrm/plugin.rb
INFO manager: Registered plugin: winrm command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/cap/plugin.rb
INFO manager: Registered plugin: cap command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/upload/plugin.rb
INFO manager: Registered plugin: upload command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/suspend/plugin.rb
INFO manager: Registered plugin: suspend command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/reload/plugin.rb
INFO manager: Registered plugin: reload command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/package/plugin.rb
INFO manager: Registered plugin: package command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/status/plugin.rb
INFO manager: Registered plugin: status command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/provider/plugin.rb
INFO manager: Registered plugin: provider command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/up/plugin.rb
INFO manager: Registered plugin: up command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/powershell/plugin.rb
INFO manager: Registered plugin: powershell command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/login/plugin.rb
INFO manager: Registered plugin: vagrant-login
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/resume/plugin.rb
INFO manager: Registered plugin: resume command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/halt/plugin.rb
INFO manager: Registered plugin: halt command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/rdp/plugin.rb
INFO manager: Registered plugin: rdp command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/list-commands/plugin.rb
INFO manager: Registered plugin: list-commands command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/autocomplete/plugin.rb
INFO manager: Registered plugin: autocomplete command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/global-status/plugin.rb
INFO manager: Registered plugin: global-status command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/version/plugin.rb
INFO manager: Registered plugin: version command
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/provisioners/cfengine/plugin.rb
INFO manager: Registered plugin: CFEngine Provisioner
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/provisioners/file/plugin.rb
INFO manager: Registered plugin: file
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/provisioners/puppet/plugin.rb
INFO manager: Registered plugin: puppet
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/provisioners/podman/plugin.rb
INFO manager: Registered plugin: podman
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/provisioners/shell/plugin.rb
INFO manager: Registered plugin: shell
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/provisioners/ansible/plugin.rb
INFO manager: Registered plugin: ansible
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/provisioners/salt/plugin.rb
INFO manager: Registered plugin: salt
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/provisioners/chef/plugin.rb
INFO manager: Registered plugin: chef
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/provisioners/docker/plugin.rb
INFO manager: Registered plugin: docker
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/provisioners/container/plugin.rb
INFO manager: Registered plugin: container
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/pushes/heroku/plugin.rb
INFO manager: Registered plugin: heroku
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/pushes/noop/plugin.rb
INFO manager: Registered plugin: noop
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/pushes/ftp/plugin.rb
INFO manager: Registered plugin: ftp
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/pushes/atlas/plugin.rb
INFO manager: Registered plugin: atlas
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/pushes/local-exec/plugin.rb
INFO manager: Registered plugin: local-exec
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/synced_folders/nfs/plugin.rb
INFO manager: Registered plugin: NFS synced folders
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/synced_folders/smb/plugin.rb
INFO manager: Registered plugin: SMB synced folders
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/synced_folders/rsync/plugin.rb
INFO manager: Registered plugin: RSync synced folders
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/hosts/arch/plugin.rb
INFO manager: Registered plugin: Arch host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/hosts/alt/plugin.rb
INFO manager: Registered plugin: ALT Platform host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/hosts/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/hosts/suse/plugin.rb
INFO manager: Registered plugin: SUSE host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/hosts/bsd/plugin.rb
INFO manager: Registered plugin: BSD host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/hosts/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/hosts/linux/plugin.rb
INFO manager: Registered plugin: Linux host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/hosts/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/hosts/windows/plugin.rb
INFO manager: Registered plugin: Windows host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/hosts/null/plugin.rb
INFO manager: Registered plugin: null host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/hosts/darwin/plugin.rb
INFO manager: Registered plugin: Mac OS X host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/hosts/slackware/plugin.rb
INFO manager: Registered plugin: Slackware host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/hosts/void/plugin.rb
INFO manager: Registered plugin: Void host
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/communicators/ssh/plugin.rb
INFO manager: Registered plugin: ssh communicator
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/communicators/winrm/plugin.rb
INFO manager: Registered plugin: winrm communicator
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/communicators/winssh/plugin.rb
INFO manager: Registered plugin: windows ssh communicator
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/providers/virtualbox/plugin.rb
INFO manager: Registered plugin: VirtualBox provider
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/providers/hyperv/plugin.rb
INFO manager: Registered plugin: Hyper-V provider
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/providers/docker/plugin.rb
INFO manager: Registered plugin: docker-provider
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/kali/plugin.rb
INFO manager: Registered plugin: Kali guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/arch/plugin.rb
INFO manager: Registered plugin: Arch guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/coreos/plugin.rb
INFO manager: Registered plugin: CoreOS guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/funtoo/plugin.rb
INFO manager: Registered plugin: Funtoo guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/alt/plugin.rb
INFO manager: Registered plugin: ALT Platform guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/pld/plugin.rb
INFO manager: Registered plugin: PLD Linux guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/redhat/plugin.rb
INFO manager: Registered plugin: Red Hat Enterprise Linux guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/photon/plugin.rb
INFO manager: Registered plugin: VMware Photon guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/solaris11/plugin.rb
INFO manager: Registered plugin: Solaris 11 guest.
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/suse/plugin.rb
INFO manager: Registered plugin: SUSE guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/mint/plugin.rb
INFO manager: Registered plugin: Mint guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/alpine/plugin.rb
INFO manager: Registered plugin: Alpine guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/dragonflybsd/plugin.rb
INFO manager: Registered plugin: DragonFly BSD guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/amazon/plugin.rb
INFO manager: Registered plugin: Amazon Linux guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/tinycore/plugin.rb
INFO manager: Registered plugin: TinyCore Linux guest.
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/solaris/plugin.rb
INFO manager: Registered plugin: Solaris guest.
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/fedora/plugin.rb
INFO manager: Registered plugin: Fedora guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/bsd/plugin.rb
INFO manager: Registered plugin: BSD-based guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/netbsd/plugin.rb
INFO manager: Registered plugin: NetBSD guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/freebsd/plugin.rb
INFO manager: Registered plugin: FreeBSD guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/linux/plugin.rb
INFO manager: Registered plugin: Linux guest.
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/smartos/plugin.rb
INFO manager: Registered plugin: SmartOS guest.
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/centos/plugin.rb
INFO manager: Registered plugin: CentOS guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/elementary/plugin.rb
INFO manager: Registered plugin: Elementary guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/atomic/plugin.rb
INFO manager: Registered plugin: Atomic Host guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/haiku/plugin.rb
INFO manager: Registered plugin: Haiku guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/esxi/plugin.rb
INFO manager: Registered plugin: ESXi guest.
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/gentoo/plugin.rb
INFO manager: Registered plugin: Gentoo guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/windows/plugin.rb
INFO manager: Registered plugin: Windows guest.
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/debian/plugin.rb
INFO manager: Registered plugin: Debian guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/openbsd/plugin.rb
INFO manager: Registered plugin: OpenBSD guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/trisquel/plugin.rb
INFO manager: Registered plugin: Trisquel guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/ubuntu/plugin.rb
INFO manager: Registered plugin: Ubuntu guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/nixos/plugin.rb
INFO manager: Registered plugin: NixOS guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/darwin/plugin.rb
INFO manager: Registered plugin: Darwin guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/slackware/plugin.rb
INFO manager: Registered plugin: Slackware guest
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/guests/omnios/plugin.rb
INFO manager: Registered plugin: OmniOS guest.
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/kernel_v1/plugin.rb
INFO manager: Registered plugin: kernel
DEBUG global: Loading core plugin: /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/kernel_v2/plugin.rb
INFO manager: Registered plugin: kernel
INFO vagrant: vagrant invoked: ["up", "goku", "--debug"]
DEBUG vagrant: Creating Vagrant environment
INFO environment: Environment initialized (#Vagrant::Environment:0x0000559855e77e88)
INFO environment: - cwd: /home/termit/capsulecorp-pentest
INFO environment: Home path: /home/termit/.vagrant.d
DEBUG environment: Effective local data path: /home/termit/capsulecorp-pentest/.vagrant
INFO environment: Local data path: /home/termit/capsulecorp-pentest/.vagrant
DEBUG environment: Creating: /home/termit/capsulecorp-pentest/.vagrant
DEBUG manager: Enabling localized plugins
INFO manager: Plugins:
DEBUG solution_file: new solution file instance plugin_file=/home/termit/capsulecorp-pentest/.vagrant/plugins.json solution_file=/home/termit/capsulecorp-pentest/.vagrant/bundler/local.sol
DEBUG solution_file: missing file so skipping loading
DEBUG bundler: solution file in use for init: Vagrant::Bundler::SolutionFile:/home/termit/capsulecorp-pentest/.vagrant/plugins.json:/home/termit/capsulecorp-pentest/.vagrant/bundler/local.sol:invalid
DEBUG bundler: Generating new builtin set instance.
DEBUG bundler: Generating new plugin set instance. Skip gems - []
DEBUG bundler: generating solution set for configured plugins
DEBUG bundler: Current generated plugin dependency list: []
DEBUG bundler: resolving solution from available specification set
DEBUG bundler: solution set for configured plugins has been resolved
DEBUG bundler: activating solution set
DEBUG bundler: Activating solution set: []
DEBUG solution_file: plugin file does not exist, not storing solution
DEBUG bundler: solution set stored to - Vagrant::Bundler::SolutionFile:/home/termit/capsulecorp-pentest/.vagrant/plugins.json:/home/termit/capsulecorp-pentest/.vagrant/bundler/local.sol:invalid
INFO manager: Loading plugins...
DEBUG manager: Enabling globalized plugins
INFO manager: Plugins:
INFO manager: - vagrant-libvirt = [installed: undefined constraint: > 0]
DEBUG solution_file: new solution file instance plugin_file=/home/termit/.vagrant.d/plugins.json solution_file=/home/termit/capsulecorp-pentest/.vagrant/bundler/global.sol
DEBUG solution_file: missing file so skipping loading
DEBUG bundler: solution file in use for init: Vagrant::Bundler::SolutionFile:/home/termit/.vagrant.d/plugins.json:/home/termit/capsulecorp-pentest/.vagrant/bundler/global.sol:invalid
DEBUG bundler: Generating new builtin set instance.
DEBUG bundler: Generating new plugin set instance. Skip gems - []
DEBUG bundler: generating solution set for configured plugins
DEBUG bundler: Current generated plugin dependency list: [<Gem::Dependency type=:runtime name="vagrant-libvirt" requirements="> 0">]
DEBUG bundler: resolving solution from available specification set
DEBUG bundler: solution set for configured plugins has been resolved
DEBUG bundler: activating solution set
DEBUG bundler: Activating solution set: ["racc-1.4.16", "nokogiri-1.11.7", "json-2.3.0", "ruby-libvirt-0.7.1", "formatador-0.2.5", "excon-0.79.0", "mime-types-data-3.2015.1120", "mime-types-3.3.1", "builder-3.2.4", "fog-core-2.1.0", "fog-xml-0.1.1", "multi_json-1.14.1", "fog-json-1.2.0", "fog-libvirt-0.8.0", "vagrant-libvirt-0.3.0"]
DEBUG bundler: Activating gem racc-1.4.16
DEBUG bundler: Activating gem nokogiri-1.11.7
DEBUG bundler: Activating gem ruby-libvirt-0.7.1
DEBUG bundler: Activating gem formatador-0.2.5
DEBUG bundler: Activating gem builder-3.2.4
DEBUG bundler: Activating gem fog-core-2.1.0
DEBUG bundler: Activating gem fog-xml-0.1.1
DEBUG bundler: Activating gem multi_json-1.14.1
DEBUG bundler: Activating gem fog-json-1.2.0
DEBUG bundler: Activating gem fog-libvirt-0.8.0
DEBUG bundler: Activating gem vagrant-libvirt-0.3.0
DEBUG solution_file: plugin file does not exist, not storing solution
DEBUG bundler: solution set stored to - Vagrant::Bundler::SolutionFile:/home/termit/.vagrant.d/plugins.json:/home/termit/capsulecorp-pentest/.vagrant/bundler/global.sol:invalid
INFO manager: Loading plugins...
INFO manager: Loading plugin vagrant-libvirt with default require: vagrant-libvirt
INFO manager: Registered plugin: libvirt
DEBUG manager: Successfully loaded plugin vagrant-libvirt.
INFO loader: Set :root = ["#Pathname:/home/termit/capsulecorp-pentest/Vagrantfile"]
DEBUG loader: Populating proc cache for #Pathname:/home/termit/capsulecorp-pentest/Vagrantfile
DEBUG loader: Load procs for pathname: /home/termit/capsulecorp-pentest/Vagrantfile
INFO loader: Loading configuration in order: [:home, :root]
DEBUG loader: Loading from: root (evaluating)
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
INFO base: VBoxManage path: VBoxManage
INFO subprocess: Starting process: ["/usr/bin/VBoxManage", "--version"]
INFO subprocess: Vagrant not running in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: 6.1.26_Debianr145957
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG meta: Finding driver for VirtualBox version: 6.1.26
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_6_1
INFO base: VBoxManage path: VBoxManage
DEBUG environment: Initial usable provider list: [[6, :virtualbox], [5, :libvirt]]
DEBUG environment: Priority sorted usable provider list: [:virtualbox, :libvirt]
DEBUG environment: Preferred provider list: []
DEBUG environment: Using provider virtualbox as it is the highest priority in the usable list.
INFO base: VBoxManage path: VBoxManage
DEBUG meta: Finding driver for VirtualBox version: 6.1.26
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_6_1
INFO base: VBoxManage path: VBoxManage
DEBUG environment: Initial usable provider list: [[6, :virtualbox], [5, :libvirt]]
DEBUG environment: Priority sorted usable provider list: [:virtualbox, :libvirt]
DEBUG environment: Preferred provider list: []
DEBUG environment: Using provider virtualbox as it is the highest priority in the usable list.
INFO loader: Set "2120_machine_goku" = ["["2", #<Proc:0x00005598563fa158 /home/termit/capsulecorp-pentest/Vagrantfile:21>]"]
DEBUG loader: Populating proc cache for ["2", #<Proc:0x00005598563fa158 /home/termit/capsulecorp-pentest/Vagrantfile:21>]
INFO loader: Loading configuration in order: [:home, :root, "2120_machine_goku"]
DEBUG loader: Loading from: root (cache)
DEBUG loader: Loading from: 2120_machine_goku (evaluating)
DEBUG provisioner: Provisioner defined:
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
INFO box_collection: Box not found: royce/capsulecorp-winsrv (virtualbox)
WARN vagrantfile: Failed to locate royce/capsulecorp-winsrv with version 0.0.5-alpha
WARN vagrantfile: Performing lookup with inital values royce/capsulecorp-winsrv with version 0.0.5-alpha
INFO box_collection: Box not found: royce/capsulecorp-winsrv (virtualbox)
INFO box_collection: Box not found: royce/capsulecorp-winsrv (virtualbox)
INFO base: VBoxManage path: VBoxManage
DEBUG meta: Finding driver for VirtualBox version: 6.1.26
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_6_1
INFO base: VBoxManage path: VBoxManage
DEBUG environment: Initial usable provider list: [[6, :virtualbox], [5, :libvirt]]
DEBUG environment: Priority sorted usable provider list: [:virtualbox, :libvirt]
DEBUG environment: Preferred provider list: []
DEBUG environment: Using provider virtualbox as it is the highest priority in the usable list.
INFO loader: Set "2120_machine_gohan" = ["["2", #<Proc:0x00005598563f9e88 /home/termit/capsulecorp-pentest/Vagrantfile:21>]"]
DEBUG loader: Populating proc cache for ["2", #<Proc:0x00005598563f9e88 /home/termit/capsulecorp-pentest/Vagrantfile:21>]
INFO loader: Loading configuration in order: [:home, :root, "2120_machine_gohan"]
ERROR loader: Unknown config sources: ["2120_machine_goku"]
DEBUG loader: Loading from: root (cache)
DEBUG loader: Loading from: 2120_machine_gohan (evaluating)
DEBUG provisioner: Provisioner defined:
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
INFO box_collection: Box not found: royce/capsulecorp-winsrv (virtualbox)
WARN vagrantfile: Failed to locate royce/capsulecorp-winsrv with version 0.0.7-alpha-dc-member
WARN vagrantfile: Performing lookup with inital values royce/capsulecorp-winsrv with version 0.0.7-alpha-dc-member
INFO box_collection: Box not found: royce/capsulecorp-winsrv (virtualbox)
INFO box_collection: Box not found: royce/capsulecorp-winsrv (virtualbox)
INFO base: VBoxManage path: VBoxManage
DEBUG meta: Finding driver for VirtualBox version: 6.1.26
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_6_1
INFO base: VBoxManage path: VBoxManage
DEBUG environment: Initial usable provider list: [[6, :virtualbox], [5, :libvirt]]
DEBUG environment: Priority sorted usable provider list: [:virtualbox, :libvirt]
DEBUG environment: Preferred provider list: []
DEBUG environment: Using provider virtualbox as it is the highest priority in the usable list.
INFO loader: Set "2120_machine_vegeta" = ["["2", #<Proc:0x00005598563f9c80 /home/termit/capsulecorp-pentest/Vagrantfile:21>]"]
DEBUG loader: Populating proc cache for ["2", #<Proc:0x00005598563f9c80 /home/termit/capsulecorp-pentest/Vagrantfile:21>]
INFO loader: Loading configuration in order: [:home, :root, "2120_machine_vegeta"]
ERROR loader: Unknown config sources: ["2120_machine_goku", "2120_machine_gohan"]
DEBUG loader: Loading from: root (cache)
DEBUG loader: Loading from: 2120_machine_vegeta (evaluating)
DEBUG provisioner: Provisioner defined:
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
INFO box_collection: Box not found: royce/capsulecorp-winsrv (virtualbox)
WARN vagrantfile: Failed to locate royce/capsulecorp-winsrv with version 0.0.7-alpha-dc-member
WARN vagrantfile: Performing lookup with inital values royce/capsulecorp-winsrv with version 0.0.7-alpha-dc-member
INFO box_collection: Box not found: royce/capsulecorp-winsrv (virtualbox)
INFO box_collection: Box not found: royce/capsulecorp-winsrv (virtualbox)
INFO base: VBoxManage path: VBoxManage
DEBUG meta: Finding driver for VirtualBox version: 6.1.26
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_6_1
INFO base: VBoxManage path: VBoxManage
DEBUG environment: Initial usable provider list: [[6, :virtualbox], [5, :libvirt]]
DEBUG environment: Priority sorted usable provider list: [:virtualbox, :libvirt]
DEBUG environment: Preferred provider list: []
DEBUG environment: Using provider virtualbox as it is the highest priority in the usable list.
INFO loader: Set "2120_machine_trunks" = ["["2", #<Proc:0x00005598563f9a78 /home/termit/capsulecorp-pentest/Vagrantfile:21>]"]
DEBUG loader: Populating proc cache for ["2", #<Proc:0x00005598563f9a78 /home/termit/capsulecorp-pentest/Vagrantfile:21>]
INFO loader: Loading configuration in order: [:home, :root, "2120_machine_trunks"]
ERROR loader: Unknown config sources: ["2120_machine_goku", "2120_machine_gohan", "2120_machine_vegeta"]
DEBUG loader: Loading from: root (cache)
DEBUG loader: Loading from: 2120_machine_trunks (evaluating)
DEBUG provisioner: Provisioner defined:
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
INFO box_collection: Box not found: royce/capsulecorp-winsrv (virtualbox)
WARN vagrantfile: Failed to locate royce/capsulecorp-winsrv with version 0.0.7-alpha-dc-member
WARN vagrantfile: Performing lookup with inital values royce/capsulecorp-winsrv with version 0.0.7-alpha-dc-member
INFO box_collection: Box not found: royce/capsulecorp-winsrv (virtualbox)
INFO box_collection: Box not found: royce/capsulecorp-winsrv (virtualbox)
INFO base: VBoxManage path: VBoxManage
DEBUG meta: Finding driver for VirtualBox version: 6.1.26
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_6_1
INFO base: VBoxManage path: VBoxManage
DEBUG environment: Initial usable provider list: [[6, :virtualbox], [5, :libvirt]]
DEBUG environment: Priority sorted usable provider list: [:virtualbox, :libvirt]
DEBUG environment: Preferred provider list: []
DEBUG environment: Using provider virtualbox as it is the highest priority in the usable list.
INFO loader: Set "2120_machine_tien" = ["["2", #<Proc:0x00005598563f9870 /home/termit/capsulecorp-pentest/Vagrantfile:21>]"]
DEBUG loader: Populating proc cache for ["2", #<Proc:0x00005598563f9870 /home/termit/capsulecorp-pentest/Vagrantfile:21>]
INFO loader: Loading configuration in order: [:home, :root, "2120_machine_tien"]
ERROR loader: Unknown config sources: ["2120_machine_goku", "2120_machine_gohan", "2120_machine_vegeta", "2120_machine_trunks"]
DEBUG loader: Loading from: root (cache)
DEBUG loader: Loading from: 2120_machine_tien (evaluating)
DEBUG provisioner: Provisioner defined:
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
INFO box_collection: Box not found: royce/capsulecorp-win7 (virtualbox)
WARN vagrantfile: Failed to locate royce/capsulecorp-win7 with version 0.0.2-alpha
WARN vagrantfile: Performing lookup with inital values royce/capsulecorp-win7 with version 0.0.2-alpha
INFO box_collection: Box not found: royce/capsulecorp-win7 (virtualbox)
INFO box_collection: Box not found: royce/capsulecorp-win7 (virtualbox)
INFO base: VBoxManage path: VBoxManage
DEBUG meta: Finding driver for VirtualBox version: 6.1.26
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_6_1
INFO base: VBoxManage path: VBoxManage
DEBUG environment: Initial usable provider list: [[6, :virtualbox], [5, :libvirt]]
DEBUG environment: Priority sorted usable provider list: [:virtualbox, :libvirt]
DEBUG environment: Preferred provider list: []
DEBUG environment: Using provider virtualbox as it is the highest priority in the usable list.
INFO loader: Set "2120_machine_raditz" = ["["2", #<Proc:0x00005598563f95f0 /home/termit/capsulecorp-pentest/Vagrantfile:21>]"]
DEBUG loader: Populating proc cache for ["2", #<Proc:0x00005598563f95f0 /home/termit/capsulecorp-pentest/Vagrantfile:21>]
INFO loader: Loading configuration in order: [:home, :root, "2120_machine_raditz"]
ERROR loader: Unknown config sources: ["2120_machine_goku", "2120_machine_gohan", "2120_machine_vegeta", "2120_machine_trunks", "2120_machine_tien"]
DEBUG loader: Loading from: root (cache)
DEBUG loader: Loading from: 2120_machine_raditz (evaluating)
DEBUG provisioner: Provisioner defined:
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
INFO box_collection: Box not found: royce/capsulecorp-winsrv (virtualbox)
WARN vagrantfile: Failed to locate royce/capsulecorp-winsrv with version 0.0.7-alpha-dc-member
WARN vagrantfile: Performing lookup with inital values royce/capsulecorp-winsrv with version 0.0.7-alpha-dc-member
INFO box_collection: Box not found: royce/capsulecorp-winsrv (virtualbox)
INFO box_collection: Box not found: royce/capsulecorp-winsrv (virtualbox)
INFO base: VBoxManage path: VBoxManage
DEBUG meta: Finding driver for VirtualBox version: 6.1.26
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_6_1
INFO base: VBoxManage path: VBoxManage
DEBUG environment: Initial usable provider list: [[6, :virtualbox], [5, :libvirt]]
DEBUG environment: Priority sorted usable provider list: [:virtualbox, :libvirt]
DEBUG environment: Preferred provider list: []
DEBUG environment: Using provider virtualbox as it is the highest priority in the usable list.
INFO loader: Set "2120_machine_pentest" = ["["2", #<Proc:0x00005598563f92f8 /home/termit/capsulecorp-pentest/Vagrantfile:34>]"]
DEBUG loader: Populating proc cache for ["2", #<Proc:0x00005598563f92f8 /home/termit/capsulecorp-pentest/Vagrantfile:34>]
INFO loader: Loading configuration in order: [:home, :root, "2120_machine_pentest"]
ERROR loader: Unknown config sources: ["2120_machine_goku", "2120_machine_gohan", "2120_machine_vegeta", "2120_machine_trunks", "2120_machine_tien", "2120_machine_raditz"]
DEBUG loader: Loading from: root (cache)
DEBUG loader: Loading from: 2120_machine_pentest (evaluating)
DEBUG provisioner: Provisioner defined:
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
INFO box_collection: Box not found: royce/capsulecorp-pentest (virtualbox)
WARN vagrantfile: Failed to locate royce/capsulecorp-pentest with version 0.0.4-alpha
WARN vagrantfile: Performing lookup with inital values royce/capsulecorp-pentest with version 0.0.4-alpha
INFO box_collection: Box not found: royce/capsulecorp-pentest (virtualbox)
INFO box_collection: Box not found: royce/capsulecorp-pentest (virtualbox)
INFO environment: Running hook: environment_plugins_loaded
INFO runner: Running action: environment_plugins_loaded #Vagrant::Action::Builder:0x00005598562f6dd8
INFO environment: Running hook: environment_load
INFO runner: Running action: environment_load #Vagrant::Action::Builder:0x00005598554c68a8
WARN checkpoint_client: checkpoint library not found. disabling.
INFO cli: CLI: [] "up" ["goku"]
DEBUG cli: Invoking command class: VagrantPlugins::CommandUp::Command ["goku"]
DEBUG checkpoint_client: waiting for checkpoint to complete...
DEBUG checkpoint_client: no information received from checkpoint
DEBUG command: 'Up' each target VM...
DEBUG command: Getting target VMs for command. Arguments:
DEBUG command: -- names: ["goku"]
DEBUG command: -- options: {:provider=>nil}
DEBUG command: Finding machine that match name: goku
INFO loader: Set "2120_machine_goku" = ["["2", #<Proc:0x00005598563fa158 /home/termit/capsulecorp-pentest/Vagrantfile:21>]"]
INFO loader: Loading configuration in order: [:home, :root, "2120_machine_goku"]
ERROR loader: Unknown config sources: ["2120_machine_gohan", "2120_machine_vegeta", "2120_machine_trunks", "2120_machine_tien", "2120_machine_raditz", "2120_machine_pentest"]
DEBUG loader: Loading from: root (cache)
DEBUG loader: Loading from: 2120_machine_goku (cache)
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
WARN vagrantfile: Failed to locate royce/capsulecorp-winsrv with version 0.0.5-alpha
WARN vagrantfile: Performing lookup with inital values royce/capsulecorp-winsrv with version 0.0.5-alpha
INFO base: VBoxManage path: VBoxManage
DEBUG meta: Finding driver for VirtualBox version: 6.1.26
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_6_1
INFO base: VBoxManage path: VBoxManage
DEBUG environment: Initial usable provider list: [[6, :virtualbox], [5, :libvirt]]
DEBUG environment: Priority sorted usable provider list: [:virtualbox, :libvirt]
DEBUG environment: Preferred provider list: []
DEBUG environment: Using provider virtualbox as it is the highest priority in the usable list.
INFO environment: Getting machine: goku (virtualbox)
INFO environment: Uncached load of machine.
INFO base: VBoxManage path: VBoxManage
DEBUG meta: Finding driver for VirtualBox version: 6.1.26
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_6_1
INFO base: VBoxManage path: VBoxManage
INFO loader: Set "2120_machine_goku" = ["["2", #<Proc:0x00005598563fa158 /home/termit/capsulecorp-pentest/Vagrantfile:21>]"]
INFO loader: Loading configuration in order: [:home, :root, "2120_machine_goku"]
ERROR loader: Unknown config sources: ["2120_machine_gohan", "2120_machine_vegeta", "2120_machine_trunks", "2120_machine_tien", "2120_machine_raditz", "2120_machine_pentest"]
DEBUG loader: Loading from: root (cache)
DEBUG loader: Loading from: 2120_machine_goku (cache)
DEBUG loader: Configuration loaded successfully, finalizing and returning
DEBUG push: finalizing
INFO box_collection: Box not found: royce/capsulecorp-winsrv (virtualbox)
WARN vagrantfile: Failed to locate royce/capsulecorp-winsrv with version 0.0.5-alpha
WARN vagrantfile: Performing lookup with inital values royce/capsulecorp-winsrv with version 0.0.5-alpha
INFO box_collection: Box not found: royce/capsulecorp-winsrv (virtualbox)
INFO box_collection: Box not found: royce/capsulecorp-winsrv (virtualbox)
INFO machine: Initializing machine: goku
INFO machine: - Provider: VagrantPlugins::ProviderVirtualBox::Provider
INFO machine: - Box:
INFO machine: - Data dir: /home/termit/capsulecorp-pentest/.vagrant/machines/goku/virtualbox
DEBUG virtualbox: Instantiating the driver for machine ID: nil
INFO base: VBoxManage path: VBoxManage
DEBUG meta: Finding driver for VirtualBox version: 6.1.26
INFO meta: Using VirtualBox driver: VagrantPlugins::ProviderVirtualBox::Driver::Version_6_1
INFO base: VBoxManage path: VBoxManage
DEBUG machine: Eager loading WinRM communicator to avoid GH-3390
INFO environment: Running hook: environment_unload
INFO host: Autodetecting host type for [#<Vagrant::Environment: /home/termit/capsulecorp-pentest>]
DEBUG host: Trying: arch
DEBUG host: Trying: alt
DEBUG host: Trying: redhat
DEBUG host: Trying: suse
DEBUG host: Trying: freebsd
DEBUG host: Trying: gentoo
DEBUG host: Trying: darwin
DEBUG host: Trying: slackware
DEBUG host: Trying: void
DEBUG host: Trying: bsd
DEBUG host: Trying: linux
INFO host: Detected: linux!
INFO runner: Running action: environment_unload #Vagrant::Action::Builder:0x000055985625ae88
Traceback (most recent call last):
25: from /usr/bin/vagrant:23:in <main>' 24: from /usr/bin/vagrant:23:in load'
23: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/bin/vagrant:200:in <top (required)>' 22: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/lib/vagrant/environment.rb:290:in cli'
21: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/lib/vagrant/cli.rb:67:in execute' 20: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/commands/up/command.rb:87:in execute'
19: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/lib/vagrant/plugin/v2/command.rb:186:in with_target_vms' 18: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/lib/vagrant/plugin/v2/command.rb:186:in each'
17: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/lib/vagrant/plugin/v2/command.rb:204:in block in with_target_vms' 16: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/lib/vagrant/plugin/v2/command.rb:180:in block in with_target_vms'
15: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/lib/vagrant/environment.rb:715:in machine' 14: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/lib/vagrant/vagrantfile.rb:81:in machine'
13: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/lib/vagrant/vagrantfile.rb:81:in new' 12: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/lib/vagrant/machine.rb:149:in initialize'
11: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/lib/vagrant/machine.rb:267:in communicate' 10: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/lib/vagrant/registry.rb:27:in get'
9: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/communicators/winrm/plugin.rb:15:in block in <class:Plugin>' 8: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in require'
7: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in require' 6: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/communicators/winrm/communicator.rb:6:in <top (required)>'
5: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/communicators/winrm/communicator.rb:6:in require_relative' 4: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/communicators/winrm/shell.rb:8:in <top (required)>'
3: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/lib/vagrant/util/silence_warnings.rb:8:in silence!' 2: from /usr/share/rubygems-integration/all/gems/vagrant-2.2.14/plugins/communicators/winrm/shell.rb:9:in block in <top (required)>'
1: from /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in require' /usr/lib/ruby/vendor_ruby/rubygems/core_ext/kernel_require.rb:85:in require': cannot load such file -- winrm (LoadError)

ip address Range issue

https://www.virtualbox.org/manual/ch06.html#network_hostonly
The IP address configured for the host-only network is not within the
allowed ranges. Please update the address used to be within the allowed
ranges and run the command again.

Address:
Ranges: 192.168.56.0/21

Valid ranges can be modified in the /etc/vbox/networks.conf file. For
more information including valid format see:
/etc/vbox/networks.conf fil -- i am unable to find this location
i

Network configuration issues

Hi Royce,

I've provisioned the four VM's as well as the pentest VM and found that the VM's are provisioned on two separte networks. Using nmap from the pentest VM shows:

• 4 VM's (including pentest) are on the 10...0/24 network and;
• 2 VM's (including pentest) are on the 172...0/24 network.

I've RPD'd into goku and checked the DNS manager which shows the following IP's:

• goku 172...100
• gohan 172...101
• vegeta 172...102
• trunks 172...103
• goku 10...15

Is this an issue with the vagrant provisioning of VM's? How do I fix this so all VM's are on the same network?

Cheers

rdesktop 172.28.128.103 problems on Trunks

I have managed to upload the webshell .war file onto the Tomcat server and I have executed all of the commands that grant write privileges to the BUILTIN\Administrators group however when I try to run rdesktop 172.28.128.103 I run into the errors:

Autoselected keyboard map en-us
ERROR: CredSSP: Initialize failed, do you have correct kerberos tgt initialized ?
Failed to connect, CredSSP required by server.

when I run xfreerdp /u:"Trunks" /p:"PasW0rd654#" /v:172.28.128.103 I get:

Autoselected keyboard map en-us
ERROR: CredSSP: Initialize failed, do you have correct kerberos tgt initialized ?

goku activation error

this one is for other people who like me need help. I've been working on this lab for 2 weeks and i managed to fix error manually which ansible could not get through.

I used this fix(I opened VirtualBox and got into goku machine, and only then I could apply these fixes):
https://www.youtube.com/watch?v=tmqNLv02KIk

and after that I ran vagrant provision goku again and the problem was solved.

Gohan SQL Server

TASK [mssql : Install SQL Server] **********************************************
fatal: [gohan]: FAILED! => {"changed": false, "module_version": "13.5.0", "msg": "Failed to invoke DSC Test method: An internal error occurred. ", "reboot_required": false

I am looking into the issue, but when I run vagrant up gohan I keep getting this Ansible failed message.

Any thoughts?

Configure the windows hosts missing tien & raditz hosts

Hello,
On the instruction page (https://github.com/r3dy/capsulecorp-pentest) on chapter "2.1. Configure the windows hosts" it missing:
~$ vagrant up tien
~$ vagrant provision tien
~$ vagrant up raditz
~$ vagrant provision raditz

Avi

Invalid permmissions on SSH private key

Got it now thanks guys!
I see the pentest box in VB

now im getting this error when i run "vagrant provision pentest"
The private key to connect to this box via SSH has invalid permissions
set on it. The permissions of the private key should be set to 0600, otherwise SSH will
ignore the key. Vagrant tried to do this automatically for you but failed. Please set the
permissions on the following file to 0600 and then try running this command again

I copied ssh/capsulecorp_id_rsa to /home/[username]/ssh/capsulecorp_id_rsa and im trying to point the Vagrantfile.

Originally posted by @bobsm1th in #25 (comment)

having problem with raditz

I deleted all of VM's and again downloaded them. i tried destroy also. but did not fix this error? how can i handle this error with ansible? does it have anything to do with vagrant and ansible versions installed? vagrant is 2.2.18 and ansible-core is 2.11.6. help me plz. I am stuck.

"winrm or requests is not installed" error message also after running "pip install pywinrm"

Hello,
I am using Windows with Ubunto 20.04 LTS.
When running "vagrant up goku" I got an error:
fatal: [goku]: FAILED! => {"msg": "winrm or requests is not installed: No module named winrm"}
Then I executed:
>pip install pywinrm
which solved the problem.
But then when running "vagrant provision goku" this error continue to appear.

/mnt/c/capsulecorp-pentest$ vagrant up goku
Bringing machine 'goku' up with 'virtualbox' provider...
==> goku: Checking if box 'royce/capsulecorp-winsrv' version '0.0.5-alpha' is up to date...
==> goku: Clearing any previously set forwarded ports...
==> goku: Clearing any previously set network interfaces...
==> goku: Preparing network interfaces based on configuration...
    goku: Adapter 1: nat
    goku: Adapter 2: hostonly
==> goku: Forwarding ports...
    goku: 3389 (guest) => 3389 (host) (adapter 1)
    goku: 5985 (guest) => 55985 (host) (adapter 1)
    goku: 5986 (guest) => 55986 (host) (adapter 1)
    goku: 22 (guest) => 2222 (host) (adapter 1)
==> goku: Booting VM...
==> goku: Waiting for machine to boot. This may take a few minutes...
    goku: WinRM address: 127.0.0.1:55985
    goku: WinRM username: vagrant
    goku: WinRM execution_time_limit: PT2H
    goku: WinRM transport: negotiate
==> goku: Machine booted and ready!
==> goku: Checking for guest additions in VM...
    goku: The guest additions on this VM do not match the installed version of
    goku: VirtualBox! In most cases this is fine, but in rare cases it can
    goku: prevent things such as shared folders from working properly. If you see
    goku: shared folder errors, please make sure the guest additions within the
    goku: virtual machine match the version of VirtualBox you have installed on
    goku: your host and reload your VM.
    goku:
    goku: Guest Additions Version: 6.0.18
    goku: VirtualBox Version: 6.1
==> goku: Configuring and enabling network interfaces...
==> goku: Mounting shared folders...
    goku: /vagrant => /mnt/c/capsulecorp-pentest
==> goku: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> goku: flag to force provisioning. Provisioners marked to run always will still run.
avi@DESKTOP-QIFF4AL:/mnt/c/capsulecorp-pentest$ vagrant provision goku
==> goku: Running provisioner: ansible...
Vagrant has automatically selected the compatibility mode '2.0'
according to the Ansible version installed (2.10.8).

Alternatively, the compatibility mode can be specified in your Vagrantfile:
https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode

    goku: Running ansible-playbook...
/home/avi/.local/lib/python2.7/site-packages/ansible/parsing/vault/__init__.py:44: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in the next release.
  from cryptography.exceptions import InvalidSignature

PLAY [goku] ********************************************************************

TASK [Gathering Facts] *********************************************************
fatal: [goku]: FAILED! => {"msg": "winrm or requests is not installed: No module named winrm"}

PLAY RECAP *********************************************************************
goku                       : ok=0    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

I am not sure, but maybe "pywinrm" was installed only on python3.8 while the ansible might works on python2 ?

/mnt/c/capsulecorp-pentest$ pip uninstall pywinrm
Found existing installation: pywinrm 0.4.1
Uninstalling pywinrm-0.4.1:
  Would remove:
    /home/avi/.local/lib/**python3.8**/site-packages/pywinrm-0.4.1.dist-info/*
    /home/avi/.local/lib/**python3.8**/site-packages/winrm/*
Proceed (y/n)?

If this is the problem, how do I fix it, and if not, any other suggestions?

Regards,
Avi

Vagrant provision failed

1. For vm vegeta
   TASK [jenkins : Set JNLP port for CLI access] **********************************
   fatal: [vegeta]: FAILED! => {"changed": false, "msg": "AnsibleUndefinedVariable: 'jenkins_jnlp_port' is undefined"}
2. For vm gohan
   ERROR! The requested handler 'reboot windows' was not found in either the main handlers list nor in the listening handlers list
3. For vm goku
   fatal: [goku]: FAILED! => {"changed": false, "elapsed": 1206, "msg": "Timed out waiting for post-reboot test command (timeout=600)", "rebooted": true}
4. For vm chunks
   fatal: [trunks]: FAILED! => {"changed": true, "msg": "failed to join domain: Computer 'WIN-VPVEIOA6767' failed to join domain 'capsulecorp.local' from its current workgroup 'WORKGROUP' with following error message: The specified domain either does not exist or could not be contacted.", "reboot_required": false}

Windows credentials Administrator:Password1! not on vegeta.capsulecorp.local

Following the book in chapter 4 Discovering network vulnerabilities and in the Appendix E we are supposed to find these vulnerabilities.

MSSQL credentials sa:Password1 on gohan.capsulecorp.local
Windows credentials Administrator:Password1! on vegeta.capsulecorp.local
Apache Tomcat credentials admin:admin on trunks.capsulecorp.local

The Windows credentials Administrator and password Password1! don't exist in the capsulecorp penetration testing environment on Vegeta however the other credentials sa:Password1 and admin:admin do exist on the other machines.

: * The host path of the shared folder is not supported from WSL. Host path of the shared folder must be located on a file system with DrvFs type. Host path: . How to resolve this issue?

Installed the plugin 'winrm-elevated (1.2.3)'!
tangoj@pakalu-papito:/mnt/c/capsulecorp-pentest$ vagrant up goku
Bringing machine 'goku' up with 'virtualbox' provider...
==> goku: Box 'royce/capsulecorp-winsrv' could not be found. Attempting to find and install...
goku: Box Provider: virtualbox
goku: Box Version: 0.0.5-alpha
==> goku: Loading metadata for box 'royce/capsulecorp-winsrv'
goku: URL: https://vagrantcloud.com/royce/capsulecorp-winsrv
==> goku: Adding box 'royce/capsulecorp-winsrv' (v0.0.5-alpha) for provider: virtualbox
goku: Downloading: https://vagrantcloud.com/royce/boxes/capsulecorp-winsrv/versions/0.0.5-alpha/providers/virtualbox.box
goku: Download redirected to host: vagrantcloud-files-production.s3-accelerate.amazonaws.com
goku: Calculating and comparing box checksum...
==> goku: Successfully added box 'royce/capsulecorp-winsrv' (v0.0.5-alpha) for 'virtualbox'!
**There are errors in the configuration of this machine. Please fix
the following errors and try again:

vm:

• The host path of the shared folder is not supported from WSL. Host
  path of the shared folder must be located on a file system with
  DrvFs type. Host path: .**

trying to rdp into goku 127.0.0.1:3389 , getting message as screenshot attached

Im using the DA creds goku\PassW0rd432!

All VMs except tien turn off after an hour

OS: Big Sur
VirtualBox 6.1.16 r140961 (Qt5.6.3)

goku.log

TASK [rvm : Add RVM GPG keys]

fatal: [pentest]: FAILED! => {"changed": true, "cmd": "gpg --keyserver hkp://pool.sks-keyservers.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 7D2BAF1CF37B13E2069D6956105BD0E739499BDB\n", "delta": "0:00:00.028044", "end": "2021-10-16 09:32:16.213332", "msg": "non-zero return code", "rc": 2, "start": "2021-10-16 09:32:16.185288", "stderr": "gpg: keyserver receive failed: No name", "stderr_lines": ["gpg: keyserver receive failed: No name"], "stdout": "", "stdout_lines": []}

fauilure on "vagrant provision raditz": Step "placeflag : Place exercise flag "

Hello,
I got an error when try to provision raditz host:

~$  vagrant provision raditz
==> raditz: Running provisioner: ansible...
Vagrant has automatically selected the compatibility mode '2.0'
according to the Ansible version installed (2.10.8).

Alternatively, the compatibility mode can be specified in your Vagrantfile:
https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode

    raditz: Running ansible-playbook...
/home/avi/.local/lib/python2.7/site-packages/ansible/parsing/vault/__init__.py:44: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in the next release.
  from cryptography.exceptions import InvalidSignature

PLAY [raditz] ******************************************************************

TASK [Gathering Facts] *********************************************************
[WARNING]: ERROR DURING WINRM SEND INPUT - attempting to recover:
WinRMOperationTimeoutError
ok: [raditz]

TASK [joindomain : Point dns to Goku] ******************************************
ok: [raditz]

TASK [joindomain : Enable Remote Desktop] **************************************
changed: [raditz]

TASK [joindomain : Open up port 445 on Windows firewall] ***********************
ok: [raditz]

TASK [joindomain : Open up port 3389 on Windows firewall] **********************
ok: [raditz]

TASK [joindomain : Join the capsulecorp.local domain] **************************
ok: [raditz]

TASK [joindomain : Reboot the server] ******************************************
changed: [raditz]

TASK [placeflag : Place exercise flag] *****************************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ConnectionError: ('Connection aborted.', BadStatusLine('No status line received - the server has closed the connection',))
fatal: [raditz]: FAILED! => {"msg": "Unexpected failure during module execution.", "stdout": ""}

PLAY RECAP *********************************************************************
raditz                     : ok=7    changed=2    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

Issue when running "vagrant up goku"

Hello,
Followed all the installation steps and everything installed successfully but when I run "vagrant up goku" its not seeing the VM and gives me this message:
"A Vagrant environment or target machine is required to run this
command. Run vagrant init to create a new Vagrant environment. Or,
get an ID of a target machine from vagrant global-status to run
this command on. A final option is to change to a directory with a
Vagrantfile and to try again."

Thank you,

vagrant up and vagrant provision commands don't work

Hi Royce, appreciate the work you've put into making this lab environment :)

Context
I'm following the Windows setup guide: I've enabled WSL, using an Ubuntu 20.04 box, and successfully installed pip, Ansible, and Vagrant (aka steps 1 - 4). However, once I've downloaded the CapsuleCorp git repo onto my Windows file system, I'm unable to successfully call the vagrant up and vagrant provision commands. Here's an example for goku:

/mnt/c/capsulecorp-pentest$ vagrant up goku
Bringing machine 'goku' up with 'virtualbox' provider...
==> goku: Checking if box 'royce/capsulecorp-winsrv' version '0.0.5-alpha' is up to date...
^@==> goku: Clearing any previously set forwarded ports...
==> goku: Fixed port collision for 3389 => 3389. Now on port 2200.
==> goku: Fixed port collision for 22 => 2222. Now on port 2201.
==> goku: Clearing any previously set network interfaces...
==> goku: Preparing network interfaces based on configuration...
    goku: Adapter 1: nat
    goku: Adapter 2: hostonly
==> goku: Forwarding ports...
    goku: 3389 (guest) => 2200 (host) (adapter 1)
    goku: 5985 (guest) => 55985 (host) (adapter 1)
    goku: 5986 (guest) => 55986 (host) (adapter 1)
    goku: 22 (guest) => 2201 (host) (adapter 1)
==> goku: Booting VM...
==> goku: Waiting for machine to boot. This may take a few minutes...
    goku: WinRM address: 127.0.0.1:55985
    goku: WinRM username: vagrant
    goku: WinRM execution_time_limit: PT2H
    goku: WinRM transport: negotiate
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

Running vagrant provision goku:

vagrant provision goku
^@==> goku: Running provisioner: ansible...
Vagrant gathered an unknown Ansible version:

ansible [core 2.11.2]
  config file = None
  configured module search path = ['/home/ping00/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /home/ping00/.local/lib/python3.8/site-packages/ansible
  ansible collection location = /home/ping00/.ansible/collections:/usr/share/ansible/collections
  executable location = /home/ping00/.local/bin/ansible
  python version = 3.8.5 (default, May 27 2021, 13:30:53) [GCC 9.3.0]
  jinja version = 2.10.1
  libyaml = True

and falls back on the compatibility mode '1.8'.

Alternatively, the compatibility mode can be specified in your Vagrantfile:
https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode

    goku: Running ansible-playbook...

PLAY [goku] ********************************************************************

TASK [Gathering Facts] *********************************************************
fatal: [goku]: FAILED! => {"msg": "winrm or requests is not installed: No module named 'winrm'"}

PLAY RECAP *********************************************************************
goku                       : ok=0    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

This one is confusing for me, since I'd installed the winrm, winrm-fs, winrm-elevated plugins like so right before:

/mnt/c/capsulecorp-pentest$ vagrant plugin install winrm
Installing the 'winrm' plugin. This can take a few minutes...
Parsing documentation for vagrant-libvirt-0.5.3
Parsing documentation for erubi-1.10.0
Parsing documentation for gssapi-1.3.1
Parsing documentation for gyoku-1.3.1
Parsing documentation for httpclient-2.8.3
Parsing documentation for little-plugger-1.1.4
Parsing documentation for logging-2.3.0
Parsing documentation for nori-2.6.0
Parsing documentation for rubyntlm-0.6.3
Parsing documentation for winrm-2.3.6
Parsing documentation for winrm-fs-1.3.5
Parsing documentation for winrm-elevated-1.2.3
unable to convert "$u" on UTF-16 for lib/winrm-elevated/scripts/elevated_shell.ps1, skipping
Done installing documentation for vagrant-libvirt, erubi, gssapi, gyoku, httpclient, little-plugger, logging, nori, rubyntlm, winrm, winrm-fs, winrm-elevated after 1 seconds
Installed the plugin 'winrm (2.3.6)'!

/mnt/c/capsulecorp-pentest$ vagrant plugin install winrm-fs
Installing the 'winrm-fs' plugin. This can take a few minutes...
Parsing documentation for vagrant-libvirt-0.5.3
Parsing documentation for erubi-1.10.0
Parsing documentation for gssapi-1.3.1
Parsing documentation for gyoku-1.3.1
Parsing documentation for httpclient-2.8.3
Parsing documentation for little-plugger-1.1.4
Parsing documentation for logging-2.3.0
Parsing documentation for nori-2.6.0
Parsing documentation for rubyntlm-0.6.3
Parsing documentation for winrm-2.3.6
Parsing documentation for winrm-fs-1.3.5
Parsing documentation for winrm-elevated-1.2.3
unable to convert "$u" on UTF-16 for lib/winrm-elevated/scripts/elevated_shell.ps1, skipping
Done installing documentation for vagrant-libvirt, erubi, gssapi, gyoku, httpclient, little-plugger, logging, nori, rubyntlm, winrm, winrm-fs, winrm-elevated after 1 seconds
Installed the plugin 'winrm-fs (1.3.5)'!

/mnt/c/capsulecorp-pentest$ vagrant plugin install winrm-elevated
Installing the 'winrm-elevated' plugin. This can take a few minutes...
Parsing documentation for vagrant-libvirt-0.5.3
Parsing documentation for erubi-1.10.0
Parsing documentation for gssapi-1.3.1
Parsing documentation for gyoku-1.3.1
Parsing documentation for httpclient-2.8.3
Parsing documentation for little-plugger-1.1.4
Parsing documentation for logging-2.3.0
Parsing documentation for nori-2.6.0
Parsing documentation for rubyntlm-0.6.3
Parsing documentation for winrm-2.3.6
Parsing documentation for winrm-fs-1.3.5
Parsing documentation for winrm-elevated-1.2.3
unable to convert "$u" on UTF-16 for lib/winrm-elevated/scripts/elevated_shell.ps1, skipping
Done installing documentation for vagrant-libvirt, erubi, gssapi, gyoku, httpclient, little-plugger, logging, nori, rubyntlm, winrm, winrm-fs, winrm-elevated after 1 seconds
Installed the plugin 'winrm-elevated (1.2.3)'!

Here's a screenshot of my VirtualBox machines if that helps shed more light on it:

I am able to start up pentest and goku, but the others are stuck in the "Guru Meditation" state. (As a side note: upon logging into pentest, I wasn't able to locate the ~/msf folder`, which makes me think something went wrong with that installation too, but it's easy enough to download and install msf, so I'm not too concerned about it)

Here's my output for vagrant up gohan (in the Guru Meditation state in the screenshot above):

/mnt/c/capsulecorp-pentest$ vagrant up gohan
Bringing machine 'gohan' up with 'virtualbox' provider...
==> gohan: Checking if box 'royce/capsulecorp-winsrv' version '0.0.7-alpha-dc-member' is up to date...
==> gohan: Clearing any previously set forwarded ports...
==> gohan: Clearing any previously set network interfaces...
==> gohan: Preparing network interfaces based on configuration...
    gohan: Adapter 1: nat
    gohan: Adapter 2: hostonly
==> gohan: Forwarding ports...
    gohan: 3389 (guest) => 3389 (host) (adapter 1)
    gohan: 5985 (guest) => 55985 (host) (adapter 1)
    gohan: 5986 (guest) => 55986 (host) (adapter 1)
    gohan: 22 (guest) => 2222 (host) (adapter 1)
==> gohan: Booting VM...
==> gohan: Waiting for machine to boot. This may take a few minutes...
    gohan: WinRM address: 127.0.0.1:55985
    gohan: WinRM username: vagrant
    gohan: WinRM execution_time_limit: PT2H
    gohan: WinRM transport: negotiate
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'gurumeditation' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.

Again, I appreciate the work you've put into this, but have you (or anyone else) encountered these errors? Would appreciate a pointer in the right direction, thanks very much.

pip fails to install in python2

During the Windows install guide for installing pip2 into the Ubuntu WSL I received the following error:

~$ python pipinstaller/get-pip.py --user
Traceback (most recent call last):
  File "pipinstaller/get-pip.py", line 24244, in <module>
    main()
  File "pipinstaller/get-pip.py", line 199, in main
    bootstrap(tmpdir=tmpdir)
  File "pipinstaller/get-pip.py", line 82, in bootstrap
    from pip._internal.cli.main import main as pip_entry_point
  File "/tmp/tmpjYusO6/pip.zip/pip/_internal/cli/main.py", line 60
    sys.stderr.write(f"ERROR: {exc}")

This is due to pip dropping support for Python 2 in January 2021.

I was able to get it installed by downloading the 2.7 versions pecifically:
~$ curl https://bootstrap.pypa.io/2.7/get-pip.py -o pipinstaller/get-pip.py

'gurumeditation' state for all the VMs except Goku

Hi,

I'm using virtualbox 6.1.14 and WSL2. I followed the instruction on the Wiki page, but I couldn't get all other boxes to work except for goku. Here's the error that occurred, any idea why?

==> gohan: Waiting for machine to boot. This may take a few minutes...
    gohan: WinRM address: 127.0.0.1:2201
    gohan: WinRM username: vagrant
    gohan: WinRM execution_time_limit: PT2H
    gohan: WinRM transport: negotiate
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'gurumeditation' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configure
```d. This is very rarely a Vagrant issue.

Vagrant don`t work on Ubuntu and Windows 10

I did everything according to the instructions in the description, but vagrant does not want to start and work further. What could be the problem? I filled in PATH correctly.

[``](

• 1. url

)

Gohan provision failed (TASK [mssql : Extract installation media] ) Pentest provision failed ( TASK [rvm : Add RVM GPG keys] )

failed provisioning pentest: TASK rvm : Add RVM GPG keys

Hi @R3dy,

The pentest VM failed vagrant provision pentest with the following error:

TASK [rvm : Add RVM GPG keys] **************************************************
fatal: [pentest]: FAILED! => {"changed": true, "cmd": "gpg --keyserver hkp://pool.sks-keyservers.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 7D2BAF1CF37B13E2069D6956105BD0E739499BDB\n", "delta": "0:00:00.372417", "end": "2020-06-22 15:56:01.250651", "msg": "non-zero return code", "rc": 2, "start": "2020-06-22 15:56:00.878234", "stderr": "gpg: keyserver receive failed: End of file", "stderr_lines": ["gpg: keyserver receive failed: End of file"], "stdout": "", "stdout_lines": []}

PLAY RECAP *********************************************************************
pentest : ok=10 changed=0 unreachable=0 failed=1 skipped=3 rescued=0 ignored=0

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

Is this something that can be skipped or is necessary?

Thanks.

what is the pentest machine password?

ansible issue when launching vagrant provision goku

Hello,

I am having an issue when launching "vagrant provision goku" Here under is the console log :

I run Windows 10 and installed Vagrant + Virtualbox and Ansible (via CyGwin on Windows)
I launched the command in the CyGwin terminal. Do you have any idea what could be the issue ?

$ vagrant provision goku
==> goku: Running provisioner: ansible...
Windows is not officially supported for the Ansible Control Machine.
Please check https://docs.ansible.com/intro_installation.html#control-machine-re
quirements
Vagrant gathered an unknown Ansible version:


and falls back on the compatibility mode '1.8'.

Alternatively, the compatibility mode can be specified in your Vagrantfile:
https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mo
de
    goku: Running ansible-playbook...
The Ansible software could not be found! Please verify
that Ansible is correctly installed on your host system.

If you haven't installed Ansible yet, please install Ansible
on your host system. Vagrant can't do this for you in a safe and
automated way.
Please check https://docs.ansible.com for more information.

Best regards,
Jan

MSSQL server on gohan is not reachable from the network

I had to manually enable TCP/IP (SQL Server Network Configuration) and disable TCP Dynamic Ports...

Ubuntu based installation Guide 20.10

Just sharing. hopefully helpful for some users.

Ubuntu 20.10

• Kernel 5.8.0-45

• virtualbox-dkms has problem with other kernels. need to use standard or specified kernel for distribution.

• other kernel 5.10 or 5.11 doesn't seem to work.

• install as usual. virtualbox -> vagrant->ansible->

[~]$ vagrant box list
royce/capsulecorp-pentest (virtualbox, 0.0.4-alpha)
royce/capsulecorp-winsrv (virtualbox, 0.0.5-alpha)
royce/capsulecorp-winsrv (virtualbox, 0.0.7-alpha-dc-member)

many thanks. it is very helpful for setup penetration testing library.

Gohan Fails: Problems adding package provider

TASK [mssql : Powershell | Check for SQLServer DSC Powershell module] **********
fatal: [gohan]: FAILED! => {"changed": false, "msg": "Problems adding package provider: No match was found for the specified search criteria for the provider 'NuGet'. The package provider requires 'PackageManagement' and 'Provider' tags. Please check if the specified package has the tags.", "nuget_changed": false, "output": "", "repository_changed": false}

PLAY RECAP *********************************************************************
gohan                      : ok=1    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

I really dont know what the issue here is. I tried vagrant destroy and then started again.. still didnt work.

I saw this article https://answers.microsoft.com/en-us/windows/forum/windows_7-performance/trying-to-install-program-using-powershell-and/4c3ac2b2-ebd4-4b2a-a673-e283827da143

not sure how to implement it with vagrant, ansible etc...

Any help would be appreciated

having problem with gohan machine, help me plz

hi Davis
it's been a while that I have problems with loading your valuable lab.
I've been reading your book but I can't practice.
please help me with this error.
by the way. i deleted all of vm's and again downloaded them. i tried destroy also. but this error in gohan doesn't fix.
I'm waiting for your help.
thank you

Cannot bring up pentest machine - SSH Issue

@R3dy @Leviter

Firstly, thank you so much for a cool project and I am loving the book by the way.

I have all of the VMs working apart from the pentest one. Set up completed on a Mac. Upon issuing vagrant up pentest, it gets to the SSH auth method: private key and then fails:

==> pentest: Booting VM...
==> pentest: Waiting for machine to boot. This may take a few minutes...
pentest: SSH address: 127.0.0.1:2217
pentest: SSH username: pentest
pentest: SSH auth method: private key
pentest: Warning: Connection reset. Retrying...

The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'aborted' state. Please verify everything is configured
properly and try again.

I did try changing the path to the key but that did not work either.

config.vm.define "pentest" do |box|
box.vm.box = "royce/capsulecorp-pentest"
box.vm.box_version ="0.0.4-alpha"
box.vm.network "private_network", ip: "172.28.128.200"
box.vm.network :forwarded_port, guest: 3389, host: 3389, auto_correct: true
box.ssh.username = "pentest"
box.ssh.private_key_path = "ssh/capsulecorp_id_rsa"
box.vm.provision "ansible" do |ansible|
ansible.playbook = "pentest.yml"

Changed to /Users/XXXXX/capsulecorp-pentest but as mentioned same error came up.

Thanks in advance

Goku Provision

What should I do?

[.xsesison file] the field 'become' has an invalid value (pentest), and could not be converted to an bool.

Hello,
When running "vagrant provision pentest" I got an error (see below).
Any suggestion?

Thanks,
Avi

/mnt/c/capsulecorp-pentest$ vagrant provision pentest
==> pentest: Running provisioner: ansible...
Vagrant has automatically selected the compatibility mode '2.0'
according to the Ansible version installed (2.10.8).

Alternatively, the compatibility mode can be specified in your Vagrantfile:
https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode

    pentest: Running ansible-playbook...
/home/avi/.local/lib/python2.7/site-packages/ansible/parsing/vault/__init__.py:44: CryptographyDeprecationWarning: Python 2 is no longer supported by the Python core team. Support for it is now deprecated in cryptography, and will be removed in the next release.
  from cryptography.exceptions import InvalidSignature

PLAY [pentest] *****************************************************************

TASK [Gathering Facts] *********************************************************
[DEPRECATION WARNING]: Distribution Ubuntu 18.04 on host pentest should use
/usr/bin/python3, but is using /usr/bin/python for backward compatibility with
prior Ansible releases. A future Ansible release will default to using the
discovered platform python for this host. See https://docs.ansible.com/ansible/
2.10/reference_appendices/interpreter_discovery.html for more information. This
 feature will be removed in version 2.12. Deprecation warnings can be disabled
by setting deprecation_warnings=False in ansible.cfg.
ok: [pentest]

TASK [crackmapexec : set_fact] *************************************************
ok: [pentest]

TASK [crackmapexec : Check if CME is already installed] ************************
ok: [pentest]

TASK [crackmapexec : shell] ****************************************************
skipping: [pentest]

TASK [crackmapexec : Ensure pip --user enabled in .bashrc] *********************
skipping: [pentest]

TASK [crackmapexec : Pip install CrackMapExec] *********************************
skipping: [pentest]

TASK [nmap : Make sure no lock files are present] ******************************
changed: [pentest] => (item=/var/lib/dpkg/lock)
changed: [pentest] => (item=/var/lib/dpkg/lock-frontend)

TASK [nmap : Apt install nmap deps] ********************************************
ok: [pentest] => (item=git)
ok: [pentest] => (item=wget)
ok: [pentest] => (item=build-essential)
ok: [pentest] => (item=checkinstall)
ok: [pentest] => (item=libpcre3-dev)
ok: [pentest] => (item=libssl-dev)
ok: [pentest] => (item=libpcap-dev)
ok: [pentest] => (item=autoconf)

TASK [nmap : Mkdir $HOME/src/] *************************************************
ok: [pentest]

TASK [nmap : Git checkout nmap source] *****************************************
ok: [pentest]

TASK [nmap : Run nmap configure] ***********************************************
ok: [pentest]

TASK [nmap : Run nmap make] ****************************************************
ok: [pentest]

TASK [nmap : Run nmap make install] ********************************************
ok: [pentest]

TASK [rvm : Add RVM GPG keys] **************************************************
changed: [pentest]

TASK [rvm : Pull down RVM and install with latest stable] **********************
changed: [pentest]

TASK [rvm : Add RVM bin path to $PATH] *****************************************
ok: [pentest]

TASK [rvm : Add pentest to the RVM group] **************************************
changed: [pentest]

TASK [rvm : Source the rvm-path.sh file] ***************************************
changed: [pentest]

TASK [metasploit : set_fact] ***************************************************
ok: [pentest]

TASK [metasploit : Install necessary gem bundler] ******************************
changed: [pentest]

TASK [metasploit : Install necessary gem wirble] *******************************
changed: [pentest]

TASK [metasploit : Install necessary gem sqlite3] ******************************
changed: [pentest]

TASK [metasploit : Apt install metasploit deps] ********************************
ok: [pentest] => (item=gpgv2)
ok: [pentest] => (item=autoconf)
ok: [pentest] => (item=bison)
ok: [pentest] => (item=build-essential)
ok: [pentest] => (item=curl)
changed: [pentest] => (item=git-core)
ok: [pentest] => (item=libapr1)
ok: [pentest] => (item=libaprutil1)
ok: [pentest] => (item=libcurl4-openssl-dev)
ok: [pentest] => (item=libgmp3-dev)
ok: [pentest] => (item=libpcap-dev)
ok: [pentest] => (item=libpq-dev)
ok: [pentest] => (item=libreadline6-dev)
ok: [pentest] => (item=libsqlite3-dev)
ok: [pentest] => (item=libssl-dev)
ok: [pentest] => (item=libsvn1)
ok: [pentest] => (item=libtool)
ok: [pentest] => (item=libxml2)
ok: [pentest] => (item=libxml2-dev)
ok: [pentest] => (item=libxslt-dev)
ok: [pentest] => (item=libyaml-dev)
ok: [pentest] => (item=locate)
ok: [pentest] => (item=ncurses-dev)
ok: [pentest] => (item=openssl)
ok: [pentest] => (item=postgresql)
ok: [pentest] => (item=postgresql-contrib)
ok: [pentest] => (item=wget)
ok: [pentest] => (item=xsel)
ok: [pentest] => (item=zlib1g)
ok: [pentest] => (item=zlib1g-dev)

TASK [metasploit : Mkdir msf directory] ****************************************
ok: [pentest]

TASK [metasploit : Git checkout metasploit source] *****************************
ok: [pentest]

TASK [metasploit : Make sure no Gemfile.lock is present] ***********************
ok: [pentest] => (item=/home/pentest/msf/Gemfile.lock)

TASK [metasploit : Run bundle install] *****************************************
changed: [pentest]

TASK [pentest : Snap install Remmina RDP client] *******************************
changed: [pentest]

TASK [pentest : Apt remove light-locker] ***************************************
changed: [pentest]

TASK [xrdp : Fix XRDP file] ****************************************************
changed: [pentest]

TASK [xrdp : Create the .xsesison file] ****************************************
fatal: [pentest]: FAILED! => {"msg": "the field 'become' has an invalid value (pentest), and could not be converted to an bool.The error was: The value 'pentest' is not a valid boolean.  Valid booleans include: 0, 'on', 'f', 'false', 1, 'no', 'n', '1', '0', 't', 'y', 'off', 'yes', 'true'"}

PLAY RECAP *********************************************************************
pentest                    : ok=27   changed=13   unreachable=0    failed=1    skipped=3    rescued=0    ignored=0

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

DEPRECATION WARNING

I am getting Deprecation Warning when installing Pentest VM , on Ubuntu version and python. I am asking if you can please ( Royce Davis ) update/upgrade the Pentest VM with the required version. I certainly believe this is the reason CrackMapExec/cme execution is failing, Ref page of the Book: 4.3.2

Thank you.

Vagrant issue when using Win10 and WSL

In step 4 of your instructions:
Check out the code from Github
https://github.com/R3dy/capsulecorp-pentest/wiki/MacOS-Setup-Guide

If I'm using Win 10 with WSL and also the following instructions from:
https://alchemist.digital/articles/vagrant-ansible-and-virtualbox-on-wsl-windows-subsystem-for-linux/

When I run :
vagrant up goku

It ends with:

There are errors in the configuration of this machine...
vm:

• The host path of the shared folder is not supported from WSL. Host
  path of the shared folder must be located on a file system with
  DrvFs type. Host path: .

I cloned the repo under:
/mnt/c/Users/MyName/Desktop/

I did google for a solutions and found this:
hashicorp/vagrant#10576

I thought being under /mnt/c would have solved the problem, but it didn't.
I'm a n00b with vagrant and WSL, so I wasn't sure what new side effects the code change would make.

Where is it safe to create the repo and run vagrant from?
I'm using Ubuntu 18, VirtualBox 6, Ansible 2.91, and Vagrant 2.2.9 (Which is also complaining about using Python 2.7)

Seems like Sticky Keys hack no longer works

Regarding chapter 05 sticky key hacks

1. the server now is win 2019
2. it says cacls is deprecate, it suggest use icacls
3. Cannot c:\windows\system32\sethc.exe to have BUILTIN\Administrators:F
4. Even use icacls, it can only modify to RX

how to manually add boxes?

hello dear Royce Davis
first of all I have to thank you for your great work on The Art of Network Penetration Testing which I bought recently and I have plane to read it through.
and second I had a question about this capsulecorp-pentest lab which you designed and seems very interesting.
I don't know why but 'vagrant up' seems very slow on downloading machines from vagrant servers.
I managed to download them manually with a downloader app and I want to manually add them to vagrant. not with 'vagrant up' command, but with 'vagrant box add' command.
I really would appreciate your help on it because I don't exactly know how to do it and how to edit your Vagrantfile.

problem with pentest machine

hi again
I have to tell you something about provisioning pentest machine. i only don't want others to bother themselves as i did.
I think you have to modify pentest ansible playbook file.

first of all; this command (gpg --keyserver hkp://pool.sks-keyservers.net --recv-keys 409B6B1796C275462A1703113804BB82D39DC0E3 7D2BAF1CF37B13E2069D6956105BD0E739499BDB) does not work most of the times. I had to install gpg2 and used official rvm document and I added this key manually. so here ansible playbook throughs an error and doesn't go further. with this: "keyserver receive failed: no name"

second. /etc/profile.d/rvm-path.sh --> this file does not exist anymore it's name is rvm.sh
and 3rd, latest stable ruby version is not 2.7 which you added to rvm paths, its version 3, and I think it will be added to paths automatically(look inside rvm.sh).

I did above jobs manually and deleted -role = rvm line from pentest.yml file and ran provision again on pentest fortunately no error left to handle.

your book is amazing but without this capsulecorp lab one can not profit enough of it, I just want others to enjoy this book as much as I am. so please make changes to this ansible files.
goku activation problem (I started an issue on this one with solution, which you closed )
raditz domain name updating problem (i started another issue on this one too with solution ) and gohan mssql downloading problem. and here was pentest vm provisioning which had multiple issues and has to be updated.

I only care, that's all.
thanks again for your work on capsulecorp pentest lab and your book on network pentesting.

for ansible

Although ansible is installed, ansible ignores when I try the "vagrant provision goku" command.

`Windows is not officially supported for the Ansible Control Machine.
Please check https://docs.ansible.com/intro_installation.html#control-machine-requirements
Vagrant gathered an unknown Ansible version:

                                                                            and falls back on the compatibility mode '1.8'.

Alternatively, the compatibility mode can be specified in your Vagrantfile:
https://www.vagrantup.com/docs/provisioning/ansible_common.html#compatibility_mode
goku: Running ansible-playbook...
The Ansible software could not be found! Please verify
that Ansible is correctly installed on your host system.

If you haven't installed Ansible yet, please install Ansible
on your host system. Vagrant can't do this for you in a safe and
automated way.
Please check https://docs.ansible.com for more information.`

Error while executing VBoxManage

What should i do?

Supplement of Windows Setup Guide in wiki

I setup capsulecorp-pentest on windows wsl, i already install vagrant plugin install winrm and other plugin,

run vagrant up goku is ok, but run vagrant provision goku has some error like this:

  from cryptography.exceptions import InvalidSignature

PLAY [goku] ********************************************************************

TASK [Gathering Facts] *********************************************************
fatal: [goku]: FAILED! => {"msg": "winrm or requests is not installed: No module named winrm"}

PLAY RECAP *********************************************************************
goku                       : ok=0    changed=0    unreachable=0    failed=1    skipped=0    rescued=0    ignored=0

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

I run pip install pywinrm to solve this problem

If run pip install pywinrm is necessary, join the wiki

great program，thank you!

Gohan: Resource SqlServerConfiguration not found

Hi @R3dy,

I'm having a similar issue when running vagrant provision gohan:

TASK [mssql : Adjust Max Server Memory to 1024] ********************************
fatal: [gohan]: FAILED! => {"changed": false, "msg": "Resource 'SqlServerConfiguration' not found."}
PLAY RECAP *********************************************************************
gohan : ok=22 changed=18 unreachable=0 failed=1 skipped=1 rescued=0 ignored=0

Was wondering if I can try your instructions:

vagrant destroy gohan
vagrant up gohan
vagrant provision gohan

I did notice most times the vagrant up command has some kind of failure and then when I run it again, it says it is installed and to run vagrant provision. Sometimes vagrant provision will have an error once and when I re-run it, everything is successful.

It's just gohan that hasn't worked when re-running vagrant provision on it.

Thanks in advance.

Originally posted by @AaronKung in #5 (comment)

Virtual machine images

Can someone share ready-made virtual machine images, preferably for VirtualBox? Specifically interested in the images of the virtual machines gohan, vegeta and trunks. I'll be very thankful)

"Guest machine entered an invalid state error" when adding gohan, vegeta and trunks

I am getting the following message when I am trying to do vargrant up for any of the other three windows machines.
I am able to successfully execute vargrant up and vargrant provision commands on goku but any of the other three returns the same error.

I suspect it has to do with virtualization by VB; however, I can't find any answer or solution online.

It's Windows 10 Home, AMD Ryzen processor.
Virtual Box Version 6.1.16 r140961 (Qt5.6.2)

Pip Installer Error

When I run the curl command (curl https://bootstrap.pypa.io/get-pip.py -o pipinstaller/get-pip.py) it looks to run successfully but when I run the next command (python pipinstaller/get-pip.py --user) I get an error that says this script does not work for python version 3.6 and suggests that I use python 2.7. If I run the recommended python 2.7, so that I can run the second command (which works), I get a warning that python 2.7 is EOL and no longer maintained. Does the command 'python pipinstaller/get-pip.py --user' need to be adjusted to work correctly for python 3.6? Below is the error:

pentest@Smart-Laptop:$ curl https://bootstrap.pypa.io/get-pip.py -o pipinstaller/get-pip.py
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1892k 100 1892k 0 0 3517k 0 --:--:-- --:--:-- --:--:-- 3524k
pentest@Smart-Laptop:$ python pipinstaller/get-pip.py --user
ERROR: This script does not work on Python 2.7 The minimum supported Python version is 3.6. Please use https://bootstrap.pypa.io/pip/2.7/get-pip.py instead.
pentest@Smart-Laptop:~$

Thank you