pull down to refresh

The last time nvk posted something in X it was to kinda maybe sorta apologize for writing software that lost people thousands of Bitcoin.

Today, he posted "This is not a drill" urging people to turn on autoupdates and do a bunch of somewhat normal "best practices" stuff.

I'm trying to figure out why I find this so irritating. Possibly it is because of nvk's past blowhard attitude or perhaps because he was unreasonably mean to many Bitcoin projects.

But if I'm honest, that stuff didn't bother me so much. What has pissed me off is this absolutely stupid attitude he's bad since a bunch of his users got absolutely wrecked.

I suppose it is true that he can't talk about anything for legal reasons, but if that is the case I expect absolute fucking silence. If he wants to weigh in on things, the only thing he should be saying is how he is going to try to fix things and how he understands that his company screwed up about as badly as possible.

Help me understand this. I don't like being angry.

Auto updates just expose you to other threats.

There's this js library I shall not name (because its just one example out of 100s). The solo maintainer doesn't like slop. Then someone filed an LLM generated security issue (in public, ugh) and a CVE (before it was fixed, ugh ugh ugh) and a ton of bots started proposing patches.

Except the details of both the issue and the CVE are wrong. So he (correctly) challenged the report, did some unrelated work, but also didn't fix the root cause of the issue. Bumped version with a release. Now everyone that trusts the CVE industry will:

  1. Install the update (which in this case isn't, but could be, introducing new but worse bugs)
  2. Think that they did something great - crisis avoided. Every tool from snyk to deno to npm will tell you that there is no issue.

The problem is that this package has a couple 100 million installs. Yet the only thing that happened is that an unrelated version bump hid the actual vuln, which still exists, but isn't visible to anyone except those that:

  1. patched their own software
  2. Track all this in their own CVE/VEX repos with a changed applicable version so that they don't fuck up in the future (every scanner will say the vuln is fixed)
  3. Deny the one thing the entire CVE industry is built upon: trust

Luckily the known impact of the vuln is not high, but that doesn't mean much anymore these days - a small vuln can make a long exploit chain viable. And this has been discussed fully in public. There are thousands upon thousands of security reports where it is omitted, I see it happening every day. All you need to do to no longer be aware of the issue is what the tool tells you to do: autoupdate.

reply

Yes. This is some of what really ticked me off. I think in the past nvk has even extolled how wise it is that bitcoin core does not even have an option for auto updates, and now here he is giving mindless hype advice to people.

reply
1042 sats \ 0 replies \ @optimism 25 Oct

I'm personally grappling with what to tell (normie) people, except that things like being conservative in what you install, and running firewalls and using things like app sandboxing can make a real difference now. Is auto-update useful when we know that most of the stuff that gets updates is vibe coded now and the amount of published bugs alone has done almost a 3x? I see the opposite in the field (and I literally live in this field at the moment.)

I haven't seen anyone speaking with an air of authority yet convincing me that the dangers from autoupdate have lessened - in fact I have seen quite the opposite happening, and the bleeding release edge is dangerous - to a point where people are putting several day delays on updates, which again is fucking awful if we're talking security updates because the aggressor won't wait several days with completely fucking you up - as we've also seen reports here on SN, with real loss.

Personally, my solution is to:

  1. Run as little 3rd party software as possible and outside of the single Macbook I didn't flash with Linux, no closed source anywhere. I work on my other hardware and this is also why I'm only on SN twice a day or so now. Which sucks tbh, not recommended.
  2. For every CVE to anything I run (hourly scans on every sbom of every system, including OS) do an impact assessment straight away with highest priority.
  3. If anything has real impact, fix it right away
  4. Scan every software update for defects that didn't get announced - but honestly I cannot cover the entire thing. My smallest linux server alone, with basically just docker and minimal tools, has 2500+ software components.
reply
302 sats \ 0 replies \ @OT 25 Oct

I won't read that but I'll take a guess that he's playing helpful as a previous victim of AI hacking.

He really needs to disappear and Coinkite needs to either be bought out or go bankrupt.

reply
302 sats \ 1 reply \ @anon 25 Oct

The guy is an asshat.
I used to think he was a smart asshat.

reply

This

reply

Slop.

reply

very irritating.

It's the inconsistency... arrogance backed up by competence is acceptable. Arrogance backed up by pride followed by an extreme fall? Well, that's a different story!

reply

I used to listen to his podcasts back in around 2023, but it reached the point where I found his ego and imperiousness tough to take. I don't think he's capable of just going away. He enjoys attention too much. It started with his demise, but I just can't can't listen to any of these supposedly brilliant devs and influencers any more who feel the need to prattle on and on, puffing themselves up while hawking products.

reply

It’s disappointing but not surprised. Maybe he’s a narcissist and has no humility.

If he can’t speak on it he should come out and say so. And have some compassion. Get on the podcast circuit he loved to do own it and tell his side of the story. But I doubt that will ever happen.

reply

He's trying to rehabilitate his image now that a class action lawsuit has been filed in Canada

reply

Isn’t NVK supposed to be addressing the funds people lost due to the COLDCARD incident first? Security advice is important, but shouldn’t accountability to affected users come before moving on to the next crisis? People deserve answers.

reply
reply

surprised hed continue to have a public persona. But then again, maybe not surprised...

reply