Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 70805

Summary:	redhat-config-samba does not display basic security settings correctly
Product:	[Retired] Red Hat Raw Hide	Reporter:	Pavel <pavelr>
Component:	redhat-config-samba	Assignee:	Brent Fox <bfox>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-12-04 19:25:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	67217

Description Pavel 2002-08-05 16:39:22 UTC

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020724

Description of problem:
redhat-config-samba does not "remember" setting in basic server setting/security
dialog. When started, it always displays DOMAIN authentication mode and YES for
encrypt password and update encrypted settings.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.run redhat-config-samba
2.open basic server settings dialog, click security tab.
3.change authentication mode, encrypt password or update encrypted settings.
4. click OK, then click apply button and exit application.
5. run application again
	

Actual Results:  The dialog above will show DOMAIN, YES, YES, but the actual
settings in the config file are as saved.

Expected Results:  Display correct settings

Additional info:

Comment 1 Brent Fox 2002-08-07 03:21:34 UTC

Should be fixed in 0.9.9-1.  Thanks for your report.

QA, please verify.

Comment 2 Jay Turner 2002-09-03 13:23:50 UTC

Deferring as redhat-config-samba wasn't quite ready for the big dance.

Comment 3 Brent Fox 2002-12-04 19:29:57 UTC

This is fixed in cvs now.  Thanks for your report.