Web capturing via SOCKS5 proxy does not work
sciguy16 opened this issue · comments
Chrome headless is returning ERR_EMPTY_RESPONSE when connecting via a SOCKS5 proxy.
Related output:
-cargo run -- --proxy socks5://\[::1\]:1080 -t https://nccgroup.com -v
Finished dev [unoptimized + debuginfo] target(s) in 0.09s
Running `target/debug/scrying --proxy 'socks5://[::1]:1080' -t 'https://nccgroup.com' -v`
Starting NCC Group Scrying...
10:25:25 [DEBUG] (1) scrying: Got opts:
Opts { files: [], targets: ["https://nccgroup.com"], mode: Auto, rdp_timeout: 2, threads: 10, log_file: None, nmaps: [], nessus: [], output_dir: "output", web_proxy: Some("socks5://[::1]:1080"), rdp_proxy: Some("socks5://[::1]:1080"), silent: false, verbose: 1, test_import: false }
10:25:25 [DEBUG] (1) scrying::parsing: https://nccgroup.com parsed as Web target
RDP targets: None
Web targets:
https://nccgroup.com/
VNC targets: None
10:25:25 [DEBUG] (3) scrying: Starting report thread
10:25:25 [DEBUG] (4) scrying: Starting Web worker threads
10:25:25 [INFO] Launching Chrome binary at "/usr/bin/chromium"
10:25:25 [INFO] Started Chrome. PID: 74750
10:25:25 [DEBUG] (4) headless_chrome::browser::process: Found debugging WS URL: "ws://127.0.0.1:8187/devtools/browser/25267de0-708b-4cd6-b959-d2bdbcdee9bf"
10:25:25 [DEBUG] (4) headless_chrome::browser::transport::web_socket_connection: Successfully connected to WebSocket: ws://127.0.0.1:8187/devtools/browser/25267de0-708b-4cd6-b959-d2bdbcdee9bf
10:25:25 [DEBUG] (7) headless_chrome::browser::tab: New tab attached with session ID: SessionId("66CFC9052B2609300398F6A2BE5518CE")
10:25:25 [INFO] Processing https://nccgroup.com/
10:25:25 [INFO] Saving image as output/web/https_nccgroup.com.png
10:25:25 [WARN] Failed to capture image: Navigate failed: net::ERR_EMPTY_RESPONSE
10:25:25 [INFO] Dropping browser
10:25:25 [INFO] Killing Chrome. PID: 74750
10:25:25 [DEBUG] (5) headless_chrome::browser::transport::web_socket_connection: WS Error Chrome #Some(74750): WebSocketError: No data available
10:25:25 [INFO] Sending shutdown message to message handling loop
10:25:25 [INFO] Received shutdown message
10:25:25 [INFO] Shutting down message handling loop
10:25:25 [INFO] cleared listeners, I think
10:25:25 [DEBUG] (7) headless_chrome::browser: Browser event sender disconnected while loop was waiting (Chrome #Some(74750))
10:25:25 [INFO] Finished browser's event handling loop
10:25:25 [INFO] finished tab's event handling loop
10:25:25 [INFO] dropping transport
10:25:25 [INFO] dropping websocket connection
10:25:25 [DEBUG] (3) scrying::reporting: Received message: GenerateReport
10:25:25 [INFO] Generating report
No longer using chromedriver.
See existing proxy issue: #11