Debian Bug report logs - #859934
enable captive portal checking by default

Display info messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Michael Stapelberg <stapelberg@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: enable captive portal checking by default

Date: Sun, 09 Apr 2017 14:04:53 +0200

Source: network-manager
Version: 1.6.2-3
Severity: wishlist

Filing this issue to get the discussion started.

I recently noticed that NetworkManager as distributed by Debian does
not do captive portal checks by default. I.e., when using an Airport
WiFi (or similar), users are left in the dark about how to connect to
the internet. Given that more and more websites go https-only, users
will just be presented with a hard-to-understand error message about
security issues.

I think having NetworkManager detect captive portals is a clear
improvement in user experience.

In technical terms:

• You can check what NetworkManager thinks of your connectivity using
  e.g. “nmcli networking connectivity”, which will result in either
  “full” or “portal”.

• In Debian, regardless of the network type, I always see “full”,
  because we don’t specify the connectivity.uri setting.

• Fedora ships the following configuration fragment to enable
  connectivity checking:
  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/20-connectivity-fedora.conf

• Not all frontends make use of the connectivity status. E.g.,
  nm-applet does not seem to do anything, whereas I’m told that GNOME
  shell will make use of the status.

Aside from the technicalities of enabling the feature, there are a
couple of open questions to answer:

1. Does enabling connectivity checking pose a privacy issue? No user
   data is transmitted in the connectivity checks, but merely making
   such a request implies that the user is running a Debian(-based)
   operating system with NetworkManager.

2. I’m assuming the ideal URL to configure as connectivity.uri is a
   Debian-specific URI (as opposed to re-using Fedora’s), and that URI
   would likely point to a vhost configured on Debian’s static
   mirroring infrastructure. Extrapolating from network-manager’s
   71874 popcon votes and a default connectivity check interval of 300
   seconds, we’d place an additional load of at least 239
   requests/second on our infrastructure. Are we equipped to handle
   this load now and in the future? Note that we could easily disable
   the feature by removing the DNS record of a single-purpose vhost
   for this feature (e.g. nm-connectivity-check.debian.org).

I’d be happy to talk to DSA to get point ② clarified, but I’m not
quite sure who can help with clarifying point ①. Any thoughts?

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel, mipsel, arm64

Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Message #10 received at 859934@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Michael Stapelberg <stapelberg@debian.org>, 859934@bugs.debian.org, Jeremy Bicha <jbicha@ubuntu.com>

Subject: Re: [Pkg-utopia-maintainers] Bug#859934: enable captive portal checking by default

Date: Sun, 9 Apr 2017 14:47:39 +0200

[Message part 1 (text/plain, inline)]

[CCed the full message so Jeremy has all context]


Hi Michael

Am 09.04.2017 um 14:04 schrieb Michael Stapelberg:
> 
> I recently noticed that NetworkManager as distributed by Debian does
> not do captive portal checks by default. I.e., when using an Airport
> WiFi (or similar), users are left in the dark about how to connect to
> the internet. Given that more and more websites go https-only, users
> will just be presented with a hard-to-understand error message about
> security issues.
> 
> I think having NetworkManager detect captive portals is a clear
> improvement in user experience.
> 
> In technical terms:
> 
> • You can check what NetworkManager thinks of your connectivity using
>   e.g. “nmcli networking connectivity”, which will result in either
>   “full” or “portal”.
> 
> • In Debian, regardless of the network type, I always see “full”,
>   because we don’t specify the connectivity.uri setting.
> 
> • Fedora ships the following configuration fragment to enable
>   connectivity checking:
>   https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/contrib/fedora/rpm/20-connectivity-fedora.conf
> 
> • Not all frontends make use of the connectivity status. E.g.,
>   nm-applet does not seem to do anything, whereas I’m told that GNOME
>   shell will make use of the status.
> 
> Aside from the technicalities of enabling the feature, there are a
> couple of open questions to answer:
> 
> 1. Does enabling connectivity checking pose a privacy issue? No user
>    data is transmitted in the connectivity checks, but merely making
>    such a request implies that the user is running a Debian(-based)
>    operating system with NetworkManager.
> 
> 2. I’m assuming the ideal URL to configure as connectivity.uri is a
>    Debian-specific URI (as opposed to re-using Fedora’s), and that URI
>    would likely point to a vhost configured on Debian’s static
>    mirroring infrastructure. Extrapolating from network-manager’s
>    71874 popcon votes and a default connectivity check interval of 300
>    seconds, we’d place an additional load of at least 239
>    requests/second on our infrastructure. Are we equipped to handle
>    this load now and in the future? Note that we could easily disable
>    the feature by removing the DNS record of a single-purpose vhost
>    for this feature (e.g. nm-connectivity-check.debian.org).
> 
> I’d be happy to talk to DSA to get point ② clarified, but I’m not
> quite sure who can help with clarifying point ①. Any thoughts?

