Mastodon Feed
Boosted by pixxl:
wfk@v.st wrote:
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?