All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Curtis <ccurtis@aet-usa.com>
To: John Bradford <john@grabjohn.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	root@chaos.analogic.com, joe briggs <jbriggs@briggsmedia.com>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: Help with virus/hackers
Date: Thu, 17 Apr 2003 13:17:39 -0400	[thread overview]
Message-ID: <3E9EE1B3.7080801@aet-usa.com> (raw)
In-Reply-To: <200304171545.h3HFjPoH000129@81-2-122-30.bradfords.org.uk>

John Bradford wrote:

> I've often wondered whether it would be worth connecting a very large
> serial EEPROM to a serial port interface, and have it effectively
> appear as a solid state printer, (to that you could cheaply log to an
> unmodifyable device).  Has anybody ever tried this?

I suspect there are better solutions; namely another host running 
something like passlogd with the xmit wires cut and the hosts sending 
udp broadcast messages (or plug it into the monitor port of the switch). 
  Also, since the poster was running Woody, apt-cron'ing security might 
also lend itself to usefulness, along with apt-listchanges and maybe a 
little expect script.

rgds,
Chris


  parent reply	other threads:[~2003-04-17 17:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-17 14:15 Help with virus/hackers joe briggs
2003-04-17 12:42 ` Alan Cox
2003-04-17 13:55 ` Richard B. Johnson
2003-04-17 14:12   ` Alan Cox
2003-04-17 15:31     ` John Jasen
2003-04-17 15:45     ` John Bradford
2003-04-17 16:26       ` Alan Cox
2003-04-17 18:00         ` John Bradford
2003-04-17 17:17       ` Christopher Curtis [this message]
2003-04-17 14:12   ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2003-04-17 16:34 Kenny Mann
2003-04-17 17:24 ` Leonard Milcin, Jr
2003-04-17 18:12 Kenny Mann
2003-04-17 20:56 Kenny Mann

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=3E9EE1B3.7080801@aet-usa.com \
    --to=ccurtis@aet-usa.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jbriggs@briggsmedia.com \
    --cc=john@grabjohn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.