From coyote@u.washington.edu Wed Apr 21 17:04:25 1999
Received: from jason03.u.washington.edu (root@jason03.u.washington.edu [140.142.77.10])
	by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA42050
	for <linux@lists.u.washington.edu>; Wed, 21 Apr 1999 17:04:24 -0700
Received: from dante40.u.washington.edu (coyote@dante40.u.washington.edu [140.142.15.200])
	by jason03.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA20008
	for <linux@u.washington.edu>; Wed, 21 Apr 1999 17:04:23 -0700
Received: from localhost (coyote@localhost)
	by dante40.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id RAA57354
	for <linux@u.washington.edu>; Wed, 21 Apr 1999 17:04:22 -0700
Date: Wed, 21 Apr 1999 17:04:22 -0700 (PDT)
From: "C. Hunter" <coyote@u.washington.edu>
To: UW Linux Group <linux@u.washington.edu>
Subject: Re: Starting programs at boot time
In-Reply-To: <Pine.A41.4.10.9904211609240.52618-100000@dante40.u.washington.edu>
Message-ID: <Pine.A41.4.10.9904211700360.87488-100000@dante40.u.washington.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


I'm aware of the DoS possiblities. Note that that only applies when you
run the program in stealth mode, which I usally don't.

-Chris

On Wed, 21 Apr 1999, vladimir p marchuk wrote:

> That utility should not be used since it has a negative side-effect.  It
> can be used as a DOS attack, someone could send spoofed packets to all
> your ports and in the end your machine is inaccessible. ;)
> The utility is really useful if you have another person sitting at that
> computer and monitoring the utility, this way a person can decide if its a
> portscan or DOS.
> P.S.
> Call the program from rc.local or... call it from inittab as runlevel 3 or
> 5.
> 
> On Wed, 21 Apr 1999, C. Hunter wrote:
> 
> > 
> > I have a portsentry program that I installed recently. It "locks" ports
> > that are not open and if someone tries to access those ports (such as a
> > portscan) it marks that host and blocks packets from it. My problem is
> > running it. I would like it to start when the machine is booted, but as it
> > stands, I have to su and run it whenever I log in. I looked into having it
> > start via one of the rc.* files, but the documentation seemed to apply to
> > daemons, which this program isn't, expressly.  Is there a particular file
> > or something to start programs you wish to run after the final runlevel
> > has been reached, before anyone logs in?
> > 
> > In a similar fashion, I would like to start tcpdump automatically whenver
> > a modem connection is made.
> > 
> > -Chris
> > 
> > 
> 
> 

.