News for hackers. Stuff that matters.
Re:Using Rust Macros to exfiltrate secrets by judofyr on Friday May 14, 2021 @12:20PM (#27155985)
> But in the end it doesn't make that much difference: nothing prevents a random library from just reading your secrets and calling curl to send it to a server at runtime.

The difference here is that it happens when you open the project in the editor. If I'm suspicious of some code my first reaction would be to open it my editor and inspect it.

The ESLint extension always asks whether you trust the `eslint` executable before it's enabled. It's still quite easy to click "allow" without thinking about it, but at least you'll have a choice to not execute potentially random code.

Re:Using Rust Macros to exfiltrate secrets by IshKebab on Friday May 14, 2021 @02:31PM (#27157971)
That's a really recent feature and I'm sure Rust-analyzer will support it soon.

I suspect the same problem exists in many other languages. How can you open a CMake project without executing it?

Re:Using Rust Macros to exfiltrate secrets by banachtarski on Saturday May 15, 2021 @12:50AM (#27162471)
In a text editor....
Re:Using Rust Macros to exfiltrate secrets by rhencke on Saturday May 15, 2021 @12:58AM (#27162522)
If they'd wanted you to do that, they would have named the files something like "CMakeLists.txt".
Re:Using Rust Macros to exfiltrate secrets by IshKebab on Saturday May 15, 2021 @04:41PM (#27168808)
You can do that with Rust too if you want to live like it's still the 70s.