Re: nfs and kerberos authentification problem.

["François Valenduc" <francois.valenduc@skynet.be>]

J. Bruce Fields a =C3=A9crit :
> On Thu, Sep 04, 2008 at 09:38:34PM +0200, Fran=C3=A7ois Valenduc wrot=
e:
>  =20
>> Kevin Coffman a =C3=A9crit :
>>    =20
>>> This may be a stupid question, but can you access the mount using
>>> auth_sys?  As I think I said before, it looks like the Kerberos par=
t
>>> is working.  (Unless there are errors on the client side from
>>> rpc.gssd.)
>>>
>>>  =20
>>>      =20
>> I finally found a solution to the problem.
>>    =20
>
> Great!
>
>  =20
>> It seems that it's needed to =20
>> compile both NFS v3 and v4 server support to make kerberos support =20
>> working. I find that a bit strange, but with this kernel configurati=
on, =20
>> it is working fine. I find that a bit strange since I export the =20
>> filesystem as NFS3.
>> Should we consider this as a bug ? I am running kernel 2.6.26.3.
>>    =20
>
> Yes, that would be a bug!  But: are you sure gss support was built in=
 on
> the server?
>
> --b.
>
>  =20
>> Thanks a lot for your patience,
>> Fran=C3=A7ois
>>    =20
>
>  =20
There is still a major problem. Even if I can now mount the filesystem=20
with kerberos authentification, I can't write any file. Furthermore, I=20
can even not see the content of the exported directory without being=20
root. Is it due to the problem of uid/gid mapping ?

=46ran=C3=A7ois