Hi there,

this is maybe not a code question, however do you have free resources to exercises that could be done with this setup?

I try to follow install vagrant box as describe but no luck get 503 errors like this

D:\pentest-env> vagrant up kali
Bringing machine 'kali' up with 'virtualbox' provider...
==> kali: Box 'kali-2016.1' could not be found. Attempting to find and install...
    kali: Box Provider: virtualbox
    kali: Box Version: >= 0
==> kali: Box file was not detected as metadata. Adding it directly...
==> kali: Adding box 'kali-2016.1' (v0) for provider: virtualbox
    kali: Downloading: http://box.hackbbs.org/kali-2016.1.box
    kali:
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

The requested URL returned error: 503 Service Unavailable

Hello,

I run into this issue when vagrant up chef-workstation (running the chef-environment example):

The install process as described in the doc went fine, no errors whatsoever.
Ask me if you need further info on my System or else.
Thanks a lot !

I don't know the password of metasploitable3-trusty

I tryied:

• vagrant/vagrant
• root/root
• root/toor
• pentest-env

Hey,

just updated to the latest git version and just realized that downloading the boxes failes. Looks like HashiCorp changed sth.

$ PENTESTRC=examples/test1.pentestrc vagrant up
Bringing machine 'kali' up with 'virtualbox' provider...
==> kali: Box 'Sliim/kali-2017.2-amd64' could not be found. Attempting to find a
nd install...
    kali: Box Provider: virtualbox
    kali: Box Version: >= 0
The box 'Sliim/kali-2017.2-amd64' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:

URL: ["https://atlas.hashicorp.com/Sliim/kali-2017.2-amd64"]
Error: The requested URL returned error: 404 Not Found

Looks like there is already an open issue at vagrant: hashicorp/vagrant#9442

I haven't tried if pentest-env works with the latest vagrant version. So temp fix is adding:
Vagrant::DEFAULT_SERVER_URL.replace('https://vagrantcloud.com') to Vagrantfile in the pentest-env root folder.

It looks like you just updated the Vagranfile. In early version I change the box URL in Vagrantfile.

I just realized that the box hosting server isn't using TLS to serve the boxes or the checksums list. Consider buying a certificate or at least using Let's Encrypt to install a free cert.

Hello there,
I tried to manually setup port forwarding on Adapter 1 via the GUI, however these settings are cleared each time the machine reboots. How can I setup port forwarding via my ~/.pentestrc?

Thank you,
tiferrei

https://app.vagrantup.com/offensive-security

Hi there, I tried adding the ssh key to get access to the vm, however, on vagrant up I always get:

Bringing machine 'kali' up with 'virtualbox' provider...
==> kali: Checking if box 'Sliim/kali-linux-2.0-amd64' is up to date...
==> kali: Clearing any previously set forwarded ports...
==> kali: Clearing any previously set network interfaces...
==> kali: Preparing network interfaces based on configuration...
    kali: Adapter 1: nat
==> kali: Forwarding ports...
    kali: 22 (guest) => 2222 (host) (adapter 1)
==> kali: Running 'pre-boot' VM customizations...
==> kali: Booting VM...
==> kali: Waiting for machine to boot. This may take a few minutes...
    kali: SSH address: 127.0.0.1:2222
    kali: SSH username: vagrant
    kali: SSH auth method: private key
    kali: Warning: Authentication failure. Retrying...
...

I am adding the private key to my host's ssh folder, am I doing something wrong?

Thank you,
Tiago

There is some issues on actual Kali box 2016.1:

1. Vagrant cannot connect to virtual machine, so no ssh, no shared folder, no provisioning...
   This issues can be resolved by setting up the eth0 interface in /etc/network/interfaces:

   auto eth0
   iface eth0 inet dhcp
   

2. Vagrant cannot configure and enable public network (private net can be affected)
   When the public network is enabled, vagrant fails with message:

   The following SSH command responded with a non-zero exit status.
   Vagrant assumes that this means the command failed!
   
   /sbin/ifdown eth1 2> /dev/null
   
   Stdout from the command:
   
   Stderr from the command:
   
   mesg: ttyname failed: Inappropriate ioctl for device
   

   No fix yet! A possible workaround is to up the kali machine without extra network (comment public & private net), wait for provisioning.. uncomment wanted network(s) and run vagrant reload kali.

Fixing these issues will result to a new Box.

Build some boxes with latest kali rolling release (2017.1)

I mean another Vagrantfile.
Hacking with Tor is already an fundamental requirement, since Tor provide anonymity over other alternatives, although not perfect, but practical enough for most scenarios.

this is a guide of configuring Kali with Tor(provided by Whonix Gateway), but not along with Vagrant.

Since Vagrant needs the adapter 1 with NAT(source). So one possible solution would be:

adapter 1: NAT(default, but need to disconnect from Internet)
adapter 2: internal network of Virtualbox
And the default route of Kali is configured to point to the Whonix Gateway. Also DNS server is pointed to Whonix.

Hi,
I am new to this and I'm trying to bring up the VM using Vagrant. I have downloaded the files into a new directory and ran "vagrant up" command but I get this error:
C:\vagrant>cd pentest-env-master

