From: "Aurélien Aptel" <aaptel@suse.com>
To: Shyam Prasad N <nspmangalore@gmail.com>,
Stefan Metzmacher <metze@samba.org>
Cc: Pavel Shilovsky <piastryyy@gmail.com>,
CIFS <linux-cifs@vger.kernel.org>,
sribhat.msa@outlook.com,
samba-technical <samba-technical@lists.samba.org>,
Steve French <smfrench@gmail.com>
Subject: Re: [PATCH][SMB3] mount.cifs integration with PAM
Date: Mon, 01 Feb 2021 11:51:32 +0100 [thread overview]
Message-ID: <871re09i2z.fsf@suse.com> (raw)
In-Reply-To: <CANT5p=rV-KhHtahaF-9YcM5X8jDMLbCx-szwLiZvACRt1oCyow@mail.gmail.com>
Shyam Prasad N <nspmangalore@gmail.com> writes:
> It just occurred to me that integrating with mount.cifs will not
> suffice for a multiuser scenario.
> It sounds like we need to modify cifscreds command to have a switch
> for cifscreds command; if used in krb5 context, instead of dealing
> with kernel keyring, we authenticate with PAM (for add) and call PAM
> logoff (for clear).
> If users are then missing krb5 tickets (logged in to ssh using private
> keys), they can call cifscreds to get the tickets.
>
> @Pavel Shilovsky @Aurélien Aptel Please let me know what you think
> about this approach.
> If you agree, I'll start working on the patch.
Hm what happens where there are multiple mounts with different auth type
on the same machine. e.g.
//host/share1 as userA in /mnt/1 via ntlmssp
//host/share2 as userA in /mnt/2 via krb
cifscreds should change both no?
Cheers,
--
Aurélien Aptel / SUSE Labs Samba Team
GPG: 1839 CB5F 9F5B FB9B AA97 8C99 03C8 A49B 521B D5D3
SUSE Software Solutions Germany GmbH, Maxfeldstr. 5, 90409 Nürnberg, DE
GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 247165 (AG München)
prev parent reply other threads:[~2021-02-01 10:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 5:45 [PATCH][SMB3] mount.cifs integration with PAM Shyam Prasad N
2020-08-14 9:52 ` Aurélien Aptel
[not found] ` <CANT5p=oeY91u17DPe6WO75Eq_bjzrVC0kmAErrZ=h3S1qh-Wxw@mail.gmail.com>
2020-08-17 8:48 ` Aurélien Aptel
[not found] ` <CANT5p=rxp3iQMgxaM_mn3RE3B+zezWr3o8zpkFyWUR27CpeVCA@mail.gmail.com>
2020-09-09 11:04 ` Shyam Prasad N
2020-09-09 14:13 ` Aurélien Aptel
2020-09-09 17:25 ` Shyam Prasad N
2020-09-10 9:43 ` Aurélien Aptel
2020-09-23 12:06 ` Shyam Prasad N
2020-09-23 13:56 ` Aurélien Aptel
2020-09-24 10:39 ` Shyam Prasad N
2020-11-09 23:42 ` Pavel Shilovsky
2020-11-10 13:20 ` Shyam Prasad N
2020-11-10 19:22 ` Pavel Shilovsky
2020-11-27 10:43 ` Shyam Prasad N
2020-12-14 18:03 ` Stefan Metzmacher
[not found] ` <CANT5p=rYiY0xE-35swsFKVitZD2yTchRiReyA0wVvY+mU_qKEw@mail.gmail.com>
2021-01-30 14:24 ` Shyam Prasad N
2021-02-01 10:51 ` Aurélien Aptel [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=871re09i2z.fsf@suse.com \
--to=aaptel@suse.com \
--cc=linux-cifs@vger.kernel.org \
--cc=metze@samba.org \
--cc=nspmangalore@gmail.com \
--cc=piastryyy@gmail.com \
--cc=samba-technical@lists.samba.org \
--cc=smfrench@gmail.com \
--cc=sribhat.msa@outlook.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.