public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Leonard Milcin Jr." <leonard.milcin@post.pl>
To: Roberto Nibali <ratz@drugphish.ch>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>, linux-kernel@vger.kernel.org
Subject: Re: [OT] Re: keyboard driver of 2.6 kernel
Date: Thu, 05 Jan 2006 12:58:44 +0100	[thread overview]
Message-ID: <43BD09F4.2090603@post.pl> (raw)
In-Reply-To: <43BCF005.1050501@drugphish.ch>

Roberto Nibali wrote:
>>> Let's pretend it's some sort of auditing ;-)
>>
>> Actually, I use my keylogger (advertised above) more for "situation 
>> reconstruction" rather than spying. When you happen to have a multi-root
>> environment and people "forget what they did", stuff like ttyrpld can 
>> really be a gift compared to .bash_history (if it exists, after all).
> 
> If one needs it a bit less intrusive, she can also patch bash. A 
> possible solution can be found here:
> 
> http://www.drugphish.ch/patches/ratz/bash/bash-3.0-fix_1439-3.diff
> 
> But http://ttyrpld.sourceforge.net/ looks indeed interesting, however no 
> 2.4.x support from what I can see.
> 
> Regards,
> Roberto Nibali, ratz

This can be very easily circumvented if you can execute another shell 
(for example your own version of bash without patch).

L.

  parent reply	other threads:[~2006-01-05 11:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-04  8:32 keyboard driver of 2.6 kernel P.Manohar
2006-01-04  8:33 ` Arjan van de Ven
2006-01-04  9:07   ` Leonard Milcin Jr.
2006-01-04  9:23     ` Jan Engelhardt
2006-01-05 10:08       ` [OT] " Roberto Nibali
2006-01-05 11:51         ` Jan Engelhardt
2006-01-05 12:43           ` Roberto Nibali
2006-01-05 21:07             ` Nuno Monteiro
2006-01-05 23:28               ` Roberto Nibali
2006-01-06  7:01                 ` Jan Engelhardt
2006-01-06 10:28                   ` Nuno Monteiro
2006-01-05 11:58         ` Leonard Milcin Jr. [this message]
2006-01-05 12:47           ` Roberto Nibali
2006-01-04 16:25   ` Dmitry Torokhov

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=43BD09F4.2090603@post.pl \
    --to=leonard.milcin@post.pl \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ratz@drugphish.ch \
    /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