Hi guys, bug 4439 describes a problem where a machine (running ubuntu) does not install wine when using wineinstall due to the fact that su dos not work..
Just a couple of questions:
Is this the case (su not working) on all Ubuntu machines, or just something broken on that users' machine?
If it is the case on all Ubuntu machines, the user has mentioned that sudo does work. sudo does require configuration prior to being used, but we could always add into the wineinstall script to configure sudo for the user, or we could ask the user to configure it themself, OR we could fall back to using su if the user answers no to having used sudo.. see below:
./tools/wineinstall
Warning: the wineinstall script installs wine using the sudo command. Have you ever used sudo on this machine before? if (yes) continue as normal else # either of these could work # option 1 Would you like to have us try to configure sudo for you? # option 2 User has not used or configured sudo, falling back to su WARNING: su may be broken on your machine, and therefore wine may be built but not installed. If you are unable to run wine after this script completes, please login as root, and do 'make install' then login as your user again.
Of course we could always just add a configure check to see if su works, and if it doesnt, die with a warning about wineinstall not working because of that.
What do you think guys?
Tom
On 1/30/06, Tom Spear (Dustin Booker, Dustin Navea) speeddymon@gmail.com wrote:
Hi guys, bug 4439 describes a problem where a machine (running ubuntu) does not install wine when using wineinstall due to the fact that su dos not work..
Just a couple of questions:
Is this the case (su not working) on all Ubuntu machines, or just something broken on that users' machine?
I think Ubuntu comes without a set root password. This is to try to dumb down the idea of having a root user (just my take on it).
If it is the case on all Ubuntu machines, the user has mentioned that sudo does work. sudo does require configuration prior to being used, but we could always add into the wineinstall script to configure sudo for the user, or we could ask the user to configure it themself, OR we could fall back to using su if the user answers no to having used sudo.. see below:
Configuring or requiring an allow-everything sudo for people is a bad idea, as it weakens security on the machine.
What would be much better and simpler for the user, is if you had to start the wineinstall script as root (using su, sudo, whatever is appropriate for the distribution/setup) and it would run a seperate process as a non-root user to perform the compiling, etc, and bits that need root would be run by the wineinstall script directly.
n0dalus.
On 1/29/06, Tom Spear (Dustin Booker, Dustin Navea) speeddymon@gmail.com wrote:
Hi guys, bug 4439 describes a problem where a machine (running ubuntu) does not install wine when using wineinstall due to the fact that su dos not work..
Just a couple of questions:
Is this the case (su not working) on all Ubuntu machines, or just something broken on that users' machine?
I believe it's a distro-specific design choice (for security) of Ubuntu, and maybe even Debian.
If it is the case on all Ubuntu machines, the user has mentioned that sudo does work. sudo does require configuration prior to being used, but we could always add into the wineinstall script to configure sudo for the user, or we could ask the user to configure it themself, OR we could fall back to using su if the user answers no to having used sudo.. see below:
If the user is not in the /etc/sudoers configuration file, it just complains you're not in the configuration and asks for the root password.
What do you think guys?
I think we should see if su exists/works and use it if it does, else use sudo.
-- James Hawkins
On 1/30/06, James Hawkins truiken@gmail.com wrote:
If the user is not in the /etc/sudoers configuration file, it just complains you're not in the configuration and asks for the root password.
/etc/sudoers is not usually world-readable. The way to do it would be with `sudo -l`, but this requires the user's password, and we'd have to parse any fine-grained security options.
Is there another way of checking to see if su(do) works?
I still think a good way would be to have the script run as root and execute a child process as a non-root user for compiling and stuff. The problem is working out what user to run as.
Alternatively, we could just split wineinstall into winecompile and wineinstall.
n0dalus.
On 1/29/06, n0dalus n0dalus+redhat@gmail.com wrote:
On 1/30/06, James Hawkins truiken@gmail.com wrote:
If the user is not in the /etc/sudoers configuration file, it just complains you're not in the configuration and asks for the root password.
/etc/sudoers is not usually world-readable. The way to do it would be with `sudo -l`, but this requires the user's password, and we'd have to parse any fine-grained security options.
I think you misunderstood what I'm saying. We don't check /etc/sudoers for the user's configuration. If the user is not in /etc/sudoers and the user runs sudo, the sudo program complains that the user is not in the configuration and asks for the root password.
-- James Hawkins
James Hawkins wrote:
If the user is not in the /etc/sudoers configuration file, it just complains you're not in the configuration and asks for the root password.
That is apparently distro-specific, as the last time I used sudo on my Slackware 10.2 box (a few months ago), as well as on my roommate's RH9 box, it wouldnt allow sudo period unless /etc/sudoers was configged for your user.
Tom
-
James Hawkins -
n0dalus -
n0dalus -
Tom Spear (Dustin Booker, Dustin Navea)