Skip to content

Commit

Permalink
Add note about windows app-bound encryption
Browse files Browse the repository at this point in the history
  • Loading branch information
j178 committed Dec 28, 2024
1 parent 22596de commit 6abcf66
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down

0 comments on commit 6abcf66

Please sign in to comment.