All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Rees <rees@umich.edu>
To: Simo Sorce <simo@redhat.com>
Cc: linux-nfs <linux-nfs@vger.kernel.org>,
	Steve Dickson <steved@redhat.com>,
	Jeffrey Layton <jlayton@redhat.com>
Subject: Re: [PATCH] Avoid PTR lookups when possible
Date: Tue, 2 Apr 2013 14:53:38 -0400	[thread overview]
Message-ID: <20130402185337.GC18900@umich.edu> (raw)
In-Reply-To: <1364928519.2660.1279.camel@willson.li.ssimo.org>

Simo Sorce wrote:

  >  And stop using the term "mitm". A mitm attack is used to
  > convince both ends of a connection that they are talking to each other. DNS
  > is not a mutually authenticated exchange.
  
  Well it is still a sort of Man in the Middle, as you also have to
  redirect communications (nfsv4 uses TCP) for it to be effective, it is
  just not exploiting a crypto issue.

Now you've lost me again. I thought we were discussing dns. What does nfs
have to do with it?

  reply	other threads:[~2013-04-02 18:53 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02 13:45 [PATCH] Avoid PTR lookups when possible Simo Sorce
2013-04-02 14:17 ` Jeff Layton
2013-04-02 15:00 ` Jim Rees
2013-04-02 16:26   ` Simo Sorce
2013-04-02 16:46     ` Jim Rees
2013-04-02 17:03       ` Simo Sorce
2013-04-02 18:39         ` Jim Rees
2013-04-02 18:48           ` Simo Sorce
2013-04-02 18:53             ` Jim Rees [this message]
2013-04-02 19:02               ` Simo Sorce
2013-04-03 13:44             ` J. Bruce Fields
2013-04-03 14:40               ` Jim Rees
2013-04-03 16:03                 ` Simo Sorce
2013-04-03 17:12                   ` J. Bruce Fields
2013-04-03 18:12                     ` Simo Sorce
2013-04-03 18:20                       ` J. Bruce Fields
2013-04-02 15:18 ` Steve Dickson
2013-04-02 15:51   ` Chuck Lever
2013-04-02 16:29     ` Simo Sorce
2013-04-02 20:21       ` Chuck Lever
2013-04-02 20:33         ` 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=20130402185337.GC18900@umich.edu \
    --to=rees@umich.edu \
    --cc=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=simo@redhat.com \
    --cc=steved@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.