- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- samba 2.2.5: Share security
Operating System - HP-UX
1753891
Members
7659
Online
108809
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2002 03:56 AM
тАО11-07-2002 03:56 AM
samba 2.2.5: Share security
There seem to be two ways to put security on samba shares:
1) with smb.conf params
valid user; read_list , write list etc.
2) using native NT server Manager. samba stores this settings in a file called share_info.tdb.
Question:
Are both ways equivalent or is there a difference i should know?
Regards
Rainer
He's a real UNIX Man, sitting in his UNIX LAN making all his UNIX plans for nobody ...
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2002 07:01 AM
тАО11-07-2002 07:01 AM
Re: samba 2.2.5: Share security
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-07-2002 07:33 AM
тАО11-07-2002 07:33 AM
Re: samba 2.2.5: Share security
The key parameter to security setup is the SECURITY= value. Which can be user, share, server, or domain. For domain and server, samba only uses an NT server for password validation, not file permission determination.
Samba attempts to map the NT username to a unix username. Then whatever security on the unix side is what determines file accesses.
Using read_list or write_list only provides a layer of security that is managed by Samba itself.
Their are of course other options available within Samba on how shares are managed. If you connect via "SWAT", you can look at each configuration parameter, click the "help" and see a good summary of the options available.
HTH
-- Rod Hills
Samba attempts to map the NT username to a unix username. Then whatever security on the unix side is what determines file accesses.
Using read_list or write_list only provides a layer of security that is managed by Samba itself.
Their are of course other options available within Samba on how shares are managed. If you connect via "SWAT", you can look at each configuration parameter, click the "help" and see a good summary of the options available.
HTH
-- Rod Hills
There be dragons...
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP