Talk:X Window System authorization
Add topic| This is the talk page for discussing improvements to the X Window System authorization article. This is not a forum for general discussion of the subject of the article. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
 | This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
| |||||||||||
Very incomplete and misleading
[edit]The article is very incomplete and misleading. (doesn't even diffenciate between authorization and access control)
It's only describing the mechanisms to authorize access to the Xserver as a whole (who may connect at all), but nothing about other mechanisms for controlling what an individual client can do once connected. That's leaving the false impressions those would'nt exist all.
In fact there are two optional mechasnism for access control:
a) classic Xsecurity (1996): dividing into privileged and unprivileged clients. The privileged have access to all operations, while the unprivileged are restricted to only those where clients cannot hurt others (eg. access their resources, copy their window content, log keystrokes, etc) b) modern Xnamespace (2025): puts (groups of) clients into separate namespaces which make it look like they were separate X servers (to the clients), anything outside some client's namespace isn't visible to it at all, but still clients within the same namespace can interact with each other like there wasn't any extra access control.
By the way, on the authorization side there're more mechanisms than the mentioned ones. — Preceding unsigned comment added by ~2026-52745-78 (talk) 11:57, 30 September 2026 (UTC)
Untitled
[edit]Is the file containing cookies .Xauthority or .Xauthorization? I have the former on my machine, but maybe I have a non-standard setup.
- It's .Xauthority indeed. Actually, it can be any file, but .Xauthority is the default. .Xauthorization was a mistake; thanks for pointing this out. - Liberatore(T) 10:54, 11 April 2006 (UTC)
Another article and disambiguation needed for XAuth
[edit]disambig needed: XAuth (Extended Authentication), an open cross-site auth platform developed by Meebo.--87.162.40.2 (talk) 13:29, 19 April 2010 (UTC)
Yes, the XAuth (platform) article needs to be created, and then a dismbiguation page for XAuth and Xauth.
More info: XAuth "XAuth, OAuth, and Yahoo! OpenID · YDN Blog".
on the Internet access full access to an X
[edit]Two times the word "access", one is enough. — Preceding unsigned comment added by 109.192.232.54 (talk) 22:20, 27 September 2011 (UTC)
Rename to X authority or X authorization
[edit]X authority is what the file is called, but X authorization perhaps makes more sense.—chbarts (talk) 02:08, 7 December 2012 (UTC)
Cookie-based access
[edit]"These cookies are created by a separate program and stored in the file .Xauthority in the user's home directory..."
Does that mean on the computer running the X client ? — Preceding unsigned comment added by 192.109.216.148 (talk) 16:32, 18 November 2015 (UTC)
Cookie-based access
[edit]"These cookies are created by a separate program and stored in the file .Xauthority in the user's home directory..."
Does that mean on the computer running the X client ? — Preceding unsigned comment added by 192.109.216.148 (talk) 18:42, 18 November 2015 (UTC)
The word server by itself is ambiguous
[edit]Server can refer to the SSHD server, or it can refer to the XServer. These are not the same machines, so referring to "server" is ambiguous as it's not clear which server is referred to. 12.51.199.242 (talk) 00:48, 24 February 2024 (UTC)
