Tighten the local SOCKS5 runtime and diagnostic path.
Changes
Require an explicit ephemeral SOCKS port
Require username/password authentication
Remove unauthenticated SOCKS5 fallback behavior
Replace supplied inbound listeners with the ReVolt-owned loopback SOCKS inbound
Keep the listener bound to 127.0.0.1
Use one total read deadline for SOCKS diagnostics
This keeps local proxy access scoped to the active ReVolt session.
## Summary
Tighten the local SOCKS5 runtime and diagnostic path.
## Changes
- Require an explicit ephemeral SOCKS port
- Require username/password authentication
- Remove unauthenticated SOCKS5 fallback behavior
- Replace supplied inbound listeners with the ReVolt-owned loopback SOCKS inbound
- Keep the listener bound to 127.0.0.1
- Use one total read deadline for SOCKS diagnostics
This keeps local proxy access scoped to the active ReVolt session.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Tighten the local SOCKS5 runtime and diagnostic path.
Changes
This keeps local proxy access scoped to the active ReVolt session.