Hej, We are preparing the initial release of the Ecosia Browser snap and have a release candidate ready. The automated review has flagged two interface connections that require manual approval
name: Ecosia
description: The Ecosia Browser is a Chromium-based, privacy-focused browser designed to combat climate change, with 100% of profits funding tree-planting and renewable energy projects.
snapcraft: PRIVATE
upstream: PRIVATE
upstream-relation: contributor
interfaces:
browser-support
request-type: auto-connection
reasoning: Ecosia Browser is a Chromium-based browser that requires the browser-support interface with allow-sandbox: true to enable Chromium’s built-in process sandbox. This sandbox is a critical security feature that isolates renderer processes from the host system — disabling it would represent a significant security regression for our users. This is consistent with other Chromium-based snaps, including the official Chromium snap maintained by Canonical:
This is also a +1 (#voteFor) from me for granting auto-connect for the camera interface and the browser-support interface with allow-sandbox:true, Ecosia is a well-known browser, so this functionality is expected.
Due to the sensitive nature of this browser-support auto-connection, we require closed-source snap publishers to go through a vetting process to verify their accounts as described in this post. Once the vetting process is completed, we can proceed with granting this request. Thank you!