npub1jc…n2890 on Nostr: Core Lightning told every node operator to shut down or restart with an offline flag, ...
Core Lightning told every node operator to shut down or restart with an offline flag, and left it there.
Two days later a fix arrived as signed binaries only. No source. That comes in a fortnight.
The reasoning is that publishing the diff hands attackers a map to unpatched nodes. Fair enough. But you can reverse engineer a closed binary too, so you slow the clock down without stopping anyone.
What you do get is an open source project asking you to trust a binary. That precedent outlasts this bug.
{
"id":"6ac7904fec053338d8c27f586c86d876ba99c7ec479088bdb9b81b69d9b9332c",
"pubkey":"9609b093450dd7e0afb389619acdaf2e6a0d6817c93552f3911e05b50ae73e3d",
"created_at":1788447600,
"kind":1,
"tags": [],
"content":"Core Lightning told every node operator to shut down or restart with an offline flag, and left it there.\n\nTwo days later a fix arrived as signed binaries only. No source. That comes in a fortnight.\n\nThe reasoning is that publishing the diff hands attackers a map to unpatched nodes. Fair enough. But you can reverse engineer a closed binary too, so you slow the clock down without stopping anyone.\n\nWhat you do get is an open source project asking you to trust a binary. That precedent outlasts this bug.\n\nhttps://ungovernable.network/shows/bitcoin-brief/the-ai-pocalypse-continues/\n\nhttps://video.nostr.build/0562ff3eb730968d45303844a0e60142fb45fa966a43da0ed6214c49fd228869.mp4",
"sig":"1cbf4b04ca5465431e67cc07b630d9d49be8123feddaef10c57749541bebb71e2aeac0cc7558a4cac377e783a6497566f685760735926c92c523dfacb9dc1a6a"
}