The last update to 7.7 was 2012
Actually, 2019 - your reference is about 7.7-RC1, but granted it s still a long time.
The last update to 7.7 was 2012
i wouldn't mind use Wayland if it don't make life harder for me as it is now as a gamer it do that's why i use x11 and you right a lot can happen in 6 years.Seems somewhat academic to me.
RHEL 9 has X11 in it. 9.0 support ends 31 May 2027, but each dot point release (9.1, 9.2 and so on) extends that out by a year, so Redhat is committed to providing support for X up to at least 2032. RHEL 10 dropped it for Wayland.
X11/X.org is in maintenance mode, no more feature development, and that means just that - maintenance and security fixes.
A lot of things can happen or change between now and 2032.
Cheers
Wizard
I get where you’re coming from, and I agree that “security panic” can easily spiral into paranoia if people go looking for ghosts everywhere. But I think a lot of these discussions miss a much more practical middle ground.Kinda amuses me, TBH. All this talk about "security" (yet again)..... Seems to me that some people - if they look hard enough, and convince themselves of its 'truth' - can find "security" holes absolutely everywhere.
I've said it before, and I'll say it yet again. If you're that worried about security.....stay off-line. Chuck the damn 'puter in the trash. And so as to resist "temptation", get rid of every aspect of your modern existence, and go live in a cave in the middle of nowhere.
Seems simple enough to me. It's not rocket-science. If something is 'bad' for you, then get rid of that thing; don't use it again.
(shrug..)
Mike.![]()
If you didn't know X was designed for being used over a network, but this was back in the day when computers were expensive and many people connected to a central computer system from a terminal (if I am not mistaken, those who have been longer around than me may correct me if I'm wrong).I get where you’re coming from, and I agree that “security panic” can easily spiral into paranoia if people go looking for ghosts everywhere. But I think a lot of these discussions miss a much more practical middle ground.
If someone genuinely cares about security and privacy, the biggest wins usually don’t come from the browser UI or swapping one desktop stack for another. They come from the network layer. That’s where you reduce the attack surface in a way that applies to everything, regardless of whether you’re on Wayland, X11, Firefox, Chromium, or something custom.
Unlike most earlier display protocols, X was specifically designed to be used over network connections rather than on an integral or attached display device. X features network transparency, which means an X program running on a computer somewhere on a network (such as the Internet) can display its user interface on an X server running on some other computer on the network.
The X Window System is an architecture that was designed at its core to run over a network. Wayland does not offer network transparency by itself however, a compositor can implement any remote desktop protocol to achieve remote display.
You’re absolutely right about the historical design of X, and that context matters. X was built in a time when computing was centralized, hardware was expensive, and network transparency was a feature, not a liability. Terminals connecting to a central system made sense in that model, and X was explicitly designed around that assumption. From a modern security standpoint, that architecture does carry baggage, especially if systems are unpatched or exposed in ways they shouldn’t be.If you didn't know X was designed for being used over a network, but this was back in the day when computers were expensive and many people connected to a central computer system from a terminal (if I am not mistaken, those who have been longer around than me may correct me if I'm wrong).
If you're that worried about security.....stay off-line.
Let me help you.... for one. anydesk does not behave well under wayland. So now you can think of something. I have others too.It's over 30 libs (depending on how your distro implements it,.
- Xlib - the basic C library for X11 protocol
- xcb (X C Bindings) - the "modern" replacement for Xlib
- Xrandr - display configuration/resolution management
- Xinerama - multi-monitor support (older approach)
- Xrender - 2D rendering with alpha compositing
- XFixes - miscellaneous fixes/extensions
- Xft - FreeType font rendering
- Xi (XInput) - input device handling
- Xext - various X extensions
- Xtst - testing/automation (XTEST extension)
- Xmu, Xaw - X miscellaneous utilities, Athena widgets
- ICE, SM - Inter-Client Exchange, Session Management
- Xdmcp - X Display Manager Control Protocol
Some haven't been updated in over a decade, some are broken, most haven't had security updates in a LONG time.
Some of the devs has even passed on. Some of it's political, I'm not updating my library, because I don't like the way you implemented this. So it's never been changed in over a decade.
Wayland, streamlined, less resources, often faster, the devs are all onboard with each other.
Wayland used to have compatibility problems a few years ago, but honeslty, I can't think of anything that doesn't run uder it.