forked from putsi/privatecollaborator
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' of github.com:putsi/privatecollaborator
- Loading branch information
Showing
1 changed file
with
2 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,6 +3,7 @@ A script for installing private Burp Collaborator with Let's Encrypt SSL-certifi | |
| Should work on (Ubuntu 18.04): | ||
| - Amazon AWS EC2 VM with or without Elastic IP. | ||
| - DigitalOcean VM with or without Floating IP. | ||
| - Azure. | ||
| - Any other platform as long as the VM has public IP. | ||
|
|
||
| Please see [this blog post](https://teamrot.fi/2019/05/23/self-hosted-burp-collaborator-with-custom-domain/) for usage instructions. | ||
|
|
@@ -11,7 +12,7 @@ Please see [this blog post](https://teamrot.fi/2019/05/23/self-hosted-burp-colla | |
|
|
||
| 1. Clone this repository. | ||
| 2. Install Burp to /usr/local/BurpSuitePro. | ||
| 3. Run `sudo ./install.sh yourdomain.fi`. | ||
| 3. Run `sudo ./install.sh yourdomain.fi [email protected]` (the email is for Let's Encrypt expiry notifications). | ||
| 4. You should now have Let's encrypt certificate for the domain and a private burp collaborator properly set up. | ||
| 5. Start the collaborator with `sudo service burpcollaborator start`. | ||
| 6. Configure your Burp Suite Professional to use it. | ||
|
|
||