[Feature] Proxy Support

[noneper]

Describe the bug
Session desktop can't send out any message even when I run lokinet client. I try to use proxy but Session desktop have not this feature. So I search long time and installed a app named Proxifier, it could force a program to use a proxy. Then Session could connecting and send out messages to my contactor.

If Session could have a option to use proxy servers I needn't any other costed app to help at all.

• OS: Windows 10
• Session Version or Git commit hash: desktop 1.5.2

[KeeJef]

Session already Onion routes all messages, support for proxying would help on some OS's like tails though but it doesn't really offer any increased privacy benefits

[depewzhang]

I have the same issue. I use proxifier on Windows, but I can't deal with that on Ubuntu. Any suggestion?

[majestrate]

in the near future session will start using lokinet for onion routing and that cannot be shoved over a proxy (this is an intentional design choice of lokinet). i personally doubt session will ever get any type of manual proxy settings.

Session already Onion routes all messages, support for proxying would help on some OS's like tails though but it doesn't really offer any increased privacy benefits

It's not about increased privacy, certain networks only have Internet access over proxy server (usually seen in school/enterprise). Currently Session Desktop client doesn't handle system proxy settings, which means one cannot use Session in such environment at all.

[BeholdersEye]

I have successfully configured Session for Windows desktop to connect through a proxy using kkcap.

https://kkcap.net/

https://github.com/ji4ozhu/kkcap

This may be a useful stopgap measure until Session adds proxy configuration settings.

[574r64z3r]

@KeeJef Can we have proxy support for fetching nodes from seedNodeHosts? Because seed*.getsession.org might be blocked.
As mentioned in issue oxen-io/session-desktop-temp#375 :

Describe the bug
cannot find path in china the first time started, while ios and android client can find the path.
after proxy/vpn enabled once and the path is found, later the path can be found without proxy/vpn.

I think the logic is that after you have initialized the seed nodes DB via proxy/vpn first, you won't need the seedNodeHosts to find a path later.

This might solve oxen-io/session-desktop-temp#238 oxen-io/session-desktop-temp#375 , https://github.com/oxen-io/session-desktop-temp/issues/389

and oxen-io/session-desktop-temp#173 oxen-io/session-desktop-temp#160 if they are able to use a proxy

[KeeJef]

I'd like to see custom proxy support in the desktop client, its in the backlog of features for now

[wangyifan349]

I also think socket5, https proxy should be added, just like telegram. Otherwise it will not work in countries with firewalls.

[wangyifan349]

It is not suitable for use with shielding, which is very troublesome.

[greatwolf]

Any updates on this proxy support issue? This is especially a problem in censorship regions like GFW. I'd like to be able to use a SOCKS5 proxy through SSH tunnel as a simple solution.

[KeeJef]

Still something I would like to work on, but remains in the backlog for now

[Bloopps]

Any update ?

[KeeJef]

Tracking internally via SES-2167, our current priority is the new groups system, updated onboarding and Lokinet support for Session clients.