On Wed, Jan 18, 2006 at 10:15:57PM -0500, [EMAIL PROTECTED] wrote:
> I've been told that if a process has a window on an X server, it can
> create fake events on any of the windows on the X server. This was,
> ages ago, a building block for various nice user interfaces, decades
> before anybody
On Wed, Jan 18, 2006 at 10:53:01AM -0500, Peter McAlpine wrote:
> Thanks, but I'm also interested in hearing how to disable all access
> control for remote connections. How can I do this?
Possibly by asking in your own thread: hijacking this one makes for some
very confusing reading.
--
Jon Dowl
On Tue, 17 Jan 2006 17:29:35 -0500
Lei Kong <[EMAIL PROTECTED]> wrote:
> I have a strange problem with my thinkpad z60t, running debian testing.
> I ran these commands in konsole or xterm under kde:
>
> $xhost +
> $ sudo -s
> #kedit
> kedit: cannot connect to X server
>
> What is wrong?
If you
John Hasler wrote
X and X applications are exceedingly complex, unaudited, and likely to be
chock full of buffer overruns, format string vulnerabilities, and other
I guess a checking on CERT's vulnerability list will reveal if this is true, X
vs
non-X.
nasties. Consider the segfaults and m
Le Mercredi 18 Janvier 2006 16:53, Peter McAlpine a écrit :
> On Wed, Jan 18, 2006 at 03:37:25PM +, Noah Dain wrote:
> > On 1/18/06, Peter McAlpine <[EMAIL PROTECTED]> wrote:
> > > Security feature or not... when I'm troubleshooting I sometimes want
> > > this disabled. If 'xhost +' no longer d
I wrote:
> Because neither X nor any X applications are secure.
Lei writes:
> True, root X session over network is insecure...
True, but not what I meant.
> What is the security concern for local root X session?
X and X applications are exceedingly complex, unaudited, and likely to be
chock ful
As about the security concern, why is it more secure not to let root log
into X than otherwise? why is not letting root start X client after
su/sudo by default a good policy?
Because neither X nor any X applications are secure.
True, root X session over network is insecure,
but how about us
Lei Kong wrote:
> As about the security concern, why is it more secure not to let root log
> into X than otherwise? why is not letting root start X client after
> su/sudo by default a good policy?
Because neither X nor any X applications are secure.
--
John Hasler
--
To UNSUBSCRIBE, email to [
On Wed, Jan 18, 2006 at 08:55:58PM -0500, Lei Kong wrote:
> thanks, sux works beautifully.
> but still I don't understand why sudo -s has problems,
> and on my desktop, on problem at all, and I don't remember
> doing special thing on it.
>
> As about the security concern, why is it more secure not
On Wed, 2006-01-18 at 20:55 -0500, Lei Kong wrote:
> thanks, sux works beautifully.
> but still I don't understand why sudo -s has problems,
> and on my desktop, on problem at all, and I don't remember
> doing special thing on it.
>
> As about the security concern, why is it more secure not to
> l
$xhost +
$ sudo -s
#kedit
kedit: cannot connect to X server
Leave off the xhost line when using sudo. It inheirets the parent shell's
environment.
I did try it without xhost+ first, didn't work.
The inherit thing is default, or I need to configure it?
On my desktop, sudo -s does allow
thanks, sux works beautifully.
but still I don't understand why sudo -s has problems,
and on my desktop, on problem at all, and I don't remember
doing special thing on it.
As about the security concern, why is it more secure not to
let root log into X than otherwise? why is not letting root start
I tried it, and it works with su, but not su - or sudo -s
then I removed these lines, and guess what,
it still allows me to open a window with su, and su -
and sudo -s still fail, mysterious, huh?
In summary, sudo -s never allows me to start an X client.
On my another machine, I never had any pr
> On Wed, Jan 18, 2006 at 12:17:27AM +, Martin OConnor wrote:
> > On Tue, 2006-01-17 at 17:29 -0500, Lei Kong wrote:
> > > Hi,
> > >
> > > I have a strange problem with my thinkpad z60t, running debian testing.
> > > I ran these commands in konsole or xterm under kde:
> > >
> > > $xhost +
> >
On Wed, Jan 18, 2006 at 03:37:25PM +, Noah Dain wrote:
> On 1/18/06, Peter McAlpine <[EMAIL PROTECTED]> wrote:
> > Security feature or not... when I'm troubleshooting I sometimes want
> > this disabled. If 'xhost +' no longer disables all access control, I'd
> > be interested in hearing the new
On 1/18/06, Peter McAlpine <[EMAIL PROTECTED]> wrote:
> Security feature or not... when I'm troubleshooting I sometimes want
> this disabled. If 'xhost +' no longer disables all access control, I'd
> be interested in hearing the new way to it.
>
> Thanks,
> -Peter
>
> On Wed, Jan 18, 2006 at 12:17:
Security feature or not... when I'm troubleshooting I sometimes want
this disabled. If 'xhost +' no longer disables all access control, I'd
be interested in hearing the new way to it.
Thanks,
-Peter
On Wed, Jan 18, 2006 at 12:17:27AM +, Martin OConnor wrote:
> On Tue, 2006-01-17 at 17:29 -050
theo wrote:
> Hi,
>
>
> Lei Kong wrote:
>>> $xhost +
>>> $ sudo -s
>>> #kedit
>>> kedit: cannot connect to X server
> You may want to try
> sudo -H kedit
> or reconsider using X applications as root.
>
> You can also try
> sudo -H bash
> or
> sudo -H xterm
> if you want a root shell able to use
On Tuesday 17 January 2006 14:29, Lei Kong wrote:
> $xhost +
> $ sudo -s
> #kedit
> kedit: cannot connect to X server
Leave off the xhost line when using sudo. It inheirets the parent shell's
environment.
--
Paul Johnson
Email and IM (XMPP & Google Talk): [EMAIL PROTECTED]
Got Jabber? http:/
On Tuesday 17 January 2006 19:17, you wrote:
> On Tue, 2006-01-17 at 17:29 -0500, Lei Kong wrote:
> > Hi,
> >
> > I have a strange problem with my thinkpad z60t, running debian testing.
> > I ran these commands in konsole or xterm under kde:
> >
> > $xhost +
> > $ sudo -s
> > #kedit
> > kedit: cann
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Lei Kong wrote:
> $xhost +
> $ sudo -s
> #kedit
> kedit: cannot connect to X server
You may want to try
sudo -H kedit
or reconsider using X applications as root.
You can also try
sudo -H bash
or
sudo -H xterm
if you want a root shell able to us
On Tue, 2006-01-17 at 17:29 -0500, Lei Kong wrote:
> Hi,
>
> I have a strange problem with my thinkpad z60t, running debian testing.
> I ran these commands in konsole or xterm under kde:
>
> $xhost +
> $ sudo -s
> #kedit
> kedit: cannot connect to X server
>
> What is wrong?
> My desktop runs d
22 matches
Mail list logo
