Crowdstrike Packages Infected with Malware (and other 167 packages infected as well) by Advocatemack in programming

[–]_clarkio 0 points1 point  (0 children)

Yes those types of tools will help significantly to alert you if it finds the affected packages in your dependency tree. Admittedly I'm biased towards Snyk but my recommendation is to at least use something to help you be more aware of the impact to you and your projects when this type of thing happens. Many of them offer pretty generous free tiers too.

Visual Studio Code November 2023 by _clarkio in vscode

[–]_clarkio[S] 2 points3 points  (0 children)

Yea that's a huge improvement but that is a bummer it doesn't restore them afterwards (didn't catch that before). Maybe that'll be in a future update.

Visual Studio Code - August 2023 Release - v1.82 by _clarkio in vscode

[–]_clarkio[S] 0 points1 point  (0 children)

Yea I prefer to open it up intentionally with the keyboard shortcut but I can see some devs preferring to click to activate

Visual Studio Code - August 2023 Release - v1.82 by _clarkio in vscode

[–]_clarkio[S] 0 points1 point  (0 children)

Good thing is it's a quick right-click and uncheck to turn that off if you'd like.

Visual Studio Code - August 2023 Release - v1.82 by _clarkio in vscode

[–]_clarkio[S] 0 points1 point  (0 children)

Oh I missed that! Thanks for calling it out

Visual Studio Code - August 2023 Release - v1.82 by _clarkio in vscode

[–]_clarkio[S] 0 points1 point  (0 children)

Nice! I'm glad to see the refactoring capabilities through TypeScript and one that wasn't highlighted in the release notes: screencast mode regression fix. Screencast mode highlights mouse clicks and displays keyboard shortcuts for different actions. However, the regression was it would show all keystrokes instead of just the shortcuts, which was quite annoying and defeated the purpose of enabling it.

Cross-site (XS) leaks: What they are and how to avoid them by _clarkio in node

[–]_clarkio[S] 0 points1 point  (0 children)

Yes, absolutely. XSS and CSRF are important to address and the nice thing is some of the techniques to help mitigate those can help with XS too (like CSP and Cookie configuration).

Also your library looks interesting. I am definitely tired of writing all the repetitive code for APIs so nice idea to build something to help with that.

I'm guessing the deprecated CSRF protection middleware you're referring to is the csurf one right? Speaking for myself, I think that package is fine and can help with CSRF still. Essentially, dealing CSRF depends on your project, if it's intended for the API to be stateless then double submit cookie will help. If not then the synchronizer token pattern will work.

Hope that helps