app_Settings

Go to file

Erik Kline 6c2ad0d62d Expressly forbid IP string literals as Private DNS hostnames

For obvious bootstrapping reasons, DNS settings have always used
IP address string literals in input fields.

However, since we can use the network-assigned nameservers to bootstrap
our way to multiple IP addresses of multiple families (!), hostnames
provide a clear simplicity and future-proofing advantage.

Permitting IP address literals means not only making sure that we can
validate X.509v3 certificates for IP addresses, but coping with the
inevitable broken configurations where users may have configured IPv4
addresses but no IPv6 addresses.  This will unnecessarily complicate
life on IPv6-only networks.

=)

Test: as follows
    - built
    - flashed
    - booted
    - tried to enter IP string literals
    - make -j50 RunSettingsRoboTests ROBOTEST_FILTER=PrivateDnsModeDialogPreferenceTest
Bug: 34953048
Bug: 64133961
Bug: 73641539

Change-Id: I7a58e86ed640ff5600906fb3d8cb9a2c75598831

2018-04-04 00:42:19 -07:00

res

Enterprice privacy: let the user know if admin enabled backups.

2018-04-03 13:58:39 +02:00

src/com/android/settings

Expressly forbid IP string literals as Private DNS hostnames

2018-04-04 00:42:19 -07:00

tests

Expressly forbid IP string literals as Private DNS hostnames

2018-04-04 00:42:19 -07:00

Android.mk

Add auto restriction for excessive background