> my workstation's hostname is the same as my login
> username, which is (obviously) also the name of my home directory.
> And yet, I've never seen this problem before.
> So, there are definitely a few more variables involved in this one.
To reproduce, run xauth list $
On Thu 31 Mar 2022 at 07:30:14 (-0400), Greg Wooledge wrote:
> On Wed, Mar 30, 2022 at 10:27:25PM -0700, Larry Doolittle wrote:
> > I seem to have rediscovered Debian bug 889720
> > xauth crashes when directory name matches host name
> > https://bugs.debian.org/cgi-bin/bug
On Wed, Mar 30, 2022 at 10:27:25PM -0700, Larry Doolittle wrote:
> I seem to have rediscovered Debian bug 889720
> xauth crashes when directory name matches host name
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889720
> (Feb 2018)
>
> So, nothing to do with the Bullseye
I seem to have rediscovered Debian bug 889720
xauth crashes when directory name matches host name
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889720
(Feb 2018)
So, nothing to do with the Bullseye upgrade.
I must have created that directory-matching-hostname in the
process of setting up for
ould install one. Try LightDM. Uncompressed Size: 852 k, plus whatever
deps.
> Would they run xauth before or after cd'ing to my home directory?
I don't know the middle of the chains of events that gets an X sessions
started, whether via DM, or startx, only some start and end point
Felix -
Felix Miata wrote:
> Is the problem avoided if you login via a display manager (gdm, sddm, lightdm,
> etc.) instead of using startx?
Beats me. I don't have any software like that installed.
Would they run xauth before or after cd'ing to my home directory?
- Larry
P
Larry Doolittle composed on 2022-03-30 08:57 (UTC-0700):
> The xauth segfault is definitely real and
> a problem for me.
Is the problem avoided if you login via a display manager (gdm, sddm, lightdm,
etc.) instead of using startx?
--
Evolution as taught in public schools is, like re
Esteemed Debian experts and maintainers -
On Sun, Mar 27, 2022 at 11:26:37PM -0700, Larry Doolittle wrote:
> On Sun, Mar 27, 2022 at 10:45:03PM -0700, Larry Doolittle wrote:
> > I just upgraded my first machine from 11.2 to 11.3.
> > xauth fails in the context of startx.
> Wor
Esteemed Debian experts and maintainers -
On Sun, Mar 27, 2022 at 10:45:03PM -0700, Larry Doolittle wrote:
> I just upgraded my first machine from 11.2 to 11.3.
> xauth fails in the context of startx.
> Message is
> xauth: timeout in locking authority file /home/[redacted]/.Xauth
Esteemed Debian experts and maintainers -
I just upgraded my first machine from 11.2 to 11.3.
xauth fails in the context of startx.
Message is
xauth: timeout in locking authority file /home/[redacted]/.Xauthority
both in the startx console, and if I run "xauth list"
in the resulting
Norma V. Finney
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Sun, Aug 13, 2006 at 20:15:23 +0200, Lubos Vrbka wrote:
> hi,
>
> >>>xauth -f /home/user/.Xauthority extract - $DISPLAY | xauth merge -
> >>>
> >>>where "user" is the user that logged on to xdm. This will extract the
> >>>user&
hi,
xauth -f /home/user/.Xauthority extract - $DISPLAY | xauth merge -
where "user" is the user that logged on to xdm. This will extract the
user's authorization cookie for the current display and merge it into
root's authority file. Then root should be able to access th
On Sun, Aug 13, 2006 at 16:19:50 +0200, Lubos Vrbka wrote:
> hi,
>
> >One possibility is
> >
> >xauth -f /home/user/.Xauthority extract - $DISPLAY | xauth merge -
> >
> >where "user" is the user that logged on to xdm. This will extract the
> >
hi,
One possibility is
xauth -f /home/user/.Xauthority extract - $DISPLAY | xauth merge -
where "user" is the user that logged on to xdm. This will extract the
user's authorization cookie for the current display and merge it into
root's authority file. Then root should b
> surely, running
> xhost +
> remedies this problem, but that doesn't seem to me as a good solution...
> so what should i do to get it back working?
One possibility is
xauth -f /home/user/.Xauthority extract - $DISPLAY | xauth merge -
where "user" is the user that logge
hi guys,
this is probably some stupid mistake or omission i made...
so far, i was starting X using the startx command (i.e., under ordinary
user). recently i installed xdm to handle my logins (so X is now started
under root, i guess). everything works fine except that after login as
an ordina
cal LAN where I
> want to run the application.
>
> The problem is the machine in the middle is a server that doesn't have
> any X libraries -- and doesn't have xauth. So ssh -vv -X
> reports:
>
> debug1: Remote: No xauth program; cannot forward with spoofing.
>
Bill Moseley <[EMAIL PROTECTED]> writes:
>
> But, I have a case where I need to first ssh to a machine on a public
> IP and then from there ssh into the machine on the local LAN where I
> want to run the application.
If you don't mind the overhead of double-encrypting, you can tunnel
SSH over SSH.
a server that doesn't have
any X libraries -- and doesn't have xauth. So ssh -vv -X
reports:
debug1: Remote: No xauth program; cannot forward with spoofing.
I don't really want to apt-get xbase-clients:
# apt-get -s install xbase-clients
Reading Package Lists... Done
Building
being a ssh x forwarding tunnel which works fine for
everything else i've ever done on it.
so basically it looks something like this. xmove is a proxy x
application. someplace along the line of connecting to the x server, it
fails to xauth itself properly. even an xhost + on every side invol
edora core1 and
one with debian sid, and a server also running debian sid. If I ssh
out of the redhat box to the server everything seems to work.
$DISPLAY is set and xauth has the correct information. But when I do
the same from my debian laptop it doesn't work. (I have three debian
sid machi
On Mon, Mar 08, 2004 at 01:26:07PM -0500, Allan Wind wrote:
>
> For the archives, let me cut this down a bit:
>
> local$ ssh -X remote; galeon
> ** (galeon-bin:11290): WARNING **: Spinner animation not found
>
> ** (galeon-bin:11290): WARNING **: Spinner animation not found
> The program 'galeon
On 2004-03-08T18:09:20+, Colin Watson wrote:
> On Mon, Mar 08, 2004 at 01:01:39PM -0500, Allan Wind wrote:
> > `local$ ssh -X remote; remote$ ssh-agent screen; remote$ galeon &` (';'
> > is short hand for enter) broke for me with a recent ssh upgrade.
For the archives, let me cut this down a b
ers things working
> again, but I suspect based on reading /usr/share/doc/ssh/README.Debian.gz
> that there is a better way with xauth.
>
> Could someone explain why the new way is better and give me an example
> of how actually do this please?
Have you read the bit in ssh_config(5) a
DME.Debian.gz
that there is a better way with xauth.
Could someone explain why the new way is better and give me an example
of how actually do this please?
/Allan
--
Allan Wind
P.O. Box 2022
Woburn, MA 01888-0022
USA
signature.asc
Description: Digital signature
Hello,
I am trying to allow access to my X server to anyone connected
locally on my machine. I know that I can "xhost +" to allow
unlimited connections, but I've read about the file /etc/X0.hosts
which may contain the list of allowed hosts to access display :0
So I've created a /etc/X0.hosts file
On Thu, Nov 28, 2002 at 11:48:13AM -0800, Roy Pluschke wrote:
> P.S. Oops!! I must apologize to Karl I hit the "Reply" button instead of
> the "Reply to list" button and by accident sent my reply to him personally.
Do they have two buttons for these functions in Sylpheed now?
--
To UNSUBSCRIB
On Thu, 28 Nov 2002 14:20:25 +
"Karl E. Jorgensen" <[EMAIL PROTECTED]> wrote:
> > On Thu, Nov 28, 2002 at 05:27:38AM -0800, Roy Pluschke wrote:
> > > Hi,
> > >
> > > Since the upgrade of X in testing I have noticed that I don't
>
On Thu, Nov 28, 2002 at 05:27:38AM -0800, Roy Pluschke wrote:
> Hi,
>
> Since the upgrade of X in testing I have noticed that I don't
> have to use xhost or xauth to run X programs after I su to root.
>
> Is this the way its now supposed to be, or has something been
>
Hi,
Since the upgrade of X in testing I have noticed that I don't
have to use xhost or xauth to run X programs after I su to root.
Is this the way its now supposed to be, or has something been
set incorrectly during the upgrade?
Thanks in advance
RJP
--
To UNSUBSCRIBE, email to [
on Fri, Dec 14, 2001 at 05:50:19PM -0800, Karsten M. Self
(kmself@ix.netcom.com) wrote:
> [This is a re-send. Posted earlier this week with no responses.
> Likewise no updates on my bug reports.]
>
> Keywords: xauth Xauthority wdm xdm gdm kdm MIT-MAGIC-COOKIE Client is
> no
[This is a re-send. Posted earlier this week with no responses.
Likewise no updates on my bug reports.]
Keywords: xauth Xauthority wdm xdm gdm kdm MIT-MAGIC-COOKIE Client is
not authorized to connect to Server
I'm using wdm as a local X display manager under Sid/i386. Following a
r
Keywords: xauth Xauthority wdm xdm gdm kdm MIT-MAGIC-COOKIE Client is
not authorized to connect to Server
I'm using wdm as a local X display manager under Sid/i386. Following a
recent update, I'm no longer able to log in as either an unprivileged
user or root.
On properly authenticat
I'm using ``xhost local:root'' to enable su using X. I'm having exmh
open most of the time, which removes this setting more or less
immediately. Is there a way to stop it from doing so?
TIA
Christoph Simon
--
^X^C
q
quit
:q
^C
end
x
exit
ZZ
^D
?
help
.
On Mon, Apr 24, 2000 at 07:10:59PM -0400, Brian Stults wrote:
> I upgraded to XFree86-4.0 recently, and now xauth doesn't seem to work.
i don't use XFree86-4.0 yet, but here's guess or two.
> I usually use ssh to work on my unix account at work and to do so, I
> have
I upgraded to XFree86-4.0 recently, and now xauth doesn't seem to work.
I usually use ssh to work on my unix account at work and to do so, I
have a script that looks like this:
ssh REMOTEHOST "/usr/openwin/bin/xauth add `grep -e IPADDR
/etc/dhcpc/dhcpcd-eth0.info | gawk -F = '
On Fri, Mar 03, 2000 at 10:40:19AM -0900, Adam Shand wrote:
>
> > /usr/bin/X11/xauth: unable to open tmp file "/home/paul/.Xauthority-n"
> > /usr/bin/X11/xauth: unable to write authority file /home/paul/.Xauthority-n
> >
> > Is this potentially a per
> /usr/bin/X11/xauth: unable to open tmp file "/home/paul/.Xauthority-n"
> /usr/bin/X11/xauth: unable to write authority file /home/paul/.Xauthority-n
>
> Is this potentially a permission problem? What should they be?
i believe i just read a message in debian-user about
> /usr/bin/X11/xauth: unable to open tmp file "/tmp/Xauthef4473-n"
> /usr/bin/X11/xauth: unable to write authority file /tmp/Xauthef4473-n
>
> and X11 forwarding does not work. This file (Xauthef4473-n) exists and has
> the following
> permissions:
> -rw--
Hi,
today I upgraded from slink to potato. Everything worked fine despite ssh.
I enabled X11 forwarding in ssh_config.
When I log from the potato box to another slink box everything works fine.
But when I ssh from a slink box into the potato machine I get a
/usr/bin/X11/xauth: unable to open
This is something important, i hope that by posting this i can help
people not fall victim to this bug.
xbase-clients version 3.3.6-4 has a nasty bug in the xauth command. This
bug will cause ssh X11 forwarding to fail, and if xauth add or xauth
remove is run on the ~/.Xauthority file it will
but
> as a side effect encrypts your entire X session!
>
I like this solution, but it degrades speed on busy machines.
>From man xauth is a example:
xauth extract - $DISPLAY | rsh otherhost xauth merge -
I modified it for using ssh instead rsh:
xauth extract - $DISPLAY | ssh otherhost xauth merge -
Mirek
On Mon, Sep 06, 1999 at 08:55:21AM -0500, Dave Sherohman wrote:
> Seth R Arnold said:
> > On a whim I added a .rhosts file with the one word "amidala" in it. No
> > change.
>
> If you want to grant global access for another machine to use your display,
> use the xhost command: xhost amidala
Hah
On Mon, 6 Sep 1999, Dave Sherohman wrote:
> Seth R Arnold said:
> > On a whim I added a .rhosts file with the one word "amidala" in it. No
> > change.
>
> If you want to grant global access for another machine to use your display,
> use the xhost command: xhost amidala
This is a bit of a securit
Seth R Arnold said:
> On a whim I added a .rhosts file with the one word "amidala" in it. No
> change.
If you want to grant global access for another machine to use your display,
use the xhost command: xhost amidala
have no keyboard or monitor on sarnold.
I want to do something like this:
DISPLAY=amidala:0.0 ; rxvt (or netscape or mozilla or ... :)
But the error message I get is:
$ DISPLAY=amidala:0.0
$ xterm &
[1] 12927
$ xterm Xt error: Can't open display:
The xauth manpage suggests this:
% xaut
usr/X11R6/bin/x11perfcomp
-rwxr-xr-x root/root 26432 1999-02-23 02:54 usr/X11R6/bin/xauth
Note the last line.
Regards,
Jor-el
Be careful of reading health books, you might die of a misprint.
-- Mark Twain
On Sat, 21 Aug 1999, J Horacio MG wrote:
> $ dpkg -l | l
On Sat, Aug 21, 1999 at 06:24:25PM +0200, J Horacio MG wrote:
> $ dpkg -l | less
>
> ii xbase-clients 3.3.2.3a-11miscellaneous X clients
>
> may be xauth is somewhere else?
>
no
check if it wasn't accidentally removed (it should be in
/usr/X11R6/bin/xauth), an
$ dpkg -l | less
ii xbase-clients 3.3.2.3a-11miscellaneous X clients
may be xauth is somewhere else?
Jor-el dijo:
>
> 'xauth' is indeed present in Debian - you just havent installed
> it. It is part of the package xbase-clients on Slink.
>
> On Sat,
Horacio,
'xauth' is indeed present in Debian - you just havent installed
it. It is part of the package xbase-clients on Slink.
Regards,
Jor-el
Be careful of reading health books, you might die of a misprint.
-- Mark Twain
On Sat, 21 Aug 1999, J Horacio MG wro
I'm trying to compile ssh1 and found the following error while
running ./configure. I su'ed root and copied the tarball to /usr/local:
$ su
...
/usr/local/ssh-1.2.27# ./configure
...
checking for xauth... no
configure: error: configuring with X but xauth not found - aborting
Since
ngs when I su from a regular user and
> this even happens when I use vim after 'su'. I am still able to edit stuff,
> and the only problem is when I need to run some X program as superuser.
> I saw somewhere how to deal with this Xauth stuff, but I don't remember where.
>
is when I need to run some X program as superuser.
> > I saw somewhere how to deal with this Xauth stuff, but I don't remember
> > where.
> I am also having the same trouble. I didn't see a reply to Andrew's
> question, so I wanted to add that I am also interes
On 09-Apr-99 Branden Robinson wrote:
> The following is one possibility, and is what I use:
>
> export XAUTHORITY=/home/branden/.Xauthority
This is what I have done after someone suggested it to me.
I first su'd to root in an xterm after starting KDE as "pollywog"
Then I entered export XAUTHORIT
em is when I need to run some X program as superuser.
> > I saw somewhere how to deal with this Xauth stuff, but I don't remember
> > where.
>
> I am also having the same trouble. I didn't see a reply to Andrew's
> question, so I wanted to add that I am also inte
problem is when I need to run some X program as superuser.
>> I saw somewhere how to deal with this Xauth stuff, but I don't remember
>> where.
>>
>> --
>> Andrew
>>
>> [PGP5.0 Key ID 0x5EE61C37]
>>
>> --
>> Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null
Pollywog wrote:
>
> I get those annoying MAGIC COOKIE warnings when I su from a regular user and
> this even happens when I use vim after 'su'. I am still able to edit stuff,
> and the only problem is when I need to run some X program as superuser.
> I saw somewhere ho
cos I don't think that should happen.
I get those annoying MAGIC COOKIE warnings when I su from a regular user and
this even happens when I use vim after 'su'. I am still able to edit stuff,
and the only problem is when I need to run some X program as superuser.
I saw somewhere ho
Apr 1999, George Bonser wrote in response to
> Steve Lamb, on 6 Apr 1999:
>
> > Subject: Re: Xauth, how to get rid of it?
>
> > Steve, you do not want to get rid of xauth ... exactly what problem are
> > you having?
>
> I have a slightly different problem:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 7 Apr 1999 09:29:49 -0400 (EDT), Will Lowe wrote:
>How about ssh? Do
>ssh remote_machine remote_app
>and ssh will set up the xauth stuff _for_ you.
M, IIRC that doesn't set up the environment, however
> >I may be missing something here. But is xhost + what you want??
> Ah, my savior. xhost +[machine name] worked nicely. Thanks for the
> help.
How about ssh? Do
ssh remote_machine remote_app
and ssh will set up the xauth stu
On Tue, 6 Apr 1999, George Bonser wrote in response to
Steve Lamb, on 6 Apr 1999:
> Subject: Re: Xauth, how to get rid of it?
> Steve, you do not want to get rid of xauth ... exactly what problem are
> you having?
I have a slightly different problem:
The presence of Xauth prevent
On Wed, Apr 07, 1999 at 12:11:54AM -0700, George Bonser wrote:
> But now any user at [machine name] may monitor everything you do.
Considering it is my laptop and I am the only user, I'm not all that
worried. And if I were on my laptop going to my main machine (sometimes
happens) then it is m
That is right. According to the HOWTO I read a while ago, hackers can overflow
the
buffers to lock the keyboard
and mouse. The standard way is to use the Xauthority to generate a cookie to the
client.
But if on a private network, xhost + will just do. :)
Shao.
Pollywog wrote:
> On 07-Apr-99 S
On 07-Apr-99 Shao Zhang wrote:
>
> I may be missing something here. But is xhost + what you want??
I believe that is one way to do it, but not the best way.
--
Andrew
[PGP5.0 Key ID 0x5EE61C37]
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 07 Apr 1999 16:49:00 +, Shao Zhang wrote:
>I may be missing something here. But is xhost + what you want??
Ah, my savior. xhost +[machine name] worked nicely. Thanks for the help.
- --
Steve C. Lamb | I'm your p
I may be missing something here. But is xhost + what you want??
Steve Lamb wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Tue, 6 Apr 1999 23:34:41 -0700 (PDT), George Bonser wrote:
>
> >Steve, you do not want to get rid of xauth ... exactly what prob
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 6 Apr 1999 23:34:41 -0700 (PDT), George Bonser wrote:
>Steve, you do not want to get rid of xauth ... exactly what problem are
>you having?
Why not? There are other methods of protecting the X port than Xauth.
Since all machines
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Subject says all. Trying to get apps to display on remote machines. I
can do it fine to my Winbox, but that is because it isn't using Xauth.
- --
Steve C. Lamb | I'm your priest, I'm your shrink, I'
On Mon, Oct 12, 1998 at 10:33:11AM -0400, Immanuel Yap wrote:
> David Karlin wrote:
> >
> > vncserver: couldn't find "xauth" on your PATH.
> >
> Do you have X11 installed?
>
> ascus:~ $ dpkg -S xauth
> xbase: /usr/X11R6/bin/xauth
> xbase:
David Karlin wrote:
>
> Hello,
> I just installed the vnc x-windows server (.deb) and when I fire up
> vncserver,
> it says:
>
> vncserver: couldn't find "xauth" on your PATH.
>
> First I checked my hard-drive for "xauth" (find / -name &quo
Hello,
I just installed the vnc x-windows server (.deb) and when I fire up
vncserver,
it says:
vncserver: couldn't find "xauth" on your PATH.
First I checked my hard-drive for "xauth" (find / -name "xauth"); the file
does not exist on my drive. Then I chec
>>> "Jan" == Jan Vroonhof <[EMAIL PROTECTED]> writes:
Jan> Deniz Dogan <[EMAIL PROTECTED]> writes:
>> How can I use a normal user`s gnuserv process as root? What I
>> want to do is: as root to use a normaluser`s emacs to edit some
>>
Deniz Dogan <[EMAIL PROTECTED]> writes:
> How can I use a normal user`s gnuserv process as root? What I want to
> do is: as root to use a normaluser`s emacs to edit some conf files.
>
> [EMAIL PROTECTED]:~# xauth -f /home/deniz/.Xauthority extract - :0.0 | xauth
> merge
Hi,
How can I use a normal user`s gnuserv process as root? What I want to
do is: as root to use a normaluser`s emacs to edit some conf files.
I tried:
[EMAIL PROTECTED]:~# xauth -f /home/deniz/.Xauthority extract - :0.0 | xauth
merge -
[EMAIL PROTECTED]:~# export DISPLAY=:0.0
[EMAIL PROTECTED
fire up X, using startx or xdm, I receive the following error:
>
> xauth: can't load library 'libXmu.so.6'
> xinit: can't load library 'libXmu.so.6'
>
> The lib file does exist,
>
> lrwxrwxrwx 1 root root13 Jun 2 15:27 /usr/X11R6/lib/li
Hello all,
When I try to fire up X, using startx or xdm, I receive the following error:
xauth: can't load library 'libXmu.so.6'
xinit: can't load library 'libXmu.so.6'
The lib file does exist,
lrwxrwxrwx 1 root root13 Jun 2 15:27 /usr/X11R6/lib/libXm
On Wed, 11 Feb 1998, Jameson Burt wrote:
> Daniel Martin suggested a magical solution, one his mail prodded me to use.
> I now have an X-session for myself on F7,
> one X-session for my wife on F8,
> one X-session for my child on F9.
> WOW
>
> Mail to debian-users on January 4, 1998, by Remco Bl
en
> wishes to run a few X applications. If so, then she can just do:
> startx -- :1
> This will give her her own X display (on the next available virtual
> console, probably number 8), and she need not mess with any xauth
> stuff. (just make certain that "Console" is in /
give her her own X display (on the next available virtual
console, probably number 8), and she need not mess with any xauth
stuff. (just make certain that "Console" is in /etc/X11/Xserver)
If you do this, you'll also probably want to make a symbolic link from
~/.xinit to ~/.xs
I leave my xdm X-windows session running 24 hours a day.
My wife uses Linux for a few minutes each day.
I could give her permissions to run X-windows applications on top of my
X-windows session with
xhost +localhost
but "xauth" is considered more secure and does not receive
In article <[EMAIL PROTECTED]>,
<[EMAIL PROTECTED]> wrote:
>I wish to thank all the responces which I received on my Xauthority problem. I
>went looking for 'ssh' when I read it in the thread, but wasn't able to find
>it in any package (bo system). Of note, I use the default 'bash' shell and
>chec
On Thu, 15 Jan 1998 [EMAIL PROTECTED] wrote:
> I wish to thank all the responces which I received on my Xauthority problem. I
> went looking for 'ssh' when I read it in the thread, but wasn't able to find
> it in any package (bo system). Of note, I use the default 'bash' shell and
> checked the va
On Thu, 15 Jan 1998 [EMAIL PROTECTED] wrote:
> I wish to thank all the responces which I received on my Xauthority problem. I
> went looking for 'ssh' when I read it in the thread, but wasn't able to find
> it in any package (bo system). Of note, I use the default 'bash' shell and
> checked the va
On Thu, 15 Jan 1998 [EMAIL PROTECTED] wrote:
> I wish to thank all the responces which I received on my Xauthority problem. I
> went looking for 'ssh' when I read it in the thread, but wasn't able to find
> it in any package (bo system). Of note, I use the default 'bash' shell and
> checked the v
I wish to thank all the responces which I received on my Xauthority problem. I
went looking for 'ssh' when I read it in the thread, but wasn't able to find
it in any package (bo system). Of note, I use the default 'bash' shell and
checked the variables (as suggested) :
XAUTHORITY=~/.Xauthority
I
On Thu, 15 Jan 1998, Daniel Martin at cush wrote:
> "Jens B. Jorgensen" <[EMAIL PROTECTED]> writes:
>
> > Sir you are missing the point. Stop confusing the guy.
>
> Assuming, of course, that root never uses the xauth command.
I already got a mail from Jens c
"Jens B. Jorgensen" <[EMAIL PROTECTED]> writes:
> Remco Blaakmeer wrote:
>
> > Don't do that. The minute root writes to that file (when root logs in to X
> > or uses the xauth command), it becomes owned by root and the user can't
> > log in to
On Thu, 15 Jan 1998, Jens B. Jorgensen wrote:
> Sir you are missing the point. Stop confusing the guy. What you're
> saying is based upon an assumption that this trick would be used
> whenever root logged in. Now why would that be necessary? If you log
> into xdm as root you won't *need* to futz w
export' the variable.
>
> So, you want to something like
>
> export XAUTHORITY=~user/.Xauthority
>
> where `user' is the name of the user that is logged in to the X display?
>
> Don't do that. The minute root writes to that file (when root logs in to X
> o
e name of the user that is logged in to the X display?
Don't do that. The minute root writes to that file (when root logs in to X
or uses the xauth command), it becomes owned by root and the user can't
log in to X anymore.
What you could do is using ssh. This command will do the trick:
gt;access("~/.Xauthority", F_OK) = -1 ENOENT (No such file or
> > > >directory)
> > >
> > > The kernel does not know about "~/" as an abbreviation of the
> > > homedirectory,
> > > that's why it fails. I think you ha
>directory)
> >
> > The kernel does not know about "~/" as an abbreviation of the homedirectory,
> > that's why it fails. I think you have set some environment variable which
> > xauth uses to "~/" or similar instead of the full path to your
pen("~/.Xauthority", O_RDONLY) = -1 ENOENT (No such file or
> >directory)
> >access("~/.Xauthority", F_OK) = -1 ENOENT (No such file or
> >directory)
>
> The kernel does not know about "~/" as an abbreviation of the homedirect
(No such file or directory)
>access("~/.Xauthority", F_OK) = -1 ENOENT (No such file or directory)
The kernel does not know about "~/" as an abbreviation of the homedirectory,
that's why it fails. I think you have set some environment variable which
xauth uses to "
I've chased this one for a while. Martin Bialasinski tried to help via private
email, but neither of us could figure out what is wrong.
# xauth -i generate westgac3/unix:0 .
xauth: creating new authority file ~/.Xauthority
xauth: unable to open tmp file "~/.Xauthority-n"
xa
Lee Bradshaw wrote:
> "Richard E. Hawkins Esq." <[EMAIL PROTECTED]> writes:
>
> > After the last round of questions & posts on the topic, I've found
> > that I can stably export xauthority by
> >
> > xauth list $DISPLAY
> >
> >
"Richard E. Hawkins Esq." <[EMAIL PROTECTED]> writes:
> After the last round of questions & posts on the topic, I've found
> that I can stably export xauthority by
>
> xauth list $DISPLAY
>
> and pasting from MIT on to
>
> xauth add $DIS
12 Jan 1998 18:03:21 -0600, Jens B. Jorgensen <[EMAIL PROTECTED]> wrote:
> You'll also need root access on the target machine in order to
> install sshd.
Not _strictly_ true, but it won't work as well. You can install it under your
home directory, and leave it running on a high numbered port. Lo
1 - 100 of 113 matches
Mail list logo
