linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Steve Dickson <SteveD@redhat.com>
Cc: Simo Sorce <simo@redhat.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] Avoid DNS reverse resolution for server names (take 3)
Date: Wed, 29 May 2013 09:04:15 +1000	[thread overview]
Message-ID: <20130529090415.27af1dec@notabene.brown> (raw)
In-Reply-To: <51A4FA3A.1080805@RedHat.com>

[-- Attachment #1: Type: text/plain, Size: 692 bytes --]

On Tue, 28 May 2013 14:40:58 -0400 Steve Dickson <SteveD@redhat.com> wrote:

> 
> 
> On 01/05/13 23:13, NeilBrown wrote:
> > Subject: Fix recent fix to Avoid DNS reverse resolution in gssd.
> > 
> > The final version for this fix that was committed inverted the test
> > so makes no change in the important cases.
> > The documentation didn't really help a naive user know when the new -D flag
> > should be used.
> > And the code (once fixed) avoided DNS resolution on non-qualified names too,
> > which probably isn't a good idea.
> > 
> > This patch fixes all three issues.
> > 
> > Signed-off-by: NeilBrown <neilb@suse.de>
> Committed....
> 

Thanks :-)

NeilBrown

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2013-05-28 23:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-19 14:16 [PATCH] Avoid DNS reverse resolution for server names (take 3) Steve Dickson
2013-04-22 17:20 ` Steve Dickson
2013-05-02  3:13 ` NeilBrown
2013-05-02  5:56   ` Jim Rees
2013-05-02 12:08     ` Simo Sorce
2013-05-02  6:53   ` NeilBrown
2013-05-07 15:20     ` Steve Dickson
2013-05-07 15:59     ` Steve Dickson
2013-05-27 23:11   ` NeilBrown
2013-05-28 14:41     ` Steve Dickson
2013-05-28 15:46     ` Steve Dickson
2013-05-28 18:40   ` Steve Dickson
2013-05-28 23:04     ` NeilBrown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-04-19 14:16 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=20130529090415.27af1dec@notabene.brown \
    --to=neilb@suse.de \
    --cc=SteveD@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=simo@redhat.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 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 NNTP newsgroup(s).