[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freedesktop-xorg-devel
Subject:    Re: [PATCH] [xhost] man: xhost can not take a user name as a
From:       Erik Saule <esaule () bmi ! osu ! edu>
Date:       2011-07-30 17:38:54
Message-ID: 20110730173853.GA6900 () eriklaptop
[Download RAW message or body]

On Mon, Jul 25, 2011 at 01:48:20PM -0700, Alan Coopersmith wrote:
> On 07/23/11 15:24, Erik Saule wrote:
> > Dear list,
> > 
> > I submit a patch for review on the man page of the xhost
> > utility. running "xhost <username>" does not work in xhost
> > anymore. This patch corrects the man page to reflect this behavior and
> > propose an alternative way of doing so.
> 
> That's an incorrect assumption - xhost +username has always worked the
> same and only supported Secure RPC authentication, which is the one place
> in the man page where it's fully described as working.
> 
> If someone could figure out how to reword the man page to make that clearer,
> I'd love to see the patch, but just removing it and pretending it doesn't
> work for Secure RPC users is the wrong answer.

Thank you for pointing out my mistake. I submit a new patch that
rephrased the description of the "name" parameter in the "options"
section as: "The name can be a host name, a Secure RPC user name or a
complete name (See NAMES for more details)."

The patch also hint to the server interpreted addresses to specify a
local user.

["0001-man-xhost-can-not-take-a-user-name-as-a-parameter.patch" (text/x-diff)]

From d5123805a607d6a263b734e074bc00ba9b0e5ae7 Mon Sep 17 00:00:00 2001
From: Erik Saule <esaule@bmi.osu.edu>
Date: Sat, 23 Jul 2011 18:11:10 -0400
Subject: [PATCH] man: xhost can not take a user name as a parameter.

However, server interpreted addresses can be used to achieve the same
behavior.
---
 man/xhost.man |   16 ++++++++++++++--
 1 files changed, 14 insertions(+), 2 deletions(-)

diff --git a/man/xhost.man b/man/xhost.man
index a805edf..aecab6e 100644
--- a/man/xhost.man
+++ b/man/xhost.man
@@ -75,11 +75,18 @@ Prints a usage message.
 .BI "[+]" "name"
 The given \fIname\fP (the plus sign is optional)
 is added to the list allowed to connect to the X server.
-The name can be a host name or a user name.
+The name can be a host name or a complete name (See
+.SM
+.B NAMES 
+for more details).
 .TP 8
 .BI \- "name"
 The given \fIname\fP is removed from the list of allowed
-to connect to the server.  The name can be a host name or a user name.
+to connect to the server.  The name can be a host name or a complete
+name (See
+.SM
+.B NAMES 
+for more details).
 Existing connections are not broken, but new
 connection attempts will be denied.
 Note that the current machine is allowed to be removed; however, further
@@ -131,6 +138,11 @@ Otherwise they are assumed to be Internet addresses. If compiled to support
 IPv6, then all IPv4 and IPv6 addresses returned by getaddrinfo(__libmansuffix__) are added to
 the access list in the appropriate inet or inet6 family.
 .PP
+The local family specifies all the local connections at once. However,
+the server interpreted address "si:localuser:\fIusername\fP" can be
+used to specify a single local user. (See the
+\fIXsecurity\fP(__miscmansuffix__) manual page for more details.)
+.PP
 Server interpreted addresses consist of a case-sensitive type tag and a
 string representing a given value, separated by a colon.  For example,
 "si:hostname:almas" is a server interpreted address of type \fIhostname\fP,
-- 
1.7.2.5



_______________________________________________
xorg-devel@lists.x.org: X.Org development
Archives: http://lists.x.org/archives/xorg-devel
Info: http://lists.x.org/mailman/listinfo/xorg-devel

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic