From: Steve Dickson <steved@redhat.com>
To: Olga Kornievskaia <olga.kornievskaia@gmail.com>
Cc: linux-nfs@vger.kernel.org, chuck.lever@oracle.com
Subject: Re: [PATCH 0/6] nfs-utils: handle BAD_INTEGRITY ERROR
Date: Wed, 3 Jan 2024 19:38:37 -0500 [thread overview]
Message-ID: <9fc4294f-4fb9-45b7-a4e8-7243f075ea16@redhat.com> (raw)
In-Reply-To: <20231206213332.55565-1-olga.kornievskaia@gmail.com>
On 12/6/23 4:33 PM, Olga Kornievskaia wrote:
> From: Olga Kornievskaia <kolga@netapp.com>
>
> This patch series is re-work of the previous patch series that handles
> gss error for bad integrity. In this version, gssd is changed to use
> rpc_gss_seccreate() function in tirpc which exposes the gss errors to
> the caller. This functionality is further checked with configure for the
> presence of this function in the tirpc library.
>
> Note that the current libtirpc (1.3.4 version) needs a fix to
> rpc_gss_seccreate() to work correctly for the gssd that passes in
> credentials to be used for the gss context establishement.
>
> Olga Kornievskaia (6):
> gssd: revert commit a5f3b7ccb01c
> gssd: revert commit 513630d720bd
> gssd: switch to using rpc_gss_seccreate()
> gssd: handle KRB5_AP_ERR_BAD_INTEGRITY for machine credentials
> gssd: handle KRB5_AP_ERR_BAD_INTEGRITY for user credentials
> configure: check for rpc_gss_seccreate
>
> aclocal/libtirpc.m4 | 5 +++++
> utils/gssd/gssd_proc.c | 26 +++++++++++++++++++++++---
> 2 files changed, 28 insertions(+), 3 deletions(-)
>
Committed... (tag: nfs-utils-2-7-1-rc3)
steved.
prev parent reply other threads:[~2024-01-04 0:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 21:33 [PATCH 0/6] nfs-utils: handle BAD_INTEGRITY ERROR Olga Kornievskaia
2023-12-06 21:33 ` [PATCH 1/6] gssd: revert commit a5f3b7ccb01c Olga Kornievskaia
2024-01-04 14:52 ` Petr Vorel
2023-12-06 21:33 ` [PATCH 2/6] gssd: revert commit 513630d720bd Olga Kornievskaia
2024-01-04 14:46 ` Petr Vorel
2023-12-06 21:33 ` [PATCH 3/6] gssd: switch to using rpc_gss_seccreate() Olga Kornievskaia
2023-12-06 21:33 ` [PATCH 4/6] gssd: handle KRB5_AP_ERR_BAD_INTEGRITY for machine credentials Olga Kornievskaia
2023-12-06 21:33 ` [PATCH 5/6] gssd: handle KRB5_AP_ERR_BAD_INTEGRITY for user credentials Olga Kornievskaia
2023-12-06 21:33 ` [PATCH 6/6] configure: check for rpc_gss_seccreate Olga Kornievskaia
2023-12-07 14:44 ` Chuck Lever
2023-12-07 22:21 ` Olga Kornievskaia
2023-12-07 22:27 ` Chuck Lever
2023-12-08 14:26 ` Olga Kornievskaia
2023-12-08 15:01 ` Steve Dickson
2023-12-08 15:22 ` Chuck Lever
2023-12-08 14:54 ` Steve Dickson
2023-12-07 14:50 ` [PATCH 0/6] nfs-utils: handle BAD_INTEGRITY ERROR Chuck Lever
2024-01-04 0:38 ` 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=9fc4294f-4fb9-45b7-a4e8-7243f075ea16@redhat.com \
--to=steved@redhat.com \
--cc=chuck.lever@oracle.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