From: Paulo Alcantara <pc@manguebit.com>
To: Steve French <smfrench@gmail.com>,
CIFS <linux-cifs@vger.kernel.org>,
samba-technical <samba-technical@lists.samba.org>
Cc: Shyam Prasad N <nspmangalore@gmail.com>,
Tom Talpey <tom@talpey.com>,
Bharath S M <bharathsm@microsoft.com>
Subject: Re: [SMB3] fix reconnect so it can handle cases where server is doing password rotation
Date: Thu, 04 Apr 2024 21:24:13 -0300 [thread overview]
Message-ID: <b1680423bce48c6ee54e43f894607ba1@manguebit.com> (raw)
In-Reply-To: <CAH2r5muFhPy+zJ7iuyOajVT8PQhO=2ruazg0kkbKOz3_YeNWSw@mail.gmail.com>
Steve French <smfrench@gmail.com> writes:
> An alternative would have been to use the kernel keyring for this but the
> processes doing the reconnect does not have access to the keyring but does
> have access to the ses structure.
Are sure? For example, DNS resolver and kerberos auth require keyring
and are used over reconnect.
prev parent reply other threads:[~2024-04-05 0:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 23:19 [SMB3] fix reconnect so it can handle cases where server is doing password rotation Steve French
2024-04-05 0:24 ` Paulo Alcantara [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=b1680423bce48c6ee54e43f894607ba1@manguebit.com \
--to=pc@manguebit.com \
--cc=bharathsm@microsoft.com \
--cc=linux-cifs@vger.kernel.org \
--cc=nspmangalore@gmail.com \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@gmail.com \
--cc=tom@talpey.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 read-only IMAP folder(s) and NNTP newsgroup(s).