From: Casey Allen Shobe <lists@seattleserver.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] VPopmail - SUID vchkpw
Date: Wed, 20 Jul 2005 05:37:19 +0000 [thread overview]
Message-ID: <200507200537.19793.lists@seattleserver.com> (raw)
In-Reply-To: <20050720024334.GA26639@curie-int.orbis-terrarum.net>
On Wednesday 20 July 2005 02:43, Robin H. Johnson wrote:
> This problem IS fixed in ~arch:
>
> line 190 of both vpopmail-5.4.10.ebuild and
> vpopmail-5.4.9-r2.ebuild: chmod 4711 ${D}${VPOP_HOME}/bin/vchkpw
Ahh okay, that explains things a bit. I'm using x86, which means
5.4.6.
> So if this is still a problem in arch, but works in ~arch, you
> SHOULD file a bug report.
Why not just wait for the newer releases to make it to arch?
> However the original reasoning for vchkpw NOT being setuid was
> that setuid is NOT always needed depending on which backend you
> are using.
I can confirm that - bincimap and qmail-pop3d run as root, so the
setuid bit is not necessary. I believe this is also the case for
dovecot 1.0 beta releases, though there are no ebuilds for them so
I haven't yet tested (<1.0 releases use libvpopmail directly
instead of the checkpassword interface). However it is necessary
for any server running as a non-root user, i.e. qmail-smtpd.
Thus I believe this should have the same treatment as binaries like
chsh - they won't work for non-root users without the setuid bit,
but running as a non-root user is generally accepted. If I want to
be paranoid (which I am), I can use suidctl (which I do), and only
uncomment the binary when I discover the need to. There's not
really any reverse of suidctl to my awareness.
Nor is there a use flag for qmail or similar on vpopmail, but the
vpopmail ebuild requires qmail regardless of USE settings (postfix
support is not present), so at least in the current state, since
the package is built for qmail, it should assume qmail's non-root
qmail-smtpd will need to access vchkpw.
I would encourage making vchkpw suid even if postfix is supported
and used instead of qmail, because there are other softwares (i.e.
IMAP & POP servers) which have a checkpassword interface which do
may not run as the root user.
> And as I've mentioned before I'd like MORE reports of packages
> working well before they are moved to stable arch. Without those
> stable working reports I don't have any means to judge just how
> much testing has been done on a package, other than my own use of
> a package (and as such I do leave things longer than the 30 days,
> because I don't entirely trust them).
This sounds like a request for the QA team. I tend to stay away
from most ~arch packages simply because most of our systems are
live production servers, but I'd be happy to test-drive new ebuilds
of vpopmail if it would help get new versions into the stable tree
faster.
Cheers,
--
Casey Allen Shobe | http://casey.shobe.info
cshobe@seattleserver.com | cell 425-443-4653
AIM & Yahoo: SomeLinuxGuy | ICQ: 1494523
SeattleServer.com, Inc. | http://www.seattleserver.com
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-20 5:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-20 1:32 [gentoo-dev] Abuse by gentoo developer Casey Allen Shobe
2005-07-20 1:41 ` Mauricio Lima PIlla
2005-07-20 1:42 ` Mike Frysinger
2005-07-20 2:21 ` Nathan L. Adams
2005-07-20 2:20 ` Mike Frysinger
2005-07-20 2:35 ` Allen Parker
2005-07-20 2:17 ` Daniel Goller
2005-07-20 5:43 ` Casey Allen Shobe
2005-07-20 2:43 ` Robin H. Johnson
2005-07-20 5:37 ` Casey Allen Shobe [this message]
2005-07-20 5:43 ` [gentoo-dev] QA feedback Mike Frysinger
2005-07-20 13:47 ` Chris Gianelloni
2005-07-23 8:06 ` Stuart Longland
2005-07-20 7:04 ` [gentoo-dev] VPopmail - SUID vchkpw Robin H. Johnson
2005-07-20 10:13 ` [gentoo-dev] " Duncan
2005-07-21 0:28 ` [gentoo-dev] " Casey Allen Shobe
2005-07-21 2:59 ` Robin H. Johnson
2005-07-21 0:32 ` Mike Frysinger
2005-07-21 5:15 ` Casey Allen Shobe
2005-07-22 8:45 ` [gentoo-dev] " Duncan
2005-07-20 9:54 ` [gentoo-dev] Re: Abuse by gentoo developer Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200507200537.19793.lists@seattleserver.com \
--to=lists@seattleserver.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox