X.Org Hit By New Security Vulnerabilities - Two Date Back To 1988 With X11R2

[CochainComplex]

Damn 6 Pages ...not settled yet. I need another round of popcorn.

[MorrisS.]

Millions of eyes already told everyone that x11 is a security shithole. That's why everyone should use wayland

Matter is that, the most of compositors are not explicit sync compliant and Vulkan is not the default graphic stack in the main environment of Linux OSes yet. This approach is necessary to guarantee compatibility and to optimize hardware as well. Development should concentrate its effort in this transition. Currently, Weston is the only compositor explict sync compliant. Not only Xorg/X11 must be deprecated but Opengl too, otherwise also linux developers will go crazy to make the software workable.

[CochainComplex]

TIL:

1) Kuch in Hindi refers in English to:—(nm) the female breast; ~[mamdala] the female breasts..—kuch (कुच) is alternatively transliterated as Kuca.

2) Kuch in Hindi refers in English to:—(nm) march, departure; —[karana] to march, to depart. —[ka damka bajana] to commence a march; —[bolana] to (order a) march..—kuch (कूच) is alternatively transliterated as Kūca.

If Wayland comes with not one but 5 parades of female breasts, I'm all in dude.

For a Linux nerd, an ideal open-source project must fullfil one of the two following requirements

1. ..offer impeccable, well-documented code and provide straightforward pathways for users and contributors, ensuring that the software is reliable, user-friendly, and perpetually enhanced.

or

2.... present it with breasts

[ehansin]

I have no horse in this race other than wanting to see cool innovations in the desktop space. I am running on Wayland whatever I run, and will not install an "X11" native DE or DM at this point. For no good purpose mind you, other than I just did it, I was running Gnome (on Wayland of course) the other day, and on three separate workspaces launched Sway, Hikari, and Hyprland; just to see what it would do. I launched Firefox in Hyprland to play a song (via video) on YT, again to see if any sound issues or whatever. Not like I was getting anything done other than having fun, but I'm not looking back at X11 (not that I am some old-school Unix-head that has a long history with it - though I'm also no spring chicken ) I find it humorous to see all the entrenched positions here, and I don't know enough to argue a stance. But Wayland is working for me, and the fact that a lot of the X11 devs have been a part of and have moved onto Wayland is enough for me. If in the future something replaces Wayland, great. Same with systemd and whatever. This is just my take, not some voice of authority.

[MorrisS.]

I've read about the several comments and I agree with both "factions"... Reality is that Wayland will be completely ready only when it is powered by Vulkan and explicit sync compositors. Wayland is ready... What is not ready, is the development around Wayland. Vulkan is ready, drivers are ready... Wayland works just in spcific case and it works well.

Has anyone set the deadline for the transition to Vulkan deprecating Opengl? Any news about explicit sync compositors?

Developers should reduce the complexity as much as possible. I would be curious if some team had developed a linux operating system based on Weston, Wayland and Vulkan, a pure Wayland operating system.

[timofonic]

I wrote here again for the popcorn. Please reach to ten pages!

[Weasel]

You can't be serious.

Get a f* grip.

I don't care where you are quoting this from. You can't be so f* naive.

You're perfect example of what a certified clown looks like.

[Weasel]

Remember guys, Wayland is a bad design, too difficult to support, global shortcuts, screen sharing, middle-button paste, you know the drill

You should turn off your internet too, then you can't get hacked, that's basically what Crapland does with such essential features.

Then you can claim you haven't been open to security holes that were never exploited in the first place, proudly, on your deathbed! Even if you never managed to get online.

Meanwhile we got work to do instead of playing with toys and paranoia like you.

[reba]

I've read about the several comments and I agree with both "factions"... Reality is that Wayland will be completely ready only when it is powered by Vulkan and explicit sync compositors. Wayland is ready... What is not ready, is the development around Wayland. Vulkan is ready, drivers are ready... Wayland works just in spcific case and it works well.

wlroots:

Implement vulkan renderer (merged)

staging/tearing-control: Add protocol support (merged)
and used in hyprland Tearing implementation (v3) (merged)

