mubeng
mubeng copied to clipboard
[BUG] tls: bad record MAC
Describe the bug
Some wierd things are happening when configuring an https proxy in the proxylist.
To Reproduce
Steps to reproduce the behavior:
> mubeng -f proxylist.txt -a localhost:8089
Proxylist contains one row: https://"replace with ip":3129
This ip runs a Squid proxy with this configuration: https_port 3129 cert=/etc/squid/certs/squid-ca-cert-key.pem
Expected behavior
Trying to run a curl against mubeng gives the following error: curl --proxy "localhost:8089" https://api.myip.com
2023/11/06 14:42:19 [001] WARN: Cannot handshake client api.myip.com:443 local error: tls: bad record MAC
Running the same curl but pointing directly to the Squid proxy gives no errors: curl --proxy-insecure --proxy "https://"replace with ip":3129" https://api.myip.com {"ip":"","country":","":""}
Screenshots
Environment (please complete the following information):
- OS: [e.g. mac, linux]: Mubeng on Windows, Squid on Arch Linux
- OS version: [uname -a] Windows 11
- mubeng Version: [mubeng -V] v0.14.1
Additional context I am trying to get my head around how to configure secure https proxy servers that works with mubeng. E.g
Requesting client <--HTTP (or HTTPS--> Mubeng <-- HTTPS ONLY --> Squid(or any other proxy)
Hi @panterlo,
Have you tried using a squid proxy on a different server with another IP? Also, do you face the same issue when your squid proxy server is set up with HTTP?
Thanks!