Linux

47923 readers

1209 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

How Wayland handles security considerations vs MacOS Quartz or Windows DWM? (lemmy.ml)

submitted 3 months ago* (last edited 3 months ago) by monovergent@lemmy.ml to c/linux@lemmy.ml

15 comments fedilink hide all child comments

As I understand it, X11 has many inherent security concerns, including programs being able to read the contents of other windows and intercept keystrokes. Wayland addresses these concerns but at the moment breaks certain functions like screen readers, cursor warping, and the ability of a program to resize its own window.

I am curious as to how the display protocols of MacOS and Windows handle these situations differently. How does a program in those operating systems gain permission to read the contents of other windows, if at all? What is to be done in Wayland for these functions to be more seamless or are there inherent obstacles?

you are viewing a single comment's thread
view the rest of the comments

[–] Max_P@lemmy.max-p.me 28 points 3 months ago (1 children)

Not sure if Windows has that but I believe on macOS what happens is the app tries to record the screen, and if it fails macOS blocks the request and opens the security settings to enable the permission, and you have restart the whole application for the permission to take.

What's done for Wayland is the portal system: applications can use portals to request access to specific things like screen recording, the DE does what it needs to do and it starts feeding the data to the application through the portal. It's working fairly well, I haven't had issues with those in a while. The application just requests what it wants, and the DE prompts the user (or auto accept the request) optionally remembering the choice as well.

Generally the solution for X11 problems is to implement a modern API for it in either Wayland or as a portal. Which breaks old stuff, but once updated it works fine.

The main obstacle is getting Gnome to agree to the protocols.

[–] vrighter@discuss.tchncs.de 4 points 3 months ago (2 children)

except the portal keeps popping up whenever I touch my controller, and the remember option does not work. It pops up in the foreground anytime I even accidentallytouch my contoller's touchpad. In home streaming is basically impossible for me rn.

[–] Zamundaaa@discuss.tchncs.de 4 points 3 months ago

That's not really a Wayland thing, that's an (apparently badly implemented) attempt to bridge X11 apps to a permission system they were never written for.

[–] ReversalHatchery@beehaw.org 1 points 3 months ago

What controller? That does not seem to be a problem with the portal concept, but a pretty weird bug in the implementation of some part of it.