After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 728764 - Options for network settings (SOCKS, IMAP proxy)
Options for network settings (SOCKS, IMAP proxy)
Status: RESOLVED OBSOLETE
Product: geary
Classification: Other
Component: client+engine
master
Other Linux
: Low enhancement
: ---
Assigned To: Geary Maintainers
Geary Maintainers
: 786434 (view as bug list)
Depends on: 714883
Blocks:
 
 
Reported: 2014-04-22 22:43 UTC by asterix
Modified: 2018-10-28 22:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description asterix 2014-04-22 22:43:11 UTC
Hi,
It would be good to have network settings as options that can be changed, to allow for proxies, etc. This could be in 'preferences', or in 'accounts', when you edit the settings for each account. At the moment it has to use the default network/proxy settings.
Comment 1 Jim Nelson 2014-04-23 00:56:05 UTC
Do you mean that each account should have separate network settings?  What situation would that be necessary?
Comment 2 asterix 2014-04-23 16:00:37 UTC
That would probably not be necessary for most people, so maybe isn't worth it - but at the moment you can't even set the network settings for geary as a whole (other than modifying system-wide settings).

An example case where it might be useful for some people, is when someone has multiple emails, and they have specific security needs, and so want to access one of their email accounts through tor or another method of connecting to the network privately. If they connect all their accounts through tor, it could potentially undermine some of the security of it, by associating a known account with a hidden one - also some services make problems for people connecting through tor, because of the high traffic, and so it might be desirable to have some accounts connected, and others not.
Comment 3 Jim Nelson 2014-04-23 19:51:10 UTC
> but at the moment you can't even set the network settings for geary as a whole
> (other than modifying system-wide settings).

I guess I see that as a feature, not a bug.  As someone who lived through a time when I had to configure each application's network settings, having a system-wide setting that networking libraries use (i.e. GIO) is a good thing.

> If they connect all their accounts through tor, it could
> potentially undermine some of the security of it, by associating a known
> account with a hidden one - also some services make problems for people
> connecting through tor, because of the high traffic, and so it might be
> desirable to have some accounts connected, and others not.

I can appreciate that.  As I understand Tor, it can be used as a SOCKS proxy, meaning that GNOME networking can be configured to send everything through Tor.  (I've never tried it, so perhaps it's more complicated than I'm saying.)  But I could a user wanting account-level control over that decision, i.e. have Geary go through a SOCKS proxy while all other apps, and even other Geary accounts, use through un-anonymizing network access.

I would want this to be an advanced setting, though, not something the average user should have to deal with.
Comment 4 asterix 2014-04-27 12:40:22 UTC
I agree, the default should be the system-wide network settings, and changing it should be more advanced settings - but I think this should be possible through the GUI, which at the moment it isn't (its not possible at all). Having different settings for each account is probably too much.
Comment 5 Michael Gratton 2017-11-21 02:53:16 UTC
This would have to be a plugin, so depending on Bug 714883.
Comment 6 Michael Gratton 2018-04-12 02:05:08 UTC
*** Bug 786434 has been marked as a duplicate of this bug. ***
Comment 7 Michael Gratton 2018-10-28 22:26:12 UTC
I just wrote up a tracking bug for the plugin system over at gitlab that collects all of the requirements for feature requests that should be implemented as plugins in the one place, so closing this bug in favour of that ticket: https://gitlab.gnome.org/GNOME/geary/issues/155