From: Steve Dickson <steved@redhat.com>
To: Olga Kornievskaia <olga.kornievskaia@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v2 0/3] nfs-utils: gssd support for KRB5_AP_ERR_BAD_INTEGRITY
Date: Mon, 16 Oct 2023 12:15:07 -0400 [thread overview]
Message-ID: <82c3168c-acf3-469b-8065-d7731e7e62ff@redhat.com> (raw)
In-Reply-To: <20231004173240.46924-1-olga.kornievskaia@gmail.com>
On 10/4/23 1:32 PM, Olga Kornievskaia wrote:
> From: Olga Kornievskaia <kolga@netapp.com>
>
> Together with libtirpc patch this series attempts to provide
> support for handling KRB5_AP_ERR_BAD_INTEGRITY.
>
> Such error can be returned by the server when it has changed
> its key material and the client is still using the service
> ticket that was issues prior to the change.
>
> Upon calling authgss_create_default() and receiving a NULL
> context, we can inspect the returned structure to see
> if gss major/minor error code was set. If the client
> determines that it received KRB5_AP_ERR_BAD_INTEGRITY error,
> it will proceed to handle it based on what type of credentials
> were used for context establishement. If machine credentials
> were used, the client can call into a routine and force
> credential renewal. If user credentials were used, the client
> needs to remove the existing service ticket and then retry
> the request.
>
> -- fix compile warning in libtirpc patch
>
> Olga Kornievskaia (3):
> gssd: enable forcing cred renewal using the keytab
> gssd: handle KRB5_AP_ERR_BAD_INTEGRITY for machine credentials
> gssd: handle KRB5_AP_ERR_BAD_INTEGRITY for user credentials
Committed... (tag: nfs-utils-2-6-4-rc4)
steved.
>
> utils/gssd/gssd_proc.c | 20 ++++++++++++--
> utils/gssd/krb5_util.c | 62 ++++++++++++++++++++++++++++++++++++------
> utils/gssd/krb5_util.h | 4 ++-
> 3 files changed, 75 insertions(+), 11 deletions(-)
>
prev parent reply other threads:[~2023-10-16 16:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 17:32 [PATCH v2 0/3] nfs-utils: gssd support for KRB5_AP_ERR_BAD_INTEGRITY Olga Kornievskaia
2023-10-04 17:32 ` [PATCH v2 1/1] gss-api: expose gss major/minor error in authgss_refresh() Olga Kornievskaia
2023-10-07 11:00 ` Steve Dickson
2023-10-04 17:32 ` [PATCH 1/3] nfs-utils: gssd: enable forcing cred renewal using the keytab Olga Kornievskaia
2023-10-04 17:32 ` [PATCH 1/1] gssd: fix handling DNS lookup failure Olga Kornievskaia
2023-10-04 17:32 ` [PATCH 2/3] nfs-utils: gssd: handle KRB5_AP_ERR_BAD_INTEGRITY for machine credentials Olga Kornievskaia
2023-10-04 17:32 ` [PATCH 3/3] nfs-utils: gssd: handle KRB5_AP_ERR_BAD_INTEGRITY for user credentials Olga Kornievskaia
2023-10-16 16:15 ` Steve Dickson [this message]
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=82c3168c-acf3-469b-8065-d7731e7e62ff@redhat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=olga.kornievskaia@gmail.com \
/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).