Bug 151131

Summary: in security tab auth=user and guest acc= none wont stay set
Product: Red Hat Enterprise Linux 3 Reporter: Nils Philippsen <nphilipp>
Component: redhat-config-sambaAssignee: Nils Philippsen <nphilipp>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 3.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard: RHEL3U7NAK
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-10-19 19:06:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On: 121745    
Bug Blocks: 189875    

Description Nils Philippsen 2005-03-15 08:16:27 UTC
+++ This bug was initially created as a clone of Bug #121745 +++

Description of problem:
in security tab under server settings auth=user and guest acc= none
wont stay set - they change to auth=share and or guest acc=nobody

Version-Release number of selected component (if applicable):
Samba Server Configuration Tool 1.1.4

How reproducible:

Steps to Reproduce:
1.set AUTH to "user"
2.set guest acc to "no guest account"
3.click ok
4.exit the app
5. start the app
6. goto the security tab
Actual results:
they change to auth=share and or guest acc=nobody

Expected results:
should stay at what i set

Additional info:

Comment 1 Nils Philippsen 2005-03-15 08:17:15 UTC
Fix backported to RHEL3 in redhat-config-samba-1.0.16-4.

Comment 2 Nils Philippsen 2005-07-29 09:18:27 UTC
Fix backed out again in redhat-config-samba-1.0.16-5.

Comment 8 RHEL Product and Program Management 2007-10-19 19:06:16 UTC
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.