[SRU] Backport to 22.04 LTS

[Gabriel Nagy]

As part of our entreprise desktop offering, there is the request to backport ubuntu-proxy-manager to 22.04 LTS. The package is in universe for now.

Ubuntu Proxy Manager is a D-Bus mediated service intended to be triggered by ADSys, our Active Directory GPO integration. ADSys has been available starting Ubuntu 21.04, and Ubuntu Proxy Manager was first released in Ubuntu 23.04.

It depends on the new golang 1.22 SRU attached to https://bugs.launchpad.net/ubuntu/+source/golang-1.22/+bug/2059756

[Impact]

 * ubuntu-proxy-manager is a new package. Impact is thus only for people installing.
 * To leverage the functionality of the package, a recent enough ADSys version must be used (at least 0.11.0, not currently in Jammy but there are approved plans to backport ADSys 0.13.2).
 * In addition to the ADSys requirement above, the machine must be Pro-enabled and a Proxy GPO must be configured on the Windows AD controller.
 * No impact is expected if the conditions above are not met.
 * This is a entreprise feature requested by desktop customers running LTS.

[Test Plan]

 1. Configure your machine with AD, with a correctly configured SSSD and KRB5 (AD user should be able to log in). Instructions can be found on https://github.com/ubuntu/adsys/wiki/2.-Prerequisites
 2. Install admx and adml files on your AD controller: https://canonical-adsys.readthedocs-hosted.com/en/stable/how-to/set-up-ad/
 3. Join machine to Ubuntu Pro to enable proxy policy application
 4. Configure some proxy settings in AD (https://canonical-adsys.readthedocs-hosted.com/en/stable/explanation/proxy/), for instance:
  * HTTP Proxy
  * Ignored hosts
 5. Install ADSys (at least version 0.11.0) and ubuntu-proxy-manager, then run `adsysctl update -m` to force a refresh of the policies
 6. Ensure GSettings/APT/environment proxy values are correctly set (full list of supported proxy backends can be seen here: https://github.com/ubuntu/ubuntu-proxy-manager#supported-backends)
 7. Remove/purge the ubuntu-proxy-manager package and run `adsysctl update -m` again -- a warning should show reflecting that ADSys has detected a configured proxy policy but ubuntu-proxy-manager is not installed for it to be applied. ADSys's exit code will remain 0.

[Where problems could occur]

 * Network access of various programs will be hindered if incorrect proxy settings are configured.

[Other Info]

 * The current version of ADSys in Jammy does not interact with this package whatsoever, but there are plans to backport the latest version.
 * A passing PPA build for ubuntu-proxy-manager can be seen here: https://launchpad.net/~gabuscus/+archive/ubuntu/ppa/+sourcepub/15678628/+listing-archive-extra
 * We have previously requested a FFe for ubuntu-proxy-manager for Focal: https://bugs.launchpad.net/ubuntu/jammy/+source/adsys/+bug/2012371

[Gabriel Nagy (gabuscus)]

ubuntu-proxy-manager (new package) is uploaded and currently in the NEW queue https://launchpad.net/ubuntu/jammy/+queue?queue_state=0&queue_text=ubuntu-proxy-manager

[Łukasz Zemczak (sil2100)]

Hello Gabriel, or anyone else affected,

Accepted ubuntu-proxy-manager into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-proxy-manager/0.1.1~22.04 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Gabriel Nagy (gabuscus)]

Validated ubuntu-proxy-manager on Jammy using the steps below:

1. Install package from proposed
root@jammy-fccb9151:~# apt-cache policy ubuntu-proxy-manager
ubuntu-proxy-manager:
  Installed: 0.1.1~22.04
  Candidate: 0.1.1~22.04
  Version table:
 *** 0.1.1~22.04 400
        400 http://archive.ubuntu.com/ubuntu jammy-proposed/universe amd64 Packages
        100 /var/lib/dpkg/status

2. Set all proxy settings
root@jammy-fccb9151:~# # Set all proxy settings
gdbus call --system --dest com.ubuntu.ProxyManager \
                    --object-path /com/ubuntu/ProxyManager \
                    --method com.ubuntu.ProxyManager.Apply \
                    "http://example.com:8080" \
                    "https://example.com:8080" \
                    "ftp://example.com:8080" \
                    "socks://example.com:8080" \
                    "localhost,127.0.0.1,::1" \
                    "http://example.com:8080/proxy.pac"
()

3. Confirm environment and APT proxy have been set, and the gschema override was created
root@jammy-fccb9151:~# cat /etc/environment.d/99ubuntu-proxy-manager.conf /etc/apt/apt.conf.d/99ubuntu-proxy-manager /usr/share/glib-2.0/schemas/99_ubuntu-proxy-manager.gschema.override
### This file was generated by ubuntu-proxy-manager - manual changes will be overwritten
HTTP_PROXY="http://example.com:8080"
http_proxy="http://example.com:8080"
HTTPS_PROXY="https://example.com:8080"
https_proxy="https://example.com:8080"
FTP_PROXY="ftp://example.com:8080"
ftp_proxy="ftp://example.com:8080"
SOCKS_PROXY="socks://example.com:8080"
socks_proxy="socks://example.com:8080"
NO_PROXY="localhost,127.0.0.1,::1"
no_proxy="localhost,127.0.0.1,::1"
### This file was generated by ubuntu-proxy-manager - manual changes will be overwritten
Acquire::http::Proxy "http://example.com:8080";
Acquire::https::Proxy "https://example.com:8080";
Acquire::ftp::Proxy "ftp://example.com:8080";
Acquire::socks::Proxy "socks://example.com:8080";
### This file was generated by ubuntu-proxy-manager - manual changes will be overwritten
[org.gnome.system.proxy.http]
host='example.com'
port=8080

[org.gnome.system.proxy.https]
host='example.com'
port=8080

[org.gnome.system.proxy.ftp]
host='example.com'
port=8080

[org.gnome.system.proxy.socks]
host='example.com'
port=8080

[org.gnome.system.proxy]
ignore-hosts=['localhost','127.0.0.1','::1']

[org.gnome.system.proxy]
autoconfig-url='http://example.com:8080/proxy.pac'

[org.gnome.system.proxy]
mode='auto'

4. Confirm GSettings proxy has been set
root@jammy-fccb9151:~# gsettings list-recursively org.gnome.system.proxy
org.gnome.system.proxy autoconfig-url 'http://example.com:8080/proxy.pac'
org.gnome.system.proxy ignore-hosts ['localhost', '127.0.0.1', '::1']
org.gnome.system.proxy mode 'auto'
org.gnome.system.proxy use-same-proxy true
org.gnome.system.proxy.ftp host 'example.com'
org.gnome.system.proxy.ftp port 8080
org.gnome.system.proxy.http authentication-password ''
org.gnome.system.proxy.http authentication-user ''
org.gnome.system.proxy.http enabled false
org.gnome.system.proxy.http host 'example.com'
org.gnome.system.proxy.http port 8080
org.gnome.system.proxy.http use-authentication false
org.gnome.system.proxy.htt...

[Andreas Hasenack (ahasenack)]

> * To leverage the functionality of the package, a recent enough ADSys version must be used (at least
> 0.11.0, not currently in Jammy but there are approved plans to backport ADSys 0.13.2).

Jammy-updates currently has 0.9.2~22.04.2, and jammy-proposed has 0.14.1~22.04. Given the above, I understand that ubuntu-proxy-manager cannot be released yet, correct?

[Gabriel Nagy (gabuscus)]

That's fine since ubuntu-proxy-manager is standalone (as per my test steps above). The ADSys proxy manager just makes a dbus call to u-p-m to apply proxy settings (if installed).

[Launchpad Janitor (janitor)]

This bug was fixed in the package ubuntu-proxy-manager - 0.1.1~22.04

---------------
ubuntu-proxy-manager (0.1.1~22.04) jammy; urgency=medium

  * Backport to Jammy (LP: #2048232)
    - Disable dh_dwz on account of go >= 1.19 compressing symbols itself
      (fixed in newer dh_golang)

 -- Gabriel Nagy <email address hidden> Tue, 23 Apr 2024 14:55:23 +0300

[Timo Aaltonen (tjaalton)]

The verification of the Stable Release Update for ubuntu-proxy-manager has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.