You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recognize that as nurupoo mentioned the authentication isn't encrypted with SOCKS5, but we've still had a few duplicate issues for qTox alone, and at least corporate proxies seems like a reasonable use case.
The text was updated successfully, but these errors were encountered:
There's not much work involved in negotiating authentication in SOCKS.
It would mean adding SOCKS_USER and SOCKS_PASSWORD fields to the ToxOptions. Ideally the iterate code should recheck the authentification and reauthenticate if necessary as corporate proxies often have short timeouts.
You should add support for a comma seperated list of IP:port for NO_PROXY.
Carrying over from irungentoo#1268.
Clients have gotten requests to support authenticated proxies, e.g.:
JFreegman/toxic#371
qTox/qTox#1286
I recognize that as nurupoo mentioned the authentication isn't encrypted with SOCKS5, but we've still had a few duplicate issues for qTox alone, and at least corporate proxies seems like a reasonable use case.
The text was updated successfully, but these errors were encountered: