Skip to content

Commit 6abcf66

Browse files
committed
Add note about windows app-bound encryption
1 parent 22596de commit 6abcf66

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

README.md

+4
Original file line numberDiff line numberDiff line change
@@ -300,6 +300,10 @@ There are three ways to make cookies available to `leetgo`:
300300
from: browser
301301
```
302302

303+
> [!IMPORTANT]
304+
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.
305+
You would need to provide cookies manually or use other browsers.
306+
303307
- Provide cookies.
304308

305309
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.

0 commit comments

Comments
 (0)