From: George Mamalakis <mamalos@eng.auth.gr>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org, kwc@citi.umich.edu
Subject: Re: nfsv3 gssapi client?
Date: Tue, 21 Sep 2010 11:36:18 +0300 [thread overview]
Message-ID: <4C986E82.7040003@eng.auth.gr> (raw)
In-Reply-To: <20100920160732.GK4580@fieldses.org>
Hi guys,
Kevin:
As stated in my first email, the linux box is running on a 2.6.35
kernel, heimdal 1.3.3-1 (the version was not mentioned in my email),
rpcbind-0.2.0-2, nfs-utils-1.2.2-3, and the distro is arch-linux.
Bruce: I would rather find an "easier" (configuration-specific) way to
overcome my problem instead of delving into the code, since I am not a
developer (I am an admin :)). Nevertheless, when I used
google.com/searchcode for _gss_get_mechanism_cred I found that there is
a libgss/g_glue.c that defines this function in the following way (the
site is svn://svn.genunix.org/on/trunk
<http://google.com/codesearch/p?hl=en#m0BoFGhUuEY/&q=_gss_get_mechanism_cred>):
/*
* Glue routine for returning the mechanism-specific credential from a
* external union credential.
*/
gss_cred_id_t
__gss_get_mechanism_cred(union_cred, mech_type)
const gss_union_cred_t union_cred;
const gss_OID mech_type;
{
int i;
if (union_cred == (gss_union_cred_t)GSS_C_NO_CREDENTIAL)
return (GSS_C_NO_CREDENTIAL);
for (i =0; i< union_cred->count; i++) {
if (g_OID_equal(mech_type,&union_cred->mechs_array[i]))
return (union_cred->cred_array[i]);
}
return (GSS_C_NO_CREDENTIAL);
}
where you can see that the guy returns a cred_array[i] element, that
obviously is null, because (most probably) the if statement above did
not match any "compatible" mechanisms during the recursion.
Maybe I am totally wrong, since I haven't checked the code thoroughly,
but I think that the problem is located somewhere in this code segment.
As I stated before, I was rather hoping to avoid this procedure, since I
decided to use the linux distro for my clients due to its
'out-of-the-box' and 'everything-is-supported' benefits as
(slightly-)opposed to fbsd (which I use in all my servers and personal
computers, and "love" as an operating system) can be a bit more
"demanding" when out-of-the-box-general-purpose issues are involved. The
thing is that the client will be used as a general-purpose student pc in
a university lab.
Thanx again for your help,
if anybody could direct me somewhere else I would be delighted to know so!
mamalos
--
George Mamalakis
IT Officer
Electrical and Computer Engineer (Aristotle Un. of Thessaloniki),
MSc (Imperial College of London)
Department of Electrical and Computer Engineering
Faculty of Engineering
Aristotle University of Thessaloniki
phone number : +30 (2310) 994379
next prev parent reply other threads:[~2010-09-21 8:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 15:54 nfsv3 gssapi client? George Mamalakis
2010-09-17 17:43 ` J. Bruce Fields
2010-09-17 18:35 ` Jeff Layton
2010-09-20 9:54 ` George Mamalakis
2010-09-17 18:39 ` Chuck Lever
2010-09-20 9:47 ` George Mamalakis
2010-09-20 14:56 ` J. Bruce Fields
2010-09-20 15:38 ` George Mamalakis
2010-09-20 16:06 ` Kevin Coffman
2010-09-20 16:07 ` J. Bruce Fields
2010-09-21 8:36 ` George Mamalakis [this message]
2010-09-21 13:51 ` J. Bruce Fields
2010-09-21 14:40 ` George Mamalakis
-- strict thread matches above, loose matches on Subject: below --
2010-09-21 14:19 George Mamalakis
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=4C986E82.7040003@eng.auth.gr \
--to=mamalos@eng.auth.gr \
--cc=bfields@fieldses.org \
--cc=kwc@citi.umich.edu \
--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).