nm-connection-editor ambiguously says "Require IPv4 addressing for this connection to complete" (and similar for IPv6) - hover contracdicts it

[nobushel]

nm-connection-editor ambiguously says "Require IPv4 addressing for this connection to complete" (and similar for IPv6).

By my reckoning, this can mean either
* For this connection to complete, require IPv4 addressing
* Require the completion of this connection's IPv4 addressing

I'm not sufficiently skilled to whether either of these can be ruled out as gibberish, on a technical level.

To further complicate matters, the general gist of either of those meanings seems to be exactly opposite to the hover text/ tool-tip, which says

When connecting to IPv6-capable networks, allows the connection to complete if IPv4 configuration fails but IPv6 configuration succeeds.

That's the IPv4 Settings tab. The IPv6 Settings tab has the same problems:

Label: Require IPv6 addressing for this connection to complete
Hover: When connecting to IPv4-capable networks, allows the connection to complete if IPv6 configuration fails but IPv4 configuration succeeds.

Suggested fix:

1. First determine which meaning is correct--that
(A) the checkbox allows the connection to exist without IPv4, or that
(B) it only allows the connection to connect if IPv4 works.

I'd do that, but I don't have an IPv6 test rig--or I just don't know enough about it.

2. Then, replace the labels and text by something like

--- MEANING (A) ---

IPv4 Settings tab
Label: For this connection, don't require successful IPv4 configuration
or perhaps
Allow this connection to fall back on IPv6
or again
Allow this connection without successful IPv4 configuration
Hover: When connecting to IPv6-capable networks, allows the connection to complete if IPv4 configuration fails but IPv6 configuration succeeds.

IPv6 Settings tab
Label: For this connection, don't require successful IPv6 configuration (or whatever format you decide on for the IPv4 label)
Hover: When connecting to IPv4-capable networks, allows the connection to complete if IPv6 configuration fails but IPv4 configuration succeeds.

--- MEANING (B) ---

IPv4 Settings tab
Label: For this connection, require successful IPv4 configuration
Hover: When connecting to IPv6-capable networks, prevents the connection from completing if IPv4 configuration fails.

IPv6 Settings tab
Label: For this connection, require successful IPv6 configuration
Hover: When connecting to IPv4-capable networks, prevents the connection from completing if IPv6 configuration fails.

Not sure whether this has implications for security.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: network-manager-gnome 0.9.6.2-0ubuntu6
ProcVersionSignature: Ubuntu 3.5.0-26.42-generic 3.5.7.6
Uname: Linux 3.5.0-26-generic x86_64
ApportVersion: 2.6.1-0ubuntu10
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory: 'iw'
Date: Mon May 13 16:51:41 2013
ExecutablePath: /usr/bin/nm-connection-editor
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-03-17 (57 days ago)
InstallationMedia: Lubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
IpRoute:
 default via 192.168.2.1 dev eth0 proto static
 192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.14 metric 1
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MarkForUpload: True
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RfKill:

SourcePackage: network-manager-applet
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
 Wired connection 1 a142ebd0-7426-463d-b3a2-b08c8101526f 802-3-ethernet 1368478293 Mon 13 May 2013 04:51:33 PM EDT yes no /org/freedesktop/NetworkManager/Settings/1
 Private Internet Access SSL 0e5695cb-9d62-4f2a-a2db-67613bdda656 vpn 1364164151 Sun 24 Mar 2013 06:29:11 PM EDT no no /org/freedesktop/NetworkManager/Settings/0
nmcli-dev:
 DEVICE TYPE STATE DBUS-PATH
 eth0 802-3-ethernet connected /org/freedesktop/NetworkManager/Devices/0
nmcli-nm:
 RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
 running 0.9.6.0 connected enabled enabled enabled enabled disabled

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Johannes Aquila (johannes-aquila)]

I think there is at least privacy issue in connection with VPNs and DNS leaks. Preventing a DNS leak requires proper configuration of IPv4 and IPv6 DNS servers. The latter are usually not needed and are more cumbersome to configure since most people can't remember IPv6 addresses for long. As the checkbox contradicts itself, someone may erroneously think they have disabled IPv6-only networking, and thus have an unexpected DNS leak. I would imagine that similar scenarios can lead to a security issue as well.

Also, the wording is really quite unclear even without the contradiction between label and tooltip. I think the OP's proposed label "Allow this connection to fall back on IPv4" is far better.