From ba95062a63bf51bbd48eb26c84f58b09bec9287d Mon Sep 17 00:00:00 2001 From: Tommy Date: Thu, 9 Jan 2025 23:44:03 -0700 Subject: [PATCH] Minor wording changes (#313) Signed-off-by: Tommy --- .../posts/knowledge/ChromeOS Questionable Encryption/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/posts/knowledge/ChromeOS Questionable Encryption/index.md b/content/posts/knowledge/ChromeOS Questionable Encryption/index.md index 05fa89f..c8ca6fd 100644 --- a/content/posts/knowledge/ChromeOS Questionable Encryption/index.md +++ b/content/posts/knowledge/ChromeOS Questionable Encryption/index.md @@ -11,7 +11,7 @@ ChromeOS encrypts user data on the disk by default. The implementation details a It is well-known that ChromeOS uses Google account passwords as the primary login credentials. This necessarily means that anyone with knowledge of the Google account password is able to unlock and therefore decrypt a ChromeOS user profile. -Recent versions of ChromeOS also allows users to use a separare login password instead of the Google account password. +Recent versions of ChromeOS allows users to use a separare login password instead of the Google account password. ![Local Password](local-password.png) @@ -27,7 +27,7 @@ As a result, someone with sufficient access to Google's servers would theoretica This differs from how encryption passwords are handled by other services like cloud‑based password managers — they use _client‑side hashing_ to deliberately blind the server from the actual password. As the name suggests, the browser locally executes a cryptographic hash function on the actual password and only transmits the _resultant hash_ to the server for authentication. -The user should be able to avoid this issue with the local password. While we have not done in-depth analysis to confirm that Google never has access to the local encryption password, this is likely the case since an account recovery using the Google password will require a Powerwash: +On newer ChromeOS versions, users should be able to avoid this issue with the local password. While we have not done in-depth analysis to confirm that Google never has access to the local encryption password, this is likely the case since an account recovery using the Google password will require a Powerwash: ![Account Recovery](account-recovery.png)