Yay. I just got hit on the nose by rsync sloprot. Somehow I had avoided it so far. The "don't worry, it's fixed in the next version. Just upgrade" response doesn't fill me with warm fuzzy feelings. I'm now pondering my options. I haven't found a clear obvious safe choice for a slop free fork yet, and switching to another implementation will involve a verification process, and possibly porting of tooling.
Can we please just keep our software working reliably?
#linux #unix
wfk
npub1cs…ln887
2026-10-05 11:38:46 UTC
Author Public Key
npub1cswlgjf6ry59vkqyfjfk8klt30uw7azxzcw3lg2z0rv4wzpusfqqhln887Seen on
wss://relay.momostr.pinkPublished at
2026-10-05 11:38:46 UTCEvent JSON
{
"id": "a8312a5254f9a8184cfa80a08882fca2fb483c4f5b56e647b5bd1abd82b3a9ea",
"pubkey": "c41df4493a19285658044c9363dbeb8bf8ef7446161d1fa14278d957083c8240",
"created_at": 1791200326,
"kind": 1,
"tags": [
[
"t",
"linux"
],
[
"t",
"unix"
],
[
"proxy",
"https://social.v.st/@wfk/117388104623086236",
"web"
],
[
"proxy",
"https://social.v.st/users/wfk/statuses/117388104623086236",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://social.v.st/users/wfk/statuses/117388104623086236",
"pink.momostr"
],
[
"-"
]
],
"content": "Yay. I just got hit on the nose by rsync sloprot. Somehow I had avoided it so far. The \"don't worry, it's fixed in the next version. Just upgrade\" response doesn't fill me with warm fuzzy feelings. I'm now pondering my options. I haven't found a clear obvious safe choice for a slop free fork yet, and switching to another implementation will involve a verification process, and possibly porting of tooling.\n\nCan we please just keep our software working reliably?\n\n#linux #unix",
"sig": "2cb02004d129ac2b8ea23764cc71b7eb1f98099505809fc7cf39734742e1a28a4895549231043e51bdd7adb8502fb924d854c3a1426333c544574c7348e7e68d"
}