public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] VPopmail - SUID vchkpw
Date: Wed, 20 Jul 2005 19:59:43 -0700	[thread overview]
Message-ID: <20050721025943.GA32187@curie-int.orbis-terrarum.net> (raw)
In-Reply-To: <200507210028.31476.lists@seattleserver.com>

[-- Attachment #1: Type: text/plain, Size: 2198 bytes --]

On Thu, Jul 21, 2005 at 12:28:31AM +0000, Casey Allen Shobe wrote:
> > 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?
I do on my production machines.

> > 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.
For the sake of completeness and as an academic exercise, I'll accept
tested patches for it ;-).

> > 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?
On the vpopmail list in the distant past, I recall mention of the
concept of an authentication server, so you could have vchkpw without
any additional permissions. Nobody took it up at the time, and I never
heard of it again. However it would be one of the best routes to solve
this. Just implement the checkpassword interface on a socket, and be
done with it.

> It seems that su could be easily used to brute-force passwords, too, 
> but it's suid by default.
Yes, but su does more logging than vchkpw ;-).

> 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?
This is getting into cfengine territory (which can do exactly what
you're asking for here).

-- 
Robin Hugh Johnson
E-Mail     : robbat2@orbis-terrarum.net
Home Page  : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ#       : 30269588 or 41961639
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

[-- Attachment #2: Type: application/pgp-signature, Size: 241 bytes --]

  reply	other threads:[~2005-07-21  3:03 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       ` [gentoo-dev] " Casey Allen Shobe
2005-07-21  2:59         ` Robin H. Johnson [this message]
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=20050721025943.GA32187@curie-int.orbis-terrarum.net \
    --to=robbat2@gentoo.org \
    --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