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:07 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
0000447	ClearOS	firewall	public	2012-02-27 15:45	2012-04-18 19:39
Reporter	dsokoloski
Assigned To	dsokoloski
Priority	normal	Severity	minor	Reproducibility	always
Status	closed	Resolution	fixed
Platform		OS		OS Version
Product Version
Target Version		Fixed in Version
Summary	0000447: Firewall rule host/domain name resolution
Description	The current ClearOS firewall (all versions) uses gethostbynam() to resolve host/domain names. If the look-up is successful, one one IP address is returned to the calling firewall script. This is not correct behavior for multi-homed servers where more than one address is assigned (ex: google.com). For those users who want to block a host/domain name, the firewall __lua_gethostbyname function needs to be changed to use getaddrinfo which returns multiple addresses.
Tags	No tags attached.
Attached Files

Relationships

Relationships

Notes
(0000409) dsokoloski (developer) 2012-02-28 11:35	Source Code Changelog --------------------------------------------------- - Changed __lua_gethostbyname to use getaddrinfo, returns a LUA table with one or more IPv4 or IPv6 (depending on build options) addresses. [fixed tracker 0000447] File Changes --------------------------------------------------- Details: http://code.clearfoundation.com/svn/revision.php?repname=ClearOS&rev=3399 [^] U packages/firewall/trunk/firewall.c U packages/firewall/trunk/firewall.spec.in

Notes

Issue History
Date Modified	Username	Field	Change
2012-02-27 15:45	dsokoloski	New Issue
2012-02-27 15:45	dsokoloski	Status	new => assigned
2012-02-27 15:45	dsokoloski	Assigned To	=> dsokoloski
2012-02-28 11:35	dsokoloski	Checkin
2012-02-28 11:35	dsokoloski	Note Added: 0000409
2012-02-28 11:35	dsokoloski	Status	assigned => resolved
2012-02-28 11:35	dsokoloski	Resolution	open => fixed
2012-04-18 19:39	user2	Status	resolved => closed

Issue History