From 6abcf66ae58ed8a519bbc92a71432af25008ca83 Mon Sep 17 00:00:00 2001
From: Jo <10510431+j178@users.noreply.github.com>
Date: Sun, 29 Dec 2024 02:29:08 +0800
Subject: [PATCH] Add note about windows app-bound encryption

---
 README.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/README.md b/README.md
index b87185b1..d0ad45c1 100644
--- a/README.md
+++ b/README.md
@@ -300,6 +300,10 @@ There are three ways to make cookies available to `leetgo`:
       from: browser
   ```
 
+  > [!IMPORTANT]  
+  On Windows, Chrome/Edge v127 enabled [App-Bound Encryption](https://security.googleblog.com/2024/07/improving-security-of-chrome-cookies-on.html) and `leetgo` can no longer decrypt cookies from Chrome/Edge.
+  You would need to provide cookies manually or use other browsers.
+
 - Provide cookies.
 
   You can get your cookies named `LEETCODE_SESSION` and `csrftoken` from browser's developer tools, and set the `LEETCODE_SESSION` and `LEETCODE_CSRFTOKEN` environment variables.  If you are using `leetcode.com`, `LEETCODE_CFCLEARANCE` should also be set to the value of the `cf_clearance` cookie.