summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDan Fedele <dan.fedele@gmail.com>2020-05-24 09:53:25 -0400
committerGitHub <noreply@github.com>2020-05-24 09:53:25 -0400
commitd39a7282ee580e476a27ab986e72dd3a0f5a157c (patch)
tree17d98bea66900ab5829dee7e7e54c87c76c14c33
parent8be3f8c003c4783b81d06850a8a88283036e4b64 (diff)
Update README.md
-rw-r--r--README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/README.md b/README.md
index 2e594c5..b2018ab 100644
--- a/README.md
+++ b/README.md
@@ -1,4 +1,4 @@
-# FreshInstall
+# Fresh Install
I believe every Kali VM should be ephemeral. Build it, do your damage, then blow it away. While that's impractical to do it for every single engagement, and since Kali is *almost perfect*, there are still a bunch of things that I modify after a fresh Kali build. Since re-doing all of those tasks is tiresome, I decided to create a solid foundation of "good enough" to start off a fresh build of Kali and download all of the tools I find myself using all the time. So I made this script. It starts a bash script to install pip, then install ansible, then use ansible to download all the appropriate packages, clone the appropriate repositories, and make the appropriate modifications to the system to get it to a point close enough to how I like.
And if you don't like my modifications, I encourage you to fork this repo and make your own changes.