2) is already solved, we have http://network-test.debian.org/nm, see
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729783

$ cat /etc/NetworkManager/conf.d/connectivity.conf
[connectivity]
uri=http://network-test.debian.org/nm

Something like this should already work today in Debian.


This feature could be considered "phoning-home", so I'm a bit concerned
in that regard indeed and do not want to enable it unconditionally and
globally for everyone. If this config is shipped in a separate package,
which can be installed (and uninstalled) on demand (and which e.g. the
gnome-core or gnome meta package could depend on), would be a reasonable
compromise I guess.

Fedora named this package NetworkManager-config-connectivity-fedora,
shipping /usr/lib/NetworkManager/conf.d/20-connectivity-fedora.conf. The
package is installed by default in a F25 workstation desktop.

Afair, Ubuntu had/has similar plans. Jeremy, can you comment on that?


Regards,
Michael
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #15 received at 859934@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Michael Stapelberg <stapelberg@debian.org>, 859934@bugs.debian.org, Jeremy Bicha <jbicha@ubuntu.com>

Subject: Re: [Pkg-utopia-maintainers] Bug#859934: enable captive portal checking by default

Date: Mon, 10 Apr 2017 01:07:52 +0200

[Message part 1 (text/plain, inline)]

Am 09.04.2017 um 14:47 schrieb Michael Biebl:

> This feature could be considered "phoning-home", so I'm a bit concerned
> in that regard indeed and do not want to enable it unconditionally and
> globally for everyone. If this config is shipped in a separate package,
> which can be installed (and uninstalled) on demand (and which e.g. the
> gnome-core or gnome meta package could depend on), would be a reasonable
> compromise I guess.
> 
> Fedora named this package NetworkManager-config-connectivity-fedora,
> shipping /usr/lib/NetworkManager/conf.d/20-connectivity-fedora.conf. The
> package is installed by default in a F25 workstation desktop.
> 
> Afair, Ubuntu had/has similar plans. Jeremy, can you comment on that?

I remember that I discussed that briefly with Jeremy on IRC. Such a
separate binary package (even if tiny) seems like an approach to me
which I'd be fine with.

I found this after a bit of searching:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/997200
https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039696.html

Next step would be to decide, how we name things, i.e. if we choose
different names for Ubuntu and Debian, like
network-manager-config-connectivity-debian and
network-manager-config-connectivity-ubuntu (quite the mouthful)
or an unbranded name like
network-manager-config-connectivity, but with different content
depending on the distro.

Any preferences?


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #20 received at 859934@bugs.debian.org (full text, mbox, reply):

From: Jeremy Bicha <jbicha@ubuntu.com>

To: Michael Biebl <biebl@debian.org>

Cc: Michael Stapelberg <stapelberg@debian.org>, 859934@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#859934: enable captive portal checking by default

Date: Sun, 9 Apr 2017 19:20:38 -0400

On Sun, Apr 9, 2017 at 8:47 AM, Michael Biebl <biebl@debian.org> wrote:
> Afair, Ubuntu had/has similar plans. Jeremy, can you comment on that?

I proposed this for Ubuntu GNOME 17.04. There was interest in enabling
the connectivity check in the default Ubuntu install too, but there
wasn't enough time to handle this well before 17.04.

