Date: Fri, 22 Nov 1996 10:27:20 +1030 (CST) From: newton@communica.com.au (Mark Newton) To: pjchilds@imforei.apana.org.au (Peter Childs) Cc: newton@communica.com.au, freebsd-security@freebsd.org, miff@spam.frisbee.net.au Subject: Re: BoS: Exploit for sendmail smtpd bug (ver. 8.7-8.8.2). Message-ID: <9611212357.AA14971@communica.com.au> In-Reply-To: <199611211112.VAA27330@al.imforei.apana.org.au> from "Peter Childs" at Nov 21, 96 09:42:22 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Childs wrote:
> Could an additional check in here just be used to check that if port
> requested is 25 and uid == mailmanager's uid then OK it?
Only if everyone wanted to roll their own patch: There is no mail manager
uid on FreeBSD in the standard installation, and there's no reason to
think that everyone who added one would use the same id.
That's certainly the right place to put any additional security mechanisms,
but I think we need one a bit more generic than that. I like the sysctl
idea, but it'd make sysctl -a unwieldy.
There is another way, though: Consider nfs serving -- mountd reads
/etc/exports, parses its contents, fills in the relevent fields of a data
structure which describes which filesystems are to be exported, and pushes
that data structure into the kernel via a system call. Why not employ
a similar mechanism to read a config file which describes which users can
bind to which ports and syscalls it into the kernel to fulfil a task
similar to what the sysctl idea was attempting to acheive but without
the elephantine MIB?
Just an idea...
- mark
---
Mark Newton Email: newton@communica.com.au
Systems Engineer Phone: +61-8-8373-2523
Communica Systems WWW: http://www.communica.com.au
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9611212357.AA14971>