From: Jeff Layton <jtlayton@poochiereds.net>
To: Olaf Kirch <okir@suse.de>
Cc: nfs@lists.sourceforge.net
Subject: Re: making the 'addr=' mount option an address hint
Date: Sun, 17 Jul 2005 13:40:14 -0400 [thread overview]
Message-ID: <1121622014.6713.56.camel@localhost.localdomain> (raw)
In-Reply-To: <20050717165143.GD22503@suse.de>
On Sun, 2005-07-17 at 18:51 +0200, Olaf Kirch wrote:
> Why just use it as a hint? Why not override address resolution completely
> when addr= is given?
I suppose that's a possibility, but it might have security implications.
My concern there would be that someone could then essentially pass an
addr= option to a mount that actually doesn't match the hostname. Then
you have a mount that appears at first glance to be from a hostname that
you believe to be valid, but is actually a different host entirely.
Then again, I suppose you can get the same effect by temporarily
spoofing hosts resolution, so perhaps just allowing addr= to override it
is the best bet.
-- Jeff
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2005-07-17 17:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-17 15:38 making the 'addr=' mount option an address hint Jeff Layton
2005-07-17 16:51 ` Olaf Kirch
2005-07-17 17:40 ` Jeff Layton [this message]
2005-07-18 15:22 ` Trond Myklebust
2005-07-18 17:55 ` Jeff Layton
2005-07-18 18:09 ` Dan Stromberg
2005-07-18 18:45 ` Trond Myklebust
2005-07-18 19:59 ` Jeff Layton
2005-07-18 15:36 ` Trond Myklebust
2005-07-18 18:24 ` [NFS] " Jeff Layton
2005-07-18 18:37 ` Trond Myklebust
2005-07-18 18:37 ` Trond Myklebust
2005-07-18 19:54 ` Olaf Kirch
2005-07-18 20:49 ` Trond Myklebust
2005-07-18 20:49 ` Trond Myklebust
2005-07-19 12:26 ` Ian Kent
2005-07-19 12:22 ` [NFS] " Ian Kent
2005-07-19 12:17 ` Ian Kent
2005-07-19 12:03 ` Ian Kent
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=1121622014.6713.56.camel@localhost.localdomain \
--to=jtlayton@poochiereds.net \
--cc=nfs@lists.sourceforge.net \
--cc=okir@suse.de \
/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.