On Sun, Oct 24, 2021 at 04:59:06PM +1100, Keith Bainbridge wrote:
>
> On 24/10/21 05:31, Charles Curley wrote:
> > alias su="su --whitelist-environment=DISPLAY,XAUTHORITY"
>
>
> Doesn't that mean that when you type 'su' at a command prompt, the response
> will be running the command
> --whitelis
On 24/10/21 05:31, Charles Curley wrote:
alias su="su --whitelist-environment=DISPLAY,XAUTHORITY"
Doesn't that mean that when you type 'su' at a command prompt, the
response will be running the command
--whitelist-environment=DISPLAY,XAUTHORITY
as root.
You won't be able to switch to root
On Fri, 22 Oct 2021 09:44:25 -0500
David Wright wrote:
> > root@jhegaala:~#
>
> I think you need su --whitelist-environment=DISPLAY,XAUTHORITY -
Thank you, also to Reco.
I did:
$ alias su="su --whitelist-environment=DISPLAY,XAUTHORITY"
That works. So I will add that to my other aliases in
Hi.
On Fri, Oct 22, 2021 at 08:25:36AM -0600, Charles Curley wrote:
> charles@jhegaala:~$ su --whitelist-environment=DISPLAY -
It won't be enough. You need this:
su --whitelist-environment=DISPLAY,XAUTHORITY -
Reco
On Fri 22 Oct 2021 at 08:25:36 (-0600), Charles Curley wrote:
> On Tue, 15 Jun 2021 21:51:28 +0200
> wrote:
>
> > Try adding
> > the option `--whitelist-environment=DISPLAY to your su command (hint:
> > you can add more variables to that whitelist, comma separated).
>
> I just tried this. No joy
On Tue, 15 Jun 2021 21:51:28 +0200
wrote:
> Try adding
> the option `--whitelist-environment=DISPLAY to your su command (hint:
> you can add more variables to that whitelist, comma separated).
I just tried this. No joy.
charles@jhegaala:~$ echo $DISPLAY
:0.0
charles@jhegaala:~$ su -
Password:
On Tue, Jun 15, 2021 at 10:17:25PM +0200, BerndSchmittNews wrote:
> Hello tomas,
>
>
> thanks for your answer.
>
> On 15.06.21 21:51, to...@tuxteam.de wrote:
> >No. It's the su, dropping the DISPLAY environment variable. Try adding
> >the option `--whitelist-environment=DISPLAY to your su comman
Hello tomas,
thanks for your answer.
On 15.06.21 21:51, to...@tuxteam.de wrote:
No. It's the su, dropping the DISPLAY environment variable. Try adding
the option `--whitelist-environment=DISPLAY to your su command
works like a charm.
Thank you
Bernd
On Tue, Jun 15, 2021 at 09:21:10PM +0200, BerndSchmittNews wrote:
> Hello.
>
> I used to use xhost-command and su -l ... -c ... to run programs as a
> different user in debian10. In debian11 I get an error about having no
> DISPLAY env variable specified.
>
> Does xhost wo
Hello.
I used to use xhost-command and su -l ... -c ... to run programs as a
different user in debian10. In debian11 I get an error about having no
DISPLAY env variable specified.
Does xhost work different now?
$ uname -a
Linux VB-Deb400 4.19.0-16-amd64 #1 SMP Debian 4.19.181-1 (2021-03-19
; to the display. The simplest solution I've found is a
> >
> > xhost +si:localuser:root
> >
> > in my .xsession file.
>
> I think more fine grained would be to use xauth extract / xauth merge.
Yes, perhaps a merge with ~root/.Xauthority
> Or just:
>
> ex
Am Dienstag, 22. Juli 2014, 17:48:24 schrieb Vincent Lefevre:
> To be able to save/restore the XKB keymap in a /etc/pm/sleep.d script
> (as a workaround for Debian bug 633849), xkbcomp needs to have access
> to the display. The simplest solution I've found is a
>
> xhos
To be able to save/restore the XKB keymap in a /etc/pm/sleep.d script
(as a workaround for Debian bug 633849), xkbcomp needs to have access
to the display. The simplest solution I've found is a
xhost +si:localuser:root
in my .xsession file.
But some users discourage to allow this a
to see the output of
pstree -aAc | grep -B2 -A2 '[X]org'
Hi Sebastian,
It's working now. I think it was caused by DisallowTCP=true in gdm.conf
Many Thanks,
Dieder.
===
die...@koala:$ xhost +
access control disabl
On Wed, Mar 18, 2009 at 23:52:00 +0100, Dieder Vervoort wrote:
> Florian Kulzer wrote:
>>>> On Sat, Mar 14, 2009 at 23:22:32 +0100, Dieder Vervoort wrote:
>>>>
>>>>> I can' t make xhost to work.
[...]
>> The first thing to check
Florian Kulzer wrote:
On Sun, Mar 15, 2009 at 22:05:20 +0100, Dirk Vervoort wrote:
Florian Kulzer wrote:
On Sat, Mar 14, 2009 at 23:22:32 +0100, Dieder Vervoort wrote:
I can' t make xhost to work.
I searched around but couldn' t find a solution.
[...
On Sun, Mar 15, 2009 at 22:05:20 +0100,
Dieder Vervoort wrote:
> Florian Kulzer wrote:
>> On Sat, Mar 14, 2009 at 23:22:32 +0100, Dieder Vervoort wrote:
>>> I can' t make xhost to work.
>>> I searched around but couldn 't find a solution.
On Sun, Mar 15, 2009 at 10:05:20PM +0100, Dirk Vervoort wrote:
> Florian Kulzer wrote:
> >On Sat, Mar 14, 2009 at 23:22:32 +0100, Dieder Vervoort wrote:
> >>I can' t make xhost to work.
> >>I searched around but couldn' t find a solution.
> >If your go
On Sun, Mar 15, 2009 at 22:05:20 +0100, Dirk Vervoort wrote:
> Florian Kulzer wrote:
>> On Sat, Mar 14, 2009 at 23:22:32 +0100, Dieder Vervoort wrote:
>>> I can' t make xhost to work.
>>> I searched around but couldn' t find a solution.
[...]
>>&
Florian Kulzer wrote:
On Sat, Mar 14, 2009 at 23:22:32 +0100, Dieder Vervoort wrote:
Hi all,
I can' t make xhost to work.
I searched around but couldn' t find a solution.
Any idea ?
[...]
die...@koala:~$ xhost +
access control disabled, clients can connect fro
On Sat, Mar 14, 2009 at 23:22:32 +0100, Dieder Vervoort wrote:
> Hi all,
>
> I can' t make xhost to work.
> I searched around but couldn' t find a solution.
> Any idea ?
[...]
> die...@koala:~$ xhost +
> access control disabled, clients can connect from any
Hi all,
I can' t make xhost to work.
I searched around but couldn' t find a solution.
Any idea ?
Many thanks,
Dieder
===
die...@koala:~$ xhost +
access control disabled, clients can connect from any host
die...@koala:~$ cat /etc/X11/xinit/xserverrc
#!/bi
Hi,
Greg Norris wrote:
On Tue, Apr 18, 2006 at 10:43:47AM -0400, Antonio Paiva wrote:
Ryan,
You probably need to run
xhost
on the client machine.
Someone suggest this virtually every time the topic comes up. It's
exceptionally bad advice... DON'T DO IT!!!
J
Thanks, but I'm still missing something. I appended the line
xhost local:
to /etc/profile, as well as ~/.bash_profile, and neither seems to have
changed anything. I've tried to wade into the bash manual and the bash
doc examples, but it's beyond me.
Thanks,
Tyler
On 12/19/0
On 12/19/05, Tyler Smith <[EMAIL PROTECTED]> wrote:
Hi,I'm using Etch with x.org, xdm, and fluxbox. I've discovered that I
can't open an X windows after I log into root using su, as when I try toopen emacs to edit a config file. I have to use 'xhost local:' first.N
Hi,
I'm using Etch with x.org, xdm, and fluxbox. I've discovered that I
can't open an X windows after I log into root using su, as when I try to
open emacs to edit a config file. I have to use 'xhost local:' first.
Not a big deal, but I have to do this everytime I l
perly. I have tryied xhost + on the
> debian computer but it still doesn't work. Any Ideas?
Don't use xhost. Pretend it doesn't exist.
Easier way: ssh -X [EMAIL PROTECTED] and just run the programs you need from
the command line, the windows will appear on your de
I am trying to use the mouse and keyboard from a suse to a dabian pc.
Both computers are Isolated, so security is not a problem. I can ssh,
so I know the network is working properly. I have tryied xhost + on the
debian computer but it still doesn't work. Any Ideas?
--
To UNSUBS
rt DISPLAY=:0.0
$ xauth merge ~username/.Xauthority
$ some_x_app &
As far as I know this should work in almost any situation I can think
of.
>
> xhost +local:
> did exactly what I wanted.
This effectively allows any local user to connect to your X.
Non-repudiation is gone if you do
~/.xauthority
which executed silently, but had no apparent effect.
Got a suggestion off-list saying to set up x-forwarding in ssh, but
that seems like unnecessary use of resources (why encrypt traffic
that's not leaving my local machine?)
But...
xhost +local:
did exactly what I wanted.
So
* Karsten M. Self ([EMAIL PROTECTED]) [030909 21:13]:
> Don't use xhost. It's inherently evil. Vaguely suitable for 1985.
> Definitely not OK in 2003.
> What you want is:
>
> xrdb -merge ~/.xauthority
You mean xauth, not xrdb.
good times,
Vineet
--
http://w
El martes, 9 de septiembre de 2003, a las 23:44, ScruLoose escribe:
> Problem is, after an "xhost +localhost", I get the same result (even
> though it claims "localhost being added to access control list").
$ xhost +local:
Regards, Ismael
--
"Tout fourmille de co
ot;:0.0" refused by server
> Xlib: Client is not authorized to connect to Server
> I googled it and found lots of hits, all saying to use "xhost
> +localhost" to allow me to do what I want.
Nope.
Don't use xhost. It's inherently evil. Vaguely suitable for 1985.
Defini
hits, all saying to use "xhost
+localhost" to allow me to do what I want.
Problem is, after an "xhost +localhost", I get the same result (even
though it claims "localhost being added to access control list").
xhost with no parameters returns "INET:shorty.ca" wh
David Z Maze wrote:
David selby <[EMAIL PROTECTED]> writes:
I can enable other users to log into my x server with xhost +, I need
to do this because I want ro run a program via user web crontab which
uses xmessage.
Uh, there's no better solution at all? With the default Debi
David selby <[EMAIL PROTECTED]> writes:
> I can enable other users to log into my x server with xhost +, I need
> to do this because I want ro run a program via user web crontab which
> uses xmessage.
Uh, there's no better solution at all? With the default Debian
settings,
I can enable other users to log into my x server with xhost +, I need to
do this because I want ro run a program via user web crontab which uses
xmessage.
Idealy I would like only root user to be able to access my x server ...
(less users who can access it, more secure ... rule of thumb) so I
* deFreese, Barry ([EMAIL PROTECTED]) [030213 11:07]:
> >-Original Message-
> >From: Haralambos Geortgilakis [mailto:[EMAIL PROTECTED]]
> >Sent: Thursday, February 13, 2003 1:30 AM
> >To: Debian User Listie
> >Subject: Synaptic & can't run in
On Thu, 13 Feb 2003 10:40:06 +0100, Haralambos Geortgilakis wrote:
> Hellene:/home/haralambos# synaptic
> Xlib: connection to ":0.0" refused by server
Hi Haralambos,
seems like you tried to run a X-program as root. 'sudo synaptic' should do
the trick (you have to be in the sudoers file for this)
>-Original Message-
>From: Haralambos Geortgilakis [mailto:[EMAIL PROTECTED]]
>Sent: Thursday, February 13, 2003 1:30 AM
>To: Debian User Listie
>Subject: Synaptic & can't run in console with "su" or "xhost local:root"
>
>Hi Yall,
>
erver
Xlib: No protocol specified
Gtk-WARNING **: cannot open display: :0
Hellene:/home/haralambos# xhost local:root
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
xhost: unable to open display ":0"
Hellene:/home/haralambos#
*BFN*
Greek Geek :-)
Every
Lo, on Monday, January 6, nate did write:
> Abdul Latip said:
>
> > IT WORKS! Thank you very much! May I know for what is
> > "-nolisten tcp" in xserverrc?
>
> sure, glad to help. the nolisten tcp is to prevent the X server
> from listening for connections on TCP ports.
... which is a good thin
Abdul Latip said:
> IT WORKS! Thank you very much! May I know for what is
> "-nolisten tcp" in xserverrc?
sure, glad to help. the nolisten tcp is to prevent the X server
from listening for connections on TCP ports. SSH bypasses this by
tunneling the connection over the SSH connection and(I think)
nate wrote (edited):
> assuming both client & server are debian ..
Actually, both are the "localhost" 127.0.0.1.
> server:/etc/ssh/sshd_config
> X11Forwarding yes
> /etc/init.d/ssh restart
> client:"ssh -l username -v -C servername -X"
>"xclock"
IT WORKS! Thank you very much! May I
m as root and run it directly.
What I do in this case is:
# export DISPLAY=:0.0
# export XAUTHORITY=~user/.Xauthority
where is the user you used to start the X session.
The file .Xauthority contains a magic cookie that is needed to connect
to the X server (assuming xhost has not been used t
Abdul Latip said:
> OK, this must be very embarassing: I still have no idea
> on how to open a X11 window with another account without
> xhost :-(.
>
> I have read this issue several times on this list. I am
> aware that it is somehow related with sshd_config and
> xserverrc.
OK, this must be very embarassing: I still have no idea
on how to open a X11 window with another account without
xhost :-(.
I have read this issue several times on this list. I am
aware that it is somehow related with sshd_config and
xserverrc. Unfortunately, I can not figure out what
to do
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 [
Problem is solved. My thanks to all who offered suggestions.
Perhaps the below may be useful to someone, sometime.
Several things went wrong - first the ugly.
xhost +localhost examines the /etc/hosts file to make sure
the host (localhost in this case) is valid.
I had copied over the most
On Sat, Oct 26, 2002 at 06:32:53AM -0500, Larry Alkoff wrote:
> Here is what I would expect to work: (I think it _used_ to work)
> As user:
> xhost +localhost
> su
> synaptic Now get error Synaptic: could not open display
>
> Here is what works:
&
On Sat, 26 Oct 2002 18:09:13 -0400, Gregory Seidman wrote:
>Larry Alkoff sez:
>} On Sat, 26 Oct 2002 11:31:12 -0700, Earl F Hampton wrote:
>[...]
>} >Try xhost +local:localhost
>}
>} Ohh, that works!
>} Thank you.
>[...]
>} However after su I must still
>} ex
Larry Alkoff sez:
} On Sat, 26 Oct 2002 11:31:12 -0700, Earl F Hampton wrote:
[...]
} >Try xhost +local:localhost
}
} Ohh, that works!
} Thank you.
[...]
} However after su I must still
} export DISPLAY=:0
}
} Then I can load synaptic.
}
} I'd like to not be required to type the
ne
>> > and there is a much greater volume of expertise here.
>> >
>> > I'm trying to use xhost +localhost in Libranet 2.7
>>
>> Try 'xhost + localhost' (and not +localhost).
>>
>Try xhost +local:localhost
>
>I think it defaults to i
ne
>> > and there is a much greater volume of expertise here.
>> >
>> > I'm trying to use xhost +localhost in Libranet 2.7
>>
>> Try 'xhost + localhost' (and not +localhost).
>>
>Try xhost +local:localhost
Ohh, that works!
Thank you.
N
On 26 Oct 2002 19:25:19 +0200, Haim Ashkenazi wrote:
>On Sat, 2002-10-26 at 13:32, Larry Alkoff wrote:
>> Forgive me for posting a Libranet question here
>> but Libranet is a very close Debian clone
>> and there is a much greater volume of expertise here.
>>
>> I
On Saturday 26 October 2002 10:25 am, Haim Ashkenazi wrote:
> On Sat, 2002-10-26 at 13:32, Larry Alkoff wrote:
> > Forgive me for posting a Libranet question here
> > but Libranet is a very close Debian clone
> > and there is a much greater volume of expertise here.
> >
On Sat, 2002-10-26 at 13:32, Larry Alkoff wrote:
> Forgive me for posting a Libranet question here
> but Libranet is a very close Debian clone
> and there is a much greater volume of expertise here.
>
> I'm trying to use xhost +localhost in Libranet 2.7
Try 'xh
Forgive me for posting a Libranet question here
but Libranet is a very close Debian clone
and there is a much greater volume of expertise here.
I'm trying to use xhost +localhost in Libranet 2.7
to load programs as root in X-windows - eg Synaptic.
I _believe_ xhost +localhost _used_ to wor
begin Karsten M. Self quotation:
>
> There is a serious problem at your site. You've raised this issue?
Deaf ears. Located in another time zone, and miles above my pay grade.
> I'll presume one end or the other is under your control.
Yes; but BOTH ends have to allow X forwarding before it w
on Mon, Apr 22, 2002, Shawn McMahon ([EMAIL PROTECTED]) wrote:
> begin Karsten M. Self quotation:
> > >
> > > Unless the other machine is not administrated by you,
> >
> > There are few X11-capable systems whic won't allow users to run
> > arbitrary clients. Including an ssh client run from fl
Hi!
On Sat, 20 Apr 2002, Alexander Schmehl wrote:
> [...]
> /etc/X11/xinit/xserverrc . Remove it, or use "ssh -x" instead of
> telnet/xhost should solve your problem.
Yes, indeed. It *did* solve my problem. Thanks a lot!
Greetings,
Holger
--
To UNSUBSCRI
Hi Bruno!
On Mon, 22 Apr 2002, Bruno Boettcher wrote:
> [...]
> as others pointed out, i don't want to open the access to the X server
> and am trying the ssh solution without success so far
>
> here's my try:
> ssh -A -X router
Yes, I got it solved. The "ssh -X" solution works for me
On Sat, Apr 20, 2002 at 05:51:43PM +0200, Holger Rauch wrote:
> When I execute "xhost +" on localhost, telnet to another machine, set the
> DISPLAY to my machine's hostname (!export DISPLAY=prag:0.0"), I get the
> error message that this connection is refused by the se
begin Karsten M. Self quotation:
> >
> > Unless the other machine is not administrated by you,
>
> There are few X11-capable systems whic won't allow users to run
> arbitrary clients. Including an ssh client run from floppy or a
> user-installed directory.
Karsten, have you ever worked somewh
* Karsten M. Self (kmself@ix.netcom.com) [020421 01:20]:
> > or doesn't allow X forwarding in it's
>
> That's "its".
>
> > ssh config.
>
> X11 forwarding effects server only. For the client, this is
That's "affects". =)
good times,
Vineet
--
Currently seeking opportunities in the SF Bay Ar
On Sun, 21 Apr 2002, Karsten M. Self wrote:
> _Not_ _an_ _excuse_. SSH is available for everything from DOS to VMS
> (though there doesn't seem to be one for MVS that I can find).
> Certainly any flavor of 'Nix, 'Doze, or Mac is covered.
If you need a Windows one, I like putty. I've mirrored it
on Sun, Apr 21, 2002, Shawn McMahon ([EMAIL PROTECTED]) wrote:
> begin David Z Maze quotation:
> >
> > "Don't do that." xhost is notoriously insecure; ssh X forwarding is
> > easier to manage, isn't vulnerable to IP spoofing attacks, and doesn't
&
begin David Z Maze quotation:
>
> "Don't do that." xhost is notoriously insecure; ssh X forwarding is
> easier to manage, isn't vulnerable to IP spoofing attacks, and doesn't
> require you to manually set DISPLAY. The X server in woody comes, by
Unless t
Holger Rauch <[EMAIL PROTECTED]> writes:
> When I execute "xhost +" on localhost, telnet to another machine,
> set the DISPLAY to my machine's hostname (!export
> DISPLAY=prag:0.0"), I get the error message that this connection is
> refused by the server? Why
* Holger Rauch <[EMAIL PROTECTED]> [020420 17:51]:
> When I execute "xhost +" on localhost, telnet to another machine, set the
> DISPLAY to my machine's hostname (!export DISPLAY=prag:0.0"), I get the
> error message that this connection is refused by the serve
Hi!
When I execute "xhost +" on localhost, telnet to another machine, set the
DISPLAY to my machine's hostname (!export DISPLAY=prag:0.0"), I get the
error message that this connection is refused by the server? Why? (It
doesn't make sense to me since I executed "
x gives the refused
connection to server error. If I do xhost + then root can start
linuxconf, but the behavior of Xdialog via 'at' is still the same, plus
that's not the solution, just tried it to see.
-CraigW
Hi
In one of my Debian-machines I am not being able to X-connect
remotely.
[EMAIL PROTECTED]:~$ bash
[EMAIL PROTECTED]:~$ xhost +
access control disabled, clients can connect from any host
[EMAIL PROTECTED]:~$ ssh erlang
8:06 -0600 (CST)
Jor-el <[EMAIL PROTECTED]> wrote:
> On Tue, 8 Jan 2002, François Chenais wrote:
>
> >I run xhost
> > Francois : xhost
> > access control enabled, only authorized cl
On Tue, 8 Jan 2002, François Chenais wrote:
> I run xhost
> Francois : xhost
> access control enabled, only authorized clients can connect
Note what it says -> ^^^
and now read 'man xauth&
xterm,
I run xhost
Francois : xhost
access control enabled, only authorized clients can connect
INET:localhost
INET:bdims
I run su - root
I run export DISPLAY=localhost:0.0
I run Eterm (or
Have a peek at /etc/X11/xinit/xserverrc, I have an option of '-nolisten' listed
there which seems like it could be your problem.
figured out yet.
I'm used to being able to redisplay programs across my network. I
generally run "xhost +" on my machine, and then "export
DISPLAY=10.15:0.0" on the foreign machine, and off I go. So far as I
understand, the X server (on my machine) is supposed to be
--- Hans Gubitz <[EMAIL PROTECTED]> wrote: > Hi,
>
> I did a
> xhost +boxb
> on my Woody-Box boxa
> and tried on boxb
> xterm -display boxa:0
>
> I'm sure this was ok some time ago, but now I get
IIMHO
xterm -display boxa:0.0
I got two boxes , weak
Hi,
I did a
xhost +boxb
on my Woody-Box boxa
and tried on boxb
xterm -display boxa:0
I'm sure this was ok some time ago, but now I get
xterm Xt error: Can't open display: boxa:0
Did I miss any change?
--
Hans Gubitz <[EMAIL PROTECTED]>
on Mon, Oct 29, 2001 at 05:54:14PM -0600, Hanasaki JiJI ([EMAIL PROTECTED])
wrote:
Please set your mailer to send text rather than HTML, particularly to
list or Usenet posts.
Thank you.
--
Karsten M. Selfhttp://kmself.home.netcom.com/
What part of "Gestalt" don't you understand?
ed to root and has the display variable set correctly and exported. The other is a common user id that has done xhost +.When I run an X program from the su'ed shell I get an errot "cannot connect" It looks alot like it would if I had not done xhost +. Any thoughts?
XF86v4 d
on Mon, Oct 29, 2001 at 12:17:13PM -0600, Hanasaki JiJI ([EMAIL PROTECTED])
wrote:
> I am running woody and have two shells open in X. One is su'ed to root
> and has the display variable set correctly and exported. The other is a
> common user id that has done xhost +.
>
On Mon, Oct 29, 2001 at 12:17:13PM -0600, Hanasaki JiJI wrote:
| I am running woody and have two shells open in X. One is su'ed to root
| and has the display variable set correctly and exported. The other is a
| common user id that has done xhost +.
|
| When I run an X program from the
I am running woody and have two shells open in X. One is su'ed to root
and has the display variable set correctly and exported. The other is a
common user id that has done xhost +.
When I run an X program from the su'ed shell I get an errot "cannot
connect" It looks alo
I usually run applications remotely and view them on with my xserver.
Since I upgraded to X4, xhost doesnt seem to make any difference.
Secondly, I have noticed that root (through su) can now use the xserver
without 'localhost' being in xhost list. All signs say that xhost is dead.
So,
On Friday 10 November 2000 12:13, GYULAI Mihaly wrote:
> When I try just: 'xhost', it gives me an error -
>
> Xlib: Connection to ":0.0" refused by Server
> Xlib: Client is not authorized to connect to Server
>
> All this I tried as root, previously as user (w
When I try just: 'xhost', it gives me an error -
Xlib: Connection to ":0.0" refused by Server
Xlib: Client is not authorized to connect to Server
All this I tried as root, previously as user (with the same result).
A day before it worked...
Why is it?
--
It used to be that I could open an eterm, su, and open whatever app
I wanted. Now it complains about not being able to connect to the
display. All of the sudden I need to xhost +localhost as non-root in
order to open and windowed apps. This is annoying, how can I make root
have permanent
Blazej Sawionek wrote:
> How do I enable a particular user on a given machine to write on my screen,
> not just anybody who is logged there?
man xauth
Basically, you'll create either a cookie for him and send it to him
or you simply copy your .Xauthority file to the users home directory,
or to
How do I enable a particular user on a given machine to write on my screen, not
just anybody who is logged there?
In particular how to enable another user logged on my machine to write on my
screen?
Blazej
Perhaps you want:
$xhost +localhost
(any user connected to your machine can use the current xsession)
The better method is to:
#export XAUTHORITY=/home//.Xauthority
after su-ing (or add to /root/.bash_profile or whatever)
HTH
Rich
M.C. Vernon wrote:
>
&
Hi,
This is probably a FAQ, but anyway. I'm trying to set things up so
that I can run a root Xterm should I need to. The methodology is:
xhost root@
su
/usr/X11R6/bin/Eterm --icon-name "ROOT" -n "ROOT"
--scrollbar-right -S "red" -b "red" -I
/u
12x24
(those are my own, for hamm). Remember xrdb -merge ~/.Xresources
for immediate effect.
I would also not recommend using xhost. Install ssh on both machines
(and its dependencies, from the non-US part of the distribution) and
then login to machine paladin by typing
ssh paladin
and yo
r xterm, use xterm -font * option, where under -font
> you can specify any font you need. Including sizes.
>
> Another is to add a line to /etc/X11/Xresources that says something like
> XTerm*font: specify your font here.
>
> > 2. I've got two systems I routinely us
our font here.
> 2. I've got two systems I routinely use X apps on, paladin and discover. In
> order to use these machines at the moment, I have to use xhost +paladin
> locally before I login to them. Where can I put something similar so these
> machines are always authorized to
tems I routinely use X apps on, paladin and discover. In
order to use these machines at the moment, I have to use xhost +paladin
locally before I login to them. Where can I put something similar so these
machines are always authorized to open the X server on my machine?
TIA
1 - 100 of 113 matches
Mail list logo
