| Documentation Changes Summary: |
The new connection form (which I think is handled in a special way on the docs side, not sure myself) now supports specifying a Socks5 proxy hostname, as well as optionally a Socks5 proxy port and/or username and password. This is mutually exclusive with the usage of SSH tunneling.
If this feature is documented (I don't think SSH tunneling support currently is), a few security aspects might be relevant to mention in the documentation:
- Socks5 transmits passwords in plaintext. Consequently, usage of a remote proxy host with Socks5 passwords is generally insecure.
- Socks5 is a proxy protocol, and as such, it is highly recommended to only use it when TLS is fully enabled and no insecure TLS options are being passed.
|