--- Jeremy Kitchen <[EMAIL PROTECTED]> wrote:
> On Wed, 2004-03-24 at 22:29, ep wrote:
> > Hi, after I add a new domain via vpopmail, like this:
> > ~vpopmail/bin/vadddomain -i 510 -d 510 somedomain.com password123
> > 
> > i cannot log in with this domain in qmailadmin!  if i leave out the
> -i
> > and -d flags & arguments, it works, but i want to store the
> "domains"
> > directory under the home dir of a specific user on the system, not
> > under vpopmail's home dir.  so i add the -i and -d, w/ vadddomain. 
> it
> > creates the dir's and files in 510's home dir, it adds the info in
> > qmail's "assign" file, but no success logging in as postmaster with
> > qmailadmin.  what is the prob?
> 
> permissions.
> 
> qmailadmin by default is setuid vpopmail.  The vpopmail user doesn't
> have access to read the files you created with vadddomain under the
> different uid/gid.
> 
> solution:  make qmailadmin setuid root
> 
> -Jeremy
> 
> -- 
> Jeremy Kitchen
> Systems Administrator
> [EMAIL PROTECTED]
> Kitchen @ #qmail on EFNet - Join the party!
> .....................
> Inter7 Internet Technologies, Inc.
> www.inter7.com
> 866.528.3530 toll free
> 847.492.0470 int'l
> 847.492.0632 fax
> GNUPG key ID: 93BDD6CE
> 

hi, thanks for the response.  i'm still having trouble with this.  how
exactly do I make qmailadmin setuid root?  is it something i have to do
at compile time?  right now, qmailadmin is located in my web server's
cgi-bin and is chown root.root and chmod 6755.  apache runs as
nobody/nobody.  i created a tiny php script in the same cgi-bin to
setuid root and then display the current uid. i set the same
permissions on this php script (owned by root/root, 6755). it displayed
"99" (nobody).  my apache has suexec, but no User/Group directives in
the VirtualHost part, so it defaults to running scripts as
nobody/nobody. ~ep

Reply via email to