2019-12-06 18:30:00

by Olga Kornievskaia

[permalink] [raw]
Subject: gssd question/patch

Hi Steve,

Question: Is this an interesting failure scenario (bug) that should be
fixed: client did a mount which acquired gss creds and stored in the
credential cache. Then say it umounts at some point. Then for some
reason the Kerberos cache is deleted (rm -f /tmp/krb5cc*). Now client
mounts again. This currently fails. Because gssd uses internal cache
to store creds lifetimes and thinks that tgt is still valid but then
trying to acquire a service ticket it fails (since there is no tgt).

Here's my proposed fix (I can send as a patch if this agreed upon).

diff --git a/utils/gssd/krb5_util.c b/utils/gssd/krb5_util.c
index 0474783..3678524 100644
--- a/utils/gssd/krb5_util.c
+++ b/utils/gssd/krb5_util.c
@@ -121,6 +121,9 @@
#include <krb5.h>
#include <rpc/auth_gss.h>

+#include <sys/types.h>
+#include <fcntl.h>
+
#include "nfslib.h"
#include "gssd.h"
#include "err_util.h"
@@ -314,6 +317,25 @@ gssd_find_existing_krb5_ccache(uid_t uid, char *dirname,
return err;
}

+/* check if the ticket cache exists, if not set nocache=1 so that new
+ * tgt is gotten
+ */
+static int
+gssd_check_if_cc_exists(struct gssd_k5_kt_princ *ple)
+{
+ int fd;
+ char cc_name[BUFSIZ];
+
+ snprintf(cc_name, sizeof(cc_name), "%s/%s%s_%s",
+ ccachesearch[0], GSSD_DEFAULT_CRED_PREFIX,
+ GSSD_DEFAULT_MACHINE_CRED_SUFFIX, ple->realm);
+ fd = open(cc_name, O_RDONLY);
+ if (fd < 0)
+ return 1;
+ close(fd);
+ return 0;
+}
+
/*
* Obtain credentials via a key in the keytab given
* a keytab handle and a gssd_k5_kt_princ structure.
@@ -348,6 +370,8 @@ gssd_get_single_krb5_cred(krb5_context context,

memset(&my_creds, 0, sizeof(my_creds));

+ if (!nocache && !use_memcache)
+ nocache = gssd_check_if_cc_exists(ple);
/*
* Workaround for clock skew among NFS server, NFS client and KDC
* 300 because clock skew must be within 300sec for kerberos


2019-12-09 16:10:20

by Steve Dickson

[permalink] [raw]
Subject: Re: gssd question/patch

Hey,

On 12/6/19 1:29 PM, Olga Kornievskaia wrote:
> Hi Steve,
>
> Question: Is this an interesting failure scenario (bug) that should be
> fixed: client did a mount which acquired gss creds and stored in the
> credential cache. Then say it umounts at some point. Then for some
> reason the Kerberos cache is deleted (rm -f /tmp/krb5cc*). Now client
> mounts again. This currently fails. Because gssd uses internal cache
> to store creds lifetimes and thinks that tgt is still valid but then
> trying to acquire a service ticket it fails (since there is no tgt).
I'm unable reproduce the scenario....

(as root) mount -o sec=krb5 server:/home/tmp /mnt/tmp
(as kuser) kinit kuser
(as kuser) touch /mnt/tmp/foobar
(as root) umount /mnt/tmp/
(as root) rm -f /tmp/krb5cc*
(as root) mount -o sec=krb5 server:/home/tmp /mnt/tmp
(as kuser) touch /mnt/tmp/foobar # which succeeds

Where am I going wrong?

steved.

>
> Here's my proposed fix (I can send as a patch if this agreed upon).
>
> diff --git a/utils/gssd/krb5_util.c b/utils/gssd/krb5_util.c
> index 0474783..3678524 100644
> --- a/utils/gssd/krb5_util.c
> +++ b/utils/gssd/krb5_util.c
> @@ -121,6 +121,9 @@
> #include <krb5.h>
> #include <rpc/auth_gss.h>
>
> +#include <sys/types.h>
> +#include <fcntl.h>
> +
> #include "nfslib.h"
> #include "gssd.h"
> #include "err_util.h"
> @@ -314,6 +317,25 @@ gssd_find_existing_krb5_ccache(uid_t uid, char *dirname,
> return err;
> }
>
> +/* check if the ticket cache exists, if not set nocache=1 so that new
> + * tgt is gotten
> + */
> +static int
> +gssd_check_if_cc_exists(struct gssd_k5_kt_princ *ple)
> +{
> + int fd;
> + char cc_name[BUFSIZ];
> +
> + snprintf(cc_name, sizeof(cc_name), "%s/%s%s_%s",
> + ccachesearch[0], GSSD_DEFAULT_CRED_PREFIX,
> + GSSD_DEFAULT_MACHINE_CRED_SUFFIX, ple->realm);
> + fd = open(cc_name, O_RDONLY);
> + if (fd < 0)
> + return 1;
> + close(fd);
> + return 0;
> +}
> +
> /*
> * Obtain credentials via a key in the keytab given
> * a keytab handle and a gssd_k5_kt_princ structure.
> @@ -348,6 +370,8 @@ gssd_get_single_krb5_cred(krb5_context context,
>
> memset(&my_creds, 0, sizeof(my_creds));
>
> + if (!nocache && !use_memcache)
> + nocache = gssd_check_if_cc_exists(ple);
> /*
> * Workaround for clock skew among NFS server, NFS client and KDC
> * 300 because clock skew must be within 300sec for kerberos
>

2019-12-09 16:50:53

by Olga Kornievskaia

[permalink] [raw]
Subject: Re: gssd question/patch

Hi Steve,

On Mon, Dec 9, 2019 at 11:10 AM Steve Dickson <[email protected]> wrote:
>
> Hey,
>
> On 12/6/19 1:29 PM, Olga Kornievskaia wrote:
> > Hi Steve,
> >
> > Question: Is this an interesting failure scenario (bug) that should be
> > fixed: client did a mount which acquired gss creds and stored in the
> > credential cache. Then say it umounts at some point. Then for some
> > reason the Kerberos cache is deleted (rm -f /tmp/krb5cc*). Now client
> > mounts again. This currently fails. Because gssd uses internal cache
> > to store creds lifetimes and thinks that tgt is still valid but then
> > trying to acquire a service ticket it fails (since there is no tgt).
> I'm unable reproduce the scenario....
>
> (as root) mount -o sec=krb5 server:/home/tmp /mnt/tmp
> (as kuser) kinit kuser
> (as kuser) touch /mnt/tmp/foobar
> (as root) umount /mnt/tmp/
> (as root) rm -f /tmp/krb5cc*
> (as root) mount -o sec=krb5 server:/home/tmp /mnt/tmp
> (as kuser) touch /mnt/tmp/foobar # which succeeds
>
> Where am I going wrong?

Not sure. Can you please post gssd verbose output?

Set up. Client kernel somewhat recent though the latest, but in
reality doesn't matter i think
gssd from nfs-utils commit 5a004c161ff6c671f73a92d818a502264367a896
"gssd: daemonize earlier"

[aglo@localhost nfs-utils]$ sudo mount -o vers=4.1,sec=krb5
192.168.1.72:/nfsshare /mnt
[aglo@localhost nfs-utils]$ touch /mnt/kerberos
[aglo@localhost nfs-utils]$ sudo umount /mnt
[aglo@localhost nfs-utils]$ sudo rm -fr /tmp/krb5cc*
[aglo@localhost nfs-utils]$ sudo mount -o vers=4.1,sec=krb5
192.168.1.72:/nfsshare /mnt
mount.nfs: access denied by server while mounting 192.168.1.72:/nfsshare

Here's the gssd error output: If you look at 1st "INFO: Credentials in
CC .... are good until..." is a lie as there isn't even a file there.

handle_gssd_upcall: 'mech=krb5 uid=0 enctypes=18,17,16,23,3,1,2' (nfs/clnt13)
krb5_use_machine_creds: uid 0 tgtname (null)
gssd_refresh_krb5_machine_credential: hostname=ipa84.gateway.2wire.net
ple=(nil) service=(null) srchost=(null)
Full hostname for 'ipa84.gateway.2wire.net' is 'ipa84.gateway.2wire.net'
Full hostname for 'ipa69.gateway.2wire.net' is 'ipa69.gateway.2wire.net'
No key table entry found for [email protected] while getting
keytab entry for '[email protected]'
No key table entry found for [email protected] while getting
keytab entry for '[email protected]'
No key table entry found for
root/[email protected] while getting keytab
entry for 'root/[email protected]'
Success getting keytab entry for 'nfs/[email protected]'
INFO: Credentials in CC 'FILE:/tmp/krb5ccmachine_GATEWAY.2WIRE.NET'
are good until 1575945300
gssd_refresh_krb5_machine_credential: hostname=(null)
ple=0x7fa590000fa0 service=(null) srchost=(null)
INFO: Credentials in CC 'FILE:/tmp/krb5ccmachine_GATEWAY.2WIRE.NET'
are good until 1575945300
ERROR: GSS-API: error in gss_acquire_cred(): GSS_S_FAILURE
(Unspecified GSS failure. Minor code may provide more information) -
No credentials cache found
WARNING: Failed while limiting krb5 encryption types for user with uid 0
WARNING: Failed to create machine krb5 context with cred cache
FILE:/tmp/krb5ccmachine_GATEWAY.2WIRE.NET for server
ipa84.gateway.2wire.net
WARNING: Machine cache prematurely expired or corrupted trying to
recreate cache for server ipa84.gateway.2wire.net
gssd_refresh_krb5_machine_credential: hostname=ipa84.gateway.2wire.net
ple=(nil) service=(null) srchost=(null)
Full hostname for 'ipa84.gateway.2wire.net' is 'ipa84.gateway.2wire.net'
Full hostname for 'ipa69.gateway.2wire.net' is 'ipa69.gateway.2wire.net'
No key table entry found for [email protected] while getting
keytab entry for '[email protected]'
No key table entry found for [email protected] while getting
keytab entry for '[email protected]'
No key table entry found for
root/[email protected] while getting keytab
entry for 'root/[email protected]'
Success getting keytab entry for 'nfs/[email protected]'
INFO: Credentials in CC 'FILE:/tmp/krb5ccmachine_GATEWAY.2WIRE.NET'
are good until 1575945300
gssd_refresh_krb5_machine_credential: hostname=(null)
ple=0x7fa590000fa0 service=(null) srchost=(null)
INFO: Credentials in CC 'FILE:/tmp/krb5ccmachine_GATEWAY.2WIRE.NET'
are good until 1575945300
ERROR: GSS-API: error in gss_acquire_cred(): GSS_S_FAILURE
(Unspecified GSS failure. Minor code may provide more information) -
No credentials cache found
WARNING: Failed while limiting krb5 encryption types for user with uid 0
WARNING: Failed to create machine krb5 context with cred cache
FILE:/tmp/krb5ccmachine_GATEWAY.2WIRE.NET for server
ipa84.gateway.2wire.net
ERROR: Failed to create machine krb5 context with any credentials
cache for server ipa84.gateway.2wire.net
doing error downcall


After applying my patch. While hard to see the difference but there
are not 2 INFO calls saying creds are good (as it actually gets the
tgt as well)
handle_gssd_upcall: 'mech=krb5 uid=0 service=*
enctypes=18,17,16,23,3,1,2' (nfs/clnt22)
krb5_use_machine_creds: uid 0 tgtname (null)
gssd_refresh_krb5_machine_credential: hostname=ipa84.gateway.2wire.net
ple=(nil) service=* srchost=(null)
Full hostname for 'ipa84.gateway.2wire.net' is 'ipa84.gateway.2wire.net'
Full hostname for 'ipa69.gateway.2wire.net' is 'ipa69.gateway.2wire.net'
No key table entry found for [email protected] while getting
keytab entry for '[email protected]'
No key table entry found for [email protected] while getting
keytab entry for '[email protected]'
No key table entry found for
root/[email protected] while getting keytab
entry for 'root/[email protected]'
Success getting keytab entry for 'nfs/[email protected]'
gssd_get_single_krb5_cred: principal
'nfs/[email protected]'
ccache:'FILE:/tmp/krb5ccmachine_GATEWAY.2WIRE.NET'
gssd_refresh_krb5_machine_credential: hostname=(null)
ple=0x7fed48000fa0 service=(null) srchost=(null)
INFO: Credentials in CC 'FILE:/tmp/krb5ccmachine_GATEWAY.2WIRE.NET'
are good until 1575945968
creating tcp client for server ipa84.gateway.2wire.net
DEBUG: port already set to 2049
creating context with server [email protected]
doing downcall: lifetime_rec=36000 [email protected]

Normally when the ticket cache file is there. It's normal to have 2
INFO lines saying creds are good.

>
> steved.
>
> >
> > Here's my proposed fix (I can send as a patch if this agreed upon).
> >
> > diff --git a/utils/gssd/krb5_util.c b/utils/gssd/krb5_util.c
> > index 0474783..3678524 100644
> > --- a/utils/gssd/krb5_util.c
> > +++ b/utils/gssd/krb5_util.c
> > @@ -121,6 +121,9 @@
> > #include <krb5.h>
> > #include <rpc/auth_gss.h>
> >
> > +#include <sys/types.h>
> > +#include <fcntl.h>
> > +
> > #include "nfslib.h"
> > #include "gssd.h"
> > #include "err_util.h"
> > @@ -314,6 +317,25 @@ gssd_find_existing_krb5_ccache(uid_t uid, char *dirname,
> > return err;
> > }
> >
> > +/* check if the ticket cache exists, if not set nocache=1 so that new
> > + * tgt is gotten
> > + */
> > +static int
> > +gssd_check_if_cc_exists(struct gssd_k5_kt_princ *ple)
> > +{
> > + int fd;
> > + char cc_name[BUFSIZ];
> > +
> > + snprintf(cc_name, sizeof(cc_name), "%s/%s%s_%s",
> > + ccachesearch[0], GSSD_DEFAULT_CRED_PREFIX,
> > + GSSD_DEFAULT_MACHINE_CRED_SUFFIX, ple->realm);
> > + fd = open(cc_name, O_RDONLY);
> > + if (fd < 0)
> > + return 1;
> > + close(fd);
> > + return 0;
> > +}
> > +
> > /*
> > * Obtain credentials via a key in the keytab given
> > * a keytab handle and a gssd_k5_kt_princ structure.
> > @@ -348,6 +370,8 @@ gssd_get_single_krb5_cred(krb5_context context,
> >
> > memset(&my_creds, 0, sizeof(my_creds));
> >
> > + if (!nocache && !use_memcache)
> > + nocache = gssd_check_if_cc_exists(ple);
> > /*
> > * Workaround for clock skew among NFS server, NFS client and KDC
> > * 300 because clock skew must be within 300sec for kerberos
> >
>

2019-12-09 20:07:00

by Steve Dickson

[permalink] [raw]
Subject: Re: gssd question/patch



On 12/9/19 11:49 AM, Olga Kornievskaia wrote:
> Hi Steve,
>
> On Mon, Dec 9, 2019 at 11:10 AM Steve Dickson <[email protected]> wrote:
>>
>> Hey,
>>
>> On 12/6/19 1:29 PM, Olga Kornievskaia wrote:
>>> Hi Steve,
>>>
>>> Question: Is this an interesting failure scenario (bug) that should be
>>> fixed: client did a mount which acquired gss creds and stored in the
>>> credential cache. Then say it umounts at some point. Then for some
>>> reason the Kerberos cache is deleted (rm -f /tmp/krb5cc*). Now client
>>> mounts again. This currently fails. Because gssd uses internal cache
>>> to store creds lifetimes and thinks that tgt is still valid but then
>>> trying to acquire a service ticket it fails (since there is no tgt).
>> I'm unable reproduce the scenario....
>>
>> (as root) mount -o sec=krb5 server:/home/tmp /mnt/tmp
>> (as kuser) kinit kuser
>> (as kuser) touch /mnt/tmp/foobar
>> (as root) umount /mnt/tmp/
>> (as root) rm -f /tmp/krb5cc*
>> (as root) mount -o sec=krb5 server:/home/tmp /mnt/tmp
>> (as kuser) touch /mnt/tmp/foobar # which succeeds
>>
>> Where am I going wrong?
>
> Not sure. Can you please post gssd verbose output?
>
> Set up. Client kernel somewhat recent though the latest, but in
> reality doesn't matter i think
> gssd from nfs-utils commit 5a004c161ff6c671f73a92d818a502264367a896
> "gssd: daemonize earlier"
>
> [aglo@localhost nfs-utils]$ sudo mount -o vers=4.1,sec=krb5
> 192.168.1.72:/nfsshare /mnt
> [aglo@localhost nfs-utils]$ touch /mnt/kerberos
Is there a kinit before this?


> [aglo@localhost nfs-utils]$ sudo umount /mnt
> [aglo@localhost nfs-utils]$ sudo rm -fr /tmp/krb5cc*
> [aglo@localhost nfs-utils]$ sudo mount -o vers=4.1,sec=krb5
> 192.168.1.72:/nfsshare /mnt
> mount.nfs: access denied by server while mounting 192.168.1.72:/nfsshare
>
> Here's the gssd error output: If you look at 1st "INFO: Credentials in
> CC .... are good until..." is a lie as there isn't even a file there.
Here is what I'm seeing:
https://paste.centos.org/view/9473f4a3

steved.

2019-12-09 20:21:38

by Olga Kornievskaia

[permalink] [raw]
Subject: Re: gssd question/patch

On Mon, Dec 9, 2019 at 3:06 PM Steve Dickson <[email protected]> wrote:
>
>
>
> On 12/9/19 11:49 AM, Olga Kornievskaia wrote:
> > Hi Steve,
> >
> > On Mon, Dec 9, 2019 at 11:10 AM Steve Dickson <[email protected]> wrote:
> >>
> >> Hey,
> >>
> >> On 12/6/19 1:29 PM, Olga Kornievskaia wrote:
> >>> Hi Steve,
> >>>
> >>> Question: Is this an interesting failure scenario (bug) that should be
> >>> fixed: client did a mount which acquired gss creds and stored in the
> >>> credential cache. Then say it umounts at some point. Then for some
> >>> reason the Kerberos cache is deleted (rm -f /tmp/krb5cc*). Now client
> >>> mounts again. This currently fails. Because gssd uses internal cache
> >>> to store creds lifetimes and thinks that tgt is still valid but then
> >>> trying to acquire a service ticket it fails (since there is no tgt).
> >> I'm unable reproduce the scenario....
> >>
> >> (as root) mount -o sec=krb5 server:/home/tmp /mnt/tmp
> >> (as kuser) kinit kuser
> >> (as kuser) touch /mnt/tmp/foobar
> >> (as root) umount /mnt/tmp/
> >> (as root) rm -f /tmp/krb5cc*
> >> (as root) mount -o sec=krb5 server:/home/tmp /mnt/tmp
> >> (as kuser) touch /mnt/tmp/foobar # which succeeds
> >>
> >> Where am I going wrong?
> >
> > Not sure. Can you please post gssd verbose output?
> >
> > Set up. Client kernel somewhat recent though the latest, but in
> > reality doesn't matter i think
> > gssd from nfs-utils commit 5a004c161ff6c671f73a92d818a502264367a896
> > "gssd: daemonize earlier"
> >
> > [aglo@localhost nfs-utils]$ sudo mount -o vers=4.1,sec=krb5
> > 192.168.1.72:/nfsshare /mnt
> > [aglo@localhost nfs-utils]$ touch /mnt/kerberos
> Is there a kinit before this?

yep.

> > [aglo@localhost nfs-utils]$ sudo umount /mnt
> > [aglo@localhost nfs-utils]$ sudo rm -fr /tmp/krb5cc*
> > [aglo@localhost nfs-utils]$ sudo mount -o vers=4.1,sec=krb5
> > 192.168.1.72:/nfsshare /mnt
> > mount.nfs: access denied by server while mounting 192.168.1.72:/nfsshare
> >
> > Here's the gssd error output: If you look at 1st "INFO: Credentials in
> > CC .... are good until..." is a lie as there isn't even a file there.
> Here is what I'm seeing:
> https://paste.centos.org/view/9473f4a3

Well, can't see anything there (well I'm seeing the same double INFO
which according to the code pass would not try to get the tgt and it
should fail).

I'm not using gss_proxy. Are you?

>
> steved.
>

2019-12-11 00:45:50

by Olga Kornievskaia

[permalink] [raw]
Subject: Re: gssd question/patch

On Mon, Dec 9, 2019 at 3:20 PM Olga Kornievskaia <[email protected]> wrote:
>
> On Mon, Dec 9, 2019 at 3:06 PM Steve Dickson <[email protected]> wrote:
> >
> >
> >
> > On 12/9/19 11:49 AM, Olga Kornievskaia wrote:
> > > Hi Steve,
> > >
> > > On Mon, Dec 9, 2019 at 11:10 AM Steve Dickson <[email protected]> wrote:
> > >>
> > >> Hey,
> > >>
> > >> On 12/6/19 1:29 PM, Olga Kornievskaia wrote:
> > >>> Hi Steve,
> > >>>
> > >>> Question: Is this an interesting failure scenario (bug) that should be
> > >>> fixed: client did a mount which acquired gss creds and stored in the
> > >>> credential cache. Then say it umounts at some point. Then for some
> > >>> reason the Kerberos cache is deleted (rm -f /tmp/krb5cc*). Now client
> > >>> mounts again. This currently fails. Because gssd uses internal cache
> > >>> to store creds lifetimes and thinks that tgt is still valid but then
> > >>> trying to acquire a service ticket it fails (since there is no tgt).
> > >> I'm unable reproduce the scenario....
> > >>
> > >> (as root) mount -o sec=krb5 server:/home/tmp /mnt/tmp
> > >> (as kuser) kinit kuser
> > >> (as kuser) touch /mnt/tmp/foobar
> > >> (as root) umount /mnt/tmp/
> > >> (as root) rm -f /tmp/krb5cc*
> > >> (as root) mount -o sec=krb5 server:/home/tmp /mnt/tmp
> > >> (as kuser) touch /mnt/tmp/foobar # which succeeds
> > >>
> > >> Where am I going wrong?
> > >
> > > Not sure. Can you please post gssd verbose output?
> > >
> > > Set up. Client kernel somewhat recent though the latest, but in
> > > reality doesn't matter i think
> > > gssd from nfs-utils commit 5a004c161ff6c671f73a92d818a502264367a896
> > > "gssd: daemonize earlier"
> > >
> > > [aglo@localhost nfs-utils]$ sudo mount -o vers=4.1,sec=krb5
> > > 192.168.1.72:/nfsshare /mnt
> > > [aglo@localhost nfs-utils]$ touch /mnt/kerberos
> > Is there a kinit before this?
>
> yep.
>
> > > [aglo@localhost nfs-utils]$ sudo umount /mnt
> > > [aglo@localhost nfs-utils]$ sudo rm -fr /tmp/krb5cc*
> > > [aglo@localhost nfs-utils]$ sudo mount -o vers=4.1,sec=krb5
> > > 192.168.1.72:/nfsshare /mnt
> > > mount.nfs: access denied by server while mounting 192.168.1.72:/nfsshare
> > >
> > > Here's the gssd error output: If you look at 1st "INFO: Credentials in
> > > CC .... are good until..." is a lie as there isn't even a file there.
> > Here is what I'm seeing:
> > https://paste.centos.org/view/9473f4a3
>
> Well, can't see anything there (well I'm seeing the same double INFO
> which according to the code pass would not try to get the tgt and it
> should fail).
>
> I'm not using gss_proxy. Are you?

Any luck reproducing? I asked Jorge to try and he sees the same problem.

>
> >
> > steved.
> >

2019-12-11 16:31:16

by Steve Dickson

[permalink] [raw]
Subject: Re: gssd question/patch



On 12/10/19 7:44 PM, Olga Kornievskaia wrote:
> On Mon, Dec 9, 2019 at 3:20 PM Olga Kornievskaia <[email protected]> wrote:
>>
>> On Mon, Dec 9, 2019 at 3:06 PM Steve Dickson <[email protected]> wrote:
>>>
>>>
>>>
>>> On 12/9/19 11:49 AM, Olga Kornievskaia wrote:
>>>> Hi Steve,
>>>>
>>>> On Mon, Dec 9, 2019 at 11:10 AM Steve Dickson <[email protected]> wrote:
>>>>>
>>>>> Hey,
>>>>>
>>>>> On 12/6/19 1:29 PM, Olga Kornievskaia wrote:
>>>>>> Hi Steve,
>>>>>>
>>>>>> Question: Is this an interesting failure scenario (bug) that should be
>>>>>> fixed: client did a mount which acquired gss creds and stored in the
>>>>>> credential cache. Then say it umounts at some point. Then for some
>>>>>> reason the Kerberos cache is deleted (rm -f /tmp/krb5cc*). Now client
>>>>>> mounts again. This currently fails. Because gssd uses internal cache
>>>>>> to store creds lifetimes and thinks that tgt is still valid but then
>>>>>> trying to acquire a service ticket it fails (since there is no tgt).
>>>>> I'm unable reproduce the scenario....
>>>>>
>>>>> (as root) mount -o sec=krb5 server:/home/tmp /mnt/tmp
>>>>> (as kuser) kinit kuser
>>>>> (as kuser) touch /mnt/tmp/foobar
>>>>> (as root) umount /mnt/tmp/
>>>>> (as root) rm -f /tmp/krb5cc*
>>>>> (as root) mount -o sec=krb5 server:/home/tmp /mnt/tmp
>>>>> (as kuser) touch /mnt/tmp/foobar # which succeeds
>>>>>
>>>>> Where am I going wrong?
>>>>
>>>> Not sure. Can you please post gssd verbose output?
>>>>
>>>> Set up. Client kernel somewhat recent though the latest, but in
>>>> reality doesn't matter i think
>>>> gssd from nfs-utils commit 5a004c161ff6c671f73a92d818a502264367a896
>>>> "gssd: daemonize earlier"
>>>>
>>>> [aglo@localhost nfs-utils]$ sudo mount -o vers=4.1,sec=krb5
>>>> 192.168.1.72:/nfsshare /mnt
>>>> [aglo@localhost nfs-utils]$ touch /mnt/kerberos
>>> Is there a kinit before this?
>>
>> yep.
>>
>>>> [aglo@localhost nfs-utils]$ sudo umount /mnt
>>>> [aglo@localhost nfs-utils]$ sudo rm -fr /tmp/krb5cc*
>>>> [aglo@localhost nfs-utils]$ sudo mount -o vers=4.1,sec=krb5
>>>> 192.168.1.72:/nfsshare /mnt
>>>> mount.nfs: access denied by server while mounting 192.168.1.72:/nfsshare
>>>>
>>>> Here's the gssd error output: If you look at 1st "INFO: Credentials in
>>>> CC .... are good until..." is a lie as there isn't even a file there.
>>> Here is what I'm seeing:
>>> https://paste.centos.org/view/9473f4a3
>>
>> Well, can't see anything there (well I'm seeing the same double INFO
>> which according to the code pass would not try to get the tgt and it
>> should fail).
>>
>> I'm not using gss_proxy. Are you?
Yes I am... I'll try turning it off..

>
> Any luck reproducing? I asked Jorge to try and he sees the same problem.
Not yet... but I'm still trying...

steved.

>
>>
>>>
>>> steved.
>>>
>

2019-12-11 16:42:26

by Steve Dickson

[permalink] [raw]
Subject: Re: gssd question/patch



On 12/6/19 1:29 PM, Olga Kornievskaia wrote:
> Hi Steve,
>
> Question: Is this an interesting failure scenario (bug) that should be
> fixed: client did a mount which acquired gss creds and stored in the
> credential cache. Then say it umounts at some point. Then for some
> reason the Kerberos cache is deleted (rm -f /tmp/krb5cc*). Now client
> mounts again. This currently fails. Because gssd uses internal cache
> to store creds lifetimes and thinks that tgt is still valid but then
> trying to acquire a service ticket it fails (since there is no tgt).
OK... turning off gssproxy... I know see the failure...
>
> Here's my proposed fix (I can send as a patch if this agreed upon).
>
> diff --git a/utils/gssd/krb5_util.c b/utils/gssd/krb5_util.c
> index 0474783..3678524 100644
> --- a/utils/gssd/krb5_util.c
> +++ b/utils/gssd/krb5_util.c
> @@ -121,6 +121,9 @@
> #include <krb5.h>
> #include <rpc/auth_gss.h>
>
> +#include <sys/types.h>
> +#include <fcntl.h>
> +
> #include "nfslib.h"
> #include "gssd.h"
> #include "err_util.h"
> @@ -314,6 +317,25 @@ gssd_find_existing_krb5_ccache(uid_t uid, char *dirname,
> return err;
> }
>
> +/* check if the ticket cache exists, if not set nocache=1 so that new
> + * tgt is gotten
> + */
> +static int
> +gssd_check_if_cc_exists(struct gssd_k5_kt_princ *ple)
> +{
> + int fd;
> + char cc_name[BUFSIZ];
> +
> + snprintf(cc_name, sizeof(cc_name), "%s/%s%s_%s",
> + ccachesearch[0], GSSD_DEFAULT_CRED_PREFIX,
> + GSSD_DEFAULT_MACHINE_CRED_SUFFIX, ple->realm);
> + fd = open(cc_name, O_RDONLY);
> + if (fd < 0)
> + return 1;
> + close(fd);
> + return 0;
> +}
> +
> /*
> * Obtain credentials via a key in the keytab given
> * a keytab handle and a gssd_k5_kt_princ structure.
> @@ -348,6 +370,8 @@ gssd_get_single_krb5_cred(krb5_context context,
>
> memset(&my_creds, 0, sizeof(my_creds));
>
> + if (!nocache && !use_memcache)
> + nocache = gssd_check_if_cc_exists(ple);
> /*
> * Workaround for clock skew among NFS server, NFS client and KDC
> * 300 because clock skew must be within 300sec for kerberos
>
I guess this seem reasonable... but it does apply on the latest upstream
version... So please do the official patch and we'll go from there..

thanks!

steved.