Add explicit synchronization, with timelines (closed)
Add explicit synchronization, with timelines, take 2 (open)

[Volta]

What do you disagree with? Do you read what you paste????

X Window System was developed at MIT.

Neither DEC nor IBM was responsible for the development of X-Windows. They mainly supplied the hardware with their software and employees to set up hundreds of terminals and dozens of minicomputers.

I can read, but it seems you've missed a large portion of text:

Although X10 offered interesting and powerful functionality, it had become obvious that the X protocol could use a more hardware-neutral redesign before it became too widely deployed, but MIT alone would not have the resources available for such a complete redesign. As it happened, DEC's Western Software Laboratory found itself between projects with an experienced team. Smokey Wallace of DEC WSL and Jim Gettys proposed that DEC WSL build X11 and make it freely available under the same terms as X9 and X10. This process started in May 1986, with the protocol finalized in August. Alpha testing of the software started in February 1987, beta-testing in May; the release of X11 finally occurred on 15 September 1987.

DEC's Research Laboratories (or Research Labs, as they were commonly known) conducted DEC's corporate research. Some of them were continued in operation by Compaq and are still operated by Hewlett-Packard. The laboratories were:

• Cambridge Research Laboratory (CRL) in Cambridge, Massachusetts, US
• MetroWest Technology Campus (MTC) in Maynard, Massachusetts, US
• Network Systems Laboratory (NSL) in Palo Alto, California, US
• Systems Research Center (SRC) in Palo Alto, California, US
• Paris Research Laboratory (PRL) in Paris, France
• Western Research Laboratory (WRL) in Palo Alto, California, US
• Western Software Laboratory (WSL) in Palo Alto, California, US

Some of the former employees of DEC's Research Labs or DEC's R&D in general include:

• Gordon Bell: technical visionary, VP Engineering 1972–1983; later moved to Microsoft Research
• Leonard Bosack: a co-founder of Cisco Systems
• Mike Burrows: an author of the Burrows–Wheeler transform
• Luca Cardelli: co-designer of the Modula-3 language
• Dave Cutler: led RSX-11M, VAX/VMS, VAXELN and MICA operating systems development; then led Windows NT development at Microsoft^[discuss]
• Ed deCastro: became co-founder of Data General Corporation
• Alan Eustace: co-author of early profiling tools; a Senior Vice President of Engineering at Google; a world-record breaker in the stratosphere jump (2014)
• Jim Gettys: early developer of X Window System^[discuss]
• Henri Gouraud: inventor of the Gouraud shading
• Jim Gray: a Turing Award winner for database research; went missing on a ship trip
• Alan Kotok: chief architect of the PDP-10 series and prolific member of World Wide Web Consortium (W3C)
• Leslie Lamport: a Turing Award recipient; first creator of LaTeX macros;
• Butler Lampson: a contributor to a wide range of personal computing concepts like WYSIWYG text formatting program
• Scott A. McGregor: co-author of the X Window System, version 11^[79]
• Louis Monier: an Internet and software entrepreneur
• Isaac Nassi: contributor to Ada programming language; co-author of the Nassi–Shneiderman diagram
• Radia Perlman: a pioneer in computer networking standartization; author of Spanning Tree Protocol
• Marcus Ranum: a computer and network security developer credited with a number innovations in firewalls
• Brian Reid: an inventor of Scribe markup language; pioneer in networking and firewalls
• Paul Vixie: a co-author of the BIND DNS server software
• Sanjay Ghemawat
• Jeff Dean
• Patrick O'Neil: a computer scientist well known for his works on databases

Just because, for example, Microsoft is a platinum member of the Linux Foundation, or that it is one of the founders of the RUST Foundation. Doesn't mean that it is responsible for every line of code.

Microsoft is responsible for spying its users, so weak example.

And you are trying to shift the responsibility.

Because of your slander? Show me proves.

What I'm suggesting is that there may be more behind some of the 'bugs' in open source than just a mistake.

Which is nothing, but FUD. The facts are there is more behind closed source than just mistakes. Let's take Microsoft and Apple. They're polluted by spying software. We don't need Russia and China here, because the USA is responsible for spying. Get the Facts!