Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 // Copyright (c) 2013 The Chromium Authors. All rights reserved. | |
| 2 // Use of this source code is governed by a BSD-style license that can be | |
| 3 // found in the LICENSE file. | |
| 4 | |
| 5 #ifndef CHROMEOS_ATTESTATION_ATTESTATION_CONSTANTS_H_ | |
| 6 #define CHROMEOS_ATTESTATION_ATTESTATION_CONSTANTS_H_ | |
| 7 | |
| 8 namespace chromeos { | |
| 9 namespace attestation { | |
| 10 | |
| 11 // Options available for customizing an attestation certificate. | |
| 12 enum AttestationCertificateOptions { | |
|
Mattias Nissler (ping if slow)
2013/04/24 12:57:53
nit: We usually follow good practice for enums to
dkrahn
2013/04/25 01:06:52
The style guide gives this as an example of a good
Daniel Erat
2013/04/25 01:15:30
I think I agree with Mattias here. Omitting prefi
dkrahn
2013/04/25 02:45:35
That makes sense, and this CL does pull these out
| |
| 13 CERTIFICATE_OPTION_NONE = 0, | |
| 14 // A stable identifier is simply an identifier that is not affected by device | |
| 15 // state changes, including device recovery. | |
| 16 INCLUDE_STABLE_ID = 1, | |
| 17 // Device state information contains a quoted assertion of whether the device | |
| 18 // is in verified mode. | |
| 19 INCLUDE_DEVICE_STATE = 1 << 1 | |
|
Mattias Nissler (ping if slow)
2013/04/24 12:57:53
nit: putting a trailing colon here makes it easier
dkrahn
2013/04/25 01:06:52
Done. Good idea. I'm not in the habit...
| |
| 20 }; | |
| 21 | |
| 22 // Key types supported by the Chrome OS attestation subsystem. | |
| 23 enum AttestationKeyType { | |
| 24 // The key will be associated with the device itself and will be available | |
| 25 // regardless of which user is signed-in. | |
| 26 DEVICE_KEY, | |
| 27 // The key will be associated with the current user and will only be available | |
| 28 // when that user is signed-in. | |
| 29 USER_KEY | |
|
Mattias Nissler (ping if slow)
2013/04/24 12:57:53
ditto
dkrahn
2013/04/25 01:06:52
Done.
| |
| 30 }; | |
| 31 | |
| 32 // Options available for customizing an attestation challenge response. | |
| 33 enum AttestationChallengeOptions { | |
| 34 CHALLENGE_RESPONSE_OPTION_NONE = 0, | |
| 35 // Indicates that a SignedPublicKeyAndChallenge should be embedded in the | |
| 36 // challenge response. | |
| 37 INCLUDE_SIGNED_PUBLIC_KEY = 1 | |
|
Mattias Nissler (ping if slow)
2013/04/24 12:57:53
ditto.
dkrahn
2013/04/25 01:06:52
Done.
| |
| 38 }; | |
| 39 | |
| 40 // Available attestation certificate profiles. | |
| 41 enum AttestationCertificateProfile { | |
| 42 // Uses the following options: INCLUDE_STABLE_ID | INCLUDE_DEVICE_STATE. | |
| 43 ENTERPRISE_MACHINE_CERTIFICATE, | |
| 44 // Uses the following options: INCLUDE_DEVICE_STATE. | |
| 45 ENTERPRISE_USER_CERTIFICATE, | |
|
Mattias Nissler (ping if slow)
2013/04/24 12:57:53
ah, and here you have it :)
dkrahn
2013/04/25 01:06:52
there was a third value at one time :)
| |
| 46 }; | |
| 47 | |
| 48 // A key name for the Enterprise Machine Key. This key should always be stored | |
| 49 // as a DEVICE_KEY. | |
| 50 extern const char kEnterpriseMachineKey[]; | |
| 51 | |
| 52 // A key name for the Enterprise User Key. This key should always be stored as | |
| 53 // a USER_KEY. | |
| 54 extern const char kEnterpriseUserKey[]; | |
| 55 | |
| 56 } // namespace attestation | |
| 57 } // namespace chromeos | |
| 58 | |
| 59 #endif // CHROMEOS_ATTESTATION_ATTESTATION_CONSTANTS_H_ | |
| OLD | NEW |