Date: Mon, 18 Nov 1996 13:27:19 -0800 From: Don Lewis <Don.Lewis@tsc.tdk.com> To: Jeff Aitken <jaitken@cslab.vt.edu>, Don.Lewis@tsc.tdk.com (Don Lewis) Cc: freebsd-security@FreeBSD.org Subject: Re: BoS: Exploit for sendmail smtpd bug (ver. 8.7-8.8.2). Message-ID: <199611182127.NAA16195@salsa.gv.ssi1.com> In-Reply-To: Jeff Aitken <jaitken@cslab.vt.edu> "Re: BoS: Exploit for sendmail smtpd bug (ver. 8.7-8.8.2)." (Nov 18, 3:42pm)
next in thread | previous in thread | raw e-mail | index | archive | help
On Nov 18, 3:42pm, Jeff Aitken wrote: } Subject: Re: BoS: Exploit for sendmail smtpd bug (ver. 8.7-8.8.2). } Don Lewis writes: } > On Nov 18, 2:16pm, Adam Shostack wrote: } > } Subject: Re: BoS: Exploit for sendmail smtpd bug (ver. 8.7-8.8.2). } > } } > } If network access went through the file system, then } > } chown smtp /dev/tcp/smtp would give us a known access control } > } mechanism, rather than trying to extend the process table. } > } > I think mapping network accesses into filesystem space is the way to } > go, but I don't know how to get the semantics right. } } Am I mis-remembering things, or is this exactly the sort of thing the } portal filesystem is supposed to provide? I don't have my 4.4BSD book } handy, but I seem to recall reading about this kind of feature. Sort of, though the classical implementation only allows you to specify the remote address for the network connection. Also, there's no way to do a chown(), so any access rights checking has to be performed by the portal daemon rather than by filesystem permission bits. --- Truck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611182127.NAA16195>