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 > let root log into X than otherwise? why is not letting root start X > client after su/sudo by default a good policy? I just feel it is a > bit funny, root can do anything, it just can't open a damn window. > Maybe I really need to dig into xauth manual for an answer. > > Lei > > >Or you can try "sux" > > > > > > > > > ># apt-cache show sux > >Package: sux > >Priority: optional > >Section: admin > >Installed-Size: 64 > >Maintainer: Millis Miller <[EMAIL PROTECTED]> > >Architecture: all > >Version: 1.0.1-3 > >Recommends: xbase-clients > >Filename: pool/main/s/sux/sux_1.0.1-3_all.deb > >Size: 8560 > >MD5sum: 868e114a14297b521a55a329c45c7d3b > >Description: wrapper around su which will transfer your X credentials > > Sux is a wrapper around the standard su command which will transfer > > your X credentials to the target user. > > . > > http://sourceforge.net/projects/sux/ > > ( from http://fgouget.free.fr/sux/ ) > >Tag: admin::login, interface::commandline, security::authentication, > >use::login, x11::application > > > > If your X system is configured to accept remote connections, it may be possible for a remote user to hijack the root X session thereby compromising system security. As a result, root access to X has been restricted unless you know what you're doing. Therefore, if you know how to disable the restriction, you know enough to know what you're doing :)
-- Your mouse has moved. Windows needs to be restarted for the changes to take effect. [OK]
signature.asc
Description: This is a digitally signed message part
