Skip to content
This is a repository that will be used to help create a process of a new kali vagrant box for hashicorp each month.
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci filtering only down to develop and master to build May 6, 2019
.github/ISSUE_TEMPLATE
ci adding codefactor.io suggestions for issues May 5, 2019
images setting 10 minutes broken up circleci Apr 30, 2019
install adding more virtual graphics ram Mar 21, 2019
prov_packer adding codefactor.io suggestions for issues May 5, 2019
prov_vagrant adding codefactor.io suggestions for issues May 5, 2019
scripts removing unused script May 7, 2019
templates making domain name dns compliant Apr 25, 2019
tmp_vagrant adding enable postgres Mar 12, 2019
.gitattributes adding git attributes Jan 16, 2019
.gitignore adding framework for text, and still working on build.sh May 5, 2019
LICENSE Create LICENSE Jan 22, 2019
README.md detailing in case of failing May 12, 2019
Vagrantfile adding framework for text, and still working on build.sh May 5, 2019
build.sh_not-working adding framework for text, and still working on build.sh May 5, 2019

README.md

Automated Kali Hashcorp Box

CircleCI CodeFactor Codacy Badge

If the build status if failing please checkout pinned issues, and if there are no pinned issues then please file a detailed bug issue (template comming soon)

Presentation

Overview

VM info

  • user: root
  • pass: toor

Installed software

listed in the scripts directory: here

what this repo will be for

So you can vagrant box update to get the new box that is created from this each month by a cron job on my server. This will allow for a fresh new image of Kali with the most up to date tools through the ease of vagrant and however you want to provision my kali box.

Based on vagrants help command (displayed below), this should destroy/delete anything from before the box was upgraded.

$ vagrant box update --help
Usage: vagrant box update [options]

Updates the box that is in use in the current Vagrant environment,
if there any updates available. This does not destroy/recreate the
machine, so you'll have to do that to see changes.

To update a specific box (not tied to a Vagrant environment), use the
--box flag.

grand scheme

packer vagrant eco So to get the new up to date kali box you would have to vagrant destroy and vagrant up it again. Then everything would be based on your Vagrantfile for provisioning.

things to consider before vagrant destroy

  • did you backup all your metasploit data? - msfconsole -q -x "db_export -f xml /root/pentesting/metasploit-backups/general/metasploit-backup-main.xml; exit"
  • did you backup all your metasploit creds (doesn't get exported by metasploit by default...)? - msfconsole -q -x "creds -o /root/pentesting/metasploit-backups/creds/metasploit-backup-creds.csv; exit"
  • do you have any customizations that could be automated in your Vagrantfile?
  • putting all your data in your /vagrant folder is ideal, to keep everything shared and making sure it doesn't get lost when destroying boxes (because it is on your local machine as a shared folder)

Dependencies

  • vagrant
  • packer
  • internet connection

Future plans

  • Create different kali box automations (i.e. with empire and other frameworks)
  • docs...eventually :D
  • different virtualization platforms (virtualbox)
You can’t perform that action at this time.