HP3000-L Archives

December 1999, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Michael L Gueterman <[log in to unmask]>
Reply To:
Date:
Fri, 24 Dec 1999 10:31:47 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (83 lines)
Bill,

  There is no direct equivalent to Resource Sharings 'Share Level'
passwords (which are also similar to WIN95/98 shared folder passwords).
You can do something similar by assigning a 'username = ' parameter
into the particular share defintion.  What will then happen is that
when a connection attempt is made by the user, the password that the
user enters will be tested against the list of users in the 'username'
parameter (as well as the default user which can become a nuisance at
times).
For example, lets say that you wanted to create a share named "docs" and
have the files reside in the path "/usr/local/docs".  You can set things
up as follows:

[docs]
 comment = User maintained documentation files.
 guest ok = no
 write ok = yes
 browseable = yes
 path = /usr/local/docs
 username = USER.MAINT,MGR.MAINT


  The above share will be visible in the 'Network Neighborhood'
(via browseable = yes).  Guests are not allowed, so user authentication
will have to occur (guest ok = no).  Users are allowed to update the
files located there (write ok = yes).  The password supplied by the
client will be checked against (in this order):
1.  The default user.
2.  USER.MAINT
3.  MGR.MAINT
  If the password doesn't match any of the mentioned users, then access
will be denied to the share.  Otherwise, the first user which matches
the supplied password will be assigned to that connection.  This means
that the security imposed will be for that MPE USER (i.e. if that user
can't write to those files, then attempts to update files via that
connection will fail even though I set 'write ok = yes' in the share
definition).  This all is predicated on giving the SMBD program PM
capability, and running the daemon under an SM user.

Hopefully that gets you started.  There are other documents that you
might find useful in the docs directory of the Samba installation as
well as at http://www.sambaix.com.

Regards,
Michael L Gueterman
Easy Does It Technologies
SIGWeb Co-Chair
http://www.editcorp.com
voice: (888) 858-EDIT -or- (573_ 368-5478
fax:   (573) 368-5479
--

> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
> Behalf Of bill grefe
> Sent: Friday, December 24, 1999 7:43 AM
> To: [log in to unmask]
> Subject: [HP3000-L] Samba share level passwords
>
>
> I have been using HP's resource sharing up till yesterday.
> On several of
> the shared discs I have had a password assigned.  The users
> would map the
> drive and supply the share password to connect.
> How do I duplicate this using Samba?  The descriptions in
> HP's Instant Info
> didn't help.
>
> On the plus side it only took about 4 hrs of down time to go
> from 5.0 to 6.0
> and another hour or so to get Samba working (without
> passwords or the 10Gb
> of data moved back).
>
> William Grefe
> [log in to unmask]
> PCI-WEDECO Environmental Technologies, Inc.
> phone: 973-575-7052
> fax: 973-575-8941
>

ATOM RSS1 RSS2