wasn't put this... seemed related stored username & pw mysql & ftp in configuration.php, not completely.
this seen feature request, seen bug fix.
i suggest ftp settings moved database. suggest because if ftp settings set incorrectly, user stuck because can no longer edit these settings (the ftp layer required so). storing these settings in database, possible user change settings without requiring them set properly.
another suggestion might smart 1.6 (i know looking ahead bit, don't think can add 1.5 @ point , want out there before forget), verify ftp settings when entered before written configuration.php file. might go far run jftp unit test specified settings during check, can see not can ftp user connect, jftp class able interact ftp server. additionally, neat provide way user can click submit report button in event unit test fails due reason other failed authentication (we need consult enno), , have try , figure out environment , send us, can see servers failing on.
the first think legitimately put in 1.5 because solves issues arise. second think not suitable current release.
ian
this seen feature request, seen bug fix.
i suggest ftp settings moved database. suggest because if ftp settings set incorrectly, user stuck because can no longer edit these settings (the ftp layer required so). storing these settings in database, possible user change settings without requiring them set properly.
another suggestion might smart 1.6 (i know looking ahead bit, don't think can add 1.5 @ point , want out there before forget), verify ftp settings when entered before written configuration.php file. might go far run jftp unit test specified settings during check, can see not can ftp user connect, jftp class able interact ftp server. additionally, neat provide way user can click submit report button in event unit test fails due reason other failed authentication (we need consult enno), , have try , figure out environment , send us, can see servers failing on.
the first think legitimately put in 1.5 because solves issues arise. second think not suitable current release.
ian
ianmac wrote:wasn't put this... seemed related stored username & pw mysql & ftp in configuration.php, not completely.
this seen feature request, seen bug fix.
i suggest ftp settings moved database. suggest because if ftp settings set incorrectly, user stuck because can no longer edit these settings (the ftp layer required so). storing these settings in database, possible user change settings without requiring them set properly.
another suggestion might smart 1.6 (i know looking ahead bit, don't think can add 1.5 @ point , want out there before forget), verify ftp settings when entered before written configuration.php file. might go far run jftp unit test specified settings during check, can see not can ftp user connect, jftp class able interact ftp server. additionally, neat provide way user can click submit report button in event unit test fails due reason other failed authentication (we need consult enno), , have try , figure out environment , send us, can see servers failing on.
the first think legitimately put in 1.5 because solves issues arise. second think not suitable current release.
ian
good point regarding lock-out.
as database structure has been frozen 1.5:
another more elegant , compatibile possibility solve lock-out issue verify ftp credentials before saving configuration if these have been changed.
security wise, recommend less (if "less" still possible
) store unencrypted sensitive items database php file: i.e. database can accessed sql injection, while reading file content requires taking more control, php or file access control.
Comments
Post a Comment