Red Hat: 2014:0231-01: openstack-nova: Moderate Advisory
(Mar 4) Updated openstack-nova packages that fix multiple security issues and several bugs are now available for Red Hat Enterprise Linux OpenStack Platform 4.0. [More…]
(Mar 4) Updated openstack-nova packages that fix multiple security issues and several bugs are now available for Red Hat Enterprise Linux OpenStack Platform 4.0. [More…]
What’s Changed
[+] Migration from Helm to Parallels Plesk Automation is now supported.
[*] The stability of the migration tool was improved. In case of network connection problems, operations are repeated several times.
[*] Error reporting in the migration tool was improved.
[*] Now Parallels Plesk Automation performs the proper translation of IP addresses during migration.
[*] Now instructions on attaching service nodes running Windows 2012 R2 are available in the Deployment Guide.
[*] The Integration Guide was updated with information about how to use the API for creating subscriptions with multiple webspaces.
[*] The Integration Guide was updated with information about how to manage DNS zones by means of the API.
[-] Updating of Parallels Plesk Automation could be blocked if users were logged in to it. The following error occurred: “[Errno 2] No such file or directory: ‘/var/cache/ppa/uc_cache/tmpGJ_m8x'”.
[-] Instead of a PHP handler’s php.ini file, the system default php.ini file was used to generate a domain-level php.ini file. As a result, sometimes custom PHP for a domain did not work.
[-] After upgrading from Parallels Plesk Automation 11.1 to 11.5, web statistics stopped working on Apache nodes.
[-] Installation of Parallels Plesk Automation failed if the SELinux configuration file /selinux/enforce was empty or the SELinux utility failed to execute the command ‘/usr/sbin/setenforce’, ‘0’.
[-] Disabled DNS zones could become enabled after syncing settings between the Administration Panel with the Hosting Panel.
[-] The link to user documentation in the Administration Panel led to a wrong page.
[-] Users who used an email address as a username could not use the backup and restoration tools.
[-] Upgrade of Parallels Plesk Automation could fail if YUM was not installed or configured, or if repositories were not accessible.
[-] Upgrade of Parallels Plesk Automation could fail if the management node could not connect to service nodes.
[-] When customers changed or added DNS records by means of the API or the console utility /usr/local/psa/bin/dns, the domain zones were filled with duplicated entries.
[-] Administrators could not add more than 256 IP addresses. The following error occurred: “Internal error: Incorrect format of RTM_GETADDR request response.”
[-] Users could not change the IP addresses of the management node by means of the ppa.ip_address utility. The following error occurred: “APS resource for ‘/aps/2/application/dns-record-mx/f81a9762-6149-42fa-8689-4ac20fff61b1’ with id ‘4555’ hasn’t been deleted. Error code: 500.”
[-] Users could not view the web server access logs for add-on domains on Apache-based hosting.
[-] After suspending and unsuspending domains hosted on IIS, users could no longer manage files in File Manager. The following error occurred: “Internal error: Unable to logon user (<host name>sub6_83s): (1331) Logon failure: account currently disabled.
[-] Users could not transfer subscriptions that used Microsoft SQL Server databases to Parallels Plesk Automation.
[-] IIS-based subscriptions could not be completely removed. Some configuration files remained in the file system after removal.
[-] Administrators could not add service nodes when the root login on the nodes was disabled, and sudo was enabled for another user.
[-] Administrators could not log in to a customer’s Hosting Panel from Parallels Business Automation Standard. The following error occurred: “Error: Logged user has no access to the subscription”.
[-] IIS-based sites using MySQL were working very slowly.
[-] Users could not create a webspace on an already existing domain.
[-] The migration tool failed to update itself.
[-] Users could not migrate subscriptions from Plesk 11.5 to Parallels Plesk Automation 11.5. The following error occurred: “Line 177 error: Element ‘cron’, attribute ‘encoding’: The attribute ‘encoding’ is not allowed.”
[-] Users could not migrate subscriptions from Plesk for Linux to Parallels Plesk Automation, if the default Linux Shared Hosting service template was used. The following error occurred: “Mail content transfer from Qmail/Postfix to SmarterMail mail service is not supported. Assign this subscription to a service template which offers Postfix mail service.”
[-] Users could not migrate Microsoft SQL Server databases. The following error occurred: “Subscription is assigned to PPA service template <template name> that has no Microsoft SQL database service. Assign this subscription to a service template which offers Microsoft SQL database service.”
[-] Users could not migrate from Plesk for Windows to Parallels Plesk Automation. The following error occurred: [ERROR] check-infrastructure| Failed to check disk space requirements. Exception message: (u’Failed to detect Plesk virtual hosts directory, reg query output is incorrect: %s’, u’
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control Session Manager\Environment plesk_vhosts REG_EXPAND_SZ D:\vhosts ‘)
[-] Migration from H-Sphere could fail even if there was a single subscription with issues.
[-] During migration from Expand, users failed to run the ppa-transfer check.
The Joomla! Project and the Production Leadership Team are proud to announce the release of Joomla! 3.2.3 which is a security release and also resolves a significant number of issues and bugs.
If you are currently running Joomla! 3.2, we urge you to apply this update immediately via either the one-click update or the update downloads available at http://www.joomla.org/download.html. For other versions of the 3.x series, applying the update is recommended as soon as possible.
Inadequate checking allowed unauthorised logins via GMail authentication.
Joomla! CMS versions 2.5.18 and earlier 2.5.x versions, 3.2.2 and earlier 3.x versions
Upgrade to version 2.5.19 or 3.2.3
The JSST at the Joomla! Security Center.
Inadequate escaping leads to XSS vulnerability.
Joomla! CMS versions 2.5.18 and earlier 2.5.x versions, 3.2.2 and earlier 3.x versions
Upgrade to version 2.5.19 or 3.2.3
The JSST at the Joomla! Security Center.
58 queries. 8.5 mb Memory usage. 0.596 seconds.