SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0002562: Special Character in Password Change - MantisBT
MantisBT - Endian Firewall
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0002562Endian FirewallInput Validationpublic2009-12-17 21:462010-09-21 19:08
Reporterben-endian 
Assigned To 
PrioritynormalSeverityfeatureReproducibilityalways
StatusconfirmedResolutionopen 
PlatformOSOS Version
Product Version2.3 
Target VersionfutureFixed in Version 
Customer Importance
Customer Occurrences
Queue
Summary0002562: Special Character in Password Change
DescriptionYou cannot use an apostrophe in any password (Web,SSH,Dial) I am guessing due to the misinterpretation of it by the server-side scripts. Need to be aware of all special characters and account for them in the password change dialog page. Note the passwords are accepted if entered from the commmand line tools (passwd/htpasswd) but the web interface does not accept any passwords with apostrophe in it.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
has duplicate 0002966closed ra-endian Endian Firewall admin password set 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-12-17 21:46ben-endianNew Issue
2009-12-17 22:12ben-endianNote Added: 0003580
2010-02-04 10:12peter-endianRelationship addedduplicate of 0002653
2010-02-04 10:12peter-endianStatusnew => confirmed
2010-02-04 10:15peter-endianTarget Version => future
2010-06-09 11:37peter-endianRelationship addedhas duplicate 0002966
2010-09-21 19:08peter-endianCategoryGUI => Input Validation

Notes
(0003580)
ben-endian   
2009-12-17 22:12   
The problem from what I can tell is that there are 2 things missing from the /etc/ppp/peers/<uplink> config file:

(1) There is no device listed no matter what is selected (Serial or USB -- /dev/tty.<xxx>) and looking at the setttings file in /var/efw/uplinks/<uplink> there is no "COMPORT=/dev/tty.<xxx>" and even if you manually add the line it doesn't get processed by the uplinksdaemon when it autogenerates the peers file

(2) The peers config file is also missing the reference to the chat script. It should have a line that is similar to following: connect "/usr/sbin/chat -f -v /etc/ppp/chat-<uplink>"