{"version":"2.1.284","anchor":"directory-sync-attach-now-needs-a-device-signing-key","canonical_anchor":"directory-sync-attach-now-needs-a-device-signing-key","heading":"Cloud folder sync stops when this machine has no signing key","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/directory-sync-attach-now-needs-a-device-signing-key","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Cloud folder sync stops when this machine has no signing key\n\nAttaching a git- or folder-backed synced session now needs a signing key for this device, and sync stops if there is none\n\n**Unclear.** Which users or sessions this sync feature is available to is not settled.\n\n**What**\n\nSome cloud sessions sync a local git repository or folder with the cloud. Attaching one of these sessions now looks for a signing key belonging to the device the session is bound to. If this machine has no such key, sync stops instead of going ahead. The sync connection only accepts signed updates.\n\nOpening git directory sync refuses in the same way when no key is available.\n\n**Why**\n\nIn practice, a machine without a device key can no longer sync unsigned changes. It stops instead.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 2\/5"}