{"version":"2.1.248","anchor":"synced-files-are-hash-checked-before-being-accepted","canonical_anchor":"synced-files-are-hash-checked-before-being-accepted","heading":"Synced files are hash-checked before being accepted","tier":"notice","area":"Directory Sync","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/synced-files-are-hash-checked-before-being-accepted","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Synced files are hash-checked before being accepted\n\nSynced files are now hash- and size-checked before being accepted.\n\n**What**\n\nDirectory 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.\n\n**Evidence**\n\n`dir-sync: refused a container object named by a carrier this side cannot read`\n\n- Area: Directory Sync\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}