All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valentijn Sessink <valentyn@blub.net>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: ipv6 + krb5, server status?
Date: Wed, 20 Oct 2010 13:01:19 +0200	[thread overview]
Message-ID: <4CBECBFF.2050802@blub.net> (raw)
In-Reply-To: <20101013104937.358fe122@corrin.poochiereds.net>

Jeff, list,

Jeff Layton schreef:
> It sounds more like you have a problem with idmapping rather than
> anything krb5 specific, but I'm not sure why that would be the case
> with sec=krb5 and not with sec=sys.

Well, I did, in fact. At least, that is what I'm currently seeing with
another system, where "networkmanager" messes with the hosts-file, and
as a result, effectively wipes out the FQDN. Thus, idmapd thinks that
"localdomain" (added by networkmanager - why?? - no that's not a
question, just venting my frustration ;) was a good guess to test the
logged in user against:

rpc.idmapd: nss_getpwnam: name 'valentyn@kantoor.openoffice.nl' domain
'localdomain': resulting localname '(null)'

(We run idmapd relying on DNS instead of a "Domain = " clause, because
we thought that made us flexible - I'll rethink that decision.)

V.

  parent reply	other threads:[~2010-10-20 11:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-13 10:57 ipv6 + krb5, server status? Valentijn Sessink
2010-10-13 12:56 ` Jeff Layton
2010-10-13 13:18   ` Valentijn Sessink
2010-10-13 12:56 ` Jim Rees
2010-10-13 13:52   ` Jeff Layton
2010-10-13 13:56     ` Valentijn Sessink
2010-10-13 14:49       ` Jeff Layton
2010-10-13 14:58         ` Jeff Layton
2010-10-20 11:01         ` Valentijn Sessink [this message]
2010-10-20 12:05           ` Jim Rees
2010-10-20 12:11             ` Valentijn Sessink
2010-10-20 12:50               ` Jim Rees
  -- strict thread matches above, loose matches on Subject: below --
2010-10-09 14:19 Valentijn Sessink

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=4CBECBFF.2050802@blub.net \
    --to=valentyn@blub.net \
    --cc=jlayton@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 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.