Xiaomi Redmi Note 8 64Gb+6Gb Dual LTE [124/132] Secure lock screen
![Xiaomi Redmi Note 8 64Gb+6Gb Dual LTE [124/132] Secure lock screen](/views2/2011691/page124/bg7c.png)
The Android Keystore System allows app developers to store cryptographic keys in a container and
use them in cryptographic operations through the KeyChain API or the Keystore API . Device
implementations:
[C-0-1] MUST allow at least 8,192 keys to be imported or generated.
[C-0-2] The lock screen authentication MUST rate-limit attempts and MUST have an
exponential backoff algorithm. Beyond 150 failed attempts, the delay MUST be at least 24
hours per attempt.
SHOULD not limit the number of keys that can be generated
When the device implementation supports a secure lock screen, it:
[C-1-1] MUST back up the keystore implementation with an isolated execution
environment.
[C-1-2] MUST have implementations of RSA, AES, ECDSA and HMAC cryptographic
algorithms and MD5, SHA1, and SHA-2 family hash functions to properly support the
Android Keystore system's supported algorithms in an area that is securely isolated from
the code running on the kernel and above. Secure isolation MUST block all potential
mechanisms by which kernel or userspace code might access the internal state of the
isolated environment, including DMA. The upstream Android Open Source Project (AOSP)
meets this requirement by using the Trusty implementation, but another ARM TrustZone-
based solution or a third-party reviewed secure implementation of a proper hypervisor-
based isolation are alternative options.
[C-1-3] MUST perform the lock screen authentication in the isolated execution
environment and only when successful, allow the authentication-bound keys to be used.
Lock screen credentials MUST be stored in a way that allows only the isolated execution
environment to perform lock screen authentication. The upstream Android Open Source
Project provides the Gatekeeper Hardware Abstraction Layer (HAL) and Trusty, which can
be used to satisfy this requirement.
[C-1-4] MUST support key attestation where the attestation signing key is protected by
secure hardware and signing is performed in secure hardware. The attestation signing
keys MUST be shared across large enough number of devices to prevent the keys from
being used as device identifiers. One way of meeting this requirement is to share the
same attestation key unless at least 100,000 units of a given SKU are produced. If more
than 100,000 units of an SKU are produced, a different key MAY be used for each 100,000
units.
[C-1-5] MUST allow the user to choose the Sleep timeout for transition from the unlocked
to the locked state, with a minimum allowable timeout up to 15 seconds.
Note that if a device implementation is already launched on an earlier Android version, such a device
is exempted from the requirement to have a keystore backed by an isolated execution environment
and support the key attestation, unless it declares the android.hardware.fingerprint feature which requires
a keystore backed by an isolated execution environment.
9.11.1. Secure Lock Screen
The AOSP implementation follows a tiered authentication model where a knowledge-factory based
primary authentication can be backed by either a secondary strong biometric, or by weaker tertiary
modalities.
Device implementations:
[C-SR] Are STRONGLY RECOMMENDED to set only one of the following as the primary
authentication method:
A numerical PIN
Page 124 of 132
Содержание
- Compatibility definition p.1
- Android 9 p.1
- Runtime compatibility p.2
- Native api compatibility p.2
- Managed api compatibility p.2
- Introduction p.2
- Handheld requirements p.2
- Document structure p.2
- Device types p.2
- Device configurations p.2
- Background restriction p.2
- Web compatibility p.2
- Automotive requirements p.2
- Watch requirements p.2
- Api namespaces p.2
- User interface compatibility p.2
- Api behavioral compatibility p.2
- Television requirements p.2
- Android library p.2
- Tablet requirements p.2
- Android extensions p.2
- Software p.2
- Soft api compatibility p.2
- Text to speech p.3
- Developer tools p.3
- Secure media p.3
- Developer options p.3
- Quick settings p.3
- Companion device pairing p.3
- Professional audio p.3
- Capture for unprocessed p.3
- Network protocols p.3
- Audio recording p.3
- Musical instrument digital interface midi p.3
- Audio playback p.3
- Multimedia compatibility p.3
- Audio latency p.3
- Media ui p.3
- Application packaging compatibility p.3
- Media codecs p.3
- Accessibility p.3
- Managed user support p.3
- Instant apps p.3
- Heavyweight apps p.3
- Hardware compatibility p.3
- Video encoding p.3
- Display and graphics p.3
- Video decoding p.3
- Device administration p.3
- Tv input framework p.3
- Developer tools and options compatibility p.3
- Sensors p.4
- Pose sensor p.4
- Memory and storage p.4
- Input devices p.4
- Data connectivity p.4
- Cameras p.4
- Updatable software p.5
- Software compatibility testing p.5
- Security model compatibility p.5
- Performance and power p.5
- Document changelog p.5
- Contact us p.5
- Document structure p.6
- Requirements by device type p.6
- Requirement id p.6
- Introduction p.6
- Requirement id in section 2 p.7
- Hardware p.7
- Handheld requirements p.7
- Device types p.7
- Device configurations p.7
- Multimedia p.10
- Software p.11
- Performance and power p.12
- Television requirements p.13
- Security model p.13
- Hardware p.14
- Multimedia p.15
- Software p.16
- Performance and power p.17
- Watch requirements p.18
- Software p.18
- Multimedia p.18
- Hardware p.18
- Performance and power p.19
- Hardware p.19
- Automotive requirements p.19
- Software p.22
- Multimedia p.22
- Performance and power p.23
- Tablet requirements p.24
- Software p.24
- Security model p.24
- Hardware p.24
- Android extensions p.25
- Managed api compatibility p.25
- Android library p.25
- Soft api compatibility p.26
- Permissions p.26
- Build parameters p.26
- Intent compatibility p.29
- Activities on secondary displays p.31
- Application binary interfaces p.32
- Native api compatibility p.32
- Bit arm native code compatibility p.33
- Webview compatibility p.34
- Web compatibility p.34
- Browser compatibility p.34
- Api behavioral compatibility p.35
- Background restriction p.36
- Api namespaces p.36
- Runtime compatibility p.37
- User interface compatibility p.39
- Launcher home screen p.39
- Widgets p.40
- Notifications p.40
- Search p.42
- Alerts and toasts p.42
- Themes p.43
- Live wallpapers p.43
- Lock screen media control p.44
- Input management p.44
- Activity switching p.44
- Unicode and font p.45
- Screen savers previously dreams p.45
- Multi windows p.45
- Location p.45
- Display cutout p.46
- Device administration p.46
- Device provisioning p.47
- Managed profile support p.48
- Text to speech p.49
- Managed user support p.49
- Accessibility p.49
- Tv input framework p.50
- Quick settings p.50
- Media ui p.50
- Instant apps p.50
- Heavyweight apps p.51
- Companion device pairing p.51
- Application packaging compatibility p.51
- Multimedia compatibility p.52
- Audio decoding p.53
- Media codecs p.53
- Audio encoding p.53
- Audio codecs details p.54
- Image encoding p.55
- Image decoding p.55
- Video codecs list p.56
- Video codecs p.56
- Image codecs details p.56
- Video encoding p.57
- Video decoding p.59
- Mpeg 4 p.59
- Mpeg 2 p.59
- H 65 hevc p.60
- Raw audio capture p.61
- Audio recording p.61
- Capture for rerouting of playback p.62
- Capture for voice recognition p.62
- Raw audio playback p.63
- Audio playback p.63
- Audio output volume p.63
- Audio latency p.63
- Audio effects p.63
- Network protocols p.65
- Secure media p.66
- Professional audio p.66
- Musical instrument digital interface midi p.66
- Capture for unprocessed p.68
- Developer tools and options compatibility p.69
- Developer tools p.69
- Hardware compatibility p.71
- Display and graphics p.71
- Developer options p.71
- Screen configuration p.72
- Screen orientation p.74
- Display metrics p.74
- D and 3d graphics acceleration p.74
- Secondary displays p.77
- Screen technology p.77
- Legacy application compatibility mode p.77
- Non touch navigation p.78
- Navigation keys p.78
- Keyboard p.78
- Input devices p.78
- Touchscreen input p.79
- Fake touch input p.80
- Game controller support p.81
- Sensors p.82
- Remote control p.82
- Accelerometer p.83
- Magnetometer p.84
- Gyroscope p.86
- Thermometer p.87
- Photometer p.87
- Barometer p.87
- Proximity sensor p.88
- High fidelity sensors p.88
- Biometric sensors p.90
- Android automotive only sensors p.92
- Telephony p.93
- Pose sensor p.93
- Data connectivity p.93
- Ieee 802 1 wi fi p.94
- Bluetooth p.97
- Near field communications p.98
- Minimum network capability p.100
- Sync settings p.101
- Secure elements p.101
- Rear facing camera p.101
- Data saver p.101
- Cameras p.101
- Front facing camera p.102
- External camera p.103
- Camera api behavior p.103
- Memory and storage p.104
- Camera orientation p.104
- Minimum memory and storage p.105
- Application shared storage p.105
- Usb peripheral mode p.106
- Adoptable storage p.106
- Usb host mode p.107
- Microphone p.108
- Audio output p.108
- Near ultrasound p.109
- Virtual reality mode high performance p.110
- Virtual reality mode p.110
- Virtual reality p.110
- User experience consistency p.112
- Power saving modes p.112
- Performance and power p.112
- File i o access performance p.112
- Power consumption accounting p.113
- Consistent performance p.113
- Security model compatibility p.114
- Permissions p.114
- Uid and process isolation p.115
- Filesystem permissions p.115
- Multi user support p.116
- Alternate execution environments p.116
- Security features p.117
- Premium sms warning p.117
- Usage history p.119
- Recording p.119
- Privacy p.119
- Network traffic p.120
- Data storage encryption p.120
- Connectivity p.120
- File based encryption p.121
- Direct boot p.121
- Full disk encryption p.122
- Device integrity p.122
- Keys and credentials p.123
- Secure lock screen p.124
- Strongbox p.127
- Safe boot mode p.128
- Data deletion p.128
- Subscription plans p.129
- Software compatibility testing p.129
- Compatibility test suite p.129
- Automotive vehicle system isolation p.129
- Updatable software p.130
- Cts verifier p.130
- Document changelog p.131
- Changelog viewing tips p.131
- Contact us p.132
Похожие устройства
-
Xiaomi Mi5c 64Gb+3Gb Dual LTEРуководство по эксплуатации -
Xiaomi Xiaomimi 7A 32GBРуководство по эксплуатации -
Xiaomi mi 6A 2GB+16GBРуководство по эксплуатации -
Xiaomi Mimi Go 8GBРуководство по эксплуатации -
Xiaomi Xiaomimi 5 16GBРуководство по эксплуатации -
Xiaomi Xiaomimi Note 8 Pro 6+128GBРуководство по эксплуатации -
Xiaomi Mi Note 64GbИнструкция по эксплуатации -
Xiaomi Xiaomimi Note 6 Pro 32GbРуководство по эксплуатации -
Xiaomi Redmi Note 8 128Gb+6Gb Dual LTEРуководство по эксплуатации -
Xiaomi Mi 3SРуководство пользователя -
Xiaomi Mi 3 ProРуководство пользователя -
Xiaomi Mi4 64GbРуководство по эксплуатации