sneakerblack

Joined 5 years ago

Karma

133

Submissions

Member since

Jan 15

View on Hacker News

Recent submissions

Comment · 5 days ago

Do you want to be targeted? Then don't look Latino, black or foreign, work blue collar or service jobs or speak a language that is not English. There are plenty of examples of law abiding citizens getting illegally arrested or killed by ICE.

ICE is facing backlash because they are breaking the law and discriminating. Flock is facing backlash because they are enabling ICE and the general oppression of opposition to the current administration. Crimes should be investigated, but this falls outside of an immigration agency's responsibilities.

All this coming from a non-american by the way.

Comment · 5 days ago

Man, you Americans are really playing with fire

Comment · 3 months ago

Skill issue

Jokes aside, I agree on the sense that this should be a solved problem. On the other hand, if the only implementation is a broken one, there's only one way to help yourself, and that is learning how to do it and helping yourself

Comment · 3 months ago

Being in Kubecon this week and now this project, I'm a bit surprised at how heavily some people lean into Operators. I've always been hesitant to deploy operators into my clusters unless they provide a significant advantage compared to just using argocd just because of how heavily they can hit the k8s API. Not sure if anyone has run into the same issues?

Comment · 4 months ago

This all stinks of Lazarus:

https://en.wikipedia.org/wiki/Lazarus_Group

I've done incident responses for this exact type of attack multiple times. They've gotten much better organized lately and will often contact developers directly (over LinkedIn or WhatsApp) to run this type of attack. (Although, usually pretending to run a test for a job interview -- which is maybe why the author was confused about the code)

I think this was posted because the of the recent Npm malware fiasco. The malware monkey-patched native JS functions to replace strings that matched crypto addresses in certain the fetch, and XMLHttpRequest functions:

https://www.aikido.dev/blog/npm-debug-and-chalk-packages-com...

Considering there's no way to check whether a function is monkey-patched, this just tells me the JavaScript ecosystem was not designed with malicious actors in mind