linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simo Sorce <simo@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: [PATCH 0/3] Avoid DNS Reverse lookups when possible
Date: Tue,  2 Apr 2013 13:49:04 -0400	[thread overview]
Message-ID: <1364924947-16985-1-git-send-email-simo@redhat.com> (raw)

This new patchset obsoletes the patch sent earlier today.
The first and third patch are obvious.

The second patch implement a new command line option -N that takes
an on|off argument.

When 'on' is specified the RPC Server name as passed from the kernel
to rpc.gssd is check to see if it really is an actual IP address, if it
is the current code is executed (and reverse resolution happens),
otherwise the name used at the mount option is used directly w/o any
DNS resolution to construct the GSSAPI name.

Avoiding Reverse name resolution helps making the system work when PTR records
cannot be properly set on a network (because the amdin does not control DNS for
example) and also avoids a potential MITM attack (as explained early on in the
original patch thread).

Simo Sorce (3):
  Fix segfault when using -R option
  Avoid reverse resolution for server name
  Document new -N option

 utils/gssd/gss_util.h  |    2 ++
 utils/gssd/gssd.c      |   18 ++++++++++++++++--
 utils/gssd/gssd.man    |   11 ++++++++++-
 utils/gssd/gssd_proc.c |   25 +++++++++++++++++++++----
 4 files changed, 49 insertions(+), 7 deletions(-)


             reply	other threads:[~2013-04-02 17:49 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 17:49 Simo Sorce [this message]
2013-04-02 17:49 ` [PATCH 1/3] Fix segfault when using -R option Simo Sorce
2013-04-02 19:11   ` Steve Dickson
2013-04-02 17:49 ` [PATCH 2/3] Avoid reverse resolution for server name Simo Sorce
2013-04-02 17:58   ` Myklebust, Trond
2013-04-02 18:08     ` Simo Sorce
2013-04-02 18:53       ` Jeff Layton
2013-04-02 18:21     ` Simo Sorce
2013-04-02 18:25       ` Steve Dickson
2013-04-02 18:44         ` Simo Sorce
2013-04-02 19:20     ` Steve Dickson
2013-04-02 19:32       ` [PATCH 0/2] Alternative patchset to avoid PTR lookups Simo Sorce
2013-04-02 19:32       ` [PATCH 1/2] Avoid reverse resolution for server name Simo Sorce
2013-04-08 13:39         ` Steve Dickson
2013-04-08 14:08           ` Simo Sorce
2013-04-09 17:15             ` Steve Dickson
2013-04-09 17:25               ` Simo Sorce
2013-04-09 17:35                 ` Steve Dickson
2013-04-09 18:02                   ` Simo Sorce
2013-04-09 18:54                   ` J. Bruce Fields
2013-04-09 19:12                     ` Steve Dickson
2013-04-09 19:22                       ` J. Bruce Fields
2013-04-10 10:43                         ` Jeff Layton
2013-04-10 14:53                         ` Steve Dickson
2013-04-02 19:32       ` [PATCH 2/2] Document new -z/-Z options Simo Sorce
2013-04-03 14:20         ` J. Bruce Fields
2013-04-03 14:35           ` Myklebust, Trond
2013-04-03 14:56             ` J. Bruce Fields
2013-04-03 15:10               ` Myklebust, Trond
2013-04-03 15:27                 ` Myklebust, Trond
2013-04-02 17:49 ` [PATCH 3/3] Document new -N option Simo Sorce

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=1364924947-16985-1-git-send-email-simo@redhat.com \
    --to=simo@redhat.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;
as well as URLs for NNTP newsgroup(s).