On Fri, 18 Jun 2004, Duane Clark wrote: > Saulius Krasuckas wrote: > > How can we configure it to run "make install" as a 'root' safely? AFAIK > > there is the only way to do it - by writing another script that wraps > > "make install" ands by placing onto the fixed path. This would let write > > all the command name with the fixed path right into the 'sudoers' file. > > I am not sure what you would gain by running "make install" with sudo. It isn't the question about me. It touches countless web references to "sudo make install" created by another people. > If it worked, that would effectively allow you to install any program > anywhere, which gives you complete control of the machine. So that > defeats the purpose of sudo, of allowing a non root user to run certain > privledged programs, without otherwise compromising security. So it > seems to me that if the root user allows sudo make install, then they > might as well just give you the root password. Exactly. I think I have tried to complain about the same thing, just using another words. Really, I am sorry for my poor english. And the reason I am interested in 'sudo' is to avoid typing root password when installing Wine. I understand, my q. should go to some another list, maybe named 'sudo-users', but maybe any user of this list will know how to run particular command (for example "make install") from the only defined directory using sudo? As I've said I can use wrapping script. But I don't like the idea of creating any additional scripts. I would like to know what do all other people use here around. Do all of you use plain 'su -c "make install"' ? Doesn't some of you use 'sudo' ? _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
