Dev Feed

2025-03-08

GitHub | bertrandom/chrome-cookies-secure

On Sonoma 14.5 when I log out the response of the SQL Lite query for `encrypted_value` it is already a Buffer. From what I've read sqlite3 should automatically retrieve BLOB columns as a Buffer. It's not obvious why Apple Silicon would change this. https://gist.github.com/creachadair/937179894a24571ce9860e2475a2d2ec - column type https://www.npmjs.com/package/sqlite3 - full blob/buffer support _I wonder if anyone else on Apple Silicon can confirm this issue?_ Can you do a fresh install? rm package-lock, node_modules etc?

2025-03-08

GitHub | bertrandom/chrome-cookies-secure

I've pulled down your changes, ran on my machine, and the tests pass. Nice. I do have a slight concern of the overhead of asking the database to run the `hex()` function on every select. Interestingly on my machine removing the `hex()` db function, but retaining the `Buffer.from(cookie.encrypted_value, 'hex')` line still passes. Does that fail on yours? I'll fire up my Windows machine and see if I can confirm behaviour there too.

2025-03-08

GitHub | bertrandom/chrome-cookies-secure

I'm gonna guess it's the OS that's the major difference and perhaps it's encrypted differently on later macOS versions... I've just tested on my machine on Node 22.11.0 and all tests pass. I'll pull down your branch and see if it works on Sonoma 14.5.

2025-03-08

GitHub | bertrandom/chrome-cookies-secure

Covered in https://github.com/bertrandom/chrome-cookies-secure/issues/64

2025-03-08

GitHub | bertrandom/chrome-cookies-secure

[IskenHuang's fork](https://github.com/IskenHuang/chrome-cookies-secure) works just fine. He cleaned a lot of things up, but it boils down to just 2 line changes in index.js There's PRs but this maintainer has not taken notice. For a quick fix, in whatever npm project you need it, run: ```sh npm add https://github.com/IskenHuang/chrome-cookies-secure ``` Beit yarn, pnpm, npm, etc.

2025-03-08

GitHub | bertrandom/chrome-cookies-secure

The current tests do not complain of the issue you see though on 3.0.0, Node 18, reading Google cookies from the Chrome default location, so something is off. "On my machine" everything passes and I do not see the block length error. I'm going to fire things up now and try with Node 22, but there are only a few things that can be different... - Node version - Cookies being retrieved - macOS version? I'm testing on Sonoma 14.5 - Chromium vs Chrome vs Brave? - ?

2025-03-08

GitHub | bertrandom/chrome-cookies-secure

The tests do pass on Node 18 for Google cookies though. Can you provide more detail on method and arguments so we can add a new test case?

2025-03-08

GitHub | bertrandom/chrome-cookies-secure

I have a Windows machine I can test this on. Hopefully this weekend.

2025-03-08

GitHub | bertrandom/chrome-cookies-secure

That was my intention. I pulled down master of the fork and rolled it in 3.0.0 so it should all be there.

2025-03-04

GitHub | bertrandom/chrome-cookies-secure

Care to share the site, and in which format they're failing? I haven't tested on Node 22.