From owner-freebsd-security@FreeBSD.ORG Tue Mar 31 11:02:19 2015 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 509AE5D5 for ; Tue, 31 Mar 2015 11:02:19 +0000 (UTC) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 05E07FAC for ; Tue, 31 Mar 2015 11:02:19 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1Yctvz-00043c-NW; Tue, 31 Mar 2015 14:02:15 +0300 Date: Tue, 31 Mar 2015 14:02:15 +0300 From: Slawa Olhovchenkov To: Willem Jan Withagen Subject: Re: ftpd don't record login in utmpx Message-ID: <20150331110215.GZ23643@zxy.spb.ru> References: <20150330142543.GD74532@zxy.spb.ru> <44y4me9gfi.fsf@lowell-desk.lan> <20150331034402.GE74532@zxy.spb.ru> <551A561C.5000904@digiware.nl> <20150331084426.GX23643@zxy.spb.ru> <551A6A1D.5030307@digiware.nl> <20150331094915.GY23643@zxy.spb.ru> <551A76B4.6050306@digiware.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <551A76B4.6050306@digiware.nl> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: freebsd-security@freebsd.org X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 11:02:19 -0000 On Tue, Mar 31, 2015 at 12:28:04PM +0200, Willem Jan Withagen wrote: > >> Slawa, > >> > >> I can't tell you that, but it is in r202209. And you can ask the one > >> that removed it (ed@). :) > >> Like r202209 says 5 years ago: > >> Maybe we can address this in the future if it turns out to be a > >> real issue. > > > > What about issue talk? > > Opened file outside chroot? /dev/null and /var/run/logpriv still opened. > > Disabling logging for chrooted accounts? Realy?! > > Read the submit message!? The reason is there, nothing with security as > I read it, but it just did not fit into the way the new lib for wtmp > worked/works. I read it. And I don't understund it. May be I don't know somewere. Or missed. Can you explain? > Clearly you do not agree, but you are rather late to the party. > > Could be that in the mean time code has been added to wtmp, and now you > can do it from inside a chroot? Perhaps ask ed@ of on hackers@?? First I am ask security@. Logging login and logout -- security task. > >> Hasn't been an issue uptill now, it seems. > >> > >> But then there are many flavours of FTP server out there ATM, so freely > >> quoted from Andy Tannenbaum: > >> If you don't like this version, get another one. > > > > Now I only see removing old and working functionality w/o reassonable > > Well that is only in your eyes. wtmp moved (on) to a different way of > storing the data. At that point in time nobody had a problem with that. > And in 5 years you are the first one to be vocal about it. All others still using old version? > >> Or write a script that actually unites the output from either the > >> database and/or last(8). > > > > You kidding. > > For this I need rearange ALL ftp acconts. Change permissions. Create > > hieararhie. Learn users. > > Well perhaps one of the other flavours of FTPDs suits your need better. I don't ask what I need do. I just ask why switch off logging. What issues may be happen?