Added explicit default values to AttestationSettingsProto.
This change has no effect on client behavior but is desirable for
robustness on the server side.
BUG=None
TEST=build
Review URL: https://codereview.chromium.org/27379002
git-svn-id: http://src.chromium.org/svn/trunk/src/chrome/browser/policy/proto@229460 4ff67af0-8c30-449e-8e8b-ad334ec8d88c
diff --git a/chromeos/chrome_device_policy.proto b/chromeos/chrome_device_policy.proto
index a7fc4fc..3623b8f 100644
--- a/chromeos/chrome_device_policy.proto
+++ b/chromeos/chrome_device_policy.proto
@@ -362,7 +362,7 @@
// this is enabled a machine key will be generated and certified by the Chrome
// OS CA. If this setting is disabled, even users with attestation settings
// enabled will not be able to use those features on the device.
- optional bool attestation_enabled = 1;
+ optional bool attestation_enabled = 1 [default = false];
// Chrome OS devices can use remote attestation (Verified Access) to get a
// certificate issued by the Chrome OS CA that asserts the device is eligible
@@ -370,7 +370,7 @@
// endorsement information to the Chrome OS CA which uniquely identifies the
// device. This setting allows this feature to be disabled for the device
// regardless of any user-specific settings.
- optional bool content_protection_enabled = 2;
+ optional bool content_protection_enabled = 2 [default = true];
}
message AccessibilitySettingsProto {
