On Wed, 8 Sep 1999, Russell Nelson wrote:
> Dmitry Niqiforoff writes:
> > Yesterday I found that any user are able to start any program at
> > server with .qmail file. This could be potentially dangerous, AFAIU.
>
> Only if you let users edit their own .qmail files. Don't. Deny them
> write permission in their home directory. If they need to upload
> html, give them write permission in public_html. If you really,
> *really* need to allow them to change their .qmail files, give them a
> "qmail" home directory, and have a root cron job which copies .qmail
> files from that directory into their home directory, editing out
> program deliveries on the way.
Will this work? What I did was edited qmail-local.c and changed the
/bin/sh to /bin/qsh. Then copied /bin/sh to /bin/qsh and removed all
rights to 'other'. It tests ok, non priv'd users can't exec env whereas
priv'd users can from within a .qmail file. Could I be missing something?
If not, perhaps Dan can add this to qmail2 (provided he didn't already
come up with something). If this works I'll write something up for
www.qmail.org.
Vince.
--
==========================================================================
Vince Vielhaber -- KA8CSH email: [EMAIL PROTECTED] flame-mail: /dev/null
# include <std/disclaimers.h> TEAM-OS2
Online Campground Directory http://www.camping-usa.com
Online Giftshop Superstore http://www.cloudninegifts.com
==========================================================================
