2.3.2 release

2.3.2
- ACMEv2 support added to comply with LetsEncrypt requirements.
- Fixed session cookie output to support EditThisCookie on the latest Chrome version.
- Increased timeouts for proxying HTTP packets to 45 seconds.
- Added support for Go modules.

CHANGELOG

@@ -1,3 +1,9 @@
+2.3.2
+- ACMEv2 support added to comply with LetsEncrypt requirements.
+- Fixed session cookie output to support EditThisCookie on the latest Chrome version.
+- Increased timeouts for proxying HTTP packets to 45 seconds.
+- Added support for Go modules.
+
 2.3.1
 - Redirection is now triggered only for responses with `text/html` content-type header.
 

Makefile

@@ -2,13 +2,10 @@ TARGET=evilginx
 PACKAGES=core database log parser
 
 .PHONY: all
-all: deps build
-
-deps: godep
-		@dep ensure
+all: build
 
 build:
-		@go build -o ./bin/$(TARGET) main.go
+		@go build -o ./bin/$(TARGET) -mod=vendor
 
 clean:
 		@go clean
@@ -18,6 +15,3 @@ install:
 		@mkdir -p /usr/share/evilginx/phishlets
 		@cp ./phishlets/* /usr/share/evilginx/phishlets/
 		@cp ./bin/$(TARGET) /usr/local/bin
-
-godep:
-		@go get -u github.com/golang/dep/...

README.md

@@ -165,7 +165,9 @@ phishlets enable linkedin
 
 Your phishing site is now live. Think of the URL, you want the victim to be redirected to on successful login and get the phishing URL like this (victim will be redirected to `https://www.google.com`):
 ```
-phishlets get-url linkedin https://www.google.com
+lures create linkedin
+lures edit redirect-url 0 https://www.google.com
+lures get-url 0
 ```
 
 Running phishlets will only respond to tokenized links, so any scanners who scan your main domain will be redirected to URL specified as `redirect_url` under `config`. If you want to hide your phishlet and make it not respond even to valid tokenized phishing URLs, use `phishlet hide/unhide <phishlet>` command.

core/banner.go

@@ -8,7 +8,7 @@ import (
 )
 
 const (
-	VERSION = "2.3.1"
+	VERSION = "2.3.2"
 )
 
 func putAsciiArt(s string) {