public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Doug Sutherland" <doug@proficio.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: shell script request? possibly?
Date: Sat, 19 May 2007 23:41:18 -0500	[thread overview]
Message-ID: <001801c79a99$1bb24450$ab00a8c0@tenstac> (raw)
In-Reply-To: <000b01c79a8a$02d50df0$6501a8c0@GRANDMA>

Regarding ip_deny perhaps what was meant was the 
hosts.deny and hosts.allow files. These only relate to
tcpwrappers, the tcpd or inetd daemons which can 
control port access. I personally think such "super"
daemons are dangerous and do not run them at all.
One process, inetd, or similar, has the ability to open
any or all ports, seems like a great possible target to
compromise a system.

Using hosts.deny is not equivalent to the iptables, 
which will drop packets at the firewall, I think 
Tyler's intention is a good one, better than deny 
by the tcpwrapper process.

> I don't have an ip.deny file


      reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Littlefield, Tyler
 ` Travis Siegel
   ` Littlefield, Tyler
     ` Travis Siegel
       ` Littlefield, Tyler
         ` Doug Sutherland [this message]

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='001801c79a99$1bb24450$ab00a8c0@tenstac' \
    --to=doug@proficio.ca \
    --cc=speakup@braille.uwo.ca \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).