From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.samba.org
Subject: Re: TCP delay, solved
Date: Thu, 13 Jun 2002 13:05:11 +0100 [thread overview]
Message-ID: <200206131205.NAA07068@slate.rockstone.co.uk> (raw)
In-Reply-To: <news2mail-ae9qee$vvr$1@babel.spoiled.org>
On Thursday 13 June 2002 10:59 am, Juri Haberland wrote:
> >> This is annoying, is there a way you can turn
> >> this off inside inetd?
> >
> > Yes, it's the bit on each line of /etc/inetd.conf which says
> > "/usr/sbin/tcpd" - it does an ident lookup and logs the access to syslog
> > before handing the connection over to the real daemon.
> >
> > If you don't want this to happen them remove the "/usr/sbin/tcpd" from
> > inetd.conf and just have the standard daemon listed there on its own.
>
> This is a very bad advice as the tcpwrappers are a standard security
> tool which shouldn't be disabled!
I wasn't advocating this as good advice - I was simply answering the question
"how do I do it".
I don't regard eliminating tcpwrappers as a good idea, just for the record.
Mind you, I do also think that ident lookups are a bit of an anachronism
which we could well do without in many situations these days, however I don't
like having a firewall which automatically responds on port 113 to anyone who
cares to probe it...
There's no satisfactory answer to this problem at present, I think.
Antony.
next prev parent reply other threads:[~2002-06-13 12:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020612154553.GI10747@hack.home.theunixman.com>
2002-06-12 16:33 ` TCP delay, solved Nathan Cassano
2002-06-12 20:02 ` Antony Stone
2002-06-13 9:59 ` Juri Haberland
2002-06-13 12:05 ` Antony Stone [this message]
2002-06-14 7:15 ` David Luyer
2002-06-14 7:55 ` Antony Stone
2002-06-14 8:17 ` David Luyer
2002-06-14 8:25 ` David Luyer
2002-06-14 9:18 ` Antony Stone
2002-06-14 20:29 ` Joe Patterson
2002-06-15 1:21 ` Joe Patterson
2002-06-14 9:16 ` Antony Stone
2002-06-14 17:28 ` Tony Earnshaw
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=200206131205.NAA07068@slate.rockstone.co.uk \
--to=antony@soft-solutions.co.uk \
--cc=netfilter@lists.samba.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