Mathieu Trudel-Lapierre thought it would be better for users if there
was a handy toggle switch (likely in gnome-control-center's Privacy
panel) before this feature was rolled out. At least for Ubuntu
Desktop, it doesn't really matter then whether the implementation is a
separate package or if gnome-control-center writes the config to an
appropriate file itself.

The tracking bug for that is https://bugzilla.gnome.org/737362

Thanks,
Jeremy

Message #25 received at 859934@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 859934@bugs.debian.org, Michael Stapelberg <stapelberg@debian.org>, Jeremy Bicha <jbicha@ubuntu.com>

Subject: Re: [Pkg-utopia-maintainers] Bug#859934: enable captive portal checking by default

Date: Fri, 26 May 2017 17:31:12 +0200

[Message part 1 (text/plain, inline)]

Hi there


On Mon, 10 Apr 2017 01:07:52 +0200 Michael Biebl <biebl@debian.org> wrote:
> Am 09.04.2017 um 14:47 schrieb Michael Biebl:
> 

> > Fedora named this package NetworkManager-config-connectivity-fedora,
> > shipping /usr/lib/NetworkManager/conf.d/20-connectivity-fedora.conf. The
> > package is installed by default in a F25 workstation desktop.
> > 
> > Afair, Ubuntu had/has similar plans. Jeremy, can you comment on that?
> 
> I remember that I discussed that briefly with Jeremy on IRC. Such a
> separate binary package (even if tiny) seems like an approach to me
> which I'd be fine with.
> 
> I found this after a bit of searching:
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/997200
> https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039696.html
> 
> Next step would be to decide, how we name things, i.e. if we choose
> different names for Ubuntu and Debian, like
> network-manager-config-connectivity-debian and

Unless someone complains loudly, I intend to go ahead using the package
name network-manager-config-connectivity-debian.

The package will provide
/usr/lib/NetworkManager/conf.d/20-connectivity-debian.conf

Enabling the feature is then as simple as installing the package,
disabling it can be achieved by uninstalling it. That's why I don't want
to install the file in /etc/NetworkManager/conf.d, as we then would have
the known issue of conffiles not being removed on "remove".

It is planned that at least the gnome (or gnome-core) meta package will
pull in this package. Other desktop environments which provide captive
portal detection can do the same.
I guess we'll make that a Recommends, so users can uninstall the package
if they so prefer (e.g. due to privacy concerns)


> Mathieu Trudel-Lapierre thought it would be better for users if there
> was a handy toggle switch (likely in gnome-control-center's Privacy
> panel) before this feature was rolled out. At least for Ubuntu
> Desktop, it doesn't really matter then whether the implementation is a
> separate package or if gnome-control-center writes the config to an
> appropriate file itself.
> 
> The tracking bug for that is https://bugzilla.gnome.org/737362

This seems like a nice alternative solution which apparently is kinda
stuck though atm.
So for the time being a separate config package it is.
If we have support in gnome-control-center one day to write out that
config snippet (or NM providing a D-Bus API for setting that), we can
revisit that decision and drop the package again.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #32 received at 859934@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 859934@bugs.debian.org, Michael Stapelberg <stapelberg@debian.org>, Jeremy Bicha <jbicha@ubuntu.com>

Subject: Re: [Pkg-utopia-maintainers] Bug#859934: enable captive portal checking by default

Date: Fri, 26 May 2017 18:04:56 +0200

[Message part 1 (text/plain, inline)]

Am 26.05.2017 um 17:31 schrieb Michael Biebl:
> Unless someone complains loudly, I intend to go ahead using the package
> name network-manager-config-connectivity-debian.
> 
> The package will provide
> /usr/lib/NetworkManager/conf.d/20-connectivity-debian.conf

I pushed
https://anonscm.debian.org/cgit/pkg-utopia/network-manager.git/commit/?h=experimental&id=292772f681

Feedback welcome. Especially regarding the package description.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #37 received at 859934@bugs.debian.org (full text, mbox, reply):

From: Michael Stapelberg <stapelberg@debian.org>

To: Michael Biebl <biebl@debian.org>

Cc: 859934@bugs.debian.org, Jeremy Bicha <jbicha@ubuntu.com>

Subject: Re: [Pkg-utopia-maintainers] Bug#859934: enable captive portal checking by default

Date: Wed, 31 May 2017 11:36:20 +0200

[Message part 1 (text/plain, inline)]

Thank you very much for working on this.

One nit regarding the package long description: we should mention the
privacy implications of this package. My suggestion:

No user data is transmitted in the connectivity checks, but merely
contacting the Debian connectivity check servers reveals that the user is
running a Debian(-based) operating system with NetworkManager.

On Fri, May 26, 2017 at 6:04 PM, Michael Biebl <biebl@debian.org> wrote:

> Am 26.05.2017 um 17:31 schrieb Michael Biebl:
> > Unless someone complains loudly, I intend to go ahead using the package
> > name network-manager-config-connectivity-debian.
> >
> > The package will provide
> > /usr/lib/NetworkManager/conf.d/20-connectivity-debian.conf
>
> I pushed
> https://anonscm.debian.org/cgit/pkg-utopia/network-manager.git/commit/?h=
> experimental&id=292772f681
>
> Feedback welcome. Especially regarding the package description.
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>


-- 
Best regards,
Michael

[Message part 2 (text/html, inline)]

Message #42 received at 859934@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: Michael Stapelberg <stapelberg@debian.org>, 859934@bugs.debian.org

Subject: Re: [Pkg-utopia-maintainers] Bug#859934: Bug#859934: enable captive portal checking by default

Date: Wed, 31 May 2017 12:06:30 +0200

[Message part 1 (text/plain, inline)]

Am 31.05.2017 um 11:36 schrieb Michael Stapelberg:
> One nit regarding the package long description: we should mention the
> privacy implications of this package. My suggestion:
> 
> No user data is transmitted in the connectivity checks, but merely
> contacting the Debian connectivity check servers reveals that the user
> is running a Debian(-based) operating system with NetworkManager.

Nod. Will add this paragraph. Thanks for the suggestion.



-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

[signature.asc (application/pgp-signature, attachment)]

Message #47 received at 859934-close@bugs.debian.org (full text, mbox, reply):

From: Michael Biebl <biebl@debian.org>

To: 859934-close@bugs.debian.org

Subject: Bug#859934: fixed in network-manager 1.8.0-3

Date: Fri, 09 Jun 2017 14:00:17 +0000

Source: network-manager
Source-Version: 1.8.0-3

