From owner-freebsd-security@FreeBSD.ORG  Tue Mar 31 13:31:15 2015
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 5CF7A61D
 for <freebsd-security@freebsd.org>; Tue, 31 Mar 2015 13:31:15 +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 10EC834D
 for <freebsd-security@freebsd.org>; Tue, 31 Mar 2015 13:31:15 +0000 (UTC)
Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1YcwG9-00077t-2t; Tue, 31 Mar 2015 16:31:13 +0300
Date: Tue, 31 Mar 2015 16:31:13 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Willem Jan Withagen <wjw@digiware.nl>
Subject: Re: ftpd don't record login in utmpx
Message-ID: <20150331133112.GB23643@zxy.spb.ru>
References: <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>
 <20150331110215.GZ23643@zxy.spb.ru> <551A9759.2020004@digiware.nl>
 <20150331130018.GA23643@zxy.spb.ru> <551A9E01.90503@digiware.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <551A9E01.90503@digiware.nl>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
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\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Mar 2015 13:31:15 -0000

On Tue, Mar 31, 2015 at 03:15:45PM +0200, Willem Jan Withagen wrote:

> On 31-3-2015 15:00, Slawa Olhovchenkov wrote:
> 
> >> Check:
> >> man utempter_add_record
> >>
> >> If you want the old behaviour, you have to dig into the code, and DIY.
> > 
> > I understund, thanks.
> > 
> >>
> >> Bluntly put: I don't think anybody is going to fix YOUR problem. If only
> >> because in 5 years time nobody had an issue with it.
> > 
> > Now I see root of problem.
> > I can choose what do: patch ftpd, do nothing or something else.
> 
> Sort of sorry, but yes.
> 
> And then those are the 3 options with every piece of open source
> software. Whereas with closed software, option 1 would be a no-go.

I know what is open source software.
I know what different with closed software.
I am don't ask about this.
And I am don't ask what I need do.
I just ask about cause of behaviors changed -- commit messages not
cleary explain this.
Thanks again, you cleary explain root cause.