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 05:30 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
0001170	ClearOS	app-port-forwarding - Port Forwarding	public	2013-06-04 08:33	2013-06-11 12:37
Reporter	bchambers
Assigned To	bchambers
Priority	normal	Severity	major	Reproducibility	always
Status	closed	Resolution	fixed
Platform		OS		OS Version
Product Version	6.4.0
Target Version	6.4.0 Updates	Fixed in Version
Summary	0001170: Possible to create invalid port forward rule when using ranges
Description	Adding port forward range takes a start port and an end port. It is possible to add a range to these fields. Eg. start: 10000:10999 end: 10000:109999 if you you misundertand the input fields. If you do the above, you have created an invalid rule and...drum roll... Firewall then panics... Bad.
Additional Information	Validate start/end to not allow ranges (eg. colon separator).
Tags	No tags attached.
Attached Files

Relationships

Relationships

Notes
(0000870) bchambers (administrator) 2013-06-04 09:27	Source Code Changelog --------------------------------------------------- - Fixed regex which allowed invalid port ranges to be entered [fixed tracker 0001170] File Changes --------------------------------------------------- Details: http://code.clearfoundation.com/svn/revision.php?repname=ClearOS&rev=6093 [^] U webconfig/apps/port_forwarding/trunk/controllers/port_forwarding.php U webconfig/apps/port_forwarding/trunk/deploy/info.php U webconfig/apps/port_forwarding/trunk/language/en_US/port_forwarding_lang.php U webconfig/apps/port_forwarding/trunk/packaging/app-port-forwarding.spec

Notes

Issue History
Date Modified	Username	Field	Change
2013-06-04 08:33	bchambers	New Issue
2013-06-04 08:33	bchambers	Status	new => assigned
2013-06-04 08:33	bchambers	Assigned To	=> bchambers
2013-06-04 09:27	bchambers	Checkin
2013-06-04 09:27	bchambers	Note Added: 0000870
2013-06-04 09:27	bchambers	Status	assigned => resolved
2013-06-04 09:27	bchambers	Resolution	open => fixed
2013-06-11 12:37	bchambers	Status	resolved => closed

Issue History