SYSTEM WARNING: 'file_get_contents(): SSL: Connection reset by peer' in '/var/www/virtual/newwrapper/cf_topmenu.inc' line 5

SYSTEM WARNING: 'file_get_contents(): Failed to enable crypto' in '/var/www/virtual/newwrapper/cf_topmenu.inc' line 5

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

Anonymous | Login

2024-12-22 00:15 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
0000403	ClearOS	openvpn	public	2011-11-29 06:40	2012-04-18 19:39
Reporter	arkinform
Assigned To	user2
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	fixed
Platform		OS		OS Version
Product Version	5.2
Target Version		Fixed in Version	6.2.0 Beta 2
Summary	0000403: Duplicated OpenVPN config files for the same login in different character case
Description	For example, I create login test_a with OpenVPN access. OpenVPN config files are created in /etc/ssl with name like "..test_a.." Then I login as Test_A. Because of LDAP authentication is case insensitive I can login in Clear OS without problems. Then I go to "Security and Keys" and download my own OpenVPN config files. At this moment Clear OS generate new config file with different name "..Test_A.." May be this problem is not only for OpenVPN config files.
Tags	No tags attached.
Attached Files

Relationships

Relationships

Notes
(0000393) user2 2011-12-01 07:47	The user password change tool won't work either.
(0000394) user2 2011-12-01 07:50	Case insensitive logins are no longer supported, so this won't be an issue moving forward. I don't think the problem is worth backporting a fix to 5.x, but anyone is welcome to disagree an re-open!

Notes

Issue History
Date Modified	Username	Field	Change
2011-11-29 06:40	arkinform	New Issue
2011-12-01 07:06	user2	Status	new => acknowledged
2011-12-01 07:47	user2	Note Added: 0000393
2011-12-01 07:47	user2	Status	acknowledged => confirmed
2011-12-01 07:50	user2	Note Added: 0000394
2011-12-01 07:50	user2	Status	confirmed => resolved
2011-12-01 07:50	user2	Fixed in Version	=> 6.1 Beta 2
2011-12-01 07:50	user2	Resolution	open => fixed
2011-12-01 07:50	user2	Assigned To	=> user2
2012-04-18 19:39	user2	Status	resolved => closed

Issue History