{"version":"2.1.281","anchor":"managed-config-serve-to-desktop-and-optional-marketplace-sh","canonical_anchor":"managed-config-serve-to-desktop-and-optional-marketplace-sh","heading":"Managed config: serve_to_desktop and optional marketplace SHA","tier":"use","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/managed-config-serve-to-desktop-and-optional-marketplace-sh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Managed config: serve_to_desktop and optional marketplace SHA\n\nManaged config entries accept serve_to_desktop, and marketplace entries no longer need a SHA-256, falling back to available without one\n\n**Unclear.** The finding does not say what `desktopSessionPayload` does, or which product the version 1.32352.0 belongs to.\n\n**What**\n\nManaged config is configuration set centrally, usually by an organisation, rather than by each user. It changes in three ways:\n\n- `serve_to_desktop`: a new option on match entries. It produces a `desktopSessionPayload`.\n\n- Marketplace SHA-256: no longer required. A SHA-256 is a fingerprint used to confirm a download is the expected one. Without it, entries marked `auto_install` or `required` behave as `available`.\n\n- `url` source: now marked as available from version 1.32352.0.\n\n**Why**\n\nAdministrators can now list a marketplace without supplying its SHA-256. The trade-off is that such an entry is not installed automatically or enforced as required. Users are only offered it.\n\n- Area: Managed Settings\n- Names: `serve_to_desktop`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}