When I type ./setup to install EPS Printpro I get the following error: Xlib: connection to ":0.0" refused by server Xlib: No protocol specified Can't open display: :0.0 What gives?????? thx
On Mon, 2004-03-01 at 19:15, Don Emmack wrote:
When I type ./setup to install EPS Printpro I get the following error:
Xlib: connection to ":0.0" refused by server Xlib: No protocol specified
Can't open display: :0.0
What gives?????? thx
Don, Are you doing the setup as root (su -), if so, open another terminal session and type "xhost +", and try ./setup again. Rudolf
* rudolf
Are you doing the setup as root (su -), if so, open another terminal session and type "xhost +", and try ./setup again.
No, 'xhost x' is *very* insecure. The command to use is 'sux'. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org
On Monday 01 March 2004 3:11 pm, Patrick Shanahan wrote:
No, 'xhost x' is *very* insecure. The command to use is 'sux'.
I can't find a manpage entry for sux, so I can't learn more about it. But my little bit of experimentation suggests that it has very different functionality from xhost. In particular, with xhost it's possible to use sudo so that root commands can be executed without a password. Now I realize that some people feel that using sudo is a terrible idea -- but if you accept its use, is there any way then to execute X commands locally that require root privilege without having to specify a password? Paul Abrahams
* Paul W. Abrahams
I can't find a manpage entry for sux, so I can't learn more about it. But my little bit of experimentation suggests that it has very different functionality from xhost. In particular, with xhost it's possible to use sudo so that root commands can be executed without a password.
sux is su with access to X.
Now I realize that some people feel that using sudo is a terrible idea -- but if you accept its use, is there any way then to execute X commands locally that require root privilege without having to specify a password?
sudo _should_not_ allow you to operate root priv w/o password unless you have specifically altered /etc/sudoers. And if you did, you apparently do not care about security. sudo is a *good* thing when used as intended. But it does not allow access to X. -- Patrick Shanahan Registered Linux User #207535 http://wahoo.no-ip.org @ http://counter.li.org
On Monday 01 March 2004 3:42 pm, Patrick Shanahan wrote:
sudo _should_not_ allow you to operate root priv w/o password unless you have specifically altered /etc/sudoers. And if you did, you apparently do not care about security.
I'd say that the security one needs depends on one's situation. In my case I have a home network sitting behind a router, so there are two kinds of possible threats: ones originating from within my house and ones from outside. The ones from within the house I don't worry about, particularly since a malevolent person with time and knowledge could do just about anything by rebooting from a rescue CD (and there aren't any malevolent persons around as far as I know). As to the outside, the router is a pretty effective firewall; even an intruder who knew my root password would have a very hard time putting it to destructive use. Things like email viruses are another matter, but so far the virus writers don't seem to consider Linux mailers a worthwhile target. Paul Abrahams
* Paul W. Abrahams (abrahams@acm.org) [040301 13:41]:
On Monday 01 March 2004 3:42 pm, Patrick Shanahan wrote:
sudo _should_not_ allow you to operate root priv w/o password unless you have specifically altered /etc/sudoers. And if you did, you apparently do not care about security.
It's not that one doesn't care about security. I for one don't like logging in as root and what if a cracker got in a replaced su or sux with something they wrote? How would you know? You wouldn't unless you had tripwire or something else. I have NO ONE in my /etc/sudoers file except myself and the entry is as follows.... ben ALL=(ALL) NOPASSWD:ALL This lets me do things like " sudo yast2 " and run it in X so that I can do what I need to do and as soon as the program exits ..poof.. everything is back to normal user. So if your trying to display programs and such remotely why not to it through an ssh tunnel?
Things like email viruses are another matter, but so far the virus writers don't seem to consider Linux mailers a worthwhile target.
This is true...because Mutt had a security issue not so long ago that would have been a nice target for script kiddies. But then again people who use mutt aren't easy to social engineer to just fire off anything at will. :) -- Linux User #147972 ---===--- mailto:ben@whack.org -- "There is no need to teach that stars can fall out of the sky and land on a flat Earth in order to defend religious faith."
participants (5)
-
Ben Rosenberg -
Don Emmack -
Patrick Shanahan -
Paul W. Abrahams -
rudolf