From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/3] nfs-utils: Enabling TCP wrappers
Date: Mon, 15 Dec 2008 12:56:38 -0500 [thread overview]
Message-ID: <49469A56.1070704@RedHat.com> (raw)
In-Reply-To: <1819C671-5353-45B4-A814-98B1B2A4BEB1@oracle.com>
Chuck Lever wrote:
> On Dec 15, 2008, at 11:54 AM, Steve Dickson wrote:
>> Recently I was asked to re-enable the TCP wrapper calls, that check the
>> validity of client that communicate with mountd and statd.
>>
>> It became very apparent this code had not been used in a while
>> and was as a bit broken. So this patch set fixes the logic and
>> tries to make the code scale better.
>>
>> The commit blobs in the set are relative to the 'tcpwrap'
>> branch in the git://linux-nfs.org/~steved/nfs-utils-exp.git
>> git tree.
>>
>> Comments?
>
> A general comment: This code will need support for IPv6 addresses.
>
> Until it has it, perhaps we should add some logic to configure.ac that
> prevents the use of tcpwrappers when --enable-ipv6 is in effect.
Good point...
steved.
next prev parent reply other threads:[~2008-12-15 17:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-15 16:54 [PATCH 0/3] nfs-utils: Enabling TCP wrappers Steve Dickson
[not found] ` <49468BC7.2000907-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-12-15 16:58 ` [PATCH 1/3] " Steve Dickson
2008-12-15 17:10 ` [PATCH 2/3] " Steve Dickson
2008-12-15 17:11 ` [PATCH 3/3] " Steve Dickson
2008-12-15 17:26 ` [PATCH 0/3] " Chuck Lever
2008-12-15 17:56 ` Steve Dickson [this message]
2008-12-18 19:59 ` Steve Dickson
[not found] ` <494AABA1.4070006-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-12-18 20:23 ` Chuck Lever
2008-12-18 20:49 ` Steve Dickson
[not found] ` <494AB74E.3040403-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2008-12-18 20:56 ` Chuck Lever
2008-12-18 21:21 ` Steve Dickson
2008-12-19 17:00 ` Steve Dickson
2008-12-20 12:35 ` Steve Dickson
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=49469A56.1070704@RedHat.com \
--to=steved@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.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