Bug 131527

Summary:	Samba access level not set to "ressource"
Product:	[openSUSE] SUSE Linux 10.1	Reporter:	Michael Stather <kontakt>
Component:	Network	Assignee:	Lars Müller <lmuelle>
Status:	RESOLVED WONTFIX	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	kde-maintainers, lnussel, samba-maintainers
Version:	RC 1
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Michael Stather 2005-10-31 00:41:29 UTC

When I install the system the access level of Samba isn´t set to "ressource" (at least the KDE control module "samba" doesn´t show it like this. But "ressource" isa the needed level because all other levels require authorisation when looking for shares.

Comment 1 Lars Müller 2005-11-02 12:13:20 UTC

kcm_samba reads the current smb.conf from /etc/samba/ and displays them.  And you got our default Samba config as we package in samba-client.

Ludwig and me recently had the discussion if our current default Samba configuration fits into the non Enterprise Server (ES) products.

As smb.conf is packaged as config(noreplace) I would not change this.  But we might add an additional non ES config which fits better to the needs of a desktop user.

If YaST samba or kcontrol detects a not modified /etc/samba/smb.conf file and we're running on a desktop system we might copy the desktop smb.conf to /etc/samba/smb.conf and continue the work based on ghis suggestion instead of our server config.

Comment 2 Lars Müller 2005-11-02 17:00:40 UTC

How abaout adding a solution to the YaST install workflow?

If we install a desktop Linux we should use the desktop smb.conf and if we have a server system we use the default config from the samba-client package.  This workflow might also include the question for your Microsoft Windows Domain name.

If this is the appropriate way I'll add the suggested desktop smb.conf to the samba-client package and the YaST team could work on the install workflow.

Andreas: Do we need a discussion regarding this feature for 10.1?

Comment 4 Lars Müller 2006-03-15 13:04:01 UTC

The alternative is to create several default config files and package them as:

samba-config-server, samba-config-desktop, samba-server-sles, samba-server-server-PDC, samba-server-server-BDC

All these packages would provide samba-config and all other samba packages would require this meta package.

Klaus and Novell Samba Team:  Please comment on this.

Comment 5 Matej Horvath 2007-02-16 14:34:15 UTC

No reaction on this bug for a long time. Closing as CANTFIX.