From owner-freebsd-current@FreeBSD.ORG  Fri May 10 21:36:12 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id C8BCC569;
 Fri, 10 May 2013 21:36:12 +0000 (UTC)
 (envelope-from lists@c0mplx.org)
Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1])
 by mx1.freebsd.org (Postfix) with ESMTP id 88F8698D;
 Fri, 10 May 2013 21:36:12 +0000 (UTC)
Received: from pi by home.opsec.eu with local (Exim 4.80.1 (FreeBSD))
 (envelope-from <lists@c0mplx.org>)
 id 1Uauz4-000Ipy-Dz; Fri, 10 May 2013 23:36:10 +0200
Date: Fri, 10 May 2013 23:36:10 +0200
From: Kurt Jaeger <lists@c0mplx.org>
To: "Ronald F. Guilmette" <rfg@tristatelogic.com>
Subject: Re: bin/152154: script(1) -k malfunctions with certain shells (e.g.
 tcsh, bash, zsh)
Message-ID: <20130510213610.GG8239@home.opsec.eu>
References: <87178.1368219589@server1.tristatelogic.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87178.1368219589@server1.tristatelogic.com>
Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 10 May 2013 21:36:12 -0000

Hi!

> http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/152154
> 
> It has been suggested to me (by a committer) that I should raise the
> issue of this PR here on these lists, because the problem described
> within the PR remains a real problem, and despite my having proposed
> something that seems to be a perfectly workable fix, no action has
> been taken on this PR for some years now.

Having looked at the PR, may I suggest that you look at sysutils/screen
and screen -L especially instead of script -k -- and add some
input logging to screen ? Or, for the tmux fraction, at sysutils/tmux ?

I'm not sure why you absolutly *need* the input logging -- can you
describe the use case ? Is it some security-audit-issue ?

-- 
pi@opsec.eu            +49 171 3101372                         7 years to go !