C:\vagrant\pentest-env-master>vagrant up
C:/vagrant/pentest-env-master/lib/pentestenv/instance.rb:18:in initialize': Spe cified instance kalinot found. (ArgumentError) from C:/vagrant/pentest-env-master/lib/pentestenv/customization.rb:18:innew'
from C:/vagrant/pentest-env-master/lib/pentestenv/customization.rb:18:in
block in register' from C:/vagrant/pentest-env-master/lib/pentestenv/customization.rb:17:in each'
from C:/vagrant/pentest-env-master/lib/pentestenv/customization.rb:17:in
register' from C:/vagrant/pentest-env-master/Vagrantfile:21:in block in <top (req
uired)>'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/c
onfig/v2/loader.rb:37:in call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/c onfig/v2/loader.rb:37:in load'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/c
onfig/loader.rb:113:in block (2 levels) in load' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/c onfig/loader.rb:107:in each'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/c
onfig/loader.rb:107:in block in load' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/c onfig/loader.rb:104:in each'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/c
onfig/loader.rb:104:in load' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/v agrantfile.rb:28:in initialize'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/e
nvironment.rb:746:in new' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/e nvironment.rb:746:in vagrantfile'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/e
nvironment.rb:492:in host' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/e nvironment.rb:214:in block in action_runner'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/a
ction/runner.rb:33:in call' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/a ction/runner.rb:33:in run'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/e
nvironment.rb:479:in hook' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/lib/vagrant/e nvironment.rb:728:in unload'
from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/bin/vagrant:1
92:in ensure in <main>' from C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.7/bin/vagrant:1 92:in

C:\vagrant\pentest-env-master>

I have not changed anything. is this how it is supposed to be? maybe I have made a wrong configuration somewhere?

You will have to excuse me as I am new to Chef and am probably misunderstanding something - I am wondering why in this example file you set both the role, 'kali-base', but also the recipe 'kali'. I looked at the kali-base role and it appears to already have this recipe in its run-list. Is it necessary to have it in both places?

I use VMWare Fusion with Vagrant because Virtualbox is just well, terrible. I was wondering how the Vagrant virtual box is pre-built/provisioned.I'd be happy to build the VMware port myself, I just would like to know what that all entails.

After I get the VM up and running I try doing vagrant ssh kali but it doesn't work. It tries to connect to [email protected], which should just be my computer not the kali vm. How can I ssh into the VM?

Thanks

Hi,

I'm installing this on the very latest version of Kali 2018.4, and I'm having issues doing the "bundle exec berks vendor -d"

I get the following argument error: ArgumentError "\x80\x00\x00\x00\e\xA3V\xC0" is not an octal string

