-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 17 Oct 2002, Christopher R. Hertel wrote:
Do I understand correctly that Samba does not offer a per-share
password, even when running under security=share?
In the original, outdated design of SMB (COREP.TXT) passwords were
assigned to
On Fri, Oct 18, 2002 at 08:43:53AM -0500, Gerald (Jerry) Carter wrote:
:
Samba always bvalidates a username/password pair. For a share level
equivalent service, do something like
[share1]
username = acct1
force user = acct1
path = /tmp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, 18 Oct 2002, Christopher R. Hertel wrote:
That's what I thought. I'm not trying to make share-level security work
as originally intended, I'm just trying to figure out how we do it.
If the client sent an SMBsessetupX request, we save the
For my book...
Do I understand correctly that Samba does not offer a per-share password,
even when running under security=share?
In the original, outdated design of SMB (COREP.TXT) passwords were assigned
to shares. I don't see a mechanism in newer Samba docs that allows for a
per-share
