public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dahl Nyerup <nyerup@one.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org, Vedpal Rajera <vedpalr@one.com>,
	Martin Topholm <mph@one.com>
Subject: Re: Using script(1) to log all user sessions
Date: Sat, 26 Apr 2014 23:27:15 +0200	[thread overview]
Message-ID: <20140426212715.GA14316@one.com> (raw)
In-Reply-To: <20140425082133.GA3790@one.com>

[-- Attachment #1: Type: text/plain, Size: 857 bytes --]

Karel,

On Apr 25  10:21, Jesper Dahl Nyerup wrote:
> This could involve:
> 
> 1. Adding a daemon next to script(1) and scriptreplay(1), eg.
> scriptcollect(1), to be in the receiving end of the traffic, optionally
> handling the timing functionality, and finally storing data in the same
> manner script(1) would.
> 
> 2. Optionally linking against some crypto library to avoid putting
> users' console data on the wire in clear text.
> 
> Ideally we'd like to upstream any changes we make, and this post serves
> as an attempt to gauge the mood and ask for guidance as to which
> direction you guys think we should take our efforts.

Do you think functionality like this belongs in script(1) et al., and do
you think you'd accept the patches, if they look sane?

J.
-- 
Jesper Dahl Nyerup
Systems Engineer
One.com, nyerup@one.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  parent reply	other threads:[~2014-04-26 21:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25  8:21 Using script(1) to log all user sessions Jesper Dahl Nyerup
2014-04-25 14:27 ` Dale R. Worley
2014-04-25 17:39   ` Jesper Dahl Nyerup
2014-04-26 21:27 ` Jesper Dahl Nyerup [this message]
2014-04-27 19:53 ` Ángel González
2014-04-29 10:00   ` Jesper Dahl Nyerup
2014-04-29 10:42     ` Karel Zak
2014-04-29 11:10       ` Jesper Dahl Nyerup
2014-04-28  7:13 ` Karel Zak
2014-04-29 11:05   ` Jesper Dahl Nyerup

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140426212715.GA14316@one.com \
    --to=nyerup@one.com \
    --cc=kzak@redhat.com \
    --cc=mph@one.com \
    --cc=util-linux@vger.kernel.org \
    --cc=vedpalr@one.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox