Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google is planning to change their way of encrypting/decrypting sensitive data for chrome and chromium based browsers. #655

Open
Onyz107 opened this issue Oct 26, 2024 · 0 comments

Comments

@Onyz107
Copy link

Onyz107 commented Oct 26, 2024

In Chrome 127 they introduced a new protection on Windows that improves on the DPAPI by providing Application-Bound (App-Bound) Encryption primitives. Rather than allowing any app running as the logged in user to access this data, Chrome can now encrypt data tied to app identity, similar to how the Keychain operates on macOS.

image

they will be migrating each type of secret to this new system starting with cookies in Chrome 127. In future releases they intend to expand this protection to passwords, payment data, and other persistent authentication tokens, further protecting users from infostealer malware.

And as they stated they did migrate this feature into cookies, I just tried using a basic script to decode the cookies on various windows platforms with the most up-to-date browser and the script failed decrypting the cookies on all of the platforms.

what solution do you think of doing when this change is migrated into browser stored passwords?

Source

@Onyz107 Onyz107 changed the title Google is planning to change their way of encrypting/decrypting cookies for chrome and chromium based browsers. Google is planning to change their way of encrypting/decrypting sensitive data for chrome and chromium based browsers. Oct 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant