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

Since google last update to Version 130.0.6723.59 (Official Build) (64-bit), this lib doesn't work. #63

Open
paskaran opened this issue Oct 21, 2024 · 6 comments

Comments

@paskaran
Copy link

Hi, since the last Chrome update, I've been facing an issue where I'm unable to retrieve cookies. It seems that the encryption/decryption process has changed, causing the library to return an empty string instead of the cookies.

Is this project still alive, does someone knows an alternative to this if no updates or fixes are to be expected?

Thanks.

@gudh
Copy link

gudh commented Oct 22, 2024

+1

@zhoukekestar
Copy link

@sagiwei
Copy link

sagiwei commented Oct 24, 2024

+1

@sagiwei
Copy link

sagiwei commented Nov 11, 2024

https://github.com/bertrandom/chrome-cookies-secure/blob/master/index.js#L46

// change slice indexStart from 0 to 32
decoded = decoded.slice(32, decoded.length - padding);

This change above work for me, all we need is change the indexStart from 0 to 32.

@TravisL12
Copy link

https://github.com/bertrandom/chrome-cookies-secure/blob/master/index.js#L46

// change slice indexStart from 0 to 32
decoded = decoded.slice(32, decoded.length - padding);

This change above work for me, all we need is change the indexStart from 0 to 32.

Bravo! This worked for me too.

@xiaospace1028
Copy link

https://github.com/bertrandom/chrome-cookies-secure/blob/master/index.js#L46

// change slice indexStart from 0 to 32
decoded = decoded.slice(32, decoded.length - padding);

This change above work for me, all we need is change the indexStart from 0 to 32.

This worked for me too.
But first, I upgraded my Node.js version, and now I'm on Node 18. I saw in other forums that it's due to a crypto version issue.

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

6 participants