mirror of
https://github.com/i2p/i2p.i2p.git
synced 2026-10-07 09:47:38 +00:00
The guard meant to reject SOCKS 4/4a on auth-enabled tunnels checked for legacy proxyUsername/proxyPassword properties that are no longer used for SOCKS, we now store sha256 digest under different properties, so when auth is enabled, a unauthenticated SOCKS 4a CONNECT was accepted. Fix by removing check for legacy properties. Reported by: haoxucu