Zoom

[Tom H]

On Mon, Mar 30, 2020 at 5:49 PM Oliver Grawert <ogra at ubuntu.com> wrote:
> Am Montag, den 30.03.2020, 17:17 +0200 schrieb Liam Proven:
>> On Mon, 30 Mar 2020 at 17:13, Oliver Grawert <ogra at ubuntu.com> wrote:
>>>
>>> i did not talk about repos (though if your system eats itself
>>> during a release-to-releaase upgrade because some third-party
>>> secretly changed our sources.list you will likely not be happy
>>> either)
>>>
>>> i explicitly talked about using dpkg -i to install some downloaded
>>> deb
>>
>> Yes, I know. So was I. I thought I was clear.
>>
>> What I am saying is that if you download a .DEB file of Google
>> Chrome, or MS Teams, Or Skype for Linux, and you install it with
>> `dpkg`, then the programs add their own repositories to your system
>> list.
>
> ah, ok, i didnt get that context somehow ....
>
> well, as long as you are okay to give microsoft (or any other 3rd
> party repo owner) full root access to your system, sure, why not ;)
>
> i personally prefer to not have microsoft, google or slack to have
> full root access to my system and rather rely on the confinement
> features snap or flatpak provide to prevent any apps from reading my
> passwords out of ~/.config or other databases they do not necessarily
> need to access ...

Or Brave, Opera, Vivaldi, ...

Up to now, users have chosen vendor repositories over snaps/flatpaks.

Which is strange given that we all use containerized apps on Android and iOS.

By the way, I've just installed the zoom-client snap (on 20.04) and
this is what I get when I start it:

zoom-client_zoom-client.desktop: cannot perform operation:
mount --rbind /root /tmp/snap.rootfs_NdC795//root: Permission denied

"/root"? I had masked the snapd units and unmasked, enabled, and
started snapd.service, so maybe I didn't have something active before
launching it and there was some freakout.