Padding is not working

[emacsenli]

I have setup 2 naive clients (both released binary not compiled myself) on my local machine. one is listening on port 1080 with padding on while the other is on port 8080 without padding

while on VPS ,if caddyfile just remove upstream section as README.md said , naive worked fine.

but if I try "padding" mode , command curl -x socks5://127.0.0.1:1080 https://www.google.com just returned error "SSL_ERROR_SYSCALL" . and tcpdump localmachine 1080 ,show that with a ClientHello then no ServerHello back from google, and tcpdump of local machine to VPS stage ,there is nothing wrong,https stream works fine. so the problem is from stage between VPS and google.
and tcpdump of this stage shows that after 3 handshakes there is not a ClientHello but an unkown record ,and google return a Fatal Alert and RST immediately .

compare both tcpdump of localhost 1080 and VPS to google ,localhost has a ClientHello of payload length 585 in socks protocol ,but VPS to google is of payload length 880.
so this is problem I think

[darhwa]

Have you enabled padding for both your naive client and the naive server behind caddy?

[emacsenli]

Have you enabled padding for both your naive client and the naive server behind caddy?

ok let me put configurations on :

local machine

config.json for naive

> {
>   "listen": "socks://127.0.0.1:1080",
>   "proxy": "https://user:passwd@myDomain",
>   //"log": ,
>   "padding":true
> }
> 

VPS

config.json for naive with padding on

>{
  **"listen": "socks://127.0.0.1:1080",**
  "padding":true,
  "log": "/var/log/naiveproxy.log"
}

and Caddy file with upstream to socks at port 1080

> myDomain {
>>root /var/www/html
>>tls myEmail@email.com
>>forwardproxy {
>>  basicauth user passwd
>>   hide_ip
>>   hide_via
>>   probe_resistance secret.localhost
>>   **upstream socks5://127.0.0.1:1080**
>>   }
> }

md5sum of latest released binary file is 55be754d56d7ec83e3edd2f7b53e49cd
but my own compilation is 06814cb70ebefbefd4a32df68cdc8fd0
does that matter?

[darhwa]

In the naive server, you have to config it to listen on http://*** instead of socks5://*** to make the padding work correctly.

I agree that this is error-prone for users.

[emacsenli]

Yes correct...Finally Done ,thanks

[KevinZonda]

@klzgrad This issue can be closed.

[klzgrad]

Padding support is now auto-configured.