Synced files are now hash- and size-checked before being accepted.
What's wrong with this entry?
Directory sync now verifies that fetched content matches the declared sha256 and length, and checks the declared hash shape and size bounds first. Content described in a transport format this side cannot read is refused and logged rather than attempted.
dir-sync: refused a container object named by a carrier this side cannot read
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.238
Sync state machine gains a moved-root case and a per-turn pull hook
Both mention directory
-
v2.1.238
Untracked-file survey extracted and shared
Both mention directory
-
v2.1.238
Sync internals reshaped around per-file credential state
Both mention directory