public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bernd Eckenfels <be-mail2005@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: nfs insecure_locks / Tru64 behaviour
Date: Fri, 23 Dec 2005 22:41:38 +0100	[thread overview]
Message-ID: <20051223214138.GA25727@lina.inka.de> (raw)
In-Reply-To: <1135371520.8555.2.camel@lade.trondhjem.org>

On Fri, Dec 23, 2005 at 09:58:40PM +0100, Trond Myklebust wrote:
> Huh? No it doesn't. The Linux NLM server requires that the client
> authenticate using AUTH_SYS (unless you use insecure_locks), but it
> certainly doesn't require you to have root privileges. That would
> violate POSIX locking rules.

Yes, however True64 does not authenticate (properly), thats why you need the
option if you want to do locking.

Gruss
Bernd
-- 
  (OO)     -- Bernd_Eckenfels@Mörscher_Strasse_8.76185Karlsruhe.de --
 ( .. )    ecki@{inka.de,linux.de,debian.org}  http://www.eckes.org/
  o--o   1024D/E383CD7E  eckes@IRCNet  v:+497211603874  f:+49721151516129
(O____O)  When cryptography is outlawed, bayl bhgynjf jvyy unir cevinpl!

  reply	other threads:[~2005-12-23 21:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-22 13:36 nfs insecure_locks / Tru64 behaviour Ron Peterson
2005-12-22 23:21 ` Trond Myklebust
2005-12-23  1:39   ` Ron Peterson
2005-12-23  1:45     ` Trond Myklebust
2005-12-23  2:21       ` Ron Peterson
2005-12-23  2:32         ` Ron Peterson
2005-12-23  8:37         ` Trond Myklebust
2005-12-23 13:38           ` Ron Peterson
2005-12-23 13:50             ` Trond Myklebust
2005-12-23 14:39               ` Ron Peterson
2005-12-23 15:00                 ` Trond Myklebust
2005-12-23 18:10     ` Bernd Eckenfels
2005-12-23 20:58       ` Trond Myklebust
2005-12-23 21:41         ` Bernd Eckenfels [this message]
2005-12-23 22:00           ` Trond Myklebust

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=20051223214138.GA25727@lina.inka.de \
    --to=be-mail2005@lina.inka.de \
    --cc=linux-kernel@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