CHANGELOG
! SECURITY: Workaround for MySQL security issue CVE-2016-5483 (https://blog.tarq.io/cve-2016-5483-backdooring-mysqldump-backups/) affecting SQL-only backups. This is a security issue in MySQL itself, not our backup engine.
+ JPS format v2.0 with improved password security
+ Restoration: options to remove server files which can get in the way of restored sites
~ Warn about queries over 1Mb which could cause backup restoration issues
~ Now using the Reverse Engineering database dump engine when a Native database dump engine is not available (PostgreSQL, Microsoft SQL Server, SQLite)
~ PHP 5.3 compatibility in PushMessages
# [HIGH] Restoration dies when no download adapter is availabl
e and you choose to replace the .htaccess file with the default
# [HIGH] PHP's memory_limit given in bytes (e.g. 134217728 instead of 128M) prevent the backup from running
# [HIGH] PHP Fatal Error if the row batch size leads to an amo
unt of data that exceeds free PHP memory
# [HIGH] Large database records can cause an infinitely growin
g runaway backup or, if you're lucky, a backup crash due to exceeding PHP time limits.
# [MEDIUM] Logic error leads to leftover temporary database du
mp files in the backup output directory under some circumstances
# [MEDIUM] Blank page if you delete all backup profiles from t
he database (a default backup profile could not be created in this case)
# [MEDIUM] Database storage wouldn't report the lack of stored
engine state, potentially causing forever stuck backups
# [MEDIUM] Database hostname localhost:3306 leads to connectio
n error under some circumstances. Note that this hostname is wrong: you should use localhost without a
port instead!
# [MEDIUM] Infinite recursion if the current profile doesn't exist
# [MEDIUM] Views defined against fully qualified tables (i.e. including the database name) could not be restored on a database with a different name
# [LOW] PHP 5.3 compatibility in the OpenSSL adapter (settings encryption)
# [LOW] FTP/SFTP over cURL uploads would fail if the remote di
rectory couldn't be created
# [LOW] The wrong message is shown by ANGIE when performing an
integrated restoration through Akeeba Backup for Joomla!