projectdiscovery/proxifyUn proxy versatile e portatile per catturare, manipolare e riprodurre il traffico HTTP/HTTPS in movimento.
Caratteristiche • Installazione • Utilizzo • Esecuzione di Proxify • Installazione del certificato SSL • Applicazioni di Proxify • Unisciti a Discord
Swiss Army Knife Proxy per distribuzioni rapide. Supporta molteplici operazioni come dump di richieste/risposte, filtraggio e manipolazione tramite linguaggio DSL, proxy upstream HTTP/Socks5. Inoltre, un'utilità di replay permette di importare il traffico dumpato (richieste/risposte con il nome di dominio corretto) in BurpSuite o in qualsiasi altro proxy semplicemente impostando il proxy upstream su proxify.
Scarica il binario pronto per l'esecuzione o installa/compila usando GO
go install -v github.com/projectdiscovery/proxify/cmd/proxify@latest
proxify -h
Questo visualizzerà l'aiuto per lo strumento. Ecco tutti i flag supportati.
Swiss Army Knife Proxy for rapid deployments. Supports multiple operations such as request/response dump,filtering and manipulation via DSL language, upstream HTTP/Socks5 proxy
Usage:
./proxify [flags]
Flags:
OUTPUT:
-sr, -store-response store raw http request / response to output directory (default proxify_logs)
-o, -output output file to store proxify logs (default proxify_logs.jsonl)
-of, -output-format string output format (jsonl/yaml) (default "jsonl")
-dump-req Dump only HTTP requests to output file
-dump-resp Dump only HTTP responses to output file
-oca, -out-ca string Generate and Save CA File to filename
UPDATE:
-up, -update update proxify to latest version
-duc, -disable-update-check disable automatic proxify update check
FILTER:
-req-fd, -request-dsl string[] Request Filter DSL
-resp-fd, -response-dsl string[] Response Filter DSL
-req-mrd, -request-match-replace-dsl string[] Request Match-Replace DSL
-resp-mrd, -response-match-replace-dsl string[] Response Match-Replace DSL
NETWORK:
-ha, -http-addr string Listening HTTP IP and Port address (ip:port) (default "127.0.0.1:8888")
-sa, -socks-addr Listening SOCKS IP and Port address (ip:port) (default 127.0.0.1:10080)
-da, -dns-addr string Listening DNS IP and Port address (ip:port)
-dm, -dns-mapping string Domain to IP DNS mapping (eg domain:ip,domain:ip,..)
-r, -resolver string Custom DNS resolvers to use (ip:port)
PROXY:
-hp, -http-proxy string[] Upstream HTTP Proxies (eg http://proxy-ip:proxy-port)
-sp, -socks5-proxy string[] Upstream SOCKS5 Proxies (eg socks5://proxy-ip:proxy-port)
-c int Number of requests before switching to the next upstream proxy (default 1)
EXPORT:
-max-size int Max export data size (request/responses will be truncated) (default 9223372036854775807)
CONFIGURATION:
-config string path to the proxify configuration file
-ec, -export-config string proxify export module configuration file (default "$CONFIG/export-config.yaml")
-config-directory string override the default config path (default "$CONFIG/proxify")
-cert-cache-size int Number of certificates to cache (default 256)
-a, -allow string[] Allowed list of IP/CIDR's to be proxied
-d, -deny string[] Denied list of IP/CIDR's to be proxied
-pt, -passthrough string[] List of passthrough domains
DEBUG:
-nc, -no-color No Color
-version Version
-silent Silent
-v, -verbose Verbose
-vv, -very-verbose Very Verbose
Esegue un proxy HTTP sulla porta 8888:
proxify
Esegue un proxy HTTP sulla porta personalizzata 1111:
proxify -http-addr ":1111"
Il flag -pt può essere utilizzato per passare attraverso (saltare) il traffico crittografato senza tentare di terminare la connessione TLS.
proxify -pt '(.*\.)?google\.co.in.*'
Esegue un proxy HTTP sulla porta 8888 e inoltra il traffico a burp sulla porta 8080:
proxify -http-proxy http://127.0.0.1:8080
Esegue un proxy HTTP sulla porta 8888 e inoltra il traffico alla rete TOR:
proxify -socks5-proxy 127.0.0.1:9050
Proxify supporta tre formati di output: JSONL, YAML e Files.
JSONL (default):
Nel formato Json Lines, ogni coppia di Richiesta/Risposta HTTP è memorizzata come oggetto json in una singola riga.
{"timestamp":"2024-02-20T01:56:49+05:30","url":"https://scanme.sh:443","request":{"header":{"Connection":"close","User-Agent":"curl/8.1.2","host":"scanme.sh:443","method":"CONNECT","path":"","scheme":"https"},"raw":"CONNECT scanme.sh:443 HTTP/1.1\r\nHost: scanme.sh:443\r\nConnection: close\r\nUser-Agent: curl/8.1.2\r\n\r\n"},"response":{"header":{"Content-Length":"0"},"raw":"HTTP/1.1 200 OK\r\nContent-Length: 0\r\n\r\n"}}
{"timestamp":"2024-02-20T01:56:49+05:30","url":"https://scanme.sh/","request":{"header":{"Accept":"*/*","Connection":"close","User-Agent":"curl/8.1.2","host":"scanme.sh","method":"GET","path":"/","scheme":"https"},"raw":"GET / HTTP/1.1\r\nHost: scanme.sh\r\nAccept: */*\r\nConnection: close\r\nUser-Agent: curl/8.1.2\r\n\r\n"},"response":{"header":{"Content-Type":"text/plain; charset=utf-8","Date":"Mon, 19 Feb 2024 20:26:49 GMT"},"body":"ok","raw":"HTTP/1.1 200 OK\r\nConnection: close\r\nContent-Type: text/plain; charset=utf-8\r\nDate: Mon, 19 Feb 2024 20:26:49 GMT\r\n\r\n"}}
Yaml MultiDoc: