Autoconnect request for Ecosia

store-requests privileged-interfaces
1

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:

        https://code.launchpad.net/~chromium-team/chromium-browser/+git/snap-from-source

    • camera
      • request-type: auto-connection
      • reasoning: Ecosia is a browser, so camera auto-connection is requred for basic scenarios as video calling or video conferencing.

Thank you :folded_hands:

1 Like
Request for human-review for ecosia snap release candidate
Request for Ecosia to be a Verified Publisher
2

This request has been added to the queue for review by the @reviewers team.

1 Like
3

Hello @ecosia!

Given the snap functionality, both requests make sense to me, so +1 (#voteFor) from my side :slight_smile:

1 Like
4

Hello @ecosia!

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! :grinning_face_with_smiling_eyes:

1 Like
5

Voting period has ended. This request is approved with 2 votes for and 0 votes against.

1 Like
6

Hi @elisehdy

Thank you for the previous upvote :green_heart: We followed your guidance and applied to become a verified publisher. The vetting process was successful as you can see in this post (Request for Ecosia to be a Verified Publisher - #3 by ecosia)

Would you therefore be so kind as to continue to the process of approving our initial submission here (OpenID transaction in progress) ? Thank you :folded_hands:

1 Like
7

The request was approved. This is now live!

2 Likes
8

Hi @jslarraz, @elisehdy,

Follow-up on the Ecosia Browser snap (snap-id 2MakkUunZD1vJLykl5QmmVDQAZdE84wY). I am a collaborator on the snap. Our new upload, revision 7 (156.2.8078.3), is held for manual review with:

human review required due to ‘allow-connection’ constraint (interface attributes) declaration-snap-v2_slots_connection (mpris, mpris)

name: ecosia
interfaces: mpris (slot)
request-type: connection (slot attribute change)
current declaration: slots.mpris.allow-connection slot-attributes name: ecosia requested declaration: slots.mpris.allow-connection slot-attributes name: chromium

reasoning: Upstream Chromium hardcodes the MPRIS well-known name it requests as org.mpris.MediaPlayer2.chromium.instance (components/system_media_controls/linux/system_media_controls_linux.cc). The “chromium” element is not tied to the Chromium snap: it is a constant shared by the whole Chromium family. Google Chrome on the same desktop owns org.mpris.MediaPlayer2.chromium.instance too. snapd’s mpris interface only permits binding org.mpris.MediaPlayer2.{,.*}, so with name: ecosia the bind is refused by AppArmor and the browser never appears as an MPRIS player: hardware media keys and desktop media controls do not work. Changing the slot to name: chromium fixes this.

Could you please update the snap declaration accordingly and approve revision 7? Thank you