On Feb 24, 2007, at 8:29 PM, Tabitha McNerney wrote:
So from a security standpoint, if one must change the hostname,
then one must also create a new .Xauthority file? I see
the .Xauthority file on my machine (with the hostname that was
changed) is not editable with a text editor (also this
On Feb 24, 2007, at 7:53 PM, Tabitha McNerney wrote:
No, I did not rebooted. Is rebooting required, such that X be able
to handle the new indirectly-changed hostname?
maybe? X11 is dumb ... I would try it (or at least stop and re-start X).
What should one do if, say, a spelling error in the
On 2/23/07, Kevin Ballard [EMAIL PROTECTED] wrote:
I'm not particularly familiar with how X servers work, but I thought that
usually to connect to a local X server you set your DISPLAY to :0.0 which
makes it connect to localhost.
Perhaps installing XFree86 does something to set DISPLAY to your
On 2/23/07, Daniel J. Luke [EMAIL PROTECTED] wrote:
On Feb 23, 2007, at 10:38 AM, Kevin Ballard wrote:
I'm not particularly familiar with how X servers work, but I
thought that usually to connect to a local X server you set your
DISPLAY to :0.0 which makes it connect to localhost.
Because
On Feb 24, 2007, at 5:02 PM, Tabitha McNerney wrote:
Xlib: connection to :0.0 refused by server
Xlib: No protocol specified
I'm not an expert with regard to X so I wonder what to make of
this. Also (even before I made the changes to the Computer Name),
once I had X up and running, I could
I don't know much about how this works, but I know there's an `xhost`
utility which can edit the .Xauthority file.
On Feb 24, 2007, at 8:29 PM, Tabitha McNerney wrote:
So from a security standpoint, if one must change the hostname,
then one must also create a new .Xauthority file? I see
I'm not particularly familiar with how X servers work, but I thought
that usually to connect to a local X server you set your DISPLAY to :
0.0 which makes it connect to localhost.
Perhaps installing XFree86 does something to set DISPLAY to your
particular hostname? This seems odd, but I
Why wouldn't localhost always be allowed to connect? It seems to me
if you use :0.0 as your DISPLAY then it'll connect on the loopback
interface rather than using the network interface, and I would expect
that to always be allowed to connect.
Where do my assumptions break down?
On Feb 23,
On Feb 23, 2007, at 11:47 AM, Kevin Ballard wrote:
Why wouldn't localhost always be allowed to connect?
because multiple users can be logged into a unix machine.
Any X11 client can get information from the Xserver about other
clients (like keystrokes).
It seems to me if you use :0.0 as
On Feb 23, 2007, at 11:55 AM, Daniel J. Luke wrote:
It seems to me if you use :0.0 as your DISPLAY then it'll connect
on the loopback interface rather than using the network interface,
and I would expect that to always be allowed to connect.
Where do my assumptions break down?
Did you
On Feb 23, 2007, at 12:01 PM, Kevin Ballard wrote:
Most of it. But I'm a bit confused. running xhost says only
authorized clients can connect, but the list is empty. This
indicates that one of the other mechanisms of access control is
active, but my .Xauthority file is empty. So I'm not
11 matches
Mail list logo
