From: Steve French <smfrench@austin.rr.com>
To: linux-cifs-client@lists.samba.org, linux-fsdevel@vger.kernel.org,
samba-technical@lists.samba.ortg
Subject: share level security mounts and user credentials
Date: Fri, 11 Aug 2006 17:16:51 -0500 [thread overview]
Message-ID: <44DD01D3.6000609@austin.rr.com> (raw)
For the case of mounts to servers (Windows 9x, Windows ME and some
appliances etc.) which only support "share level" security (passwords on
mounts, but no username) ... any opinions about the right multiuser
behavior (in regards to credentials). cifs vfs has two security modes:
1) (default) credentials (the smb_uid on all network requests) used is
always the same over the mount for all users on the system
2) (not default, but enabled when /proc/fs/cifs/MultiuserMount is set to
1) cifs client tries to find a matching smb_uid for the particular user
corresponding to the local linux uid making the request
The difficulty with the latter is that we may have to multiplex among
smb_tids (tree ids) to the same resource, each mounted with different
passwords. It is common to have two different passwords on the same
share (one for full access, one for read only access) so it is
reasonable to assume that one uid would have all requests to that
superblock use a different tid than other users - but it is odd because
there is no username on the wire. Currently cifs code checks at mount
time to see if we have a connection to the target server (ip address)
with a particular username - but it looks like this has to change - we
have to not only check if we have a particular connection with this
password if it is a share level security server but also have to map
access (when MultiuserMount is enabled) to that share from on tid to
another based on the incoming uid.
Ideas?
reply other threads:[~2006-08-11 22:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=44DD01D3.6000609@austin.rr.com \
--to=smfrench@austin.rr.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=samba-technical@lists.samba.ortg \
/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 NNTP newsgroup(s).