Re: nfsv3 gssapi client?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



 On 21/09/2010 16:51, J. Bruce Fields wrote:
On Tue, Sep 21, 2010 at 11:36:18AM +0300, George Mamalakis wrote:
  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),
As Kevin says, it would be worth trying MIT kerberos instead of heimdal
if you can, as that is generally better tested.

--b.

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

Ok Bruce and Kevin,

I'll try and do that. I only hope that MIT-client is compatible with Heimdal-server (if I manage to install it on archlinux through AUR...:)).

--
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

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Filesystem Development]     [Linux USB Development]     [Linux Media Development]     [Video for Linux]     [Linux NILFS]     [Linux Audio Users]     [Yosemite Info]     [Linux SCSI]

  Powered by Linux