From: Mike Fedyk <mfedyk@matchmail.com>
To: Esben Stien <executiv@online.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: logging all input and output on a tty
Date: Wed, 21 Jan 2004 13:41:52 -0800 [thread overview]
Message-ID: <20040121214152.GO23765@srv-lnx2600.matchmail.com> (raw)
In-Reply-To: <87u12p3s1e.fsf@online.no>
On Wed, Jan 21, 2004 at 10:34:05PM +0100, Esben Stien wrote:
> Ludootje <ludootje@linux.be> writes:
>
> > You can just cat the device, like cat /dev/tty<number>. So you can also
> > use normal redirectors (> , >> etc) or use a pager.
>
> If I do cat /dev/tty1 on /dev/tty2, I see what I write to /dev/tty1 on /dev/tty2, but I don't see what I write to /dev/tty1 while working in /dev/tty1 (all the input is being printed on /dev/tty2) . And besides, I only see the input I type, not the output of f.ex a command (on /dev/tty2). I want to monitor users and log everything that is done on a specific tty when they log in.
This is in debian:
Package: ttysnoop
Priority: optional
Section: admin
Installed-Size: 56
Maintainer: Alberto Gonzalez Iniesta <agi@agi.as>
Architecture: i386
Version: 0.12c-8
Depends: libc6 (>= 2.3.2-1)
Filename: pool/main/t/ttysnoop/ttysnoop_0.12c-8_i386.deb
Size: 15126
MD5sum: 462a28b83327bd2ae987791528e9e095
Description: TTY Snoop - allows you to spy on telnet+serial connections
TTYSnoop allows you to snoop on login tty's through another tty-device or
pseudo-tty. The snoop-tty becomes a 'clone' of the original tty,
redirecting both input and output from/to it.
next prev parent reply other threads:[~2004-01-21 21:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 16:48 Esben Stien
2004-01-21 17:12 ` Andreas Dilger
2004-01-21 21:37 ` Esben Stien
2004-01-21 18:04 ` Ludootje
2004-01-21 21:34 ` Esben Stien
2004-01-21 21:41 ` Mike Fedyk [this message]
2004-01-21 21:55 ` William Stearns
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=20040121214152.GO23765@srv-lnx2600.matchmail.com \
--to=mfedyk@matchmail.com \
--cc=executiv@online.no \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®