We believe that the bug you reported is fixed in the latest version of
network-manager, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 859934@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Biebl <biebl@debian.org> (supplier of updated network-manager package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 26 May 2017 23:49:46 +0200
Source: network-manager
Binary: network-manager network-manager-dev libnm-glib4 libnm-glib-dev libnm-glib-vpn1 libnm-glib-vpn-dev libnm-util2 libnm-util-dev libnm0 libnm-dev gir1.2-networkmanager-1.0 gir1.2-nm-1.0 network-manager-config-connectivity-debian
Architecture: source amd64 all
Version: 1.8.0-3
Distribution: experimental
Urgency: medium
Maintainer: Utopia Maintenance Team <pkg-utopia-maintainers@lists.alioth.debian.org>
Changed-By: Michael Biebl <biebl@debian.org>
Description:
 gir1.2-networkmanager-1.0 - GObject introspection data for the libnm-glib/libnm-util library
 gir1.2-nm-1.0 - GObject introspection data for the libnm library
 libnm-dev  - GObject-based client library for NetworkManager (development file
 libnm-glib-dev - network management framework (GLib interface)
 libnm-glib-vpn-dev - network management framework (GLib interface)
 libnm-glib-vpn1 - network management framework (GLib VPN shared library)
 libnm-glib4 - network management framework (GLib shared library)
 libnm-util-dev - network management framework (development files)
 libnm-util2 - network management framework (shared library)
 libnm0     - GObject-based client library for NetworkManager
 network-manager - network management framework (daemon and userspace tools)
 network-manager-config-connectivity-debian - NetworkManager configuration to enable connectivity checking
 network-manager-dev - network management framework (development files)
Closes: 729783 859934
Changes:
 network-manager (1.8.0-3) experimental; urgency=medium
 .
   [ Rico Tzschichholz ]
   * Enable vala bindings support
 .
   [ Michael Biebl ]
   * Enable connectivity checking functionality.
     Provide a new package called network-manager-config-connectivity-debian
     which can be installed to enable NetworkManager's connectivity checking
     functionality. This is particularly useful for captive portal detection.
     (Closes: #729783, #859934)
   * Reload NetworkManager after installing
     network-manager-config-connectivity-debian
   * Drop obsolete migration code
   * Stop reloading dbus after installing network-manager.
     Nowadays this is done automatically by dbus via dpkg file triggers.
Checksums-Sha1:
 b19db47f042c65e103edbb38295642b97a482cc0 3844 network-manager_1.8.0-3.dsc
 c5c4b4419587899f9f4814aa2f97440cf092066c 46404 network-manager_1.8.0-3.debian.tar.xz
 e84b05aba414f69874c563f64b90b3d412e2b4da 69296 gir1.2-networkmanager-1.0_1.8.0-3_amd64.deb
 42a68c85359661c1102888357aeacbf51cbd5a9b 77514 gir1.2-nm-1.0_1.8.0-3_amd64.deb
 e3a53bf7562d9eeea85b39f6652a65c2647ff6db 500526 libnm-dev_1.8.0-3_amd64.deb
 cd10fc3b4c4a7bcb9111eb88fcdb37b1412941d5 225780 libnm-glib-dev_1.8.0-3_amd64.deb
 5ec48911f59df90a08847b72ce48f403b9708cc8 34236 libnm-glib-vpn-dev_1.8.0-3_amd64.deb
 c5a5e59562f0832392023d54c50e66584d4b9a56 44046 libnm-glib-vpn1-dbgsym_1.8.0-3_amd64.deb
 f006cb24577d51beaa9f446f093ceb8d5fdc4d11 41668 libnm-glib-vpn1_1.8.0-3_amd64.deb
 43d32711224821db5ed8615d20819990440099b0 333608 libnm-glib4-dbgsym_1.8.0-3_amd64.deb
 116c138be9ef6450ef609142ed21e7900ca8e0a9 107908 libnm-glib4_1.8.0-3_amd64.deb
 9440790b902026bf1297561da064b3d8f0b37c21 238904 libnm-util-dev_1.8.0-3_amd64.deb
 b2d72d0bfcc146b645e642be4d14ea62f7064ab2 435796 libnm-util2-dbgsym_1.8.0-3_amd64.deb
 4d5220f865fd113f7024de1b3913f4d596d59958 144744 libnm-util2_1.8.0-3_amd64.deb
 7674abb9e64666cacebc8a8cab582f0bdad4d081 1516934 libnm0-dbgsym_1.8.0-3_amd64.deb
 2811149ebdf5728c6e47db9612623797e45b905e 293194 libnm0_1.8.0-3_amd64.deb
 2139a1c9dd0e52a78f6b58e67e044d91edf28118 29972 network-manager-config-connectivity-debian_1.8.0-3_all.deb
 3945fbae00817bfb2a905737989b47202b73f7f4 9214516 network-manager-dbgsym_1.8.0-3_amd64.deb
 21cf20a45b59f8ccce3f2f6e9e7f94813ef487ad 185262 network-manager-dev_1.8.0-3_amd64.deb
 8875280141632b1fc2cae8c3cb80c6e0f8740f78 16355 network-manager_1.8.0-3_amd64.buildinfo
 b310707db0e6de07354f8671f15d23a889ec17e9 2056468 network-manager_1.8.0-3_amd64.deb
Checksums-Sha256:
 5236d9773b8b1eaf86911f183c9235d9d023fb4213e3b0e95f465dd34483b422 3844 network-manager_1.8.0-3.dsc
 deef35468b716c4537e5bcdb50f70cb46f04898afe241da04bee12c98e88958f 46404 network-manager_1.8.0-3.debian.tar.xz
 8114543be653c549b6d9baf5a6115e85ebcde1cf9e4a6959173ff72eb9f3c14f 69296 gir1.2-networkmanager-1.0_1.8.0-3_amd64.deb
 f8310aacb17c77a198bbe5ffcfe1e8d82f9a3cce41cb6cf1169b792cf4a20eca 77514 gir1.2-nm-1.0_1.8.0-3_amd64.deb
 42ac8c17d39b606c07224713664c3ec3c194e1073d53f699128a0e57f96c2b08 500526 libnm-dev_1.8.0-3_amd64.deb
 8997a172b4215af34f3de61e8c195a84a1358407c90444451166198b444808e3 225780 libnm-glib-dev_1.8.0-3_amd64.deb
 550249ae72123bcb533c0f947e036ca6e45517ddd4d13b666aa47830dad0857c 34236 libnm-glib-vpn-dev_1.8.0-3_amd64.deb
 a20ac9914cd9341d0ad5e5371dc36afcbe5e621ae151ec9c5d93097c55178160 44046 libnm-glib-vpn1-dbgsym_1.8.0-3_amd64.deb
 3d5f8a6268acae10f0113e1d25e3f4e41b2654236aa328caf41ad378965140ad 41668 libnm-glib-vpn1_1.8.0-3_amd64.deb
 29e460b763895eb316c9034e8b161c834834576d6de978210c1341df8677f878 333608 libnm-glib4-dbgsym_1.8.0-3_amd64.deb
 56bd30f037a18a42379b31b2aa6ce5ecc9b514a6053b04833ff9d6f7332f4715 107908 libnm-glib4_1.8.0-3_amd64.deb
 b9a5d01f5e9705235fda8277b552f968a4a9d0fabcdd64d9fb55db40a25569ed 238904 libnm-util-dev_1.8.0-3_amd64.deb
 6555316cb9771e5feec46785d8549a90004c654985e8ae8473fa33502dee722f 435796 libnm-util2-dbgsym_1.8.0-3_amd64.deb
 a212ced0d68cdd15d649b62d7afcf5824cebfede19d00bad3d2512c4ce4fad0b 144744 libnm-util2_1.8.0-3_amd64.deb
 de78a07d42e5c2eb3793fe032e705fe0cb865df88e52b9efdf3aca0f83b9abbf 1516934 libnm0-dbgsym_1.8.0-3_amd64.deb
 9cb8ddf4f1cbba46e9a0b054e9ea12c93f60300a33f8cd6bbc795fa81dbb5f37 293194 libnm0_1.8.0-3_amd64.deb
 d60393bb690348512f24d32853ad9a74fde10475f44d91bf30e6fb9bd4729b52 29972 network-manager-config-connectivity-debian_1.8.0-3_all.deb
 ed15a40291827cbaaa6bfc11177d81fc2fb5e93640d74936248f61d3e2f7c541 9214516 network-manager-dbgsym_1.8.0-3_amd64.deb
 5aa8208ee3901afba7790d78d976625e2467ecad2778607c37393a6185256129 185262 network-manager-dev_1.8.0-3_amd64.deb
 851c489f231b1d6ddc54cf5570f2180c4d3a600412d1e444dee0d05f899b9bcd 16355 network-manager_1.8.0-3_amd64.buildinfo
 9d871b67e9c8e46a2d9bffc6662ca894e2b3af4d02f00618ca662800462c6319 2056468 network-manager_1.8.0-3_amd64.deb
Files:
 6560e7c6658bc354e5f888ef138db3a4 3844 net optional network-manager_1.8.0-3.dsc
 7206c68b54275352b67405543bfe8d9e 46404 net optional network-manager_1.8.0-3.debian.tar.xz
 012d85e40c7fce76a6754a01586de6c1 69296 introspection optional gir1.2-networkmanager-1.0_1.8.0-3_amd64.deb
 73a3193c7492690f1ac6a627b16757df 77514 introspection optional gir1.2-nm-1.0_1.8.0-3_amd64.deb
 a44e4442dbfb3c3f7085af1fa79b498c 500526 libdevel optional libnm-dev_1.8.0-3_amd64.deb
 c6a8f0ec7494922035eb4ebcdceb533d 225780 libdevel optional libnm-glib-dev_1.8.0-3_amd64.deb
 0fee2af266b2305c527ddeadb50d8135 34236 libdevel optional libnm-glib-vpn-dev_1.8.0-3_amd64.deb
 e39d578727a434da5f7d1869b41ddd08 44046 debug extra libnm-glib-vpn1-dbgsym_1.8.0-3_amd64.deb
 6f76bf60fe8e9c16bf7ae10445f998b4 41668 libs optional libnm-glib-vpn1_1.8.0-3_amd64.deb
 d3f78a78626f3b981f5fd77368f0ae4f 333608 debug extra libnm-glib4-dbgsym_1.8.0-3_amd64.deb
 84b4a01b408af34f9f5fce5474b83689 107908 libs optional libnm-glib4_1.8.0-3_amd64.deb
 a21cf4f6004292667252192e94f203a3 238904 libdevel optional libnm-util-dev_1.8.0-3_amd64.deb
 bc0cb531eb859049ca6c42153f073983 435796 debug extra libnm-util2-dbgsym_1.8.0-3_amd64.deb
 d93544ce54e26e2dfea6b98676d9e954 144744 libs optional libnm-util2_1.8.0-3_amd64.deb
 d20e1d34d2111ccae229090747901a46 1516934 debug extra libnm0-dbgsym_1.8.0-3_amd64.deb
 3d5c6bd01daf988016dcec50cdc9b32e 293194 libs optional libnm0_1.8.0-3_amd64.deb
 82f60afd28ffaa765dab7dbe6d70e722 29972 net optional network-manager-config-connectivity-debian_1.8.0-3_all.deb
 55a0c56254959c0f0c3c4a7215dbe862 9214516 debug extra network-manager-dbgsym_1.8.0-3_amd64.deb
 bc46eef7b7d135ee56eaa204ae7a8402 185262 devel optional network-manager-dev_1.8.0-3_amd64.deb
 13e76f49a21d7890d93aff0d176f6e69 16355 net optional network-manager_1.8.0-3_amd64.buildinfo
 3a5b491eeee9f1be168360c1f0861745 2056468 net optional network-manager_1.8.0-3_amd64.deb

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEECbOsLssWnJBDRcxUauHfDWCPItwFAlkotSEACgkQauHfDWCP
ItztoBAAiTi7IEMwVz8lrHBGB2S/UcHnZ7bwUolJUXICHhty87sWP5yfdeyJBRxT
it9Yoz1+vtLWOKo9S56vnSvi0IIYG1dvVLN8fBQuzGNQEYMmsWdO+0yt4PFQyxSE
DExQjMfZk1fyYOG4HijYmaBL699bQKkog2NqZGWYF8bm5/YOsVI/lSCQNvmZ0jUG
P4j+JiLrsYZt7k1RTUsiUMrx9jwbAlq1WDU4wBE0A29IilMpc0w/r7SMrUa1SfKO
yM2OSetM0cdcZWPM/ZFMhhDrEJkh6qRWpTuarq8UYTubH98lfXCBd7JJEJ7ycvdp
gtjhPCd/6Axtc516eHPkEHZ0aGFx1isf+gHNaH7Rw/dm+W6Yl2QJ3QJJe3NIxPU6
IP3Ce0EgAaxlTabiT4uZ/PRJ+gO4VPUDS2F8BanMwSB6z4+u4MxSuaVAJrcbBENm
9qTTvlShHDikHW/rK97ZwNqR4OqWsU1Kpjmg+nieIF5JuxV7VPERH5ASQa6yxrPe
YLbTszUIBlFUxJz+MKpsmPJegvOIIILDPb5Gs2CsnK9plMofsnfiM19Fjc7RhA9b
Qzxgnxb3MNqOUAFG9ycVK+qzXz3UzAqgLS9SVuaHCg4B6M4ObHecKUKGdhh6Live
Gd9OFIwgvH04ai9rrFilHfkJSkY5OOdyXw7dGbEauu4wKtsj4i8=
=7Hui
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.