Package: network-manager Version: 1.6.2-3 Severity: normal Tags: patch The README.Debian file contains outdated references to the 0.9 version, and documentation. Also updated to expand reference to the command line tools, since nmtui has been expanded. Fix other minor grammar bits too.
-- System Information: Debian Release: 9.0 APT prefers testing-debug APT policy: (500, 'testing-debug'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.11.0-rc8-drm-tip+ (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages network-manager depends on: ii adduser 3.115 ii dbus 1.10.18-1 ii init-system-helpers 1.48 ii libaudit1 1:2.6.7-2 ii libbluetooth3 5.43-2 ii libc6 2.24-10 ii libglib2.0-0 2.50.3-2 ii libgnutls30 3.5.8-5 ii libgudev-1.0-0 230-3 ii libjansson4 2.9-1 ii libmm-glib0 1.6.4-1 ii libndp0 1.6-1+b1 ii libnewt0.52 0.52.19-1+b1 ii libnl-3-200 3.2.27-2 ii libnm0 1.6.2-3 ii libpam-systemd 232-23 ii libpolkit-agent-1-0 0.105-17 ii libpolkit-gobject-1-0 0.105-17 ii libreadline7 7.0-3 ii libselinux1 2.6-3+b1 ii libsoup2.4-1 2.56.0-2 ii libsystemd0 232-23 ii libteamdctl0 1.26-1+b1 ii libuuid1 2.29.2-1 ii lsb-base 9.20161125 ii policykit-1 0.105-17 ii udev 232-23 ii wpasupplicant 2:2.4-1 Versions of packages network-manager recommends: ii crda 3.18-1 ii dnsmasq-base 2.76-5+b1 ii iptables 1.6.0+snapshot20161117-6 pn iputils-arping <none> ii isc-dhcp-client 4.3.5-3 ii modemmanager 1.6.4-1 ii ppp 2.4.7-1+4 Versions of packages network-manager suggests: pn libteam-utils <none> -- debconf-show failed
--- README.Debian.orig 2017-06-06 11:10:22.195294649 +0100 +++ README.Debian 2017-06-07 08:57:04.746395076 +0100 @@ -4,16 +4,16 @@ It has two components: -1. a system level service which manages connections and reports network changes -2. a graphical desktop applet which allows the user to manipulate network - connections. The nmcli tool provides similar functionality on the command - line. +1. A system level service which manages connections and reports network changes +2. A managment tool (cli, text or graphical desktop applet) which allows ther + user to monitor and manipulate network connections. The included nmcli and + nmtui tools provide similar functionality from the command line. system connections and security ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -In NetworkManager version 0.9, network connections are stored as keyfiles in +In NetworkManager version 1.6, network connections are stored as keyfiles in the /etc/NetworkManager/system-connections/ directory. When creating new wireless or wired connections, they are by default system-owned (i.e. available to everyone) and the secrets (e.g WPA-PSK or WEP @@ -24,10 +24,10 @@ To avoid prompts for the root/admin password, NetworkManager ships a PolicyKit configuration file which grants everyone in group "netdev" or "sudo" the privilege to modify a system connection without prior authentication. Adding a -user to group sudo grants him root-like privileges though. If that is not -wanted, you can choose to add him to group netdev instead. +user to group sudo grants them root-like privileges though. If that is not +wanted, you can choose to add them to group netdev instead. If the user should not have the privilege to add and modify system connections -don't add him to either groups. +don't add them to either group. In that case, the user clients (like nm-applet) will default to creating user-owned connections where the secrets are stored in the user keyring. VPN and 3G type connections are by default also user-owned. @@ -36,7 +36,7 @@ http://live.gnome.org/NetworkManager/SystemSettings The keyfile specification is available at -https://developer.gnome.org/NetworkManager/0.9/ref-settings.html +https://developer.gnome.org/NetworkManager/1.6/ref-settings.html unmanaged devices and /etc/network/interfaces ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -49,4 +49,3 @@ recommended to manually remove any configuration for that interface from /etc/network/interfaces. You need to restart NetworkManager afterwards via "service network-manager restart". -