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 work different now?
No. I
Florian Kulzer wrote:
Hmm, on my system that is enough to make Xorg listen to port 6000 (after
I restart kdm). However, looking at /etc/init.d/kdm I get the impression
that in some cases you also have to edit /var/run/kdm/kdmrc to remove
ServerArgsLocal.
If that does not help then I would like t
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 is if X really was started without "-nolisten
>> tcp":
>>
>>
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.
[...]
die...@koal
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.
[...]
>>> die...@koala:~$ xhost +
>>> acce
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 goal is to run X applications via ssh, then I
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.
[...]
>>> die...@koala:~$ xhost +
>>> access control disable
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 from any host
If
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 host
If your goal is to run X applica
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, Feb 24, 2004 at 11:30:13AM -0500, Bill wrote:
> 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 h
On Thu, 11 Sep 2003, ScruLoose wrote:
> On Tue, Sep 09, 2003 at 11:44:22PM -0400, ScruLoose wrote:
> >
> > So I want to log in to X as one regular (non-root) user, and then allow
> > a different regular user to run X apps.
> >
> > Xlib: connection to ":0.0" refused by server
> > Xlib: Client i
On Tue, Sep 09, 2003 at 11:44:22PM -0400, ScruLoose wrote:
>
> So I want to log in to X as one regular (non-root) user, and then allow
> a different regular user to run X apps.
>
> Xlib: connection to ":0.0" refused by server
> Xlib: Client is not authorized to connect to Server
Okay, got a
* 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://www.doorstop.net/
--
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 commentaries; d'auteurs il en est
on Tue, Sep 09, 2003 at 11:44:22PM -0400, ScruLoose ([EMAIL PROTECTED]) wrote:
> Hey folks,
>
> So I want to log in to X as one regular (non-root) user, and then allow
> a different regular user to run X apps.
>
> After getting this error:
> Xlib: connection to ":0.0" refused by server
> Xlib
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 recen
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:
> As user:
> xhost
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
>} export DISPLAY=:0
>}
>} Then I can load
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
} export DISPLA
On Sat, 26 Oct 2002 11:31:12 -0700, Earl F Hampton wrote:
>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 gr
On Sat, 26 Oct 2002 11:31:12 -0700, Earl F Hampton wrote:
>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 gr
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'm trying to use xhost +localhost
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.
> >
> > I'm trying to use xhost
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 'xhost + localhost' (and not +localhost
Hello,
In fact, this come from the '-nolisten tcp' X option in
/etc/X11/xinit/xserverrc
This option disable the tcp connection . And something strange,
the local connection is tcp !
François
On Tue, 8 Jan 2002 18:18:06 -0600 (
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'. xhost will only all
--- 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 one and strong one, connected
via plip, and
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 (with the same result).
>
> A day before
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
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,
>
>
On Mon, 1 Feb 1999, Richard Hall wrote:
> According to the man pages, xhost uses a file called "/etc/X*.hosts". I
> haven't got this file. There are several /etc/host* files, none of which
> control X access, and no *host* files in /etc/X11. So where is the file
> that xhost uses to control acc
Hi Richard
> According to the man pages, xhost uses a file called "/etc/X*.hosts". I
> haven't got this file. There are several /etc/host* files, none of which
> control X access, and no *host* files in /etc/X11. So where is the file
> that xhost uses to control access to my X server?
>
> Than
On Fri, 26 Jun 1998 [EMAIL PROTECTED] wrote:
: Ok, so the gov't thinks strong encryption is munitions so you can't export it.
: Why have non-us.debian.org: You can't import it either? Or you just can't use
: it at all in the US?
Uh, you can import and use the software, but you can't _export_ it f
Ok. The government of the USA classifies encryption code as a munition, ie a
tool of war; presumably because it is in fact used during wars to stop the
enemy from recieving messages intended for your own side. Ok. So, there is also
this law about not exporting munitions from the USA. Also a USA-spe
Ok, so the gov't thinks strong encryption is munitions so you can't export it.
Why have non-us.debian.org: You can't import it either? Or you just can't use
it at all in the US?
.Not like making _rules_ about import and export can actually stop what
people do with source available on the net?.
Can someone explain the deal with encryption and the US? Why all the
drama with having to use non-us.debian.org and all that to get ssh? Are people
living in the US not allowed to use ssh etc? And why all the fuss over
gov't approved 128bit DES not being strong enough when one can simply us
>> "GL" == 44 1785 248131 writes:
GL> I am trying to configure my debian 1.3.1 box to allow me to run X
GL> programs from
GL> the root account when I am logged in as another user, this is because
GL> the root
GL> Also I have root's profile script set to export the DISPLAY environment
GL> varia
-> I am trying to configure my debian 1.3.1 box to allow me to run X
-> programs from the root account when I am logged in as another user, this
-> is because the root account is locked so I have to 'su' to root, the
-> problem I am having is that before I 'su' to root I have to run xhost
-> . Is
If you always su to root from the same account (as i do), you can
simply create a symbolic link from /root/.Xauthority to
/home/xyz/.Xauthority (with xyz being your user name).
Stefan
__
Stefan Gödel <[EMAIL PROTECTED]> Deu
47 matches
Mail list logo
