the ability to bind a socks5 listener to 0.0.0.0 without specifying a user\pass

[zjmo]

Issue Details

It's hardcoded now that if the bind isn't on the loopback and the user\pass aren't specified, it throws an error and won't launch

Proposed solution

I suggest adding some variable to the config (something like "i_understand_the_security_risks") and if it is specified, allow binding to 0.0.0.0 without a user\pass

Alternative solution

No response

[Any4Den]

I would like to highly support this feature request. The lack of anonymous (no-auth) local listeners creates severe architectural limitations for standard desktop workflows.

My Use Case / Infrastructure Scheme:

PC Browser (SwitchyOmega) -> Local TrustTunnel Client (LAN Gateway, 0.0.0.0) -> Remote TrustTunnel VPS Endpoint

In a typical home server or local network (LAN) environment, we run the trusttunnel_client as a systemd gateway service listening on 0.0.0.0 so that all local devices (PCs, laptops, phones) can utilize the tunnel.

The Core Problem with Web Browsers:

The mandatory username/password requirement for local listeners breaks web browsers entirely. Chromium-based browsers (Google Chrome, Microsoft Edge, Brave, Opera, etc.) do not support SOCKS5 username/password authentication out of the box. When configuring a SOCKS5 proxy via native system settings or extensions like Proxy SwitchyOmega, Chromium physically fails to pass or prompt for SOCKS5 credentials (unlike HTTP proxies, which can trigger native authentication popups).

Because trusttunnel_client strictly enforces credentials on the local listener, a direct connection from a standard web browser to the local TrustTunnel port is impossible.

Current Ugly Workaround:

To bypass this limitation inside a private, trusted local network, users are forced to set up complex, resource-heavy proxy-chaining workarounds on top of the client (such as wrapping connections via autossh tunnels, socat relays, or writing custom local Python scripts) just to strip away the authentication credentials locally so that Chrome can talk to the gateway.

Proposed Solution:

Please allow username and password parameters to be optional in the [listener.socks] and [listener.http] configuration blocks, or introduce a simple toggle like auth_enabled = false. If disabled, the client should allow anonymous connections from the local network.

This change will massively improve usability for anyone using standard web browsers as their main proxy clients. Thank you!