you are viewing a single comment's thread
view the rest of the comments
[–] 52 points 1 month ago (7 children)

Affected users who are running X11 should audit their Zoom version, isolate conferencing workloads onto dedicated hardware or virtual machines, or move to a browser-based version of Zoom where sandboxing prevents unprompted clipboard access.

Anyone running a Linux system with Wayland should be OK.

  • source
  • hideshow 7 child comments
  • [–] 45 points 1 month ago (2 children)

    Anyone running a Linux system with Wayland should be OK.

    And this is exactly why I put up with the functionality regressions of Wayland over X11 for the first few years.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 month ago

    It's been quite a while since I've had issues with Wayland, but for a while there I was convinced that the only testing done on it was on a single screen laptop, because as soon as you attached a second standalone monitor (or third or fourth) all hell broke loose.

  • source
  • parent
  • [–] 8 points 1 month ago (1 child)

    I understood that all X11 apps running under Wayland are running inside the same environment, or is that wrong?

    In other words, all X11 clipboards are shared.

    I'm also not sure about clipboard isolation, since I'd have thought that copy/paste between Wayland and X11 would be expected.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 5 points 1 month ago

    The Wayland spec doesn't allow for clients to arbitrarily get clipboard data under typical conditions. Since most applications these days are running under Wayland, it should be that copying to the clipboard isn't exposed to X11 clients most of the time (only when copying from or pasting into XWayland).

  • source
  • parent