...
I, [2018-11-06T01:14:26.396480 #900]  INFO -- : Installing selinux_policy (2.1.0)
D, [2018-11-06T01:14:26.399569 #900] DEBUG -- :   Already installed - skipping install
Using pentester (1.6.1)
D, [2018-11-06T01:14:26.400041 #900] DEBUG -- :   Already installed - skipping install
Using selinux_policy (2.1.0)
ArgumentError "\x80\x00\x00\x00\e\xA3V\xC0" is not an octal string
	/usr/lib/ruby/2.5.0/rubygems/package/tar_header.rb:128:in `strict_oct'
	/usr/lib/ruby/2.5.0/rubygems/package/tar_header.rb:108:in `from'
	/usr/lib/ruby/2.5.0/rubygems/package/tar_reader.rb:59:in `each'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/mixlib-archive-0.4.18/lib/mixlib/archive/tar.rb:28:in `block in extract'
	/usr/lib/ruby/2.5.0/rubygems/package/tar_reader.rb:29:in `new'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/mixlib-archive-0.4.18/lib/mixlib/archive/tar.rb:145:in `reader'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/mixlib-archive-0.4.18/lib/mixlib/archive/tar.rb:26:in `extract'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/mixlib-archive-0.4.18/lib/mixlib/archive.rb:47:in `extract'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/berkshelf-7.0.6/lib/berkshelf/community_rest.rb:15:in `unpack'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/berkshelf-7.0.6/lib/berkshelf/community_rest.rb:94:in `download'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/berkshelf-7.0.6/lib/berkshelf/downloader.rb:71:in `try_download'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/berkshelf-7.0.6/lib/berkshelf/downloader.rb:41:in `block in download'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/berkshelf-7.0.6/lib/berkshelf/downloader.rb:40:in `each'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/berkshelf-7.0.6/lib/berkshelf/downloader.rb:40:in `download'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/berkshelf-7.0.6/lib/berkshelf/installer.rb:108:in `install'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/berkshelf-7.0.6/lib/berkshelf/installer.rb:181:in `block (2 levels) in install_from_universe'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/concurrent-ruby-1.1.1/lib/concurrent/executor/safe_task_executor.rb:24:in `block in execute'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/concurrent-ruby-1.1.1/lib/concurrent/synchronization/mutex_lockable_object.rb:41:in `block in synchronize'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/concurrent-ruby-1.1.1/lib/concurrent/synchronization/mutex_lockable_object.rb:41:in `synchronize'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/concurrent-ruby-1.1.1/lib/concurrent/synchronization/mutex_lockable_object.rb:41:in `synchronize'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/concurrent-ruby-1.1.1/lib/concurrent/executor/safe_task_executor.rb:19:in `execute'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/concurrent-ruby-1.1.1/lib/concurrent/ivar.rb:169:in `safe_execute'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/concurrent-ruby-1.1.1/lib/concurrent/future.rb:55:in `block in execute'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/concurrent-ruby-1.1.1/lib/concurrent/executor/ruby_thread_pool_executor.rb:348:in `run_task'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/concurrent-ruby-1.1.1/lib/concurrent/executor/ruby_thread_pool_executor.rb:337:in `block (3 levels) in create_worker'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/concurrent-ruby-1.1.1/lib/concurrent/executor/ruby_thread_pool_executor.rb:320:in `loop'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/concurrent-ruby-1.1.1/lib/concurrent/executor/ruby_thread_pool_executor.rb:320:in `block (2 levels) in create_worker'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/concurrent-ruby-1.1.1/lib/concurrent/executor/ruby_thread_pool_executor.rb:319:in `catch'
	/opt/pentest-env/vendor/bundle/ruby/2.5.0/gems/concurrent-ruby-1.1.1/lib/concurrent/executor/ruby_thread_pool_executor.rb:319:in `block in create_worker'

Create or use an existing vagrant box for BlackArch OS

Hi,
I'm new to all of this so i'm trying to learn and figure out a lot of things. I have used the command:
"vagrant init Sliim/kali-linux-2.0-amd64; vagrant up --provider virtualbox" to bring up the VM. it worked fine but I got an error trying to do the SSH for verifiying:
C:\vagrant>vagrant up kali
Bringing machine 'kali' up with 'virtualbox' provider...
==> kali: Box 'Sliim/kali-linux-2.0-amd64' could not be found. Attempting to fi
d and install...
kali: Box Provider: virtualbox
kali: Box Version: >= 0
==> kali: Loading metadata for box 'Sliim/kali-linux-2.0-amd64'
kali: URL: https://atlas.hashicorp.com/Sliim/kali-linux-2.0-amd64
==> kali: Adding box 'Sliim/kali-linux-2.0-amd64' (v2.0) for provider: virtualb
x
kali: Downloading: https://atlas.hashicorp.com/Sliim/boxes/kali-linux-2.0-a
d64/versions/2.0/providers/virtualbox.box
kali: Progress: 100% (Rate: 9255k/s, Estimated time remaining: --:--:--)
==> kali: Successfully added box 'Sliim/kali-linux-2.0-amd64' (v2.0) for 'virtu
lbox'!
==> kali: Importing base box 'Sliim/kali-linux-2.0-amd64'...
==> kali: Matching MAC address for NAT networking...
==> kali: Checking if box 'Sliim/kali-linux-2.0-amd64' is up to date...
==> kali: Setting the name of the VM: vagrant_kali_1479656317418_68770
==> kali: Clearing any previously set network interfaces...
==> kali: Preparing network interfaces based on configuration...
kali: Adapter 1: nat
==> kali: Forwarding ports...
kali: 22 (guest) => 2222 (host) (adapter 1)
==> kali: Booting VM...
==> kali: Waiting for machine to boot. This may take a few minutes...
kali: SSH address: 127.0.0.1:2222
kali: SSH username: vagrant
kali: SSH auth method: private key
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
kali: Warning: Authentication failure. Retrying...
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.

after this I can do "vagrant ssh" to the VM but I get a request for password (for vagrant user I guess).
i have tired to use the "toor" password and i have tried to do SHS directly with root but nothing is working.
I have the private key from here:
https://github.com/Sliim/pentest-env/blob/master/ssh-keys/pentest-env
but I have no idea how to use it, can someone help me with understanding how can I make vagrant use the ssh key? where to put it and make vagrant use it correctly?

Is it possible to update to Kali Linux 1.1.0a?

Thanks

Error below: running 'rake --trace'

** Invoke default (first_time)
** Invoke vendor (first_time)
** Execute vendor
rm -rf cookbooks
berks vendor cookbooks
rake aborted!
Command failed with status (127): [berks vendor cookbooks...]
/Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/file_utils.rb:66:in block in create_shell_runner' /Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/file_utils.rb:56:in call'
/Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/file_utils.rb:56:in sh' /Users/Shared/pentest-env/Rakefile:5:in block in <top (required)>'
/Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/task.rb:250:in call' /Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/task.rb:250:in block in execute'
/Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/task.rb:250:in each' /Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/task.rb:250:in execute'
/Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/task.rb:194:in block in invoke_with_call_chain' /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/monitor.rb:211:in mon_synchronize'
/Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/task.rb:187:in invoke_with_call_chain' /Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/task.rb:216:in block in invoke_prerequisites'
/Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/task.rb:214:in each' /Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/task.rb:214:in invoke_prerequisites'
/Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/task.rb:193:in block in invoke_with_call_chain' /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/monitor.rb:211:in mon_synchronize'
/Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/task.rb:187:in invoke_with_call_chain' /Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/task.rb:180:in invoke'
/Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/application.rb:152:in invoke_task' /Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/application.rb:108:in block (2 levels) in top_level'
/Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/application.rb:108:in each' /Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/application.rb:108:in block in top_level'
/Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/application.rb:117:in run_with_threads' /Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/application.rb:102:in top_level'
/Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/application.rb:80:in block in run' /Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/application.rb:178:in standard_exception_handling'
/Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/lib/rake/application.rb:77:in run' /Library/Ruby/Gems/2.0.0/gems/rake-12.0.0/exe/rake:27:in <top (required)>'
/usr/local/bin/rake:23:in load' /usr/local/bin/rake:23:in

Hi Sliim,
I thought I would point out that the gpg key in the 2017.2 images has expired.

Kali upstream updated their keys with a new expiry date, which has been pushed out (new version of kali-archive-keyring should be 2018.1). The problem is that you have to update your key manually if you didn't get the debian package on time. Meaning the system won't update at that point anymore.

Maybe you could publish a new version with the new keyring?

Manual workaround that worked for me:
gpg --list-keys --keyring /usr/share/keyrings/kali-archive-keyring.gpg # to verify key id
gpg --keyring /usr/share/keyrings/kali-archive-keyring.gpg --keyserver hkp://keys.gnupg.net --recv-keys 44C6513A8E4FB3D30875F758ED444FF07D8D0BF6

Cheers,
octes

Using a checkout from yesterday, I've installed a Kali box. It starts off using the English Language but a French layout. This seems unlikely to be on purpose.

To check that it wasn't part of the chef provisioning or something, I made a Vagrant file that only uses your box file but does nothing else special, it still defaults to French layout.

This box file: http://ftp.sliim-projects.eu/boxes/kali-1.1.0-amd64.box

Sorry if this is a false report, but I couldn't find anything about my setup that might be causing this.

--2017-04-16 15:03:17-- https://atlas.hashicorp.com/Sliim/boxes/kali-2016.2-amd64/versions/2016.2.1/providers/virtualbox.box
Resolving atlas.hashicorp.com (atlas.hashicorp.com)... 52.200.255.5, 52.206.86.0, 52.55.203.197
Connecting to atlas.hashicorp.com (atlas.hashicorp.com)|52.200.255.5|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://archivist.hashicorp.com/v1/object/eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJrZXkiOiJib3hlcy9mbGF0dGVuZWQvZGE5MjQyOTYtNjgzZi00OGZjLThhMTMtZWM2NWVhZTlhNGNjIiwibW9kZSI6InIiLCJleHBpcmUiOjE0OTIzNTQ5OTR9.wG3WVBT8jw5FJ7XyYPwblxUo2YqR0ueXuKhU8zkdnVY [following]
--2017-04-16 15:03:19-- https://archivist.hashicorp.com/v1/object/eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJrZXkiOiJib3hlcy9mbGF0dGVuZWQvZGE5MjQyOTYtNjgzZi00OGZjLThhMTMtZWM2NWVhZTlhNGNjIiwibW9kZSI6InIiLCJleHBpcmUiOjE0OTIzNTQ5OTR9.wG3WVBT8jw5FJ7XyYPwblxUo2YqR0ueXuKhU8zkdnVY
Resolving archivist.hashicorp.com (archivist.hashicorp.com)... 52.72.237.68, 52.54.158.220, 54.208.253.53
Connecting to archivist.hashicorp.com (archivist.hashicorp.com)|52.72.237.68|:443... connected.
HTTP request sent, awaiting response... 307 Temporary Redirect
Location: https://hc-prod-storagelocker.s3.amazonaws.com/boxes/flattened/da924296-683f-48fc-8a13-ec65eae9a4cc?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJBKZ6DNPERBCPYKQ%2F20170416%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20170416T070316Z&X-Amz-Expires=60&X-Amz-SignedHeaders=host&X-Amz-Signature=e93879031e0445a5eed5ffb599a779f7eb2224fd5782b36d8da33247766814e8 [following]
--2017-04-16 15:03:21-- https://hc-prod-storagelocker.s3.amazonaws.com/boxes/flattened/da924296-683f-48fc-8a13-ec65eae9a4cc?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJBKZ6DNPERBCPYKQ%2F20170416%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20170416T070316Z&X-Amz-Expires=60&X-Amz-SignedHeaders=host&X-Amz-Signature=e93879031e0445a5eed5ffb599a779f7eb2224fd5782b36d8da33247766814e8
Resolving hc-prod-storagelocker.s3.amazonaws.com (hc-prod-storagelocker.s3.amazonaws.com)... 54.231.82.42
Connecting to hc-prod-storagelocker.s3.amazonaws.com (hc-prod-storagelocker.s3.amazonaws.com)|54.231.82.42|:443... failed: Connection timed out.
Retrying.

--2017-04-16 15:03:43-- (try: 2) https://hc-prod-storagelocker.s3.amazonaws.com/boxes/flattened/da924296-683f-48fc-8a13-ec65eae9a4cc?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJBKZ6DNPERBCPYKQ%2F20170416%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20170416T070316Z&X-Amz-Expires=60&X-Amz-SignedHeaders=host&X-Amz-Signature=e93879031e0445a5eed5ffb599a779f7eb2224fd5782b36d8da33247766814e8
Connecting to hc-prod-storagelocker.s3.amazonaws.com (hc-prod-storagelocker.s3.amazonaws.com)|54.231.82.42|:443... failed: Connection timed out.
Retrying.

--2017-04-16 15:04:06-- (try: 3) https://hc-prod-storagelocker.s3.amazonaws.com/boxes/flattened/da924296-683f-48fc-8a13-ec65eae9a4cc?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJBKZ6DNPERBCPYKQ%2F20170416%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20170416T070316Z&X-Amz-Expires=60&X-Amz-SignedHeaders=host&X-Amz-Signature=e93879031e0445a5eed5ffb599a779f7eb2224fd5782b36d8da33247766814e8
Connecting to hc-prod-storagelocker.s3.amazonaws.com (hc-prod-storagelocker.s3.amazonaws.com)|54.231.82.42|:443... connected.
GnuTLS: Error in the pull function.

A Vagrantfile has been placed in this directory. You are now
ready to vagrant up your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
vagrantup.com for more information on using Vagrant.
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'Sliim/kali-2016.2-amd64' could not be found. Attempting to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'Sliim/kali-2016.2-amd64'
default: URL: https://atlas.hashicorp.com/Sliim/kali-2016.2-amd64
==> default: Adding box 'Sliim/kali-2016.2-amd64' (v2016.2.1) for provider: virtualbox
default: Downloading: https://atlas.hashicorp.com/Sliim/boxes/kali-2016.2-amd64/versions/2016.2.1/p roviders/virtualbox.box
==> default: Box download is resuming from prior download progress
default:
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

Failed to connect to hc-prod-storagelocker.s3.amazonaws.com port 443: Timed out

In China, I downloaded about 9% of the connection timeout (I used the proxy), how should I pull kali * .box

Here's what I did:

git clone [email protected]:Sliim/pentest-env.git
cd pentest-env/
vagrant up kali

And here's the abbreviated output of vagrant up kali:

Bringing machine 'kali' up with 'virtualbox' provider...
==> kali: Box 'kali-2016.1' could not be found. Attempting to find and install...
    kali: Box Provider: virtualbox
    kali: Box Version: >= 0
==> kali: Box file was not detected as metadata. Adding it directly...
==> kali: Adding box 'kali-2016.1' (v0) for provider: virtualbox
    kali: Downloading: http://box.hackbbs.org/kali-2016.1.box
==> kali: Successfully added box 'kali-2016.1' (v0) for 'virtualbox'!
==> kali: Importing base box 'kali-2016.1'...
==> kali: Matching MAC address for NAT networking...
==> kali: Setting the name of the VM: pentest-env_kali_1455735303577_33251
==> kali: The cookbook path '/Users/matt/sm/vm/slim/pentest-env/cookbooks' doesn't exist. Ignoring...
==> kali: The cookbook path '/Users/matt/sm/vm/slim/pentest-env/chef-repo/roles' doesn't exist. Ignoring...
==> kali: Clearing any previously set network interfaces...
==> kali: Preparing network interfaces based on configuration...
    kali: Adapter 1: nat
==> kali: Forwarding ports...
    kali: 22 => 2222 (adapter 1)
==> kali: Running 'pre-boot' VM customizations...
==> kali: Booting VM...
==> kali: Waiting for machine to boot. This may take a few minutes...
    kali: SSH address: 127.0.0.1:2222
    kali: SSH username: root
    kali: SSH auth method: private key
    kali: Warning: Connection timeout. Retrying...
==> kali: Machine booted and ready!
==> kali: Checking for guest additions in VM...
==> kali: Mounting shared folders...
    kali: /vagrant => /Users/matt/sm/vm/slim/pentest-env
==> kali: Running provisioner: shell...
    kali: Running: inline script
==> kali: mesg: 
==> kali: ttyname failed
==> kali: : 
==> kali: Inappropriate ioctl for device
==> kali: --2016-02-17 13:55:23--  https://opscode-omnibus-packages.s3.amazonaws.com/debian/6/x86_64/chef_12.2.1-1_amd64.deb
==> kali: Resolving opscode-omnibus-packages.s3.amazonaws.com (opscode-omnibus-packages.s3.amazonaws.com)... 
==> kali: 54.231.8.153
==> kali: Connecting to opscode-omnibus-packages.s3.amazonaws.com (opscode-omnibus-packages.s3.amazonaws.com)|54.231.8.153|:443... 
==> kali: connected.
==> kali: HTTP request sent, awaiting response... 
==> kali: 200 OK
==> kali: Length: 
==> kali: 38763294
==> kali:  (37M)
==> kali:  [application/x-debian-package]
==> kali: Saving to: ‘chef_12.2.1-1_amd64.deb’
==> kali: 
==> kali:      0K
==> kali:  
==> kali: .
...
==> kali: ..... 99% 3.72M 0s
==> kali:  37850K ....                                                  100% 9116G=12s
==> kali: 
==> kali: 2016-02-17 13:55:36 (3.02 MB/s) - ‘chef_12.2.1-1_amd64.deb’ saved [38763294/38763294]
==> kali: Selecting previously unselected package chef.
==> kali: (Reading database ... 309169 files and directories currently installed.)
==> kali: Preparing to unpack chef_12.2.1-1_amd64.deb ...
==> kali: Unpacking chef (12.2.1-1) ...
==> kali: Setting up chef (12.2.1-1) ...
==> kali: Thank you for installing Chef!
==> kali: Running provisioner: chef_solo...
Generating chef JSON and uploading...
==> kali: Running chef-solo...
==> kali: mesg: 
==> kali: ttyname failed
==> kali: : 
==> kali: Inappropriate ioctl for device
==> kali: [2016-02-17T13:55:50-05:00] INFO: Forking chef instance to converge...
==> kali: Starting Chef Client, version 12.2.1
==> kali: [2016-02-17T13:55:50-05:00] INFO: *** Chef 12.2.1 ***
==> kali: [2016-02-17T13:55:50-05:00] INFO: Chef-client pid: 1328
==> kali: [2016-02-17T13:55:52-05:00] INFO: Setting the run_list to ["recipe[apt]", "role[kali-base]"] from CLI options
==> kali: [2016-02-17T13:55:52-05:00] ERROR: Role kali-base (included by 'top level') is in the runlist but does not exist. Skipping expand.
==> kali: 
==> kali: ================================================================================
==> kali: Error expanding the run_list:
==> kali: ================================================================================
==> kali: 
==> kali: 
==> kali: Missing Role(s) in Run List:
==> kali: ----------------------------
==> kali: * kali-base included by 'top level'
==> kali: 
==> kali: 
==> kali: Original Run List
==> kali: -----------------
==> kali: * recipe[apt]
==> kali: 
==> kali: * role[kali-base]
==> kali: 
==> kali: 
==> kali: [2016-02-17T13:55:52-05:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
==> kali: Chef Client failed. 0 resources updated in 1.496812778 seconds
==> kali: [2016-02-17T13:55:52-05:00] ERROR: The expanded run list includes nonexistent roles: kali-base
==> kali: [2016-02-17T13:55:52-05:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1)
Chef never successfully completed! Any errors should be visible in the
output above. Please fix your recipes so that they properly complete.

$ vagrant version
Installed Version: 1.7.4

Bringing machine 'kali' up with 'virtualbox' provider...
==> kali: Box 'Kali' could not be found. Attempting to find and install...
kali: Box Provider: virtualbox
kali: Box Version: >= 0
==> kali: Adding box 'Kali' (v0) for provider: virtualbox
kali: Downloading: file:///path-to-downloaded-kali-box/kali-2.0-amd64.box
==> kali: Successfully added box 'Kali' (v0) for 'virtualbox'!
There are errors in the configuration of this machine. Please fix
the following errors and try again:

chef solo provisioner:

• The following settings shouldn't exist: install
• The following settings shouldn't exist: install

Hello again,

I am currently looking at GNS3 (https://wiki.archlinux.org/index.php/GNS3) for setting up a network environment based on your project's vms. I have only overlooked Chef provisioning and Vagrant (did a couple exercises on their websites) and got basic management on your pentestrc files, so maybe my question is stupid:
Would integration with GNS3 be interesting to you ?
Is it possible ?
Would it be possible while retaining the functionality of your tool ?

For instance, one problem comes with interface management, on which seems to rely a lot of tools available in GNS3. Because of own host has the different interfaces (vboxnet0,1,2) for each subnet defined in the pentestrc, it might be a little complex to merge this with GNS3. Just a opinion, waiting for feedback.

Thanks for answers

Unable to install the Vagrant Plugin

I believe that I might be using a version that's too new or something. I could not install the plugin (see below)

root@kali-lb:/opt/pentest-env# vagrant plugin install vagrant-openstack-provider
Installing the 'vagrant-openstack-provider' plugin. This can take a few minutes...
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

conflicting dependencies json (> 1.6) and json (= 2.1.0)
Activated json-2.1.0
which does not match conflicting dependency (> 1.6)

Conflicting dependency chains:
json (= 2.1.0), 2.1.0 activated

versus:
dm-serializer (= 1.2.2), 1.2.2 activated, depends on
json (~> 1.6)

Since it seemed like this project isn't using dm_serializer, I removed it, but afterwards I got the following error:

root@kali-lb:/opt/pentest-env# vagrant plugin install vagrant-openstack-provider
Installing the 'vagrant-openstack-provider' plugin. This can take a few minutes...
Bundler, the underlying system Vagrant uses to install plugins,
reported an error. The error is shown below. These errors are usually
caused by misconfigured plugin installations or transient network
issues. The error from Bundler is:

conflicting dependencies timers (= 4.1.1) and timers (~> 4.0.1)
Activated timers-4.0.1
which does not match conflicting dependency (= 4.1.1)

Conflicting dependency chains:
rubydns (= 1.0.3), 1.0.3 activated, depends on
timers (~> 4.0.1), 4.0.1 activated

versus:
timers (= 4.1.1)

Gems matching timers (= 4.1.1):
timers-4.1.1

Do I have top downgrade the version of Ruby on my Kali or something like that?

Hello there,

I wanted to connect my USB wireless adapter and use it as main wlan0 interface, so that I can use airmon-ng utilities, how can I do this?

I have already added the device manually through the GUI:

But I am not sure how to enable it. Any help is highly appreciated.
Thanks

Not sure what the issue is, after following your instructions starting from 'Installation' wiki then 'Customizations' - pretty sure it's something I've done wrong

Everytime I type vagrant status on my host Windows 10 machine in the git root, I only get the Kali VM and not the dvwa target I setup. Here's the .pentestrc

If it helps, I can't seem to find anything at ~/.pentest.d/scripts or ~/.pentest.d/targets

I followed the instructions to install pentest-env, twice actually with the same results. When I run rake an SSL validation error is returned.

$ rake
rm -rf cookbooks
berks vendor cookbooks
Resolving cookbook dependencies...
Fetching 'couchdb' from https://github.com/sliim-cookbooks/couchdb-cookbook (at master)
Fetching 'network_interfaces' from https://github.com/sliim-cookbooks/network_interfaces (at fixes)
Fetching 'pentest-env' from source at cookbook
Fetching cookbook index from https://supermarket.getchef.com...
[2017-11-11T00:32:58-07:00] ERROR: SSL Validation failure connecting to host: supermarket.getchef.com - SSL_connect returned=1 errno=0 state=error: certificate verify failed
/opt/vagrant/embedded/lib/ruby/gems/2.3.0/gems/chef-13.6.4/lib/chef/http.rb:446:in `rescue in retrying_http_errors': SSL Error connecting to https://supermarket.getchef.com/universe - SSL_connect returned=1 errno=0 state=error: certificate verify failed (OpenSSL::SSL::SSLError)
	from /opt/vagrant/embedded/lib/ruby/gems/2.3.0/gems/chef-13.6.4/lib/chef/http.rb:403:in `retrying_http_errors'
	from /opt/vagrant/embedded/lib/ruby/gems/2.3.0/gems/chef-13.6.4/lib/chef/http.rb:367:in `send_http_request'
	from /opt/vagrant/embedded/lib/ruby/gems/2.3.0/gems/chef-13.6.4/lib/chef/http.rb:149:in `request'
	from /opt/vagrant/embedded/lib/ruby/gems/2.3.0/gems/chef-13.6.4/lib/chef/http.rb:115:in `get'
	from /opt/vagrant/embedded/lib/ruby/gems/2.3.0/gems/berkshelf-6.3.1/lib/berkshelf/ridley_compat.rb:30:in `get'
	from /opt/vagrant/embedded/lib/ruby/gems/2.3.0/gems/berkshelf-6.3.1/lib/berkshelf/api_client/connection.rb:46:in `universe'
	from /opt/vagrant/embedded/lib/ruby/gems/2.3.0/gems/berkshelf-6.3.1/lib/berkshelf/source.rb:85:in `build_universe'
	from /opt/vagrant/embedded/lib/ruby/gems/2.3.0/gems/berkshelf-6.3.1/lib/berkshelf/installer.rb:24:in `block (2 levels) in build_universe'
rake aborted!
Command failed with status (1): [berks vendor cookbooks...]
/opt/vagrant_servers/pentest-env/Rakefile:5:in `block in <top (required)>'
Tasks: TOP => default => vendor
(See full trace by running task with --trace)

The weird thing is to me is, I am able to grab the HTTP file using wget, like this:
wget https://supermarket.getchef.com/universe

I don't really know much about Ruby, so I'm at a bit of a loss here. Does anyone have an idea of how to fix this issue?

Since some time there is 2.0

Kali 2017.2 is released.
https://www.kali.org/news/kali-linux-2017-2-release/

Hello there, whenever I start my machine with vagrant up, VirtualBox pops up and opens the VM's GUI.
Is it supposed to do this? If so, how can I disable it, so that only the CLI part runs?

Thank you,
Tiago

Hello,

I run into this issue when vagrant up chef-workstation (running the chef-environment example):
==> chef-workstation: Warning: Chef run list is empty. This may not be what you want. ==> chef-workstation: Running chef-client... ==> chef-workstation: [2019-02-06T08:58:34+00:00] INFO: Forking chef instance to converge... ==> chef-workstation: Starting Chef Client, version 12.17.44 ==> chef-workstation: [2019-02-06T08:58:34+00:00] INFO: *** Chef 12.17.44 *** ==> chef-workstation: [2019-02-06T08:58:34+00:00] INFO: Platform: x86_64-linux ==> chef-workstation: [2019-02-06T08:58:34+00:00] INFO: Chef-client pid: 4376 ==> chef-workstation: Creating a new client identity for workstation using the validator key. ==> chef-workstation: [2019-02-06T08:58:36+00:00] INFO: Client key /etc/chef/client.pem is not present - registering ==> chef-workstation: [2019-02-06T08:58:36+00:00] INFO: Run List is [recipe[hostname], recipe[pentest-env::cron_chef_client]] ==> chef-workstation: [2019-02-06T08:58:36+00:00] INFO: Run List expands to [hostname, pentest-env::cron_chef_client] ==> chef-workstation: [2019-02-06T08:58:36+00:00] INFO: Starting Chef Run for workstation ==> chef-workstation: [2019-02-06T08:58:36+00:00] INFO: Running start handlers ==> chef-workstation: [2019-02-06T08:58:36+00:00] INFO: Start handlers complete. ==> chef-workstation: [2019-02-06T08:58:36+00:00] INFO: HTTP Request Returned 404 Not Found: ==> chef-workstation: [2019-02-06T08:58:36+00:00] INFO: HTTP Request Returned 404 Not Found: ==> chef-workstation: [2019-02-06T08:58:36+00:00] INFO: Error while reporting run start to Data Collector. URL: https://chef-server.pentest.env/organizations/pentest-env/data-collector Exception: 404 -- 404 "Not Found" (This is normal if you do not have Chef Automate) ==> chef-workstation: resolving cookbooks for run list: ["hostname", "pentest-env::cron_chef_client"] ==> chef-workstation: [2019-02-06T08:58:39+00:00] INFO: Loading cookbooks [[email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]] ==> chef-workstation: ==> chef-workstation: ================================================================================ ==> chef-workstation: Error Syncing Cookbooks: ==> chef-workstation: ================================================================================ ==> chef-workstation: ==> chef-workstation: ==> chef-workstation: Unexpected Error: ==> chef-workstation: ----------------- ==> chef-workstation: NoMethodError: private method select' called for nil:NilClass
==> chef-workstation:
==> chef-workstation:
==> chef-workstation: Platform:
==> chef-workstation: ---------
==> chef-workstation: x86_64-linux
==> chef-workstation:
==> chef-workstation:
==> chef-workstation:
==> chef-workstation: Running handlers:
==> chef-workstation: [2019-02-06T08:58:39+00:00] ERROR: Running exception handlers
==> chef-workstation: Running handlers complete
==> chef-workstation:
==> chef-workstation: [2019-02-06T08:58:39+00:00] ERROR: Exception handlers complete
==> chef-workstation: Chef Client failed. 0 resources updated in 04 seconds
==> chef-workstation: [2019-02-06T08:58:39+00:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
==> chef-workstation: [2019-02-06T08:58:39+00:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
==> chef-workstation: [2019-02-06T08:58:39+00:00] ERROR: private method select' called for nil:NilClass ==> chef-workstation: [2019-02-06T08:58:39+00:00] FATAL: Chef::Exceptions::ChildConvergeError: Chef run process exited unsuccessfully (exit code 1) Chef never successfully completed! Any errors should be visible in the output above. Please fix your recipes so that they properly complete.

The install process as described in the doc went fine, no errors whatsoever.
Ask me if you need further info on my System or else.
Thanks a lot !

Note: i'm not sure if i'm doing the correct step since i'm new to all this.

After a successful vagrant up:

$ PENTESTRC=examples/tor-proxy.pentestrc vagrant up 
Bringing machine 'kali' up with 'virtualbox' provider...
==> kali: Checking if box 'Sliim/kali-2018.1-amd64' is up to date...
==> kali: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> kali: flag to force provisioning. Provisioners marked to run always will still run

when I do

$ PENTESTRC=examples/tor-proxy.pentestrc vagrant provision kali

I got following output:

==> kali: Running provisioner: shell...
    kali: Running: inline script
==> kali: Running provisioner: chef_solo...
==> kali: Generating chef JSON and uploading...
==> kali: Running chef-solo...
==> kali: [2018-10-01T20:28:48-04:00] INFO: Started chef-zero at chefzero://localhost:1 with repository at /tmp/vagrant-chef/2993b48a6912fb37af194703e2dff78b
==> kali:   One version per cookbook
==> kali:   roles at /tmp/vagrant-chef/22fc37727897b737d7a8c6e1a6deb80d/roles
==> kali: Starting Chef Client, version 14.3.37
==> kali: [2018-10-01T20:28:48-04:00] INFO: *** Chef 14.3.37 ***
==> kali: [2018-10-01T20:28:48-04:00] INFO: Platform: x86_64-linux
==> kali: [2018-10-01T20:28:48-04:00] INFO: Chef-client pid: 1747
==> kali: [2018-10-01T20:28:48-04:00] INFO: The plugin path /etc/chef/ohai/plugins does not exist. Skipping...
==> kali: [2018-10-01T20:28:50-04:00] INFO: Setting the run_list to ["recipe[apt]", "role[kali-base]", "role[tor-proxy]"] from CLI options
==> kali: [2018-10-01T20:28:51-04:00] INFO: Run List is [recipe[apt], role[kali-base], role[tor-proxy]]
==> kali: [2018-10-01T20:28:51-04:00] INFO: Run List expands to [apt, kali, tor-full, proxychains]
==> kali: [2018-10-01T20:28:51-04:00] INFO: Starting Chef Run for vagrant-d3b8c460
==> kali: [2018-10-01T20:28:51-04:00] INFO: Running start handlers
==> kali: [2018-10-01T20:28:51-04:00] INFO: Start handlers complete.
==> kali: resolving cookbooks for run list: ["apt", "kali", "tor-full", "proxychains"]
==> kali: [2018-10-01T20:29:02-04:00] INFO: Loading cookbooks [[email protected], [email protected], [email protected], [email protected], [email protected]]
==> kali: Synchronizing Cookbooks:
==> kali:   
==> kali: - apt (7.1.0)
==> kali:   
==> kali: - tor-full (0.2.0)
==> kali:   
==> kali: - yum (3.13.0)
==> kali:   - kali (2.0.0)
==> kali:   
==> kali: - proxychains (0.2.0)
==> kali: Installing Cookbook Gems:
==> kali: Compiling Cookbooks...
==> kali: 
==> kali: ================================================================================
==> kali: Recipe Compile Error in /var/chef/cache/cookbooks/tor-full/recipes/default.rb
==> kali: ================================================================================
==> kali: 
==> kali: 
==> kali: NoMethodError
==> kali: -------------
==> kali: undefined method `tor' for #<Chef::Node::Attribute:0x0000000004c387d8>
==> kali: 
==> kali: 
==> kali: Cookbook Trace:
==> kali: ---------------
==> kali:   /var/chef/cache/cookbooks/tor-full/recipes/default.rb:90:in `block in from_file'
==> kali: 
==> kali:   /var/chef/cache/cookbooks/tor-full/recipes/default.rb:85:in `from_file'
==> kali: 
==> kali: Relevant File Content:
==> kali: ----------------------
==> kali: /var/chef/cache/cookbooks/tor-full/recipes/default.rb:
==> kali: 
==> kali:  83:  
==> kali:  84:  # Build torrc configuration file
==> kali:  85:  template '/etc/tor/torrc' do
==> kali:  86:    source 'torrc.erb'
==> kali:  87:    notifies :restart, 'service[tor]', :immediately
==> kali:  88:    notifies :run, "ruby_block[read-hostnames]"
==> kali:  89:    # Set default HiddenServiceDir
==> kali:  90>>   node.tor.HiddenServices.each do |name, service|
==> kali:  91:      node.default['tor']['HiddenServices'][name]['HiddenServiceDir'] = File.join("/var/lib/tor/", name, "/")
==> kali:  92:    end
==> kali:  93:  end
==> kali:  94:  
==> kali:  95:  # Install exit policy notice
==> kali:  96:  template '/etc/tor/tor-exit-notice.html' do
==> kali:  97:    source 'tor-exit-notice.html.erb'
==> kali:  98:  end
==> kali:  99:  
==> kali: 
==> kali: System Info:
==> kali: ------------
==> kali: chef_version=14.3.37
==> kali: platform=debian
==> kali: platform_version=kali-rolling
==> kali: ruby=ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux]
==> kali: program_name=/usr/bin/chef-solo
==> kali: executable=/opt/chef/bin/chef-solo
==> kali: 
==> kali: 
==> kali: 
==> kali: Running handlers:
==> kali: [2018-10-01T20:29:02-04:00] ERROR: Running exception handlers
==> kali: Running handlers complete
==> kali: 
==> kali: [2018-10-01T20:29:02-04:00] ERROR: Exception handlers complete
==> kali: Chef Client failed. 0 resources updated in 14 seconds
==> kali: [2018-10-01T20:29:02-04:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
==> kali: [2018-10-01T20:29:02-04:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
==> kali: [2018-10-01T20:29:02-04:00] FATAL: NoMethodError: undefined method `tor' for #<Chef::Node::Attribute:0x0000000004c387d8>
Chef never successfully completed! Any errors should be visible in the
output above. Please fix your recipes so that they properly complete.

Is this something related to this error?

kali: Recipe Compile Error in /var/chef/cache/cookbooks/tor-full/recipes/default.rb

info regarding versions:

• VirtualBox:

VirtualBox Graphical User Interface Version 5.2.10_Ubuntu r121806

$ uname -a
Linux mymachine 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.1 LTS
Release:	18.04
Codename:	bionic

- $ ruby --version
ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux-gnu]

-- $ vagrant --version
Vagrant 2.1.5

Been using pentest-env a while, have not come across this issue. This happens during provisioning. Not sure what to do.

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

curl -sL https://omnitruck.chef.io/install.sh | bash -s -- -P "chef" -c "stable"

Stdout from the command:

kali kali-rolling x86_64
Getting information for chef stable  for kali...
downloading https://omnitruck.chef.io/stable/chef/metadata?v=&p=kali&pv=kali-rolling&m=x86_64
  to file /tmp/install.sh.19875/metadata.txt
trying wget...
ERROR 404
Omnitruck artifact does not exist for version  on platform kali

Either this means:
   - We do not support kali
   - We do not have an artifact for 

This is often the latter case due to running a prerelease or RC version of chef
or a gem version which was only pushed to rubygems and not omnitruck.

You may be able to set your knife[:bootstrap_version] to the most recent stable
release of Chef to fix this problem (or the most recent stable major version number).

In order to test the version parameter, adventurous users may take the Metadata URL
below and modify the '&v=<number>' parameter until you successfully get a URL that
does not 404 (e.g. via curl or wget).  You should be able to use '&v=11' or '&v=12'
succesfully.

If you cannot fix this problem by setting the bootstrap_version, it probably means
that kali is not supported.

Metadata URL: https://omnitruck.chef.io/stable/chef/metadata?v=&p=kali&pv=kali-rolling&m=x86_64


Stderr from the command:

Please switch to https-download of the .box-file.

Hello,

When running the chef-environment from the examples directory, and when vagrant up any of the machines (except the chef-server), an error is thrown during chef provisioning that the installed chef version is too old for some packages (12.7, instead of >=13).
(I'm sorry I solved my issue and I don't wan't to do all over again so I don't have the precise package complaining.)
I fixed that by simply puting 'version: 13.2.20' in the pentestrc file. I'm opening an issue in case where that is an intentional stuff !

where is the vagrant shared folder? I don't see /vagrant. How can I configure one?

Is there a source for more insight into what the different instances really are and what makes them different?

Check compatibility with vagrant 2.0