[Bug 1587204] [NEW] Spams motd with "proxy ... looks invalid"

Robie Basak 1587204 at bugs.launchpad.net
Tue May 31 01:47:09 UTC 2016


Public bug reported:

On login, occasionally I see:

proxy 'http://[<ipv6 address redacted>]:3128/' looks invalid

I tracked this down to /etc/update-motd.d/91-release-upgrade which is
calling "/usr/lib/ubuntu-release-upgrader/check-new-release -q" when a
cache is stale, and I can reproduce this every time by running "sudo
usr/lib/ubuntu-release-upgrader/check-new-release -q".

It looks like UpdateManager/Core/utils.py has an incomplete regexp
"http://\w+", which does not catch the square brackets used around an
IPv6 address. Presumably the regexp needs extending. In my case I'm
specifying my proxy by IP because I use Zeroconf names (using mdns) but
in this case am using it inside a container that is bridged so .local
names do not resolve there.

This presumably means that it ignores my proxy definition too, though I
haven't tested this.

This is with update-manager-core 1:16.04.3 but it looks like the source
from 1:16.10.1 is still affected.

** Affects: update-manager (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to update-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1587204

Title:
  Spams motd with "proxy ... looks invalid"

Status in update-manager package in Ubuntu:
  New

Bug description:
  On login, occasionally I see:

  proxy 'http://[<ipv6 address redacted>]:3128/' looks invalid

  I tracked this down to /etc/update-motd.d/91-release-upgrade which is
  calling "/usr/lib/ubuntu-release-upgrader/check-new-release -q" when a
  cache is stale, and I can reproduce this every time by running "sudo
  usr/lib/ubuntu-release-upgrader/check-new-release -q".

  It looks like UpdateManager/Core/utils.py has an incomplete regexp
  "http://\w+", which does not catch the square brackets used around an
  IPv6 address. Presumably the regexp needs extending. In my case I'm
  specifying my proxy by IP because I use Zeroconf names (using mdns)
  but in this case am using it inside a container that is bridged so
  .local names do not resolve there.

  This presumably means that it ignores my proxy definition too, though
  I haven't tested this.

  This is with update-manager-core 1:16.04.3 but it looks like the
  source from 1:16.10.1 is still affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1587204/+subscriptions



More information about the foundations-bugs mailing list