mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-19 12:23:37 +00:00
Update hello-faq.yml
hello-faq.yml https://microsoft-ce-csi.acrolinx.cloud/api/v1/checking/scorecards/1d1a9154-130b-4baf-b1a4-f2d6fb33a323#CORRECTNESS Line 160: a SHA256 hash > an SHA256 hash
This commit is contained in:
committed by
GitHub
parent
cd3e995b5d
commit
3457ee1bbb
@ -157,7 +157,7 @@ sections:
|
|||||||
|
|
||||||
- question: What is the format used to store Windows Hello biometrics data on the device?
|
- question: What is the format used to store Windows Hello biometrics data on the device?
|
||||||
answer: |
|
answer: |
|
||||||
Windows Hello biometrics data is stored on the device as an encrypted template database. The data from the biometrics sensor (e.g., face camera or fingerprint reader) creates a data representation—or graph—that is then encrypted before it’s stored on the device. Each biometrics sensor on the device which is used by Windows Hello (face or fingerprint) will have its own biometric database file where template data is stored. Each biometrics database file is encrypted with unique, randomly generated key that is encrypted to the system using AES encryption producing a SHA256 hash.
|
Windows Hello biometrics data is stored on the device as an encrypted template database. The data from the biometrics sensor (e.g., face camera or fingerprint reader) creates a data representation—or graph—that is then encrypted before it’s stored on the device. Each biometrics sensor on the device which is used by Windows Hello (face or fingerprint) will have its own biometric database file where template data is stored. Each biometrics database file is encrypted with unique, randomly generated key that is encrypted to the system using AES encryption producing an SHA256 hash.
|
||||||
|
|
||||||
- question: Who has access on Windows Hello biometrics data?
|
- question: Who has access on Windows Hello biometrics data?
|
||||||
answer: |
|
answer: |
|
||||||
|
Reference in New Issue
Block a user