From: "Mantas Mikulėnas" <grawity@gmail.com>
To: Nick Guenther <nick.guenther@polymtl.ca>, linux-cifs@vger.kernel.org
Subject: Re: pam_cifscreds, tmux and session keyrings
Date: Fri, 22 Jul 2022 21:38:25 +0300 [thread overview]
Message-ID: <705265ea-37a3-6029-362a-572bbaab6639@gmail.com> (raw)
In-Reply-To: <774233f766bf26976c0d923cc1dc53c7@polymtl.ca>
On 2022-07-21 23:45, Nick Guenther wrote:
> [...]
> I see in this old thread https://www.spinics.net/lists/linux-cifs/msg18249.html that you actually want to go the _other_ direction, and isolate your sessions even more:
>
>>> multiuser SMB connections should also be initiated per session, same like the
>>> keyring. Currently the cifs SMB connections are accessible also from other all
>>> sessions.
>>
>> That needs to be implemented indeed.
>
> but that doesn't sound like it would make my users happy. In their perspective, tmux should be the same environment as ssh or as the GUI, just more persistent. And I tend to agree.
>
> Anyway, I hope this isn't too intricate or confusing for you. I would really appreciate a second opinion, and maybe a consideration of that patch, if that patch is actually the right answer.
As another user, I'd expect the keyring search to be done recursively --
start from the session keyring as now, but follow the link into the user
keyring, which is usually present (and isn't that its whole purpose?)
Then pam_cifscreds could be told which one to insert keys to, allowing
it to be used both ways depending on needs -- just like how Kerberos or
AFS can also have either isolated credentials or user-wide ones.
next prev parent reply other threads:[~2022-07-22 18:38 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 [this message]
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
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=705265ea-37a3-6029-362a-572bbaab6639@gmail.com \
--to=grawity@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=nick.guenther@polymtl.ca \
/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