On Fri, 31 Aug 2001, Jaco Bongers wrote:
> Charlie Brady wrote:
>
> > No. My guess is that the problem is that the script is not running with
> > sufficient privilege to read the configuration database, and therefore
> > cannot determine that the admin password in fact has been set.
> >
> > Scripts which are run as part of the e-smith manager usually need to have
> > root privilege to interact with critical parts of the system. For this
> > reason, they are mostly setuid root perl scripts.
...
> It seems that the problem is /home/e-smith/configuration is:
> drwx------ 5 admin admin 4096 Mar 30 03:02 Maildir
> -rw-r--r-- 1 root admin 4655 Aug 30 21:15 accounts
> -rw------- 1 root root 3659 Aug 31 10:17 configuration
>
> With no read permissions for the group the script is unable to query the
> e-smith database.
>
> Should these be the permissions on the file? If not, where are they set?
Yes, these are the correct permissions. As I said, the problem is the
permissions of the script (not the permissions of the database), and if
the RPM had been built in the way that we have documented, using the tools
that we have made available, then the script would have the correct
permissions.
--
Charlie Brady [EMAIL PROTECTED]
Lead Product Developer
Network Server Solutions Group http://www.e-smith.com/
Mitel Networks Corporation http://www.mitel.com/
Phone: +1 (613) 368 4376 or 564 8000 Fax: +1 (613) 564 7739
--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL PROTECTED] (only) to discuss security issues
Support for registered customers and partners to [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
