SYSTEM WARNING: 'file_get_contents(https://www.clearos.com/?rendertype=json&get=header): failed to open stream: Connection refused' in '/var/www/virtual/newwrapper/cf_topmenu.inc' line 5

Anonymous | Login

2024-12-22 00:10 MST

Project: All Projects ClearCenter ClearOS

Main | My View | View Issues | Change Log | Roadmap | Repositories

View Issue Details [ Jump to Notes ]				[ Issue History ] [ Print ]
ID	Project	Category	View Status	Date Submitted	Last Update
0000782	ClearOS	dansguardian-av	public	2012-10-15 09:40	2012-12-12 13:39
Reporter	user2
Assigned To	user2
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	closed	Resolution	duplicate
Platform		OS		OS Version
Product Version
Target Version	6.4.0 Beta 1	Fixed in Version
Summary	0000782: Upper case letters in username (external directory) causes grief
Description	DL: There seems to be a problem CLASSIFYING users to groups in DansGuardian. When we use the ntlm_auth parameter for squid authentication, the authentication works fine. However, when DansGuardian goes to look up the user in the group it is doing so in a case sensitive manner. For example, the user David (mixed case) will not properly classify and will authenticate but will end up in the default policy group because Squid says yes but the group has the user listed as david (lower case)... no match. If we rename the user to david, it all works! For some reason Dansguardian seems to not match the user to the right policy if the NTLM parameter passes any upper case characters. Winbind, of course enumerates all these users in lower case only because ntlm authentication is all caseless and therefore rendered LOWER under the CIFS protocol.
Tags	No tags attached.
Attached Files

Relationships

duplicate of  0000885 closed dsokoloski  Pam_listfile case sensitivity is problematic

Relationships

Notes
(0000610) user2 2012-12-12 13:39	Continued in 0000885 (pam)

Notes

Issue History
Date Modified	Username	Field	Change
2012-10-15 09:40	user2	New Issue
2012-10-15 09:41	user2	Assigned To	=> user2
2012-10-15 09:41	user2	Status	new => confirmed
2012-12-06 12:35	user2	Target Version	6.4.0 Alpha 1 => 6.4.0 Beta 1
2012-12-12 13:38	user2	Relationship added	related to 0000885
2012-12-12 13:39	user2	Note Added: 0000610
2012-12-12 13:39	user2	Relationship replaced	duplicate of 0000885
2012-12-12 13:39	user2	Status	confirmed => resolved
2012-12-12 13:39	user2	Resolution	open => duplicate
2012-12-12 13:39	user2	Status	resolved => closed

Issue History