Auto-connection for personal-files for Bitwarden Desktop

store-requests privileged-interfaces
21

That means you should probably put an

assumes: [ snapd2.62 ]

into your snapcraft.yaml to make sure the snap doesn’t break on distros running with an old snapd

1 Like
22

Hello all!

Given the detailed discussion, this is a +1 from my end in support of @0xnishit’s modified suggestion. To specify, that means granting auto-connection write-access for the personal-files interface for the following paths:

"personal-files": {
  "write": [
    "$HOME/.config/google-chrome/NativeMessagingHosts",
    "$HOME/.config/chromium/NativeMessagingHosts",
    "$HOME/.config/microsoft-edge/NativeMessagingHosts",
    "$HOME/.mozilla/native-messaging-hosts"
  ]
}

Additionally, adding my -1 for granting the additional */snap/* paths, as I agree this access falls too far outside of the intended use-case for the personal-files interface.

2 Likes
23

Thanks all for the responses so far. In that case I’ll update the upstream side to be the paths @0xnishit noted - excluding the snap paths. We’ll revisit how we can bring support for snap browsers later.

Is there anything else needed from my side before granting approval? I believe we have the required +2 approvals for:

"personal-files": {
  "write": [
    "$HOME/.config/google-chrome/NativeMessagingHosts",
    "$HOME/.config/chromium/NativeMessagingHosts",
    "$HOME/.config/microsoft-edge/NativeMessagingHosts",
    "$HOME/.mozilla/native-messaging-hosts"
  ]
}

specifically.

24

+2 for, 0 against

Since the snap is already published by the verified publisher, there is no need of vetting required.

Granting personal-files interface as mentioned above to this snap. This is now live.

1 Like