From: Casey Allen Shobe <lists@seattleserver.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] VPopmail - SUID vchkpw
Date: Thu, 21 Jul 2005 00:28:31 +0000 [thread overview]
Message-ID: <200507210028.31476.lists@seattleserver.com> (raw)
In-Reply-To: <20050720070457.GC11608@curie-int.orbis-terrarum.net>
On Wednesday 20 July 2005 07:04, Robin H. Johnson wrote:
> For common operation of qmail-smtpd, vchkpw is NOT required. SMTP
> AUTH is the only reason qmail-smtpd would call vchkpw.
True. Sorry for not realizing that.
> chsh has also been vetted for security problems a LOT more
> closely than vchkpw. I don't trust vchkpw with suid-root.
Then use suidctl?
> The postfix maintainers were asked about it once before, and the
> answer was that there wasn't enough demand for it. You're only
> the second person that's asked (that I am aware of).
...and I'm not actually asking for it, though it would be nice to be
in the ebuild just for the sake of completeness. I don't actually
know anybody who uses postfix+vpopmail on the vpopmail list.
> This is decidedly not a good idea, unless vchkpw gets locked up
> more so that only specific things can run it (otherwise it can
> easily be used to brute-force passwords).
True. Would the best way to do that be to only give the vpopmail
group execute access to vchkpw, and then add qmail-smtpd to that
group, but still have vchkpw suid?
It seems that su could be easily used to brute-force passwords, too,
but it's suid by default.
Maybe what is needed is an extension to suidctl where emerge checks
any installed binaries against things present in suidctl.conf that
*should* be made suid if they're listed in there even if they're
not suid by default?
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-21 0:30 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 ` [gentoo-dev] VPopmail - SUID vchkpw Casey Allen Shobe
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 ` Casey Allen Shobe [this message]
2005-07-21 2:59 ` [gentoo-dev] " 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=200507210028.31476.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