{"version":"2.1.284","anchor":"cloud-folder-sync-now-requires-a-device-signing-key-all-lan","canonical_anchor":"cloud-folder-sync-now-requires-a-device-signing-key-all-lan","heading":"Cloud folder sync now needs a device signing key and signs every request","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/cloud-folder-sync-now-requires-a-device-signing-key-all-lan","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Cloud folder sync now needs a device signing key and signs every request\n\nCloud folder sync refuses to start without a device signing key, and any request it cannot sign is stopped rather than sent unsigned\n\n**Unclear.** The settings or switches that make cloud folder sync available in the first place are not described.\n\n**What**\n\nFolder sync copies files between your machine and a cloud session. It now needs a device key, a key stored on your machine that is used to sign requests and prove where they came from. Without one, folder sync stops at startup and reports that the device key is unavailable.\n\nWhat gets signed has changed too:\n\n- Every request folder sync makes must now be signed. If signing fails, the request is abandoned instead of being sent without a signature.\n\n- The requests that start and finish an upload are now signed, as well as the request that sends each file.\n\nBefore, only the file uploads were signed, and a failed signature fell back to sending the upload unsigned.\n\n**Why**\n\nThis tightens security on the sync path. Machines that have no device key can no longer use cloud folder sync.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}