On Sat, 11 Jul 2026, Thorsten Glaser wrote: >My apologies; turns out that that one special user >has a command= in its authoried_keys server-side >which points to a user-local copy of rsync with >extra capabilities so it can read the source tree.
Oh, aaaaaaaaaaaaaaaaah. I blame the heat, and that it’s been a while since I initially set up the sync between these systems and had not needed -c yet, and that I did it different for these than I used to do. Of COURSE adding -c also changes the command sent to the server. When having command="…" in authorized_keys, it does of course include the flags. (Used to use anoncvssh which allowed only cvs, svn, git, rsync, and checked for a few sets of flags instead of hardcoding the set to use.) OK, problem solved, it now syncs (or, rather, is still checksumming for the file list). I just wish the protocol made mismatches like that easier to debug, it didn’t even output the sender version in all those error messages… nothing you can do of course, even more so as upstream is now slop. Sorry for taking up the time, but I found *so few* info on the net for these error messages… maybe someone in the future will find this. bye, //mirabilos -- [16:04:33] bkix: "veni vidi violini" [16:04:45] bkix: "ich kam, sah und vergeigte"...
