Date: Wed, 25 Feb 2004 02:59:22 +0300 From: Andrey Chernov <ache@nagual.pp.ru> To: John Baldwin <jhb@FreeBSD.ORG> Cc: kientzle@acm.org Subject: Re: What to do about nologin(8)? Message-ID: <20040224235920.GA32548@nagual.pp.ru> In-Reply-To: <200402241027.58978.jhb@FreeBSD.org> References: <6.0.1.1.1.20040223171828.03de8b30@imap.sfu.ca> <200402231553.34677.jhb@FreeBSD.org> <403A7DD0.2090802@kientzle.com> <200402241027.58978.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Feb 24, 2004 at 10:27:58AM -0500, John Baldwin wrote: > > Armoring nologin(8) is insufficient. Yes. > > In particular, as David Schultz pointed out, there are a lot > > of home-grown nologin scripts out there that are potentially > > vulnerable regardless of what we do with the "official" > > nologin program. > > Then do both. :) People please be aware that it is not nologin problem at all, so please not touch nologin in this direction. F.e. any 3rd party shell from ports or any home-grown admin shells/scripts _generally_ suffer of this problem. It means that login, telnetd, su etc. whatever log in and call shell should be fixed to never pas LD_* variables to the shell. Don't pick one particular shell (nologin) and think you are secure. -- Andrey Chernov | http://ache.pp.ru/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040224235920.GA32548>