Package Details: zoom 6.2.11-1

Git Clone URL: https://aur.archlinux.org/zoom.git (read-only, click to copy)
Package Base: zoom
Description: Video Conferencing and Web Conferencing Service
Upstream URL: https://zoom.us/
Keywords: call conference meeting video
Licenses: LicenseRef-zoom
Submitter: edh
Maintainer: edh
Last Packager: edh
Votes: 670
Popularity: 6.81
First Submitted: 2015-08-15 13:18 (UTC)
Last Updated: 2024-11-25 17:39 (UTC)

Pinned Comments

erbrecht commented on 2024-11-19 13:06 (UTC)

@Rhinoceros - I finally got screen sharing to work under KDE with Wayland. Looks like I'm using the same versions as you:

  • Zoom 6.2.10
  • pipewire 1.2.6

I followed the Screen share section on the Zoom wiki page:

https://wiki.archlinux.org/title/Zoom_Meetings

The only thing I didn't need to do was set XDG_CURRENT_DESKTOP=gnome. I followed the other steps, and now I can choose my desktop/window to share. Prior to following the wiki I couldn't stop screen sharing without the hanging issue, which I was experiencing prior to 6.2.10.

edh commented on 2016-08-26 11:03 (UTC) (edited on 2017-03-09 10:48 (UTC) by edh)

I contacted the zoom support on 13th July 2016 and tried to lure them into creating a proper PKGBUILD respectively adopting this one, considering they are providing a package over very none standard ways to the Arch Linux community (downloading via a *foreign* site) and not through the official repo or the AUR. However there was little to no progress so far.

Latest Comments

« First ‹ Previous 1 .. 18 19 20 21 22 23 24 25 26 27 28 .. 78 Next › Last »

edh commented on 2023-01-11 11:21 (UTC)

@nicktee This kind of problem discussion is part of what this comment section is for :)

nicktee commented on 2023-01-10 22:46 (UTC) (edited on 2023-01-10 22:55 (UTC) by nicktee)

@jakommo - I still have this problem with the 5.13.4-1 package. I thought it was fixed a few times because I started zoom successfully but realised the problem only manifests when I start zoom and slack concurrently (both electron apps I think?)

Some things I know

  • the whole system freezes, I can't switch to another terminal and fix things
  • it occurs on Wayland and XOrg
  • it is resolved by starting with linux-lts (5.15.86-1) instead of linux (6.1.4.arch1-1)

This suggests to me it's a kernel bug, but I'm no guru. I will post to the arch forums and see if anyone knows anything else. Sorry (@edh for spamming your package)

Forum post here https://bbs.archlinux.org/viewtopic.php?id=282713

jakommo commented on 2023-01-10 09:11 (UTC)

Similar to nicktee, my machine would freeze instantaneously when opening zoom 5.13.3. They released 5.13.4 now and I manually updated the PKGBUILD and that version works again.

nicktee commented on 2023-01-05 05:31 (UTC) (edited on 2023-01-06 03:20 (UTC) by nicktee)

~~When I run 5.13.3-1 it freezes up my Gnome session. Can't find any indication of why in any logs I can find (~/.zoom/logs/* or journal).~~

Actually ignore this, it looks like an issue with electron, not zoom or this package specifically.

ttshaw1 commented on 2022-12-22 03:27 (UTC)

Is anyone else having trouble with scheduled meetings? I'm using KDE Wayland and Zoom silently crashes when I try to schedule a meeting or join a scheduled meeting. It's been like this for at least a few months

edh commented on 2022-11-30 15:49 (UTC)

Personally, I rather expose myself to kernel-bugs than chrome-sandbox bugs (in a binary-only version of it as packaged by zoom!). If there is no consensus to the contrary, I would not set the SUID bit.

eclairevoyant commented on 2022-11-30 05:22 (UTC) (edited on 2022-11-30 05:25 (UTC) by eclairevoyant)

@hawath pretty sure flatpaks also require unprivileged user namespaces, so you'll run into the same issue there. Also, I don't see what additional benefits a flatpak would provide here.

If the only issue for you is the setuid being off, you can edit the PKGBUILD and turn it on right?

W47MPUSv commented on 2022-11-30 04:48 (UTC)

@eclairevoyant Thank you for your informative reply. I decided to try the flatpak version of Zoom.

eclairevoyant commented on 2022-11-28 23:03 (UTC) (edited on 2022-11-28 23:12 (UTC) by eclairevoyant)

Fair enough on the version. Regarding kernel.unprivileged_userns_clone=0, the attack surface is reduced because you're only using setuid on specific programs rather than allowing all users and all programs to create user namespaces. Also, oops, I meant to provide a link to this Security SE topic, not ServerFault. As mentioned there:

The reason for this is that much of the kernel that is only intended to be reachable by UID 0 is not audited particularly well, given that the code is typically considered to be trusted. That is, a bug that requires a UID of 0 is rarely considered a serious bug. Unfortunately, unprivileged user namespaces make it possible for unprivileged users to access this very same code and exploit security bugs.

In both scenarios (zoom with setuid but without unprivileged user namespaces, vs zoom with unprivileged user namespaces), zoom has root access. However, in the second scenario, potentially any other program also has root access.

That being said, in the second scenario, the program has to do some work to take advantage of a privesc vuln to break out of the container. In the first scenario you've already given it root for free. So FWIW I'm personally in favour of not using setuid.

IMO if you need the security of a hardened kernel in a desktop environment, you either shouldn't be running zoom or you should keep your valuable data on a separate machine/network (that way it doesn't matter if zoom runs as root).

edh commented on 2022-11-28 22:06 (UTC)

@eclairevoyant

AFAIK $subver is merely a build tag and not part of the advertised version.

I do not understand how adding a SUID bit decreases the attack surface.

« First ‹ Previous 1 .. 18 19 20 21 22 23 24 25 26 27 28 .. 78 Next › Last »