Date: Fri, 10 May 2013 23:36:10 +0200 From: Kurt Jaeger <lists@c0mplx.org> To: "Ronald F. Guilmette" <rfg@tristatelogic.com> Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: bin/152154: script(1) -k malfunctions with certain shells (e.g. tcsh, bash, zsh) Message-ID: <20130510213610.GG8239@home.opsec.eu> In-Reply-To: <87178.1368219589@server1.tristatelogic.com> References: <87178.1368219589@server1.tristatelogic.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 !
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130510213610.GG8239>