From 5c17b00a3d6ab7da56abc423db36def90a85301b Mon Sep 17 00:00:00 2001 From: Tommy Date: Wed, 24 Apr 2024 15:39:31 -0700 Subject: [PATCH] Update ChromeOS Questionable Encryption.md Signed-off-by: Tommy --- content/posts/linux/ChromeOS Questionable Encryption.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/posts/linux/ChromeOS Questionable Encryption.md b/content/posts/linux/ChromeOS Questionable Encryption.md index b275717..1e2a8f3 100644 --- a/content/posts/linux/ChromeOS Questionable Encryption.md +++ b/content/posts/linux/ChromeOS Questionable Encryption.md @@ -9,7 +9,7 @@ author: Tommy ChromeOS encrypts user data on the disk by default. The encryption key is protected using a number of factors, which is documented in the [ChromeOS Documentation](https://www.chromium.org/developers/design-documents/tpm-usage/#TOC-Protecting-User-Data-Encryption-Keys). -Essentially, the user's Google account password, when typed into a the Chromebook (with the security chip intact - be it the TPM, Titan C, or some other chips), will give the encryption key to unlock their files. As such, for confidentiality, it is important that the user's Google account password is never exposed to an attacker. If the threat model requires protection against Google or an attacker who has compromised their servers, the password should be hashed client side before being sent to Google's server. +The user's Google account password, when typed into a the Chromebook (with the security chip intact - be it the TPM, Titan C, or some other chips), will give the encryption key to unlock their files. As such, for confidentiality, it is important that the user's Google account password is never exposed to an attacker. If the threat model requires protection against Google or an attacker who has compromised their servers, the password should be hashed client side before being sent to Google's server. ## What Happens in Practice @@ -21,6 +21,6 @@ As you can see in the screenshot, the login password "mygloriouspassword" is sub ## What This Means -Essentially, this means that if Google is malicious, coerced by the government, or hacked, their servers can record the user password prior to it being hashed. That password can then be used to gain access to the files on the hardware when the attacker gains physical access. +This means that if Google is malicious, coerced by the government, or hacked, their servers can record the user password prior to it being hashed. That password can then be used to gain access to the files on the hardware when the attacker gains physical access. -Just to be clear here, this is not a vulnerability, it's just how the system is designed. \ No newline at end of file +Just to be clear here, this is not a vulnerability, it's just how the system is designed.