My specific point here was about how this friend doesn’t trust the results AND still goes to Google/others to verify, so he’s effectively doubled his workload for every search.

I’ve had this argument with friends a lot recently.

Them: it’s so cool that I can just ask chatgpt to summarise something and I can get a concise answer rather than googling a lot for the same thing.

Me: But it gets things wrong all the time.

Them: Oh I know so I Google it anyway.

Doesn’t make sense to me.

I’ve been programming for too long, my brain just autocorrected the typo so initially didn’t get the joke…

Either works

Yes I was wrong to say that this an implementation detail rather than a protocol problem as the OpenSSH release notes to prevent this vulnerability include extensions to the SSH Transport Protocol, however I still believe that the headline is sensationalist at best since it can and has been protected against by patching ssh clients and servers. It would be entirely unreasonable in the majority of cases to simply stop using SSH on the basis of this vulnerability and that’s why I think the headline exaggerates the problem. The Register has a much more measured take on this including comments from the paper’s authors that people shouldn’t panic and try to fix immediately.

Bit of an alarmist headline here. The vulnerability has been patched in the most common clients (openssh) and it was because the protocol wasn’t being implemented correctly. To say that the SSH protocol “just got a lot weaker” is just not true.

I disagree with the $ per hour framing (it’s more about the value the entertainment provides than the amount of time it takes to consume) but yes you should pay for your entertainment. I got far too used to paying nothing or close to nothing as a student that it took me a while to readjust.