Authenticated SOCKS5 proxy not working in Chromium about browser-extension

[ericjung]

I am fairly sure Chrome never natively supported authentication with SOCKS5 servers. If so, username/password should be disabled on chrome when SOCKS5 server is setup or imported from Firefox; it has to be supported by the browser for it to work.

I will double-check this and reply again.

[unrealtournament]

I see, if that is the case it should probably be reflected in the UI somehow as you said, as right now it allows you to enter a user/password. Thank you anyway.

[erosman]

Chrome never supported SOCKS5 authentication. In fact, Firefox is the only browser that has an API to support SOCKS5 authentication.

It is outlined in FoxyProxy Help under "Proxy Authentication".

FoxyProxy 8 has a unified code on Chrome & Firefox, enabling users to import/export settings between browsers.

• Removing the data when importing would interfere with sharing between browsers
• Removing the data would also interfere with proxy type switching
• Removing the UI in Chrome will affect editing and sharing between browsers
• Disabling the UI can result in user/pass showing in imported settings and no way to edit it

[randomstuff]

For reference see Proxy support in Chrome:

No authentication methods are supported for SOCKSv5 in Chrome (although some do exist for the protocol).

[ericjung]

Chrome never supported SOCKS5 authentication. In fact, Firefox is the only browser that has an API to support SOCKS5 authentication.

It is outlined in FoxyProxy Help under "Proxy Authentication".

FoxyProxy 8 has a unified code on Chrome & Firefox, enabling users to import/export settings between browsers.

• Removing the data when importing would interfere with sharing between browsers
• Removing the data would also interfere with proxy type switching
• Removing the UI in Chrome will affect editing and sharing between browsers
• Disabling the UI can result in user/pass showing in imported settings and no way to edit it

We can warn the user when importing into chrome settings with a socks proxy server with authentication. If we don’t do anything at all (like now), I expect more tickets like this in the future.

[erosman]

We can warn the user when importing into chrome settings with a socks proxy server with authentication. If we don’t do anything at all (like now), I expect more tickets like this in the future.

I will update the UI for v8.5