pull down to refresh

Well, he did say he was a “layman”, right? 😂 Considering he’s 80 years old, that’s still quite impressive. He may not be an AI expert, but he’s a highly respected investor.
I dug through the commit history because the release notes are vague. The main issue appears to be SSRF (Server-Side Request Forgery): several LNbits features accept user-controlled URLs, and the old destination checks could potentially let an attacker use the LNbits server as a proxy to reach the instance itself, its host/internal services, or cloud metadata endpoints. That could expose wallet keys, funding-source credentials, or other secrets and ultimately put funds at risk.
v1.7.0 centralizes outbound-request validation, blocks self/private/metadata targets, pins DNS results to prevent rebinding, revalidates redirects, hardens registration, and adds bulk wallet-key rotation. LNbits has not yet published the full exploit chain, so the exact entry point used in the incident is still unknown. Given their recovery guidance, operators should treat existing secrets as potentially compromised—upgrading alone is not enough; wallet keys, funding-source credentials, and other stored secrets should also be rotated.
Absolutely. We shouldn’t blindly trust authority. I found his questions quite thought-provoking, which is why I wanted to share this. Investing in AI is all the rage right now, but I’ve never had a clear sense of where the industry is headed, so I’ve stayed out of it. I like hearing perspectives from all sides and trying to form my own view.