Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: "Nick Guenther" <nick.guenther@polymtl.ca>
To: "Nick Guenther" <nick.guenther@polymtl.ca>,
	"CIFS" <linux-cifs@vger.kernel.org>
Cc: "Shyam Prasad N" <nspmangalore@gmail.com>,
	"Steve French" <smfrench@gmail.com>
Subject: Re: [PATCH] pam_cifscreds, tmux and session keyrings
Date: Tue, 16 Aug 2022 19:14:36 +0000	[thread overview]
Message-ID: <aee6b84aa00466880aa7eb2a82d57680@polymtl.ca> (raw)
In-Reply-To: <57efeb6859dbc2a38714fba882a7635b@polymtl.ca>

August 3, 2022 4:29 PM, "Nick Guenther" <nick.guenther@polymtl.ca> wrote:

> August 1, 2022 12:10 AM, "Steve French" <smfrench@gmail.com> wrote:
> 
>> On Thu, Jul 28, 2022 at 9:50 PM Nick Guenther <nick.guenther@polymtl.ca> wrote:
>>> 
>>> Would there be interest in switching to KEY_SPEC_USER_KEYRING? Would it be a good idea? Can I
>>> assume the kernel CIFS code would need a matching change?
>>
>> Adding Shyam to this discussion - interesting questions worth investigating.
>> 
>
> I've written a patch that switches cifs-utils to KEY_SPEC_USER_KEYRING. It seems to behave --
> `keylist list @u` shows the cifs key instead of `keyctl list @s` -- but it doesn't solve my problem
> without being combined with the 'revoke' workaround, because the kernel is still using
> KEY_SPEC_SESSION_KEYRING.

Hey all,

I'm going to unsubscribe from linux-cifs. It's mostly over my head and not really my interests. But if you find some time to review this patch and find interest in it, please make sure to CC me to keep me in the loop!

Thanks for your consideration!

-Nick

      reply	other threads:[~2022-08-16 19:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-21 20:45 pam_cifscreds, tmux and session keyrings Nick Guenther
2022-07-22 18:38 ` Mantas Mikulėnas
2022-07-29  2:47   ` Nick Guenther
2022-08-01  4:10     ` Steve French
2022-08-03 20:29       ` [PATCH] " Nick Guenther
2022-08-16 19:14         ` Nick Guenther [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=aee6b84aa00466880aa7eb2a82d57680@polymtl.ca \
    --to=nick.guenther@polymtl.ca \
    --cc=linux-cifs@vger.kernel.org \
    --cc=nspmangalore@gmail.com \
    --cc=smfrench@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