BZ#720458

If a server sent a response to an unbind request and the client simply closed the connection, Directory Server 8.2 logged "Netscape Portable Runtime error -5961 (TCP connection reset by peer.)".

BZ#752155

An incorrect SELinux context caused AVC errors in /var/log/audit/audit.log.

BZ#697663, BZ#700665, BZ#711533, BZ#711241, BZ#726136, BZ#700215

A number of memory leaks and performance errors were fixed.

BZ#711266

The DS could not restart after a new object class was created which used the entryUSN attribute.

BZ#712167

The ns-slapd process segfaulted if suffix referrals were enabled.

BZ#711513

A high volume of TCP traffic could cause the slapd process to quit responding to clients.

BZ#714298

Attempting to delete a VLV index caused the server to hang.

BZ#720051

Connections to the DS by an RSA authentication server using simple paged results by default would timeout.

BZ#735217

Running a simple paged search against a subtree with a host-based ACI would hang the server.

BZ#733443

If the target attribute list for an ACI had syntax errors and more than five attributes, the server crashed.

BZ#734267

It was not possible to set account lockout policies after upgrading from RHDS 8.1.

BZ#720452

Adding an entry with an RDN containing a % caused the server to crash.

BZ#709868

Only FIPS-supported ciphers can be used if the server is running in FIPS mode.

BZ#711265

It is possible to disable SSLv3 and only allow TLS.

BZ#713317, BZ#713318

If the changelog was encrypted and the certificate became corrupt, the server crashed.

BZ#733434

If the passwordisglobalpolicy attribute was enabled on a chained server, a secure connection to the master failed.

BZ#714310

If a chained database was replicated, the server could segfault.

BZ#694571

Editing a replication agreement to use SASL/GSS-API failed with GSS-API errors.

BZ#742611

In replication, a msgid may not be sent to the right thread, which caused "Bad parameter to an LDAP routine" errors. This causes failures to propagate up and halt replication.

BZ#701057

Password changes were replicated among masters replication, but not to consumers.

BZ#717066

If an entry was modified on RHDS and the corresponding entry was deleted on the Windows side, the sync operation attempts to use the wrong entry.

BZ#734831

Some changes were not properly synced over to RHDS from Windows.

BZ#726273

RHDS entries were not synced over to Windows if the user's CN had a comma.

BZ#718351

Intensive update loads on master servers could break the cache on the consumer, causing it to crash.

BZ#699458

Syncing a multi-valued attribute could delete all the other instances of that attribute when a new value was added.

BZ#729817

If a synced user subtree on Windows was deleted and then a user password was changed on the RHDS, the DS would crash.

BZ#742382

The nsslapd-idlistscanlimit configuration attribute can be set dynamically, instead of requiring a restart.

BZ#742661

Separate resource limits can be set for paged searches, independent of resource limits for regular searches.

BZ#720459

The sudo schema has been updated.

BZ#739959

A new configuration attribute sets a different list of replicated attributes for a total update versus an incremental update.

BZ#733440

A new configuration option allows the server to be started with an expired certificate.

BZ#720461

New TLS/SSL error messages have been added to the replication error log level.

BZ#758682

When the LDAP server was under a heavy load, and the network was congested, client connections could experience problems. If there was a connection problem while the server was sending Simple Paged Result (SPR) search results to the client, the LDAP server called a cleanup routine incorrectly. This led to a memory leak and the server terminated unexpectedly. With this update, the underlying code has been modified to ensure that cleanup tasks are run correctly and memory leaks no longer occur. The LDAP server no longer crashes in this scenario.

BZ#758683

Previously, certain operations with the Change Sequence Number (CSN) were not very effective in 389 Directory Server. Therefore, performing a large number of the modrdn operations during Directory Server content replications led to poor performance, and the ns-slapd daemon consumed up to 100% CPU under these circumstances. With this update, the underlying code has been modified to use these CSN operations efficiently so that replications in Directory Server now work as expected in this scenario.

BZ#758688

Previously, allocated memory was not correctly released in the underlying code for the SASL GSSAPI authentication method, when checking the Simple Authentication and Security Layer (SASL) identity mappings. This problem could cause memory leaks when processing SASL bind requests, which eventually caused the LDAP server to terminate unexpectedly with a segmentation fault. This update adds function calls that are needed to free allocated memory correctly. Memory leaks no longer occur and the LDAP server no longer crashes in this scenario.

BZ#771631

Previously, 389 Directory Server used the Netscape Portable Runtime (NSPR) implementation of the read/write locking mechanism. This implementation allowed deadlocks to occur if 389 Directory Server was under a heavy load, which caused the server to become unresponsive. With this update, 389 Directory Server now uses the POSIX implementation of the locking mechanism, and deadlocks no longer occur under a heavy load.

BZ#771632

Under a heavy load in replicated environments, 389 Directory Server did not handle the Entry USN index correctly. Consequently, the index could become out of sync with the main database and search operations on USN entries returned incorrect results. This update modifies the Entry USN plug-in and 389 Directory Server now handles the Entry USN index as expected.

BZ#610603

The abrt-gui application used to list plug-ins multiple times if they were configured in the configuration file. This is now fixed.

BZ#627621

In the previous version of ABRT, a daemon restart was required for any changes in the configuration to take effect. In the new version, most of the options in the configuration file no longer require a restart.

BZ#653872

Support for retrace server has been added. Refer to https://fedorahosted.org/abrt/wiki/AbrtRetraceServer for more information about this new feature.

BZ#671354

By default, ABRT stores all problem information in the /var/spool/abrt/ directory. Previously, this path was hard coded and could not be changed in the configuration. With this update, this path can be changed in the /etc/abrt/abrt.conf configuration file.

BZ#671359

The previous documentation failed to cover some customer use cases. This error has been fixed, and all of these use cases are now covered in the Red Hat Enterprise Linux 6 Deployment Guide.

BZ#673173

In ABRT version 1, it was not possible to use wildcards to specify that some action should happen for any user. ABRT version 2 adds support for this functionality.

BZ#695416

The lacking information about configuring a proxy has been added to the Red Hat Enterprise Linux 6 Deployment Guide.

BZ#707950

Previously, a bug in ABRT version 1 was preventing a local Python build to finish. This is now fixed.

BZ#725660

The previous report tool and report library have been obsoleted by abrt and libreport. Users can notice the change in the problem reporting user interface of Anaconda, setroubleshoot, and ABRT.

BZ#674883

Prior to this update, the setfacl.1 man page was not intelligible in that it did not state that removing a non-existent ACL entry is not considered to be an error. With this update, the setfacl.1 man page has been updated so that its content is now intelligible and exactly specifies the aforementioned behavior with regard to removing a non-existent ACL entry.

BZ#702638

Prior to this update, the package specification did not reflect a change of the upstream project web page address. This update corrects the respective address in the package specification.

BZ#720318

Prior to this update, the ACL library did not provide any function to check for extended ACLs of a file without following symbolic links. The only available function, acl_extended_file(), used to cause unnecessary mounts of autofs. This update introduces a new function, acl_extended_file_nofollow(), that checks for extended ACLs of a file without following symbolic links.

BZ#723998

Previously, the ACL library was linked without support for RELRO (read-only relocations) flags. With this update, the library is now linked with partial RELRO support.

BZ#811936

Previously, the aide utility incorrectly initialized the gcrypt library. This consequently prevented aide to initialize its database if the system was running in FIPS-compliant mode. The initialization routine has been corrected, and along with an extension to the libgcrypt's API introduced in the RHEA-2012:0486 advisory, aide now initializes its database as expected if run in a FIPS-compliant way.

BZ#704772

Prior to this update, the alsa output plugin for the Audacious Audio Player did not work correctly. As a result, Audacious could under certain circumstances fail to generate any sound and display error messages. With this update, alsa-lib is modified so that Audacious can now generate sound as expected.

BZ#641861

Issues with "interactive" mode partitioning are fixed.

BZ#731274

The network command is parsed correctly.

BZ#689996

The /boot partition on EFI systems is handled correctly.

BZ#705274

Files that are necessary for libreport and SSL installation mode have been added.

BZ#676404

Symbolic links to LVM commands have been added to the rescue image.

BZ#730650

The /sbin/cio_ignore command is added to initrd.img for IBM System z.

BZ#689029

Support for dracut-style "rdloaddriver=" and "rdblacklist=" parameters is added.

BZ#679108

Support for static addresses in "ipv6=" is added.

BZ#706099

A testing framework for stub commands is added.

BZ#699745

Driver disks support multiple kernel versions and are also built for Red Hat Enterprise Linux 6.0 and 6.1.

BZ#668570

Network connection is brought up before saving a bug report.

BZ#715130

Errors in .treeinfo are detected.

BZ#698282

The xhost authentication is changed when performing live installation.

BZ#664981, BZ#726804

Debugging improvements in loader and package installation code have been made.

BZ#679810

The dialog box focus and initialization have been corrected.

BZ#701220

The iSCSI Login button is disabled when no nodes are selected.

BZ#695362

When a mount point is set to /boot, the file system type is no longer changed.

BZ#728280, BZ#725777, BZ#723194, BZ#723344, BZ#694800, BZ#621175

EDD handling improvements have been made, including Xen and CCISS.

BZ#698429

Extended partitions are handled correctly.

BZ#681803

Handling of "network --device=bootif" is corrected.

BZ#750764

Centering of the Anaconda window when an external display is present is corrected.

BZ#605938

Encrypted device lines written to kickstart files are corrected.

BZ#618535

zFCP multipath devices can be added in the user interface as expected.

BZ#732380

iSCSI discovery that returns no devices is handled correctly.

BZ#704593

Systems with more than 2147483647 kB of memory are handled properly.

BZ#712487

The header image is hidden on all but 800x600 displays.

BZ#690058

The "noprobe" parameter for driver disks is honored.

BZ#713991

The "linksleep=" boot parameter is honored.

BZ#699640

Installation sources (including NFS ISO storages) are mounted correctly.

BZ#679397

Processes in the anaconda process group are killed when the system is shut down.

BZ#693271

Partitioning alignment is corrected.

BZ#616641

Progress indicator improvements for device discovery and command line mode have been made.

BZ#691817, BZ#690748

Kickstart network failures and device name collisions are handled properly.

BZ#691910

The "crashkernel=" parameter in a kickstart file is handled properly.

BZ#712195

Support for the "ext4migrate" parameter has been removed.

BZ#706675

The language and keyboard selection screens are now skipped in stage2 when possible.

BZ#614504

Device capacity values are sorted as numbers, not characters.

BZ#695740

Swap partitions are handled correctly.

BZ#676118

The "--target" option is used in kickstart files for iSCSI devices.

BZ#701371, BZ#696876, BZ#674241, BZ#734374, BZ#729716

Various multipath and raid storage bugs are fixed.

BZ#679073

Anaconda verifies that devices specified with "part" can be partitioned.

BZ#659790

Vendor-provided tools on driver disks are now allowed.

BZ#694198

The initrd.img file is compressed with LZMA.

BZ#696696

The "noverifyssl" boot parameter is added.

BZ#697419

The tboot package is configured when it is installed.

BZ#709653

Multipath device can now be specified using WWID.

BZ#830265

Previously, a bug in the handling of IPv6 sockets was present in the apr_mcast_hops() function. This bug could have prevented applications from successfully using multicast with IPv6 sockets. With this update, this bug has been fixed so that the applications now operate correctly.

BZ#783190

Due to an error in the time-parsing routine, the "at" command incorrectly calculated the year when a job was scheduled by using days on input. For example: "at now + 10 days". This update fixes erroneous grammar so that "at" now schedules jobs correctly.

BZ#651119

Prior to this update, the setfattr utility could not restore the original values of the attributes when the "getfattr -e text" or "getfattr --encoding=text" command was used to dump attributes with embedded null characters. This update fixes the encoding of these values in getfattr to prevent information loss.

BZ#665049

Prior to this update, the getfattr utility followed symbolic links to directories even if the "-h" or "--no-dereference" option was specified. Additionally, the description in the getfattr(1) man page that related to this functionality was misleading. This update fixes getfattr with the "-h" option so that it no longer follows the symbolic links and the related content of the getfattr(1) man page is now correct.

BZ#665050

Prior to this update, the getfattr utility did not return a non-zero exit code when an attribute specified in the "getfattr" command did not exist. This update fixes getfattr so that it now returns a non-zero exit code when an attribute does not exist.

BZ#674870

Prior to this update, supported methods for encoding values of the extended attributes were not properly described in the setfattr(1) man page. This update adds the appropriate descriptions of the encoding methods to the setfattr(1) man page.

BZ#702639

Prior to this update, the project web page address as stated in the package specification did not reflect the change of the upstream project web page address. This update corrects the project web page address in the package specification.

BZ#727307

Prior to this update, the attr library was built without support for read-only relocations (RELRO) flags. With this update, the library is now built with partial RELRO support.

BZ#715279

Previously, the audit daemon was logging messages even when configured to ignore "disk full" and "disk error" actions. With this update, audit now does nothing if it is set to ignore these actions, and no messages are logged in the described scenario.

BZ#715315

Previously, the Audit remote logging client received a "disk error" event instead of "disk full" event from a server when the server's disk space ran out. This bug has been fixed and the logging client now returns the correct event in the described scenario.

BZ#748124

Prior to this update, the audit system was identifying the accept4() system call as the now deprecated paccept() system call. Now, the code has been fixed and audit uses the correct identifier for the accept4() system call.

BZ#709345

Previously, the "auditctl -l" command returned 0 even if it failed because of dropped capabilities. This bug has been fixed and a non-zero value is now returned if the operation is not permitted.

BZ#728475

When Kerberos support was disabled, some configuration options in the audisp-remote.conf file related to Kerberos 5 generated warning messages about GSSAPI support during boot. With this update, the options are now commented out in the described scenario and the messages are no longer returned.

BZ#700005

On i386 and IBM System z architectures, the "autrace -r /bin/ls" command returned error messages even though all relevant rules were added correctly. This bug has been fixed and no error messages about sending add rule data requests are now returned in the described scenario.

BZ#693539

Previously, due to a bug in the source code, parsing invalid files failed silently without any error message. With this update, error messages are provided to inform users about the problem.

Bug Fixes

BZ#704935

The autofs utility did not reset the map entry status on a reload request. As a result, newly added map entries that had previously recorded a mount failure failed to work. With this update, autofs resets the map entry status on a reload request and map entries are mounted as expected.

BZ#704939

The autofs utility could have terminated with a segmentation fault when attempting certain mounts. This occurred due to a race condition between mount handling threads for mounts that had previously recorded a mount failure. The automount cache map entry is now verified to be valid.

BZ#704940

The automount(8) man page referred to a non-existent man page. This was caused by a typographical error in the code. With this update, the man page reference has been corrected and the man page is displayed as expected.

BZ#704929

Due to a deadlock, autofs could stop responding when attempting to mount map entries that were nested within maps. With this update, the underlying code has been changed and, where possible, nested map entries mount correctly.

BZ#704933

Prior to this update, automount could terminate unexpectedly with a pthreads error. This occurred because attempts to acquire the master map lock occasionally failed as the lock was held by another thread. With this update, the underlying code has been adapted to wait for a short time before failing.

BZ#704928, BZ#704927

When retrieving paged results from an LDAP (Lightweight Directory Access Protocol) server, autofs handled certain cases incorrectly, which caused the query to not obtain all results. This update adds the code that handles these additional cases.

BZ#704937

Prior to this update, if a key entry of an automount map began with an asterisk (*) sign, the daemon failed with a segmentation fault because the sign was not matched correctly. With this update, such asterisk signs are handled correctly.

BZ#704228

When using GSSAPI authentication, the fact that an incorrect authentication host name was being used caused the connection to fail. This update now gets the correct host name for the connection.

BZ#692816

automount was not performing sufficient sanity checks of server names in its configuration. This update corrects the configuration entry parsing.

BZ#700136

Error reporting for invalid mount locations was unclear. This update improves the error reporting.

BZ#703332

When an automount map key is present in a file map and is also present in an included map source, if the file map entry was removed and a lookup performed before a re-load was issued, the map lookup would have failed. This update corrects the logic used to determine if the lookup needs to continue into included maps.

BZ#718927

When reloading maps that include a combination of direct and indirect maps, it was possible for automount to deadlock due to incorrect lock ordering.

BZ#

There was inadvertent use of a small amount of GPLv3-licensed code from Samba in autofs. While this was permissible, it would have entailed explicitly relicensing autofs from "GPLv2 or later" to "GPLv3", which is not intended for autofs at this time. Therefore, the Samba-derived code has been replaced in order to maintain the "GPLv2 or later" licensing status of autofs.

Enhancements

BZ#704416

This update adds the "--dumpmaps" option to the automount command, which allows you to dump the maps from their source as seen by the automount daemon.

BZ#704932

This update adds simple Base64 encoding for LDAP and thus allows hashing of the password entries in the /etc/autofs_ldap_auth.conf configuration file.

BZ#787122

A function to check validity of a mount location was meant to check only for a small subset of map location errors. A recent improvement modification in error reporting inverted a logic test in this validating function. Consequently, the scope of the test was widened, which caused automount to report false positive failures. With this update, the faulty logic test has been corrected and false positive failures no longer occur.

Bug Fix

BZ#658057

When installing autotrace-devel multilib RPM packages from the optional repository, file conflicts between these packages appeared, causing the installation transaction to abort. This problem has been fixed and the installation transaction now proceeds without conflicts.

BZ#651776

Prior to this update, the bacula packages were not distributed with the applybaculadate file. As a result, the logwatch cron script failed. The problem has been fixed by including the applybaculadate file in the bacula packages so that the logwatch cron script now works as expected.

BZ#651780

Prior to this update, the make_catalog_backup.pl script created a MySQL configuration file, which had the file permissions set to world-writeable and world-readable so that MySQL did not accept the configuration file with these permissions and the MySQL database login configuration was not used. As a result, it was not possible to complete a MySQL database dump. With this update, the configuration file is now created with correct permissions, and the MySQL database login configuration is used by MySQL so that it is now possible to complete the MySQL database dump as expected.

BZ#651786

Prior to this update, there was no option to change Bacula's runtime user. As a consequence, Bacula was always run under the root user. The problem has been fixed by adding support for the bacula-dir, bacula-fd, and bacula-sd files in the /etc/sysconfig/ directory; these files can be used for specifying a non-root user and group with the DIR_USER, FD_USER, SD_USER, and DIR_GROUP, FD_GROUP and SD_GROUP options, respectively. With this update, Bacula can be run under the specified user.

BZ#651787

Prior to this update, when creating a symbolic link to the "bscan" utility, the new link was erroneously named "dbcheck". As a result, the already existing "dbcheck" symbolic link was overwritten by the erroneous one. Thus the "dbcheck" command ran the "bscan" utility so that it was not possible to execute the "bscan" utility with the "bscan" command. The problem has been fixed in this update so that the "dbcheck" and "bscan" utilities now work as expected.

BZ#657297

Prior to this update, Bacula's default configuration missed a required option. As a result, the Bacula tray monitor component terminated unexpectedly. The problem has been fixed by adding the "Address" option to the "Director" section in the Bacula tray monitor configuration file so that the Bacula tray monitor now works as expected with the default configuration file. Note that this bug fix does not alter any existing Bacula tray monitor configuration file. As a consequence, the Bacula tray monitor can terminate unexpectedly if the existing Bacula tray monitor configuration is incorrect.

BZ#689400

Prior to this update, the backup size was computed incorrectly under certain circumstances. As a consequence, the reported size of the incremental backup could have been wrong. The problem has been fixed by correcting the backup size computation process so that the size of the incremental backup is now reported correctly.

BZ#712794

Prior to this update, the shadow-utils package was not listed among the package dependencies for Bacula. As a result, the bacula user and bacula group were not created when the shadow-utils package was not present on the system, and a warning message was displayed during the bacula packages installation. This bug has been fixed by adding shadow-utils to the package dependencies.

BZ#712804

Prior to this update, the chkconfig package, which contains the "alternatives" utility, was not listed among the package dependencies for Bacula. As a result, the bacula-dir and bacula-sd services were not configured, the "alternatives" utility was not found, and Bacula's symbolic links were not created. These problems have been fixed by adding chkconfig to the package dependencies.

BZ#814271

When a SIGCHLD signal was received in job control mode and a handler for the signal was installed, Bash called the trap handler within the signal handler itself. This was unsafe and could cause Bash to enter a deadlock or to terminate unexpectedly with a segmentation fault due to memory corruption. With this update, the trap handler is now called outside of the signal handler, and Bash no longer enters a deadlock, neither crashes in this scenario.

Security Fixes

CVE-2012-1667

A flaw was found in the way BIND handled zero length resource data records. A malicious owner of a DNS domain could use this flaw to create specially-crafted DNS resource records that would cause a recursive resolver or secondary server to crash or, possibly, disclose portions of its memory.

CVE-2012-1033

A flaw was found in the way BIND handled the updating of cached name server (NS) resource records. A malicious owner of a DNS domain could use this flaw to keep the domain resolvable by the BIND server even after the delegation was removed from the parent DNS zone. With this update, BIND limits the time-to-live of the replacement record to that of the time-to-live of the record being replaced.

BZ#699951

Prior to this update, the code in libdns which sends DNS requests was not robust enough and suffered from a race condition. If a race condition occurred, the "named" name service daemon logged an error message in the format "zone xxx.xxx.xxx.in-addr.arpa/IN: refresh: failure trying master xxx.xxx.xxx.xxx#53 (source xxx.xxx.xxx.xxx#0): operation canceled" even when zone refresh was successful. This update improves the code to prevent a race condition in libdns and the error no longer occurs in the scenario described.

BZ#700097

A command or script traditionally gives a non-zero exit status to indicate an error. Prior to this update, the nsupdate utility incorrectly returned the exit status "0" (zero) when the target DNS zone did not exist. Consequently, the nsupdate command returned "success" even though the update failed. This update corrects this error and nsupdate now returns the exit status "2" in the scenario described.

BZ#725577

Prior to this update, named did not unload the bind-dyndb-ldap plugin in the correct places in the code. Consequently, named sometimes terminated unexpectedly during reload or stop when the bind-dyndb-ldap plugin was used. This update corrects the code, the plug-in is now unloaded in the correct places, and named no longer crashes in the scenario described.

BZ#693982

A non-writable working directory is a long time feature on all Red Hat systems. Previously, named wrote "the working directory is not writable" as an error to the system log. This update changes the code so that named now writes this information only into the debug log.

BZ#717468

The named initscript lacked the "configtest" option that was available in earlier releases. Consequently, users of the bind initscript could not use the "service named configtest" command. This update adds the option and users can now test their DNS configurations for correct syntax using the "service named configtest" command.

BZ#758669

Prior to this update, errors arising on automatic updates of DNSSEC trust anchors were handled incorrectly. Consequently, the named daemon could become unresponsive on shutdown. With this update, the error handling has been improved and named exits on shutdown gracefully.

BZ#758670

Prior to this update, a race condition could occur on validation of DNSSEC-signed NXDOMAIN responses and the named daemon could terminate unexpectedly. With this update, the underlying code has been fixed and the race condition no longer occurs.

BZ#769366

The multi-threaded named daemon uses the atomic operations feature to speed-up an access to shared data. This feature did not work correctly on the 32-bit and 64-bit PowerPC architectures. Therefore, the named daemon sometimes became unresponsive on these architectures. This update disables the atomic operations feature on the 32-bit and 64-bit PowerPC architectures, which ensures that the named daemon is now more stable, reliable and no longer hangs.

Security Fix

CVE-2012-2134

A flaw was found in the way bind-dyndb-ldap handled LDAP query errors. If a remote attacker were able to send DNS queries to a named server that is configured to use bind-dyndb-ldap, they could trigger such an error with a DNS query leveraging bind-dyndb-ldap's insufficient escaping of the LDAP base DN (distinguished name). This would result in an invalid LDAP query that named would retry in a loop, preventing it from responding to other DNS queries. With this update, bind-dyndb-ldap only attempts to retry one time when an LDAP search returns an unexpected error.

BZ#742368

Previously, the bind-dyndb-ldap plug-in could faile to honor the selected authentication method because it did not call the ldap_bind() function on reconnection. Consequently, the plug-in connected to the LDAP server anonymously. With this update, the ldap_bind() function is executed on reconnection and the plug-in uses the correct authentication method in the described scenario.

BZ#707255

The bind-dyndb-ldap plug-in failed to load new zones from the LDAP server runtime. This update adds the zone_refresh parameter to the plug-in which controls how often the zone check is performed.

BZ#745045

The bind-dyndb-ldap plug-in could fail to connect to the LDAP server. This happened when the LDAP server was using localhost and FreeIPA installation was using a name different from the machine hostname. This update adds to the plug-in the ldap_hostname option, which can be used to set the correct LDAP server hostname.

BZ#727856

The "named" process could have remained unresponsive due to a race condition in the bind-dyndb-ldap plug-in. With this update, the race condition has been resolved and the problem no longer occurs.

Bug Fixes

BZ#664640

Prior to this update, the readelf utility added 0x40 into a character in order to display a non-printing character but did not do so when processing a multibyte character. As a result, the readelf utility did not display a multibyte character in the ELF header correctly. The code has been corrected and readelf no longer displays garbled characters when processing multibyte, or non-ASCII, characters.

BZ#674925

An unneeded patch to bineutils caused a large link time degradation when using the binutils --build-id command. This update removes that patch.

BZ#689829

An Operating System (OS) Application Binary Interface (ABI) describes the low-level interface between a program and the operating system (OS/ABI). The indirect meta-function, ifunc(), whose value can be determined at load time, allows for architecture dependent optimization. Prior to this update, the OS/ABI preprocessor macro was erroneously set to UNIX - Linux instead of UNIX - System V in an ELF header by a dynamic executable which used ifunc(). This update applies a backported patch which corrects the code and the error no longer occurs.

BZ#698005

Prior to this update, the binutils' strip command, which is run as part of the RPM build process, did not copy the EI_OSABI value in the ELF file header properly, it set the value to zero. Consequently, if the EI_OSABI field of the debug file had a value of 3 (ABI tag for GNU/Linux), in the stripped file it was erroneously set to 0 (UNIX - System V). This update corrects the problem and strip now leaves the field intact.

BZ#701586

On 64-bit PowerPC platforms, the position of -ldl in the list compiler options caused unexpected behavior when compiling C++ code. If -ldl was not placed at the end of parameter list, the GNU C Compiler (GCC) failed with an error in the format:

libtest.a(some_object_file.o): undefined reference to `.dlerror'

With this update, the code has been corrected and the GCC compiler functions as expected.

BZ#707387

When compiling C source code using the GNU C Compiler (GCC), a Table Of Contents (TOC), is created for every executable file. Prior to this update, compiling C++ code using GCC for 64-bit PowerPC, using -mcmodel=small -mno-minimal-toc as options, GNU linker, (ld), erroneously decided that if a section did not make use of the TOC it could belong to any TOC group. Consequently, when a local function call was made from one section of code to another section in the same object file, due to the two sections being assigned to different TOC groups, a failure occurred and an error message in the following format was logged.

libbackend.a(cse.o)(.text.unlikely+0x60): sibling call optimization to `.opd' does not allow automatic multiple TOCs; recompile with -mminimal-toc or -fno-optimize-sibling-calls, or make `.opd' extern

This update applies an upstream patch to improve the partitioning of sections of code, which make local function calls, into multiple TOC groups. As a result the error no longer occurs in the scenario described.

Note

It is necessary to relink executables and shared libraries containing objects which were compiled with -mcmodel=small -mno-minimal-toc. Therefore code should be recompiled by running these commands again after applying the update.

BZ#714824

Prior to this update, after compiling a kernel from source code with debugging information, some debug information was missing. Consequently, when using the GNU Project's debugger (GDB) utility, if a user issued the command l setup_arch to determine the target architecture, the following error was displayed.

No line number known for setup_arch

This update corrects the code and the GDB utility now correctly displays the architecture for which the code was compiled.

BZ#721079

Compilers used for producing code optimized for 64-bit PowerPC platforms use the default Red Hat Enterprise Linux system linker, ld, provided with the operating system to produce executables and libraries. Some object code generated by the IBM XL compiler caused ld to terminate unexpectedly with a segmentation fault. Consequently, users were not able to produce optimized executables or libraries. With this update, a backported patch has been applied to correct the problem and ld no longer crashes in the scenario described.

BZ#733122

When linking FORTRAN programs with the IBM XL compiler and the default Red Hat Enterprise Linux 6.1 system linker, ld sometimes terminated unexpectedly with a segmentation fault. This updates applies an upstream patch to correct the problem and ld no longer crashes in the scenario described.

BZ#747695

The assembler, as, when generating a memory reference to a local symbol plus or minus an offset, did not include the constant offset when generating 32-bit x86 code. Consequently, when the local symbol being referenced was defined before the instruction using the symbol with an offset, an error would occur. This update corrects the code and the problem no longer occurs.

Enhancements

BZ#696368

With this update, backported patches have been included to support new AMD processors.

BZ#696494

Certain Intel processors support a new RdRand instruction to generate a true random number in a short time. This update includes support for this new instruction.

BZ#700248

When NPAR (NIC Partitioning) is enabled, the partition number should be appended as a suffix to the interface name. Previously, biosdevname did not add partition numbers to interface names, for example, instead of naming an interface "em3_1", the interface was named "em3". Consequently, partitioned network interfaces were missing the suffix necessary to describe the partition. Now, biosdevname correctly recognizes the VPD (Vital Product Data) suffix and full interface names are created correctly.

BZ#700251

When biosdevname ran in a guest environment, it suggested names to new network interfaces as if it was in a host environment. Consequently, affected network interfaces were incorrectly renamed. Now, biosdevname no longer suggests names in the described scenario.

BZ#729591

When biosdevname was reading VPD information to retrieve NPAR-related data, the read operations failed or became unresponsive on certain RAID controllers. Additionally, biosdevname sometimes attempted to read beyond the VPD boundary in the sysfs VPD file, which also resulted in a hang. This bug has been fixed and biosdevname now performs the read operation correctly in the described scenarios.

BZ#739592

Previously, the "--smbios" and "--nopirq" command-line parameters were missing in the biosdevname binary. Consequently, consistent network device naming could not be enabled because biosdevname exited without suggesting a name. This update adds support for these parameters and enables the device naming.

BZ#740532

Previously, NICs (Network Interface Cards) on biosdevname-compatible machines were given traditional "eth*" names instead of "em*" or "p*p*" names. This bug has been fixed and biosdevname now provides correct names for the NICs.

BZ#696252

With this update, "--smbios" and "--nopirq" command-line parameters have been added to biosdevname.

BZ#736442

The biosdevname man page has been updated to explain the functionality of the "--smbios" and "--nopirq" command-line parameters.

BZ#705128

Prior to this update, the blkparse code contained a misprint. As a result, blkparse used the wrong variable when printing the PC Writes Completed. This update modifies the code so that blkparse now prints the correct value for PC Writes Completed.

BZ#736399

This update adds FLUSH/FUA support to blktrace.

BZ#618308

Prior to this update, the bltk tree was corrupted. As a result, the bltk_report script failed. This update modifies the settings of the bltk root path. Now, the report script works as expected.

BZ#679028

Prior to this update, bltk could be installed without requiring the gnuplot binary. As a result, the bltk_plot script exited with an error message when the gnuplot package was not installed and the charts were shown from measured data. This update requires the gnuplot package for its installation. Now, the bltk_plot script no longer exits with an error.

BZ#660347

Prior to this update, cachefilesd used the wrong log level for cull info messages. As a result, the /var/log/messages file could become overloaded. This update reduces the messages to the debug level. Now, /var/log/messages no longer becomes overloaded.

BZ#723890

Prior to this update, cachefilesd depended on a specific version of the SELinux policy package. As a result, only the nominated version was allowed. This update permits the nominated version and any later versions. Now, the SELinux policy dependency works as expected.

BZ#692766

Previously, the certmonger service could access a Network Security Services (NSS) database without a password, despite being configured to use a password to access that database. This behavior was not recognized as an error. This update correctly diagnoses this inconsistency as an error.

BZ#694184

Previously, if the certmonger service could not generate a key pair in an NSS database because it did not have the password that was required for accessing the database, the certmonger service did not recover when it was subsequently given the correct password. This update handles this case correctly.

BZ#697058

Previously, the certmonger service did not correctly diagnose a missing token if the name of the token to use was specified when the service was instructed to generate a key pair for storage in an NSS database. This update corrects this error.

BZ#712500

Previously, the certmonger service encountered an assertion failure if the D-Bus message bus service was not already running when certmonger was started. This update modifies the certmonger service so that no more assertion problems occur in such a situation.

BZ#721392

Previously, when the getcert command needed to report an error message which it received from the certmonger service, it exited unexpectedly due to a logic error. This update corrects the logic so that the error message is correctly reported.

BZ#727863

Previously, the certmonger service was not fully compatible with newer versions of the xmlrpc-c and libcurl packages. As a result, credentials could not be delegated when using GSSAPI authentication with a CA that was accessed via XML-RPC. This update includes the necessary changes to continue to be able to delegate credentials when using GSSAPI authentication with a CA that is accessed using XML-RPC, such as IPA.

BZ#699059, BZ#739903

Previously, when the getcert request command was given a location for key or certificate storage using a relative path, and the location did not exist, the error was only reported after multiple warnings during which the command attempted to convert the relative path to an absolute path. This update suppresses these warnings.

BZ#741262

Previously, an incorrect error message was displayed if the getcert resubmit command was invoked with the -i flag to specify which request should be resubmitted to a CA but no request that matched the provided value was present. This update displays the correct error message.

BZ#742348

Due to a logic error, attempts to save a newly-obtained certificate to an NSS database could fail intermittently. This update corrects the error.

BZ#698772

Previously, the getcert list command only printed information about every certificate and enrollment request being managed by certmonger, and there was no way to narrow down the results. This update includes an updated version of the command which can narrow the result set if the invoking user provides information about the location of the certificate or key in which the user is interested

BZ#750617

This update now includes an HTTP "Referer:" header value when submitting requests to CAs which are accessed using XML-RPC, as is expected to be required by future releases of the IPA CA

BZ#797847

When installing multiple Linux Standard Base (LSB) services which only had LSB headers, the stop priority of the related LSB init scripts could have been miscalculated and set to "-1". With this update, the LSB init script ordering mechanism has been fixed, and the stop priority of the LSB init scripts is now set correctly.

BZ#797846

When an LSB init script requiring the "$local_fs" facility was installed with the "install_initd" command, the installation of the script could fail under certain circumstances. With this update, the underlying code has been modified to ignore this requirement because the "$local_fs" facility is always implicitly provided. LSB init scripts with requirements on "$local_fs" are now installed correctly.

BZ#676439

Prior to this update, mount.cifs dropped the CAP_DAC_READ_SEARCH flag together with most of the other capability flags before it performed a mount. As a result, mounting onto a directory without execute permissions failed if mount.cifs was installed as a setuid program and the user mount was configured in the /etc/fstab file. This update reinstates the CAP_DAC_READ_SEARCH flag before calling mount. Now, mounting no longer fails.

BZ#719363

Prior to this update, several mount options were missing from the mount.cifs(8) man page. With this update, the man page documents all mount options.

BZ#682650

Prior to this update, when viewing the U+4190 CJK character with the AR PL UMing font and the font size 10, this character was not displayed properly. This bug has been corrected in this update so that the character is now correctly displayed as expected.

Bug Fix

BZ#849048

Previously, it was not possible to specify start-up options to the dlm_controld daemon. As a consequence, certain features were not working as expected. With this update, it is possible to use the /etc/sysconfig/cman configuration file to specify dlm_controld start-up options, thus fixing this bug.

Bug Fixes

BZ#707115

The cluster and gfs2-utils packages have been upgraded to upstream version 3.0.12.1, which provides a number of bug fixes over the previous version.

BZ#713977

Previously, when a custom multicast address was configured, the configuration parser incorrectly set the default value of the time-to-live (TTL) variable for multicast packet to 0. As a consequence, cluster nodes were not able to communicate with each other. With this update, the default TTL value is set to 1, which fixes the problem.

BZ#726777

A section describing the "suborg" option for the fence_cisco_usc agent was not present in the RELAX NG schema which is used to validate the cluster.conf file. As a consequence, validation of cluster.conf failed even if the file was valid. The suborg section has been added to the RELAX NG schema and cluster.conf is now validated correctly.

BZ#707091

Building the resource group index for a new GFS2 file system using the mkfs.gfs2 utility used all the space allocated. If the file system filled up completely, no room was left to write a new rindex entry. As a consequence, the gfs2_grow utility was unable to expand the file system. The mkfs.gfs2 utility has been modified so that enough space is now allocated for the entire rindex file, and one extra rindex entry. The gfs2_grow source code has been modified to utilize the unused rindex space. As a result, gfs2_grow is now able to expand a completely full GFS2 file system.

BZ#678585

GFS2 POSIX (Portable Operating System Interface) lock operations (implemented in Distributed Lock Manager, also known as DLM) are not interruptible when they wait for another POSIX lock. Previously, processes that created a deadlock with POSIX locks could not be killed to resolve the problem, and one node had to be reset. DLM now uses a new kernel feature that allows the waiting process to be killed, and information about the killed process is now passed to the dlm_controld daemon to be cleaned up. Processes deadlocked on GFS2 POSIX locks can now be recovered by killing one or more of them.

BZ#719135

Prior to this update, boundaries for the locktable and label fields in the GFS2 superblock were not properly checked by the tunegfs2 tool. As a consequence, running the "gfs2_tool sb" command could terminate unexpectedly with buffer overflow. In addition, invalid characters could be printed when using tunegfs2 to change locktable or label to a minimum or maximum length (63 characters). The tunegfs tool has been modified to check the correct boundaries of the locktable and label fields. As a result, tunegfs2 no longer creates invalid locktables or labels, and therefore gfs2_tool prints the superblock values properly.

BZ#740385

When executing the cman utility by using the init script with enabled debugging, a file descriptor leaked. The file pointed to the file descriptor would continue to grow endlessly, filling up the /tmp file system. This update ensures that the file descriptor is closed after a successful cman startup. Space in /tmp is now released correctly.

BZ#695795

The cman utility implements a complex set of checks to configure the Totem protocol. One of the checks that copies the configuration data was incorrect and the transport protocol option was not handled correctly as a consequence. A patch has been applied to address this issue and cman now handles the transport option properly.

BZ#679566

When the user executed the "gfs2_edit savemeta" command to save the metadata for a target GFS2 file system, not all of the directory information was saved for large directories. If the metadata was restored to another device, the fsck.gfs2 tool found directory corruption because of a missing leaf block. This was due to gfs2_edit treating the directory leaf index (also known as the directory hash table) like a normal data file. With this update, gfs2_edit's savemeta function is modified to actually read all the data (the directory hash table) for large directories and traverse the hash table, saving all the leaf blocks. Now, all leaf blocks are saved properly.

BZ#679080

When the fsck.gfs2 tool was resolving block references and no valid reference was found, the reference list became empty. As a consequence, fsck.gfs2 check in pass1b terminated unexpectedly with a segmentation fault. With this update, pass1b is modified to check that the list is empty. The segmentation fault no longer occurs and fsck.gfs2 proceeds as expected.

BZ#731775

The dlm_controld daemon passed error results back to the kernel for POSIX unlock operations flagged with CLOSE. As a consequence, the kernel displayed the "dlm: dev_write no op" error messages, most of them when using non-POSIX locks, flocks. The dlm_controld daemon has been fixed to not pass error results to the kernel for POSIX unlock operations flagged with CLOSE. As a result, error messages no longer appear.

BZ#729071

Previously, the mount.gfs2 utility passed the "loop" option to the GFS2 kernel module which treated it as an invalid option. Mounting a GFS2 file system on loopback devices failed with an "Invalid argument" error message. With this update, mount.gfs2 is modified to avoid passing the "loop" option to the kernel. Mounting GFS2 systems on loopback devices now works as expected.

BZ#728230

Missing sanity checks related to the length of a cluster name caused the cman utility to fail to start. The correct sanity checks have been implemented with this update. The cman utility starts successfully and informs the user of the incorrect value of the cluster name, if necessary.

BZ#726065

The XML format requires special handling of certain special characters. Handling of these characters was not implemented correctly, which caused the cluster.conf file to not function as expected. Correct handling of the characters has been implemented and cluster.conf now works as expected.

BZ#706141

The exact device/mount paths were not compared due to incorrect logic in mount.gfs2 when trying to find mtab entries for deletion. The original entry was not found during remounts and therefore was not deleted. This resulted in double mtab entries. With this update, the realpath() function is used on the device/mount paths so that they match the content of mtab. As a result, the correct original mtab entry is deleted during a remount, and a replacement entry with the new mount options is inserted in its place.

BZ#720668

Previously, mkfs.gfs2 treated normal files incorrectly as if they were block devices. Attempting to create a GFS2 file system on a normal file caused mkfs.gfs2 to fail with a "not a block device" error message. Additional checks have been added so that mkfs.gfs2 does not call functions specific for block devices on normal files. GFS2 file systems can now be created on normal files. However, use of GFS2 in such cases is not recommended.

BZ#719126

The tunegfs2 command line usage message was not updated to reflect the available arguments which are documented in the man page. As a consequence, tunegfs2 printed an inaccurate usage message. The usage message has been updated and tunegfs2 now prints an accurate message.

BZ#719124

Previously, certain argument validation functions did not return error values, and tunegfs2 therefore printed confusing error messages instead of exiting quietly. Error handling has been improved in these validation functions, and tunegfs2 now exits quietly instead of printing the confusing messages.

BZ#694823

Previously, the gfs2_tool command printed the UUID (Universally Unique Identifier) output in uppercase. Certain applications expecting the output being in lowercase (such as mount) could have malfunctioned as a consequence. With this update, gfs2_tool is modified to print UUIDs in lowercase so that they are in a commonly accepted format.

BZ#735917

The qdisk daemon did not allow cman to upgrade the quorum disk device name. The quorum disk device name was not updated when the device was changed and, in very rare cases, the number of qdiskd votes would therefore not be correct. A new quorum API call has been implemented to update the name and votes of a quorum device. As a result, quorum disk device names and votes are updated consistently and faster than before.

BZ#683104

Prior to this update, the fsck.gfs2 utility used the number of entries in the journal index to look for missing journals. As a consequence, if more than one journal was missing, not all journals were rebuilt and subsequent runs of fsck.gfs2 were needed to recover all the journals. Each node needs its own journal; fsck.gfs2 has therefore been modified to use the "per_node" system directory to determine the correct number of journals to repair. As a result, fsck.gfs2 now repairs all the journals in one run.

BZ#663397

Previously, token timeout intervals of corosync were larger than the time it took a failed node to rejoin the cluster. Consequently, corosync did not detect that a node had failed until it rejoined. The failed node had been added again before the dlm_controld daemon asked corosync for the new member list, but dlm_controld did not notice this change. This eventually caused the DLM (Distributed Lock Manager) lockspace operations to get stuck. With this update, dlm_controld can notice that a node was removed and added between checks by looking for a changed incarnation number. Now, dlm_controld can properly handle nodes that are quickly removed and added again during large token timeouts.

BZ#732991

Previously, if a cluster was configured with a redundant corosync ring, the dlm_controld daemon would log harmless EEXIST errors, "mkdir failed: 17". This update removes these error messages so that they no longer appear.

Enhancements

BZ#733345

The corosync IPC port allows, when configured correctly, non-privileged users to access corosync services. Prior to this update, the cman utility did not handle such connections correctly. As a consequence, users were not able to configure unprivileged access to corosync when it was executed using cman. This update adds support to cman to configure unprivileged access. As a result, configured users and groups can now access corosync services without root privileges.

BZ#680930

This update introduces dynamic schema generation, which provides a lot of flexibility for end users. Users can plug into Red Hat Enterprise Linux High Availability Add-On custom resource and fence agents, and still retain the possibility to validate their cluster.conf file against those agents.

BZ#732635, BZ#735912

This update adds support for Redundant Ring Protocol, which aligns the default configuration of cman with corosync. Note that this enhancement is included as a Technology Preview.

BZ#702313

Previously, gfs2_edit saved GFS2 metadata uncompressed. Saved GFS2 metadata sets could have filled up a lot of storage space, and transferring them (for example, for support and debugging) would be slow. This update adds gzip compression to the metadata saving and restoring functions of gfs2_edit. GFS2 metadata sets are now compressed when saving and decompressed when restoring them. The user can specify the compression level with a command line option.

BZ#704178

With this update, the tunegfs2 utility replaces the superblock manipulating feature of gfs2_tool.

BZ#673575

Previously, the fence_scsi agent did not reboot a node when it was fenced. As a consequence, the node had to be rebooted manually before rejoining the cluster. This update provides a script for detecting loss of SCSI reservations. This can be used in conjunction with the watchdog package in order to reboot a failed host.

BZ#820357

Prior to this update, the cmannotifyd did not correctly generate a cluster status notification message at first cluster startup. This update addresses the problem and now cmannotifyd will correctly trigger the notification hooks when the daemon is started.

BZ#634373

Previously, the clustermon tool failed to shut down nodes if the user had mounted a GFS2 file system that was not listed in the /etc/fstab file. This was caused by clustermon relying on the rgmanager tool and the GFS2 init scripts to unmount all file systems, but the cluster stack would not stop properly if the user mounted the file system manually. This has been fixed: clustermon now ensures that there are no cluster file systems mounted and then attempts to stop the cluster stack.

BZ#724978

The "get_cluster_schema" function call has been added to allow users to easily get the XML cluster schema content.

BZ#578690

This update adds support for Personal Identity Verification (PIV) smart cards.

BZ#700907

Common Access Cards (CAC) are defined to have exactly three certificates. However, some cards that used the CAC interface supplied one or two certificates only, which may have caused the coolkey utility to fail. CAC smart cards that contain less than three certificates are now supported.

BZ#691292

Prior to this update, SELinux appeared to be disabled when building coreutils in Mock. As a result, coreutils did not build. With this update, SELinux determines more precisely whether it is disabled or not. Now, the packages are built successfully.

BZ#703712

Previously, incorrect signal handling could cause various problems for tcsh users logging into the root shell using the su utility. Signal masking in the subshell called by the su utility has been modified to respect the SIGTSTP signal as well as the SIGSTOP signal.

BZ#715557

When using the "-Z/--context" option in the cp utility, the SELinux context of a file was not changed if the file destination already existed. The utility has been modified and the context is changed as expected. However, this option is not portable to other systems.

BZ#720325

Prior to this update, the acl_extended_file() function could cause unnecessary mounts of autofs when using the ls command on a directory with autofs mounted. This update adds the new acl function, acl_extended_file_nofollow(), to prevent unnecessary autofs mounts.

BZ#725618

The description of the "--sleep-interval" option in the tail(1) manual page has been improved to be clearer about the behavior and to match the upstream version of coreutils.

Bug Fix

BZ#849553

Previously, the corosync-notifyd daemon, with dbus output enabled, waited 0.5 seconds each time a message was sent through dbus. Consequently, corosync-notifyd was extremely slow in producing output and memory of the Corosync server grew. In addition, when corosync-notifyd was killed, its memory was not freed. With this update, corosync-notifyd no longer slows down its operation with these half-second delays and Corosync now properly frees memory when an IPC client exits.

Bug Fixes

BZ#677583

Prior to this update, the corosync-blackbox command could, under certain circumstances, produce a backtrace in the output and consequently terminate with a segmentation fault. With this update, Corosync creates correct fdata files and also corosync-fplay is more resistant when dealing with incorrect fdata files.

BZ#677583

Prior to this update, cpg did not use the "left_nodes" field in the downlist message. As a consequence, a node could miss a configuration change and report larger old_members than expected if one node was paused. This update modifies the downlist so that the "left_nodes" field is used. Now, the membership events are correct.

BZ#692620

Prior to this update, cpg did not use the "left_nodes" field in the downlist message. As a consequence, a node could miss a configuration change and report larger old_members than expected if one node was paused. This update modifies the downlist so that the "left_nodes" field is used. Now, the membership events are correct.

BZ#696883

Prior to this update, running Corosync could cause a segmentation fault on multiple nodes when executed via CMAN. This update modifies the code so that executing Corosync via CMAN no longer causes segmentation faults with the pacemaker test suite.

BZ#696887

Prior to this update, the reference counting on the configuration server in Corosync was incorrect. As a consequence, terminating the corosync-cfgtool -r command before completing caused a segmentation fault. This update adds the correct reference counting for each architecture. Now, Corosync no longer encounters segmentation faults in this situation.

BZ#707860

Prior to this update, Corosync could terminate with a segmentation fault if it ran out of available open files. This update handles the maximum number of open files more gracefully. Now, Corosync no longer crashes when going over open file limits.

BZ#707867

Prior to this update, corosync-objctl could not create a new object/key and display double or float values. This update adds float and double support to corosync-objctl. Now, corosync-objctl can display object values with double or float types.

BZ#707873

Prior to this update, Corosync could terminate with a segmentation fault if it encountered a negative value for the message type on systems where char is signed. This update improves the check of the message type for incoming messages.

BZ#707875

Prior to this update, an error message was wrongly displayed if files in the service.d directory differed from the service key. With this update, Corosync longer checks for sub parameters in files in the service.d directory. Now, files in service.d directory can contain every possible configuration option.

BZ#709758

Prior to this update, Corosync used a spinlock around I/O operations. As a consequence, Corosync consumed an extremely high portion of the central processing unit (CPU) when running a large amount of inter-process communication (IPC) operations because the spinlocks would spin during I/O. This update replaces the spinlock with a mutual exclusion (mutex), which releases the processor from spinning but enforces correct behavior.

BZ#712115

Prior to this update, an incorrect mutex in the internal confdb data storage system could, under certain circumstances, cause Corosync to terminate with a segmentation fault. This update corrects the mutex and objdb API iteration no longer causes Corosync to terminate with a segmentation fault.

BZ#712188

Prior to this update, Corosync became locked with contrived test cases when the tracking functionality of the internal object database was enabled if it was under heavy load. This update modifies Corosync so that the tracking functionality under heavy load no longer causes Corosync to lock up.

BZ#725058

Prior to this update, retransmit list errors could occur on slower hardware due to high multicast traffic and slow CPU usage. This update processes the multicast buffer queue more frequently and retransmit errors are now less probable.

BZ#732698

Prior to this update, Corosync sometimes terminated unexpectedly when Corosync ran the cman_tool join and cman_tool leave commands in a loop. This update modifies the code so that no more segmentation faults occur in such situations.

Enhancements

BZ#529136

Prior to this update, the protocol in Corosync unnecessarily copied memory on AMD64 and EM64T architectures to align data structures for architectures which do not handle alignment correctly. As a consequence, the utilization of the central processing unit (CPU) was increased. This update can conditionally avoid copies on unaligned safe architectures such as Intel 80386, AMD64, and EM64T architectures. Now the CPU utilization is reduced by around 20%.

BZ#599327

Prior to this update, no diagnostic message was available when the multicast was blocked. As a consequence, each partition lost quorum which never remerged. This update displays a diagnostic warning that the node can not exit the GATHER state when a local NIC (network interface card) fault occurs or the firewall prevents totem from forming a cluster. In addition, the runtime.totem.pg.mrp.srp.firewall_enabled_or_nic_failure key is now set to 1.

BZ#667652

Prior to this update, fenced nodes where not safely powered up due to issues with the boot sequence. As a consequence, users had to skip cluster services at boot to avoid problems such as long response times and fences in two-node clusters. With this update, setting the nocluster boot parameter prevents Corosync to start automatically.

BZ#688260

Prior to this update, configuring two rings with different IP subnets only duplicated the IP address data of one ring. This update adds support for the redundant ring functionality to Corosync as a Technology Preview.

BZ#707876

Prior to this update, the corosync init script did not depend on syslog. As a consequence, syslog logging did not work if the user turned off syslog. This update adds syslog as a dependency to the init script. Now, logging works in all cases.

BZ#722469

Prior to this update, configuring two rings with different IP subnets only duplicated the IP address data of one ring. This update adds support for the redundant ring functionality to Corosync as a Technology Preview.

BZ#791236

Previously, the range condition for the update_aru() function could cause incorrect check of message IDs. Due to this, in rare cases, the corosync utility entered the "FAILED TO RECEIVE" state, and so failed to receive multicast packets. With this update, the range value in the update_aru() function is no longer checked for; the fail_to_recv_const constant performs such checks. Now, corosync does not fail to receive packets.

BZ#810917

Previously, the underlying library of corosync did not delete temporary buffers used for Inter-Process Communication (IPC) that are stored in the /dev/shm shared memory file system. Therefore, if the user without proper privileges attempted to establish an IPC connection, the attempt failed with an error message as expected but memory allocated for temporary buffers was not released. This could eventually result in /dev/shm being fully used and Denial of Service. This update modifies the coroipcc library to let applications delete temporary buffers if the buffers were not deleted by the corosync server. The /dev/shm file system is no longer cluttered with needless data in this scenario and IPC connections can be established as expected.

BZ#828432

Previously, it was not possible to activate or deactivate debug logs at runtime due to memory corruption in the objdb structure. With this update, the debug logging can now be activated or deactivated on runtime, for example with the command "corosync-objctl -w logging.debug=off".

Bug Fix

BZ#929098

When running applications which used the Corosync IPC library, some messages in the dispatch() function were lost or duplicated. This update properly checks the return values of the dispatch_put() function, returns the correct remaining bytes in the IPC ring buffer, and ensures that the IPC client is correctly informed about the real number of messages in the ring buffer. Now, messages in the dispatch() function are no longer lost or duplicated.

BZ#675734

Prior to this update, the cpufreq-aperf utility did not run on 32-bit systems due to an incorrect argument passed to the read() call. This problem has been fixed: the buffer size is now used instead of the size of the pointer and the cpufreq-aperf utility runs as expected.

BZ#710193

The crash package has been upgraded to upstream version 5.1.8, which provides a number of enhancements and bug fixes over the previous version.

BZ#705142

Previously, compressed kdump dump files were handled incorrectly on AMD64 and Intel 64 architectures if a system contained more than 454 CPUs. In such a case, the crash session terminated during initialization with the "crash: compressed kdump: invalid nr_cpus value: [cpus]" error message. A patch has been provided to address this issue, and the compressed dump files are now handled properly, thus fixing this bug.

BZ#716931

When the first chunk of physical memory on a system was assigned to NUMA (Non-Uniform Memory Architecture) node 1 (typically it is assigned to NUMA node 0), the "kmem -s" or "kmem -S" command incorrectly showed all cache blocks allocated by the slab allocator as empty. This bug has been fixed, and the kmem command now shows populated kmem_cache slab data correctly.

BZ#712214

In a rare scenario, a non-crashing CPU received a shutdown NMI (non-maskable interrupt) immediately after receiving an interrupt from another source. Because the IRQ entry-point symbols "IRQ0x00_interrupt" through "IRQ0x##_interrupt" no longer existed, the bt command terminated with the "bt: cannot transition from exception stack to current process stack" error message on AMD64 and Intel 64 architectures. This bug has been fixed, and backtrace now properly transitions from the NMI stack back to the interrupted process stack.

BZ#695413

The crash.8 man page and the associated built-in "crash -h" output have been re-written. The crash.8 man page now clarifies the required invocation options, adds all of the rarely-used command line options that have proliferated over the years, and updates the ENVIRONMENT variables section. The "crash -h" output now closely mimics the relevant parts of the crash.8 man page.

BZ#703467

With this update, the new "--osrelease [dump_file]" command line option that displays the OSRELEASE vmcoreinfo string from a kdump dump file has been added.

BZ#609544

Prior to this update, an example included in the /etc/crontab file contained an omission. It did not state that defining a job in crontab requires a username to be defined. The missing information has been added to the /etc/crontab file in this update.

BZ#713410

When the cryptsetup or libcryptsetup utility was run in FIPS (Federal Information Processing Standards) mode, the "Running in FIPS mode." message was displayed during initialization of all commands. This sometimes caused minor issues with associated scripts. This bug has been fixed and the message is now displayed only in verbose mode.

BZ#732179

Prior to this update, several directives were missing in cryptsetup status command implementation. Therefore, the cryptsetup status command always returned the exit code 0 when verifying the status of a mapped device. To fix this issue, the code has been modified. The cryptsetup status command now returns the 0 value only if the device checked is active.

BZ#701936

Previously, the libcryptsetup crypt_get_volume_key() function allowed to perform an action not compliant with FIPS. To conform FIPS requirements, the function is now disabled in FIPS mode and returns an EACCES error code to indicate it. Note that the "luksDump --dump-master-key" command and the key escrow functionality of the volume_key package are also disabled in FIPS mode as a consequence of this update.

BZ#728545

Prior to this update, the ctdb daemon leaked a file descriptor to anon_inodefs. This update modifies ctdb so that this file discriptor can no longer leak.

BZ#672641

This update adds support for Clustered Samba on top of GFS2 as a Technology Preview.

Security Fix

CVE-2011-2896

A heap-based buffer overflow flaw was found in the Lempel-Ziv-Welch (LZW) decompression algorithm implementation used by the CUPS GIF image format reader. An attacker could create a malicious GIF image file that, when printed, could possibly cause CUPS to crash or, potentially, execute arbitrary code with the privileges of the "lp" user.

BZ#681836

Previously CUPS was not correctly handling the language setting LANG=en_US.ASCII. As a consequence lpadmin, lpstat and lpinfo binaries were not displaying any output when the LANG=en_US.ASCII environment variable was used. As a result of this update the problem is fixed and the expected output is now displayed.

BZ#706673

Previously the scheduler did not check for empty values of several configuration directives. As a consequence it was possible for the CUPS daemon (cupsd) to crash when a configuration file contained certain empty values. With this update the problem is fixed and cupsd no longer crashes when reading such a configuration file.

BZ#709896

Previously when printing to a raw print queue, when using certain printer models, CUPS was incorrectly sending SNMP queries. As a consequence there was a noticeable 4-second delay between queueing the job and the start of printing. With this update the problem is fixed and CUPS no longer tries to collect SNMP supply and status information for raw print queues.

BZ#712430

Previously when using the BrowsePoll directive it could happen that the CUPS printer polling daemon (cups-polld) began polling before the network interfaces were set up after a system boot. CUPS was then caching the failed hostname lookup. As a consequence no printers were found and the error, "Host name lookup failure", was logged. With this update the code that re-initializes the resolver after failure in cups-polld is fixed and as a result CUPS will obtain the correct network settings to use in printer discovery.

BZ#735505

The MaxJobs directive controls the maximum number of print jobs that are kept in memory. Previously, once the number of jobs reached the limit, the CUPS system failed to automatically purge the data file associated with the oldest completed job from the system in order to make room for a new print job. This bug has been fixed, and the jobs beyond the set limit are now properly purged.

BZ#744791

The cups init script (/etc/rc.d/init.d/cups) uses the daemon function (from /etc/rc.d/init.d/functions) to start the cups process, but previously it did not source a configuration file from the /etc/sysconfig/ directory. As a consequence, it was difficult to cleanly set the nice level or cgroup for the cups daemon by setting the NICELEVEL or CGROUP_DAEMON variables. With this update, the init script is fixed.

BZ#803419

Previously, empty jobs could be created using the "lp" command either by submitting an empty file to print (for example by executing "lp /dev/null") or by providing an empty file as standard input. In this way, a job was created but was never processed. With this update, creation of empty print jobs is not allowed, and the user is now informed that no file is in the request.

BZ#800903

Previously, SSL connections could not be established with libcurl if the selected Network Security Services (NSS) database was broken or invalid. This update modifies the code of libcurl to initialize NSS without a valid database, which allows applications to establish SSL connections as expected in this scenario.

BZ#800904

The OpenLDAP suite was recently modified to use NSS instead of OpenSSL as the SSL back end. This change led to collisions between libcurl and OpenLDAP on NSS initialization and shutdown. Consequently, applications that were using both, libcurl and OpenLDAP, failed to establish SSL connections. This update modifies libcurl to use the same NSS API as OpenLDAP, which prevents collisions from occurring. Applications using OpenLDAP and libcurl can now connect to the LDAP server over SSL as expected.

Security Fix

CVE-2012-0804

A heap-based buffer overflow flaw was found in the way the CVS client handled responses from HTTP proxies. A malicious HTTP proxy could use this flaw to cause the CVS client to crash or, possibly, execute arbitrary code with the privileges of the user running the CVS client.

BZ#818209

Previously, the idled daemon incorrectly used signals for communication with the imapd daemon. This could cause a user's mailbox to become unresponsive. To prevent this problem, idled no longer uses signals to communicate with imapd; the AF_UNIX datagram sockets are now used instead.

BZ#720451

Prior to this update, the ntlm plug-in did not work due to a code error. This update modifies the source code so that the plug-in now works as expected.

BZ#730242

Prior to this update, creating the user ID and the group ID of the saslauth daemon caused conflicts. This update corrects this behavior and now the saslauth daemon works as expected.

BZ#730246

Prior to this update, cyrus-sasl displayed redundant warnings during the compilation. With this update, cyrus-sasl has been modified and now works as expected.

BZ#727274

This update adds support of partial Relocation Read-Only (RELRO) for the cyrus-sasl libraries.

Bug Fixes

BZ#677449

DM Multipath removed a device if it failed to check the device status due to insufficient memory. This happened because the command checking if the device map existed failed as the system returned an error. With this update, Multipath no longer returns an error under these circumstances and no devices are removed if the system runs out of memory while checking device status.

BZ#678673

If a device-mapper-multipath device was open but all attached device paths had been lost, the device was unable to create a new table with no device paths. As a concequence the multipath -ll command returned output indicating that no paths to the device were available with confusing "failed faulty running" rows presenting the missing paths. Multipath devices now reload tables with no device paths correctly.

BZ#689504

Device paths could fail even if unavailable only temporarily. This happened because the RDAC (Redundant Disk Array Controller) checker function did not recheck the status of hosts if it had received a temporary error code. The function now rechecks the path after it has received such error codes and the path failures are transient as expected.

BZ#697386

A previous bug fix introduced a race condition between the main thread and the thread running the checkerloop routine as the checkerloop thread was created with deferred cancellation type. The checkerloop thread continued running and attempted to access a property, which had been previously unallocated by the main thread. This caused the multipathd daemon to shutdown with a segmentation fault. Now the checkerloop thread checks if a shutdown is in progress and the deamon shuts down gracefully.

BZ#700169

The Multipath daemon failed to include some ghost paths when counting the number of active paths; however, when the ghost paths failed, they were subtracted from the number of active paths. This caused multipathd to fail IO requests even though some paths were still available. The Multipath daemon now counts ghost paths correctly and no longer fails IO requests while there are still active paths available.

BZ#705854

If the user set dev_loss_tmo to a value greater than 600 in multipath.conf without setting the fast_io_fail_tmo value, the multipathd daemon did not notify the user that fast_io_fail_tmo was not set. Multipath now issues a warning that fast_io_fail_tmo is not set under such circumstances.

BZ#706555

On shared-storage multipath setups that set failback to manual, multipath could keep alternating from the failover pathgroup to the primary pathgroup infinitely. This happened because multipath was incorrectly failing back to the primary pathgroup whenever a path priority changed. With this update, multipath no longer fails back to the primary pathgroup when a path's priority changes under such circumstances.

BZ#707560

If the multipath device was deleted while a path was being checked, multipathd did not abort the path check and terminated unexpectedly when trying to access the multipath device information. The Multipath daemon now aborts any path checks when the multipath device is removed and the problem no longer occurs.

BZ#714821

The Multipath daemon was removing a multipath device twice. This could cause multipathd to access memory already used for another purpose, and caused the multipathd daemon to terminate unexpectedly. The multipathd daemon now removes the device once and the problem no longer occurs.

BZ#719571

The kpartx utility built partition devices for invalid GUID partition tables (GPT) because it did not validate the size of GUID partitions. The kpartx utility now checks the partition size, and does not build devices for invalid GPTs.

BZ#723168

Multipath previously returned an unclear error message when it failed to find rport_id. The returned message and its severity have been adjusted.

BZ#725541

Several upstream commits have been included in the device-mapper-multipath package providing a number of bug fixes and enhancements over the previous version.

BZ#738298

Anaconda failed to recognize an existing filesystem on a zSeries Linux fibre-channel adapter (zFCP) LUN and marked it as 'Unknown' when reinstalling the system. This happened due to an incorrect setting of the DM_UDEV_DISABLE_DISK_RULES_FLAG property. Filesystem on a multipath zFCP LUN is now correctly recognized during the installation.

BZ#747604

The asynchronous TUR path checker caused multipathd to terminate unexpectedly due to memory corruption. This happened if multipathd attempted to delete a path while the asynchronous TUR checker was running on the path. The asynchronous TUR checker code has been removed, and multipathd no longer crashes on path removal.

Enhancements

BZ#636009

Multipath now supports up to 8000 device paths.

BZ#683616

To provide support for Asymmetric Logical Unit Access (ALUA), the RDAC checker has been modified to work better with devices in IOSHIP mode. The checker now sets the Task Aborted Status (TAS) bit to 1 if the TAS bit is set to 0 and changeable on a LUN (Logical Unit Number) discovery. The function now also reports PATH_UP for both the path groups in the RDAC storage in IOSHIP mode.

BZ#694602

To run multipath on IBM BladeCenter S-series with RAIDed Shared Storage Module (RSSM) demanded a manual multipath configuration to enable RSSM. Multipath now configures the server automatically.

BZ#699577

The text in the defaults multipaths devices sections of the multipath.conf man page has been improved to provide a better clarification.

BZ#713754

The rr_min_io_rq option has been added to the default, devices, and multipaths sections of the multipath.conf file. This option defines the number of I/O requests to route to a path before switching to the next path in the current path group. Note that the rr_min_io option is no longer used.

BZ#710478

UID, GID, and mode owner settings defined in /etc/multipath.conf for a multipath device are ignored. These access permissions are now set with the udev rules.

BZ#802433

Device-Mapper Multipath uses certain regular expressions in the built-in device configurations to determine a multipath device so that the correct configuration can be applied to the device. Previously, some regular expressions for the device vendor and product ID were set too broad. As a consequence, some devices could be matched with incorrect device configurations. With this update, the product and vendor regular expressions have been set more strict so that all multipath devices can now be properly configured.

BZ#625880

To allow administrators easily disable the suspend and hibernate actions on the system, DeviceKit-power now checks the PolicyKit authorization before deciding whether an action can be completed.

BZ#727544

This update introduces a new sub-package DeviceKit-power-devel-docs, which contains developer's documentation for DeviceKit-power, so that it is now possible to install the DeviceKit-power-devel package on machines with multiple architectures without file conflicts.

Security Fix

CVE-2011-4539

A denial of service flaw was found in the way the dhcpd daemon handled DHCP request packets when regular expression matching was used in "/etc/dhcp/dhcpd.conf". A remote attacker could use this flaw to crash dhcpd.

BZ#694798

Previously, when multiple DHCP clients were launched at the same time to handle multiple virtual interfaces on the same network interface card (NIC), the clients used the same seed to choose when to renew their leases. Consequently, these virtual interfaces for some clients could have been removed over time. With this update, the dhclient utility uses the Process Identifier (PID) for seeding the random number generator, which fixes the bug.

BZ#694799

If a system was rebooted while a network switch was inoperative, the network connection would recover successfully. However, it was no longer configured to use DHCP even if the dhclient utility had been running in persistent mode. With this update, the dhclient-script file has been modified to refresh the ARP (Address Resolution Protocol) table and the routing table instead of bringing the interface down, which fixes the bug.

BZ#731990

If the system included network interfaces with no hardware address, the dhcpd scan could have experienced a segmentation fault when scanning such an interface. As a consequence, the dhcpd daemon unexpectedly terminated. To prevent this issue, dhcpd now tests a pointer which represents the hardware address of the interface for the NULL value. The dhcp daemon no longer crashes.

BZ#736999

Previously, all source files were compiled with the "-fpie" or "fPIE" flag. As a consequence, the libraries used by dhcp could not have been used to build Perl modules. To fix this problem, all respective dhcp Makefiles have been modified to compile libraries with the "-fpic" or "-fPIC" flag. The libraries used by dhcp are now built without the previous restrictions.

BZ#736194

Previously, both dhcp and dhclient packages included the dhcp-options(5) and dhcp-eval(5) man pages. As a consequence, a conflict could have occurred when any of these man pages were updated, because dhcp and dhclient packages could have been upgraded separately. To prevent the problem from occurring in future updates, shared files of dhcp and dhclient packages have been moved to the dhcp-common package that is required by both dhcp and dhclient as a dependency.

BZ#706974

A feature has been backported from dhcp version 4.2.0. This feature allows the DHCPv6 server to be configured to identify DHCPv6 clients in accordance with their link-layer address and their network hardware type. With this update, it is now possible to define a static IPv6 address for the DHCPv6 client with a known link-layer address.

BZ#693381

Previously, the dhcpd daemon ran as root. With this update, new "-user" and "-group" options can be used with dhcpd. These options allow dhcpd to change the effective user and group ID after it starts. The dhcpd and dhcpd6 services now run the dhcpd daemon with the "-user dhcpd -group dhcpd" parameters, which means that the dhcpd daemon runs as the dhcpd user and group instead root.

Bug Fixes

BZ#584009

Three changes were made to /etc/init.d/dnsmasq, the dnsmasq startup script:

• If dnsmasq was started or restarted by a non-privileged user, the startup script previously failed silently. With this update, the dnsmasq startup script now exits with a status code of 4 (user had insufficient privilege) and returns a "User has insufficient privilege" error to STD OUT when started or restarted by a non-privileged user.
• A "force-reload" option was added: The "service force-reload dnsmasq" command now forces dnsmasq to reload. Previously, it did nothing.
• If /etc/init.d/dnsmasq passed an invalid argument, previously the startup script exited with a status code of 1 (generic or unspecified error). With this update, the startup script now exits correctly, returning a status code of 2 (invalid or excess argument) in such a circumstance.

BZ#704073

If the virtual bridge interface (virbr0) was up and dnsmasq was started by default, dnsmasq could, in some circumstances, write a "DHCP packet received on eth(x) which has no address" message to /var/log/messages. Note: this message was not in error. The message was written if an actual interface (eg eth1) was up; did not have a configured IP address (eg was slaved to a logical bonded interface); and was in the same LAN as another host which generated a DHCP request. The message had little-to-no utility, however: it presented a warning where none was needed. With this update, this message is no longer written to /var/log/messages in these, and equivalent, circumstances.

BZ#624596

Previously, when the dosfsck and the dosfslabel utilities were executed on the IBM System z architecture using a FAT32 file system, they terminated with this error message: "Logical sector size is zero". This was caused by unaligned fields which were first byte-wise copied. With this fix, the fields are not pre-copied any more, but are accessed the same way as on the i686 architecture.

BZ#677789

The fsck.vfat utility terminated due to buffer overflow. This occurred when checking a device with the corrupted VFAT file system if there were any chains of orphaned clusters. The name of the newly created file that contained these clusters was printed directly into the name field, which led to an out of boundary write. The name is now printed into the buffer and individual parts are then correctly copied into the appropriate field.

BZ#688128

The dosfslabel utility displayed an error message when labeling the FAT32 file system due to some of its internal structures being initialized incorrectly. The dosfslabel utility now reads the FAT file system first, which fixes the problem.

BZ#709266

The mkfs.vfat utility did not correctly detect device partitions on RAID devices. As a consequence, formatting failed with an error message. This was caused by an invalid mask for the statbuf.st_rdev variable. The mask has been fixed to be at least four bytes long and the problem no longer occurs.

BZ#690076

Prior to this update, Doxygen required invalid BuildRequires on the qt-devel package. With this update, packages with BuildRequires dependencies on the qt-devel package have been fixed. Now, these packages explicitly require qt4-devel.

Bug Fix

BZ#860350

If the "/boot/" directory was not on a separate file system, dracut called the sha512hmac utility with a file name prefixed with "/sysroot/boot". Consequently, sha512mac searched for the file checksum in "/boot/", returned errors, and dracut considered the FIPS check to have failed. Eventually, a kernel panic occurred. With this update, dracut uses a symlink linking "/boot" to "/sysroot/boot", sha512mac can now access files in "/boot/", and FIPS checks now pass, allowing the system to boot properly in the described scenario.

Bug Fixes

BZ#659076

Previously, dracut incorrectly displayed that it loaded SELinux even if SELinux was disabled in the config file and "selinux=0" was not specified on the kernel command line. As a consequence, an error message could confuse the user when booting the system. With this update, the dracut utility is modified and the error message no longer appears.

BZ#696980

Due to an error in the dracut module script, the system could fail to find the root volume if a static IP address was specified. As a consequence, the system did not boot. With this update, the error is corrected, and the system is able to boot with a static IP address.

BZ#698160

When mounting the root device over the NFS (Network File System) protocol, the /var/lib/rpcbind directory created by initramfs was world-writable. The dracut tool has been modified to generate initramfs which now sets the ownership to the rpc user and the group.

BZ#698165

When auto-assembling an md RAID device, initramfs used an invalid parameter when calling the mdadm tool. This prevented the system from booting if the root device was on the RAID device. The invalid parameter has been removed and the system now boots properly.

BZ#698215

When auto-assembling an md RAID device, an error in the mdraid_start.sh script prevented the system from booting if the root device was on the RAID device. The error in the script has been fixed and the system now boots correctly.

BZ#701309

Prior to this update, the /var/lib/nfs/prc_pipefs partition could not be accessed on system boot. The problem occurred when booting the system with NFS set as the root partition with at least one separate /var partition. This was caused by initramfs mounting the /var partition over the existing rpc_pipefs partition. The initramfs file system now mounts entries in /etc/fstab.sys, which fixes the problem.

BZ#707609

The dm-mod and dm-crypt kernel modules were missing from the list of kernel modules, which are pre-loaded for the FIPS-140 check. These modules have been added to the list with this update.

BZ#712254

When loading SELinux from inside initramfs, the output of the SELinux commands could be garbled if the user used non-Latin locales. The initramfs file system has been modified to turn off localization for the SElinux commands, which results in readable messages.

BZ#737134

The QLogic qla4xxx iSCSI driver and the iSCSI (Internet Small Computer System Interface) transport layer now support iSCSI boot from Storage Area Network (SAN) using the iscsistart. With this update, dracut is modified to support these changes.

BZ#737593

If the user installed a system with rootfs on a RAID device where RAID members were encrypted, dracut failed to assemble the RAID device on reboot. As a consequence, the system did not boot. A patch has been applied to address this issue, and the RAID device is now assembled on every boot so that the system boots successfully.

BZ#741430

When applying SELinux labels for /dev in initramfs, the restorecon tool did not alter the MCS/MLS label only types. To fix this problem, the "-F" option has been added to all calls of restorecon.

BZ#742920

Prior to this update, the boot process timed out for network settings with DHCP involved. A patch has been applied to extend the timeout interval if DHCP is involved, which fixes the problem.

Enhancements

BZ#701864

This update adds support for iSCSI (Internet Small Computer System Interface) partial offload functionality for certain Broadcom network devices.

BZ#740487

This update adds the dracut-fips-aesni subpackage. Note that the package should be installed when using the aesni-intel module in FIPS mode.

BZ#723548

This update adds support for Logical Volume Management (LVM) mirror devices to serve as root devices. Additionally degraded mirrors are used after a certain timeout if the other half cannot be found at booting time.

BZ#729573

This update adds support for configuring an interface with automatic IPv6 and DHCP over IPv4 by using the "ip=[interface]:dhcp,auto6" command line parameter.

BZ#736094

With this update, the Broadcom FCoE (Fibre Channel over Ethernet) offload driver is now supported.

BZ#790943

When sourcing dracut modules, dracut did not check whether the "install" script for the module exists and is executable. Therefore, if the script was missing, an attempt to execute the script failed. As a consequence, dracut did not execute the "installkernel" script, and the module was not included in the initramfs image. This problem has been fixed, dracut now performs the check and only executes the "install" script when it exists. Then, the "installkernel" script is correctly executed and the module is installed in the initramfs image.

BZ#791128

Previously, dracut did not correctly handle a situation when booting a system with a degraded RAID array. In such a case, the initial RAM disk image (initramfs) was not able to start the array and the system did not boot. With this update, the initramfs forces the array to start and the system now boots as expected.

BZ#702593

Prior to this update, the dump utility passed wrong arguments to the "clone(2)" system call. As a result, dump became unresponsive when executed on the S/390 or IBM System z architecture. This bug has been fixed in this update so that dump now passes correct arguments and no longer hangs.

BZ#691434

Under certain circumstances, the dump utility could have failed to detect holes in files correctly. When a user attempted to restore an erroneous backup using the "restore" command, an error message "Missing blocks at end of [path], assuming hole" could have been displayed. In such case, the backup could have not been restored properly. This bug has been fixed in this update so that dump now handles holes in files as expected.

BZ#658890

Prior to this update, the "dump -w" command did not recognize ext4 file systems as supported. With this update, the bug has been fixed so that "dump -w" now recognizes the ext4 file systems as supported.

BZ#676465

Running the "e2fsck" command on certain corrupted file systems failed to correct all errors during the first run. This occurred when a file had its xattr block cloned as a duplicate, but the block was later removed from the file because the file system did not contain the xattr feature. However, the block was not cleared from the block bitmaps. During the second run, e2fsck found the cloned xattr block as in use, but not owned by any file, and had to repair the block bitmaps. With this update, the processing of duplicate xattr blocks is skipped on non-xattr file systems. All problems are now discovered during the first run.

BZ#679931

On certain devices with very large physical sector size, the mke2fs utility set the block size to be as large as the size of the physical sector. In some cases, the size of the physical sector was larger than the page size. As a consequence, the file system could not be mounted and, in rare cases, the utility could even fail. With this update, the default block size is not set to be larger than the system's page size, even for large physical sector devices.

BZ#683906

Previously, multiple manual pages contained typos. These typos have been corrected with this update.

BZ#713475

This update modifies parameters of the "mke2fs" command to be consistent with the "discard" and "nodiscard" mount options for all system tools (like mount, fsck, or mkfs). The user is now also informed about the ongoing discard process.

BZ#730083

Previously, the libcomm_err libraries were built without the read-only relocation (RELRO) flag. Programs built against these libraries could be vulnerable to various attacks based on overwriting the ELF section of a program. To enhance the security, the e2fsprogs package is now provided with partial RELRO support.

BZ#679892

Previously, the tune2fs tool could not set "barrier=0" as the default option on the ext3 and ext4 file systems. With this update, users are now able to set this option when creating the file system, and do not have to maintain the option in the /etc/fstab file across all of the file systems and servers.

BZ#713468

Previously, raw e2image output files could be extremely large sparse files, which were difficult to copy, archive, and transport. This update adds support for exporting images in the qcow format. Images in this format are small and easy to manipulate.

BZ#769673

Emacs did not properly terminate if it was started remotely and the remote client session was closed while Emacs was suspended. Under these conditions, Emacs entered an infinite loop in the code and gradually consumed all available computer resources, which caused the system to become unstable. With this update, Emacs has been modified, and it now terminates correctly when the remote session is closed.

BZ#796053

In ispell mode, Emacs used the spell checkers in the following order: Ispell, Aspell, and Hunspell. However, Ispell is no longer available and Aspell does not have any dictionaries installed by default. Consequently, because Emacs found Aspell before the default Hunspell, the spell check failed and Emacs reported the following error message:

ispell-init-process: Error: No word lists can be found for the language "en_US".

With this update, Emacs has been modified to look for the spell checkers in the following order: Hunspell, Aspell, and Ispell. This ensures that Hunspell is used by default when it is available.

BZ#253077

If the user resized an ESC window and closed it, the window did not preserve its size when opening it again. If the user wanted the window to be larger, for example, to make it easier to read, the user had to resize the window every single time when it was opened again. A patch has been applied to address this issue and the previous window size is now restored when opening ESC.

BZ#682216

Previously, during the shut down sequence of the escd daemon, the daemon reported a failure of certain instances. ESC terminated unexpectedly with a segmentation fault as a consequence. This update modifies the daemon to exit quietly. As a result, ESC no longer terminates unexpectedly.

BZ#702683

The esc-prefs.js file contains helpful commented settings designed to assist the user in trying rarely used settings if the situation warrants. A number of these settings in the file contained typos. The typos have been corrected with this update.

BZ#704281

Previously, ESC could have terminated with a segmentation fault after the user had inserted a new smart card into the reader. This was due to a bug in the code which helped to bring a pop-up window to the foreground. The code is no longer needed to assure window focus, therefore it is no longer being executed. As a result, ESC no longer terminates in the scenario described.

BZ#807264

The ESC utility did not start when the latest 10 series release of the XULRunner runtime environment was installed on the system. This update includes necessary changes to ensure that ESC works as expected with the latest version of XULRunner.

BZ#807806

After removing and replacing an enrolled token, ESC could terminate unexpectedly followed by a traceback. A patch has been applied to address this issue and ESC now displays the enrolled smart card details as expected.

Security Fixes

CVE-2012-0876

A denial of service flaw was found in the implementation of hash arrays in Expat. An attacker could use this flaw to make an application using Expat consume an excessive amount of CPU time by providing a specially-crafted XML file that triggers multiple hash function collisions. To mitigate this issue, randomization has been added to the hash function to reduce the chance of an attacker successfully causing intentional collisions.

CVE-2012-1148

A memory leak flaw was found in Expat. If an XML file processed by an application linked against Expat triggered a memory re-allocation failure, Expat failed to free the previously allocated memory. This could cause the application to exit unexpectedly or crash when all available memory is exhausted.

BZ#639466

When stopping the fcoe service, the fcoe initscript did not properly clean up after itself as expected (did not remove FCoE devices, kill related processes and unload FCoE drivers). As a consequence, FCoE interfaces were not brought down and FCoE related threads were still running after the fcoe had been stopped. The "service fcoe stop" command is used to ensure safe after-update service restarts on FCoE dependent systems, therefore it cannot be used to remove FCoE devices and unload related kernel modules. Concerning this situation, the initscript has been modified to use the "stop force" command option to completely remove FCoE devices and unload related kernel modules. The fcoe service now should be stopped using the "service fcoe stop force" command.

BZ#732485

When removing a network interface with no fcoe port using the "fcoeadm -d" command, the fcoe port state machine set the removal operation incorrectly to wait without responding to fcoemon. This led to an internal error because fcoemon timed out waiting for the response. To resolve the problem, the code has been modified to return the code for no further action under these circumstances. The "fcoeadm -d" command now works for interfaces without the fcoe port as expected.

BZ#732485

The fcoemon service did not maintain any information about the relative state of a physical network interface and its dependent VLAN interfaces. As a consequence, the fcoe port of the VLAN interface could have been out of sync with the fcoe port of the physical device, resulting in undesired behavior, such as processing link events improperly. To fix this problem, a ready flag has been introduced. This flag is set to false when the physical port is disabled. Link events are now processed correctly for the vlan ports.

BZ#732485

When answering to an FCoE Initialization Protocol (FIP) VLAN Discovery request, some switches encapsulate FIP VLAN Discovery replies in a VLAN 0 tag which is wrapped around the packet's FIP frame header. Previously, when a packet containing such a reply reached a target network interface, some devices did not remove the VLAN tag before they started to process the FIP header. If the VLAN tag was not removed, the length of the processed header was larger than was expected, therefore the FIP parsing logic was not able to parse the FIP header correctly causing a loss of the packet. With this update, the parsing logic has been modified to skip over the VLAN header when necessary, and point to the correct start of the FIP header.

BZ#743689

The timeout for a kernel reply to fcoeadm operations was set to 5 seconds, which was not enough when processing an fcoeadm operation on a system with a large number of FCoE ports while a kernel was under heavy load. As a consequence, the "internal error" message was displayed even though the operation was finished successfully. To prevent this bug, the timeout for the kernel reply was increased to 30 seconds. No error message is now sent when an fcoeadm operation succeeds.

BZ#731166

Due to a change in REST API, the fence_rhevm utility incorrectly reported status "UP" as "RUNNING". Consequently, the "fence_rhevm -o status" command always reported "OFF". This bug has been fixed, and fence_rhevm now reports status correctly.

BZ#718924

The fence_drac5 agent failed to clear its SSH sessions on exit as expected by firmware. Consequently, the fence agent appeared to be still connected to the device, and once the connection limit was reached, further logins to the device were not allowed. This bug has been fixed, and fence_drac5 now clears its SSH sessions properly.

BZ#693428

The "monitor" and "status" commands of the fence_ipmilan agent returned chassis status instead of the fence device status. As a result, when a server chassis was powered off, the fence_ipmilan agent exited with the incorrect result code "2" when passed one of these commands. Now, fence_ipmilan returns the correct result code "0" in the described scenario.

BZ#708052

When a blade server was removed from a blade chassis and was fenced via the fence_bladecenter utility with the "--missing-as-off" option enabled, and was scheduled with the "reboot" action, the fence failed. This bug has been fixed, and fence_bladecenter no longer returns an error if a blade server is missing.

BZ#718196

A list operation on fence_drac5 agents resulted in unexpected termination of fence agents. A patch has been provided to address this issue, and fence_drac5 agents now work correctly in the described scenario.

BZ#718207

When the pyOpenSSL package was not present in the system, when an error occurred, the fence_ilo agent terminated with a generic error message, making it difficult to debug the problem. Now, fence_ilo reports that a dependent package is missing in the described scenario, thus fixing this bug.

BZ#732372

The verbose mode of the fence_ipmilan agent exposed user passwords when the whole command was logged by an IPMI tool. Now, the fence_ipmilan output has been changed, and passwords remain undisclosed in the described scenario.

BZ#738384

During simultaneous unfencing operations performed via the fence_scsi agent, all nodes launched their reservation commands at the same time. Consequently, some of the commands failed. Now, fence_scsi retries to unfence a node until its reservation command succeeds.

BZ#734429

A null dereference was discovered in the fence_kdump agent, when the strchr() function returned the NULL value. With this update, the dereference has been fixed in the code and no longer occurs.

BZ#624673

With this update, the new fence_vmware_soap() function has been provided to enable fencing of VMware guests in ESX environments.

BZ#461948

The fence_kdump utility has been updated to integrate fencing with the kernel dump environment.

BZ#698365

With this update, the RelaxNG schema generation for fence-agents has been updated with the rha:description and rha:name attributes in its output to fence attribute group elements.

BZ#726571

The fence_ipmilan agent has been updated to support the -L option of the ipmilan daemon, thus supporting fencing with user session privileges level.

BZ#785816

The fence_rhevm fencing agent uses the Red Hat Enterprise Virtualization API to check the power status ("on" or "off") of a virtual machine. In addition to the states of "up" and "down", the API includes other states like "unassigned", "powering_up", "paused", "migrating", "unknown", "not_responding", "wait_for_launch", "reboot_in_progress", "saving_state", "restoring_state", "suspended", "image_illegal", "image_locked" or "powering_down". Previously, only if the machine was in the "up" state, the "on" power status was returned. The "off" status was returned for all other states although the machine was actually running. This allowed for successful fencing even before the machine was really powered off. With this update, the fence_rhevm agent detects power status of a cluster node more conservatively, and the "off" status is returned only if the machine is really powered off, it means in the "off" state.

BZ#811873

Previously, the fence_vmware_soap fence agent did not expose the full path to a virtual machine that is required for fencing. With this update, fence_vmware_soap has been modified to support identification of virtual machines as expected.

BZ#814843

Previously, fencing a Red Hat Enterprise Linux cluster node with the fence_soap_vmware fence agent running in a virtual machine on VMWare could fail with the following error message:

KeyError: 'config.uuid'

This was because the fence agent was not able to work with more than one hundred machines in a cluster. With this update, the underlying source code has been modified to support fencing of such clusters.

Bug Fix

BZ#1012574

Prior to this update, the fence agent for IPMI (Intelligent Platform Management Interface) could return an invalid return code when the "-M cycle" option was used. This invalid return code could cause invalid interpretation of success of a fence action, eventually causing the cluster to become unresponsive. This bug has been fixed and only predefined return codes are now returned in the described scenario.

BZ#719645

Prior to this update, the domain parameter was missing from the metadata. As a consequence, existing configurations utilizing the domain parameter did not function correctly when fencing. This update adds the domain parameter for compatibility. Now, existing configurations work as expected.

BZ#720767

Prior to this update, hash mismatches falsely returned successes for fencing. As a consequence, data corruption could occur in live-hang scenarios. This update corrects the hash handling of mismatches. Now, no more false successes are returned and the data integrity is preserved.

BZ#691200

With this update, the libvirt-qpid plugin now operates using QMF version 2.

BZ#807270

Previously, the libvirt-qpid plug-in was linked directly against Qpid libraries instead of being linked only against QMFv2 libraries. As a consequence, newer versions of Qpid libraries could not be used with the libvirt-qpid plug-in. This update modifies the appropriate makefile so that libvirt-qpid is no longer linked directly against the Qpid libraries. The libvirt-qpid plug-in does not have to be re-linked to work with the newer Qpid libraries.

BZ#676045, BZ#712992, BZ#712988

Prior to this update, the file utility could have been unable to recognize RPM files for certain supported architectures. This update improves the file type recognition, and the RPM files for all supported architectures are now correctly identified as expected.

BZ#688700

Prior to this update, the file utility did not correctly recognized the IBM System z kernel images. This problem has been corrected so that the IBM System z kernel images are now correctly recognized as expected.

BZ#692098

Prior to this update, the file utility attempted to show information related to core dumps for binary files that were not core dumps. This undesired behavior has been fixed in this update so that information related to core dumps is showed only for core dumps and not for the binary files which are not core dumps.

BZ#675691

Prior to this update, file patterns for LaTeX checked only the first 400 bytes of a file to determine the pattern type. This caused an incorrect pattern type recognition as some files could have contained a larger number of comments at the beginning of the file. Furthermore, file patterns which matched a Python script were tried before the LaTeX patterns and this undesired behavior could have caused an incorrect pattern type recognition as LaTeX files could have included a source code written in Python. With this update, the aforementioned problems have been fixed by increasing the number of first bytes checked for a LaTeX file to 4096 bytes, and by trying the LaTeX patterns before the Python patterns.

BZ#690801

Prior to this update, there were several spelling mistakes contained in the magic(5) manual page. This update corrects the spelling mistakes in the respective manual page.

BZ#716665

Prior to this update, the file utility treated MP3 files as text files, and therefore was unable to recognize the MP3 files. This undesired behavior has been fixed in this update, and the file utility now treats the MP3 files as binary files and is able to properly recognize them.

BZ#620063

Prior to this update, certain locale subdirectories in the /usr/share/locale/ directory did not have any owner set. With this update, this bug has been fixed so that the filesystem package now owns the subdirectories of the following locales: bg_BG (Bulgarian), en_NZ (New Zealand English), fi_FI (Finnish), gl_ES (Galician), lv_LV (Latvian), ms_MY (Malaysian), sr_RS (Serbian), en@shaw (Shavian), zh_CN.GB2312 (Chinese Simplified), sr@ijekavian (Serbian Jekavian), and sr@ijekavianlatin (Serbian Jekavian Latin).

BZ#727277

Prior to this update, the fipscheck library was linked without support for read-only relocations (RELRO) flags. The updated fipscheck packages are now provided with partial RELRO support.

Security Fixes

CVE-2011-3659

A use-after-free flaw was found in the way Firefox removed nsDOMAttribute child nodes. In certain circumstances, due to the premature notification of AttributeChildRemoved, a malicious script could possibly use this flaw to cause Firefox to crash or, potentially, execute arbitrary code with the privileges of the user running Firefox.

CVE-2012-0442

Several flaws were found in the processing of malformed web content. A web page containing malicious content could cause Firefox to crash or, potentially, execute arbitrary code with the privileges of the user running Firefox.

CVE-2012-0444

A flaw was found in the way Firefox parsed Ogg Vorbis media files. A web page containing a malicious Ogg Vorbis media file could cause Firefox to crash or, potentially, execute arbitrary code with the privileges of the user running Firefox.

CVE-2012-0449

A flaw was found in the way Firefox parsed certain Scalable Vector Graphics (SVG) image files that contained eXtensible Style Sheet Language Transformations (XSLT). A web page containing a malicious SVG image file could cause Firefox to crash or, potentially, execute arbitrary code with the privileges of the user running Firefox.

CVE-2011-3670

The same-origin policy in Firefox treated http://example.com and http://[example.com] as interchangeable. A malicious script could possibly use this flaw to gain access to sensitive information (such as a client's IP and user e-mail address, or httpOnly cookies) that may be included in HTTP proxy error replies, generated in response to invalid URLs using square brackets.

Security Fixes

CVE-2012-0461, CVE-2012-0462, CVE-2012-0464

Several flaws were found in the processing of malformed web content. A web page containing malicious content could cause Firefox to crash or, potentially, execute arbitrary code with the privileges of the user running Firefox.

CVE-2012-0456, CVE-2012-0457

Two flaws were found in the way Firefox parsed certain Scalable Vector Graphics (SVG) image files. A web page containing a malicious SVG image file could cause an information leak, or cause Firefox to crash or, potentially, execute arbitrary code with the privileges of the user running Firefox.

CVE-2012-0455

A flaw could allow a malicious site to bypass intended restrictions, possibly leading to a cross-site scripting (XSS) attack if a user were tricked into dropping a "javascript:" link onto a frame.

CVE-2012-0458

It was found that the home page could be set to a "javascript:" link. If a user were tricked into setting such a home page by dragging a link to the home button, it could cause Firefox to repeatedly crash, eventually leading to arbitrary code execution with the privileges of the user running Firefox.

CVE-2012-0459

A flaw was found in the way Firefox parsed certain web content containing "cssText". A web page containing malicious content could cause Firefox to crash or, potentially, execute arbitrary code with the privileges of the user running Firefox.

CVE-2012-0460

It was found that by using the DOM fullscreen API, untrusted content could bypass the mozRequestFullscreen security protections. A web page containing malicious web content could exploit this API flaw to cause user interface spoofing.

CVE-2012-0451

A flaw was found in the way Firefox handled pages with multiple Content Security Policy (CSP) headers. This could lead to a cross-site scripting attack if used in conjunction with a website that has a header injection flaw.

BZ#729632

When using the Traditional Chinese locale (zh-TW), a segmentation fault sometimes occurred when closing Firefox.

BZ#784048

Inputting any text in the Web Console (Tools -> Web Developer -> Web Console) caused Firefox to crash.

BZ#799042

The java-1.6.0-ibm-plugin and java-1.6.0-sun-plugin packages require the "/usr/lib/mozilla/plugins/" directory on 32-bit systems, and the "/usr/lib64/mozilla/plugins/" directory on 64-bit systems. These directories are created by the xulrunner package; however, they were missing from the xulrunner package provided by the RHEA-2012:0327 update. Therefore, upgrading to RHEA-2012:0327 removed those directories, causing dependency errors when attempting to install the java-1.6.0-ibm-plugin or java-1.6.0-sun-plugin package. With this update, xulrunner once again creates the plugins directory. This issue did not affect users of Red Hat Enterprise Linux 6.

Security Fixes

CVE-2011-3062

A flaw was found in Sanitiser for OpenType (OTS), used by Firefox to help prevent potential exploits in malformed OpenType fonts. A web page containing malicious content could cause Firefox to crash or, under certain conditions, possibly execute arbitrary code with the privileges of the user running Firefox.

CVE-2012-0467, CVE-2012-0468, CVE-2012-0469

A web page containing malicious content could cause Firefox to crash or, potentially, execute arbitrary code with the privileges of the user running Firefox.

CVE-2012-0470

A web page containing a malicious Scalable Vector Graphics (SVG) image file could cause Firefox to crash or, potentially, execute arbitrary code with the privileges of the user running Firefox.

CVE-2012-0472

A flaw was found in the way Firefox used its embedded Cairo library to render certain fonts. A web page containing malicious content could cause Firefox to crash or, under certain conditions, possibly execute arbitrary code with the privileges of the user running Firefox.

CVE-2012-0478

A flaw was found in the way Firefox rendered certain images using WebGL. A web page containing malicious content could cause Firefox to crash or, under certain conditions, possibly execute arbitrary code with the privileges of the user running Firefox.

CVE-2012-0471

A cross-site scripting (XSS) flaw was found in the way Firefox handled certain multibyte character sets. A web page containing malicious content could cause Firefox to run JavaScript code with the permissions of a different website.

CVE-2012-0473

A flaw was found in the way Firefox rendered certain graphics using WebGL. A web page containing malicious content could cause Firefox to crash.

CVE-2012-0474

A flaw in Firefox allowed the address bar to display a different website than the one the user was visiting. An attacker could use this flaw to conceal a malicious URL, possibly tricking a user into believing they are viewing a trusted site, or allowing scripts to be loaded from the attacker's site, possibly leading to cross-site scripting (XSS) attacks.

CVE-2012-0477

A flaw was found in the way Firefox decoded the ISO-2022-KR and ISO-2022-CN character sets. A web page containing malicious content could cause Firefox to run JavaScript code with the permissions of a different website.

CVE-2012-0479

A flaw was found in the way Firefox handled RSS and Atom feeds. Invalid RSS or Atom content loaded over HTTPS caused Firefox to display the address of said content in the location bar, but not the content in the main window. The previous content continued to be displayed. An attacker could use this flaw to perform phishing attacks, or trick users into thinking they are visiting the site reported by the location bar, when the page is actually content controlled by an attacker.

Security Fixes

CVE-2011-3101, CVE-2012-1937, CVE-2012-1938, CVE-2012-1939, CVE-2012-1940, CVE-2012-1941, CVE-2012-1946, CVE-2012-1947

Several flaws were found in the processing of malformed web content. A web page containing malicious content could cause Firefox to crash or, potentially, execute arbitrary code with the privileges of the user running Firefox.

CVE-2012-1944

Note: CVE-2011-3101 only affected users of certain NVIDIA display drivers with graphics cards that have hardware acceleration enabled.

It was found that the Content Security Policy (CSP) implementation in Firefox no longer blocked Firefox inline event handlers. A remote attacker could use this flaw to possibly bypass a web application's intended restrictions, if that application relied on CSP to protect against flaws such as cross-site scripting (XSS).

CVE-2012-1945

If a web server hosted HTML files that are stored on a Microsoft Windows share, or a Samba share, loading such files with Firefox could result in Windows shortcut files (.lnk) in the same share also being loaded. An attacker could use this flaw to view the contents of local files and directories on the victim's system. This issue also affected users opening HTML files from Microsoft Windows shares, or Samba shares, that are mounted on their systems.

BZ#664876

Previously, FirstAidKit's GRUB plug-in incorrectly reported failure if GRUB was installed into the Master Boot Record (MBR). Due to the plug-in being unreliable, it has been removed from the firstaidkit package.

BZ#738563

The firstaidkit-plugin-grub package has been removed from Red Hat Enterprise Linux 6.2. As a consequence, in rare cases, the system upgrade operation may fail with unresolved dependencies if the plug-in has been installed in a previous version of Red Hat Enterprise Linux. To avoid this problem, the firstaidkit-plugin-grub package should be removed before upgrading the system. However, in most cases, the system upgrade completes as expected.

BZ#700283

Previously, the Traditional Chinese translation (zh_TW) of the Forward button on the welcome page was different from the action mentioned in the text, on the same page, referring to this button. This update provides the corrected translation.

BZ#700305

Previously, when running firstboot in Japanese locale and the user attempted to continue without setting up an account, an untranslated warning message appeared. With this update, the message is properly translated into Japanese.

Security Fixes

CVE-2012-1134, CVE-2012-1136, CVE-2012-1142, CVE-2012-1144

Multiple flaws were found in the way FreeType handled TrueType Font (TTF), Glyph Bitmap Distribution Format (BDF), Windows .fnt and .fon, and PostScript Type 1 fonts. If a specially-crafted font file was loaded by an application linked against FreeType, it could cause the application to crash or, potentially, execute arbitrary code with the privileges of the user running the application.

CVE-2012-1126, CVE-2012-1127, CVE-2012-1130, CVE-2012-1131, CVE-2012-1132, CVE-2012-1137, CVE-2012-1139, CVE-2012-1140, CVE-2012-1141, CVE-2012-1143

Multiple flaws were found in the way FreeType handled fonts in various formats. If a specially-crafted font file was loaded by an application linked against FreeType, it could cause the application to crash.

Bug Fix

BZ#723757

Prior to this update, fusermount used an incorrect path to unmount. As a result, fusermount was unable to unmount mounted fuse file systems. This update, modifies fusermount to use the correct mount path. Now, mounted fuse file systems can be successfully unmounted with fusermount.

BZ#696352

The previous version of GCC incorrectly assumed that processors based on the AMD's multi-core architecture code named Bulldozer support the 3DNow! instruction set. This update adapts the underlying source code to make sure that GCC no longer uses the 3DNow! instructions on these processors.

BZ#705764

On the PowerPC architecture, GCC previously passed the V2DImode vector parameters using the stack and returned them in integer registers, which does not comply with the Application Binary Interface (ABI). This update corrects this error so that GCC now passes these parameters using the AltiVec parameter registers and returns them via the AltiVec return value register.

BZ#721376

Previously, GCC did not flush all pending register saves in a Frame Description Entry (FDE) before inline assembly instructions. This may have led to various problems when the inline assembly code modified those registers. With this update, GCC has been adapted to flush pending register saves in FDE before inline assembly instructions, resolving this issue.

BZ#732802

Prior to this update, the gcov test coverage utility sometimes incorrectly counted even opening brackets, which caused it to produce inaccurate statistics. This update applies a patch that corrects this error so that gcov ignores such brackets, as expected.

BZ#732807

When processing source code that extensively used overloading (that is, with hundreds or more overloads of the same function or method), the previous version of the C++ front end consumed a large amount of memory. This negatively affected the overall compile time and the amount of used system resources. With this update, the C++ front end has been optimized to use less resources in this scenario.

BZ#696145

This update adds support for new "-mfsgsbase", "-mf16c", and "-mrdrnd" command line options, as well as corresponding intrinsics to the immintrin.h header file. This allows for reading FS and GS base registers, retrieving random data from the random data generator, and converting between floating point and half-precision floating-point types.

BZ#696370

GCC now supports AMD's next generation processors. These processors can now be specified on the command line via the "-march=" and "-mtune=" command line options.

BZ#696495

GCC now supports Intel's next generation processor instrinsics and instructions for reading the hardware random number generator.

BZ#669432

Prior to this update, GDB could stop on error when trying to access the libpthread shared library before the library was relocated. Fixed GDB lets the relocations to be resolved first, making such program debuggable.

BZ#669434

The Intel Fortran Compiler records certain debug info symbols in uppercase but the gfortran compiler writes case-insensitive symbols in lowercase. As a result, GDB could terminate unexpectedly when accessing uppercase characters in the debug information from the Intel Fortran Compiler. With this update, GDB properly implements case insensitivity and ignores the symbols case in the symbol files.

BZ#692386

When the user selected the "-statistics" option with a negative number as a result, GDB printed the minus sign twice. This has been fixed and GDB now displays negative numbers with one minus sign only.

BZ#697900

On the PowerPC and the IBM System z architectures, GDB displayed only LWP (light-weight process) identifiers which matched the Linux TID (Thread Identifier) values for the threads found in the core file. GDB has been fixed to initialize the libthread_db threads debugging library when accessing the core file. GDB now correctly displays the pthread_t identifier in addition to the LWP identifier on the aforementioned architectures.

BZ#702427

Structure field offsets above 65535 described by the DWARF DW_AT_data_member_location attribute were improperly interpreted as a 0 value. GDB has been modified and can now handle also large structures and their fields.

BZ#704010

The difference between the very closely related "ptype" and "whatis" commands was not clearly defined in the gdb info manual. Detailed differences between these commands have been described in the manual.

BZ#712117

Prior to this update, the "info sources" subcommand printed only relative paths to the source files. GDB has been modified to correctly display the full path name to the source file.

BZ#730475

Modifying a string in the executable using the "-write" command line option could fail with an error if the executable was not running. With this update, GDB can modify executables even before they are started.

BZ#696890

With this update, Float16 instructions on future Intel processors are now supported.

BZ#698001

Debugged programs can open many shared libraries on demand at runtime using the dlopen() function. Prior to this update, tracking shared libraries that were in use by the debugged program could lead to overhead. The debugging performance of GDB has been improved: the overhead is now lower if applications load many objects.

BZ#718141

Prior to this update, GDB did not handle DWARF 4 .debug_types data correctly. Now, GDB can correctly process data in the DWARF 4 format.

Bug Fix

BZ#860645

When gdm was used to connect to a server via XDMCP (X Display Manager Control Protocol), another connection to a remote system using the "ssh -X" command resulted in wrong authorization with the X server. Consequently, applications such as xterm could not be displayed on the remote system. This update provides a compatible MIT-MAGIC-COOKIE-1 key in the described scenario, thus fixing this bug.

BZ#661618

GDM did not properly queue up multiple authentication messages so that messages could quickly be overwritten by newer messages. The queueing mechanism has been modified, and this problem no longer occurs.

BZ#628462

If a Russian keyboard layout was chosen during system installation, the login screen was configured to use Russian input for user names and passwords by default. However, GDM did not provide any visible way to switch between keyboard layouts, and pressing Left Shift and Right Shift keys did not cause the input to change to ASCII mode in GDM. Consequently, users were not able to log in to the system. With this update, GDM allows users to switch keyboard layout properly using the keyboard layout indicator, and users can now log in as expected.

BZ#723515

GDM did not properly release file descriptors used with XDMCP indirect queries. As a consequence, the number of file descriptors used by GDM increased with every XDMCP chooser restart, which, in some cases, led to memory exhaustion and a GDM crash. The underlying GDM code has been modified to manage file descriptors properly, and the problem no longer occurs in this scenario.

BZ#670619

In multi-monitor setups, GDM always displayed the login window on the screen that was determined as active by the mouse pointer position. This behavior caused unpredictable login window placement in dual screen setups when using the NVIDIA's TwinView Dual-Display Architecture because the mouse pointer initially appeared exactly between the monitors outside of the visible screen. GDM now uses new logic to ensure that the initial placement of the mouse pointer and the login window are consistently on one screen.

BZ#645453

The GDM simple greeter login window displayed "Suspend", "Restart" and "Shut Down" buttons even though the buttons were disabled in GDM configuration and the PolicyKit toolkit disallowed any stop, restart, suspend actions on the system. With this update, GDM logic responsible for setting up the greeter login window has been modified and these buttons are no longer displayed under these circumstances

BZ#622561

When authenticating to a system and the fingerprint authentication method was enabled, but no fingerprint reader was attached to the machine, GDM erroneously displayed authentication method buttons for a brief moment. With this update, GDM displays authentication method buttons only if the authentication method is enabled and a reading device is connected.

BZ#708430

GDM did not properly handle its message queue. Therefore, when resetting a password on user login, GDM displayed an error message from a previous unsuccessful attempt. The queueing mechanism has been modified, and this problem no longer occurs.

BZ#688158

When logging into a system using LDAP authentication, GDM did not properly handle LDAP usernames containing backslash characters. As a consequence, such usernames were not recognized and users were not able to log in even though they provided valid credentials. With this update, GDM now handles usernames with backslash characters correctly and users can log in as expected.

BZ#799940

Previously, X server audit messages were not included by default in the X server log. Now, those messages are unconditionally included in the log. Also, with this update, verbose messages are added to the X server log if debugging is enabled in the /etc/gdm/custom.conf file (by setting "Enable=true" in the [debug] section).

Security Fixes

CVE-2009-3743

An integer overflow flaw was found in Ghostscript's TrueType bytecode interpreter. An attacker could create a specially-crafted PostScript or PDF file that, when interpreted, could cause Ghostscript to crash or, potentially, execute arbitrary code.

CVE-2010-2055

It was found that Ghostscript always tried to read Ghostscript system initialization files from the current working directory before checking other directories, even if a search path that did not contain the current working directory was specified with the "-I" option, or the "-P-" option was used (to prevent the current working directory being searched first). If a user ran Ghostscript in an attacker-controlled directory containing a system initialization file, it could cause Ghostscript to execute arbitrary PostScript code.

CVE-2010-4820

Ghostscript included the current working directory in its library search path by default. If a user ran Ghostscript without the "-P-" option in an attacker-controlled directory containing a specially-crafted PostScript library file, it could cause Ghostscript to execute arbitrary PostScript code. With this update, Ghostscript no longer searches the current working directory for library files by default.

Note

The fix for CVE-2010-4820 could possibly break existing configurations. To use the previous, vulnerable behavior, run Ghostscript with the "-P" option (to always search the current working directory first).

CVE-2010-4054

A flaw was found in the way Ghostscript interpreted PostScript Type 1 and PostScript Type 2 font files. An attacker could create a specially-crafted PostScript Type 1 or PostScript Type 2 font file that, when interpreted, could cause Ghostscript to crash or, potentially, execute arbitrary code.

Security Fixes

CVE-2009-5064

A flaw was found in the way the ldd utility identified dynamically linked libraries. If an attacker could trick a user into running ldd on a malicious binary, it could result in arbitrary code execution with the privileges of the user running ldd.

CVE-2011-1089

It was found that the glibc addmntent() function, used by various mount helper utilities, did not handle certain errors correctly when updating the mtab (mounted file systems table) file. If such utilities had the setuid bit set, a local attacker could use this flaw to corrupt the mtab file.

Bug Fixes

BZ#676467

The installation of the glibc-debuginfo.i686 and glibc-debuginfo.x86_64 packages failed with a transaction check error due to a conflict between the packages. This update adds the glibc-debuginfo-common package that contains debuginfo data that are common for all platforms. The package depends on the glibc-debuginfo package and the user can now install debuginfo packages for different platforms on a single machine.

BZ#676591

When a process corrupted its heap, the malloc() function could enter a deadlock while creating an error message string. As a result, the process could become unresponsive. With this update, the process uses the mmap() function to allocate memory for the error message instead of the malloc() function. The malloc() deadlock therefore no longer occurs and the process with a corrupted heap now aborts gracefully.

BZ#692838

India has adopted a new symbol for the Indian rupee leaving the currency symbol for its Unicode U20B9 outdated. The rupee symbol has been updated for all Indian locales.

BZ#694386

The strncmp() function, which compares characters of two strings, optimized for IBM POWER4 and POWER7 architectures could return incorrect data. This happened because the function accessed the data past the zero byte (\0) of the string under certain circumstances. With this update, the function has been modified to access the string data only until the zero byte and returns correct data.

BZ#699724

The crypt() function could cause a memory leak if used with a more complex salt. The leak arose when the underlying NSS library attempted to call the dlopen() function from libnspr4.so with the RTLD_NOLOAD flag. With this update, the dlopen() with the RTLD_NOLOAD flag has been fixed and the memory leak no longer occurs.

BZ#700507

On startup, the nscd daemon logged the following error into the log file if SELinux was active:

rhel61 nscd: Can't send to audit system: USER_AVC avc:  netlink
poll: error 4#012: exe="?" sauid=28 hostname=? addr=? terminal=?

This happened because glibc failed to preserve the respective capabilities on UID change in the AVC thread. With this update, the AVC thread preservers the respective capabilities after the nscd startup.

BZ#703481, BZ#703480

When a host was temporarily unavailable, the nscd daemon cached an error, which did not signalize that the problem was only transient, and the request failed. With this update, the daemon caches a value signalizing that the unavailability is temporary and retries to obtain new data after a set time limit.

BZ#705465

When a module did not provide its own method for retrieving a user list of supplemental group memberships, the libc library's default method was used instead and all groups known to the module were examined to acquire the information. Consequently, applications which attempted to retrieve the information from multiple threads simultaneously, interfered with each other and received an incomplete result set. This update provides a module-specific method which prevents this interference.

BZ#706903

On machines using the Network Information Service (NIS), the getpwuid() function failed to resolve UIDs to user names when using the passwd utility in the compat mode with a big netgroup. This occurred because glibc was compiled without the -DUSE_BINDINGDIR=1 option. With this update, glibc has been compiled correctly and getpwuid() function works as expected.

BZ#711927

A debugger could have been presented with an inconsistent state after loading a library. This happened because the ld-linux program did not relocate the library before calling the debugger. With this update, the library is relocated prior to the calling of the debugger and the library is accessed successfully.

BZ#714823

The getaddrinfo() function internally uses the simpler gethostbyaddr() functions. In some cases, this could result in incorrect name canonicalization. With this update, the code has been modified and the getaddrinfo() function uses the gethostbyaddr() functions only when appropriate.

BZ#718057

The getpwent() lookups to LDAP (Lightweight Directory Access Protocol) did not return any netgroup users if the NIS (Network Information Service) domain for individual users was not defined in /etc/passwd. This happened when the nss_compat mode was set as the mode was primarily intended for use with NIS. With this update, getpwent returns LDAP netgroup users even if the users have no NIS domain defined.

BZ#730379

The libresolv library is now compiled with the stack protector enabled.

BZ#731042

The pthread_create() function failed to cancel a thread properly if setting of the real time policy failed. This occurred the because __pthread_enable_asynccancel() function as a non-leaf function did not align the stack on the 16-byte boundary as required by AMD64 ABI (Application Binary Interface). With this update, the stack alignment is preserved accros functions.

BZ#736346

When calling the setgroups function after creating threads, glibc did not cross-thread signal and supplementary group IDs were set only for the calling thread. With this update, the cross-thread signaling in the function has been introduced and supplementary group IDs are set on all involved threads as expected.

BZ#737778

The setlocale() function could fail. This happened because parameter values were parsed in the set locale. With this update, the parsing is locale-independent.

BZ#738665

A write barrier was missing in the implementation of addition to linked list of threads. This could result in the list corruption after several threads called the fork() function at the same time. The barrier has been added and the problem no longer occurs.

BZ#739184

Statically-linked binaries that call the gethostbyname() function terminated because of division by zero. This happened because the getpagesize() function required the dl_pagesize field in the dynamic linker's read-only state to be set. However, the field was not initialized when a statically linked binary loaded the dynamic linker. With this update, the getpagesize() function no longer requires a non-zero value in the dl_pagesize field and falls back to querying the value through the syscall() function if the field value is not set.

Enhancements

BZ#712248

For some queries, the pathconf() and fpathconf() functions need details about each filesystem type: mapping of its superblock magic number to various filesystem properties that cannot be queried from the kernel. This update adds support for the Lustre file system to pathconf and fpathconf.

BZ#695595

The glibc package now provides functions optimized for the Intel 6 series and Intel Xeon 5600 processors.

BZ#695963

The glibc package now supports SSE2 (Streaming SIMD Extensions 2) instructions on the strlen() function for the AMD FX processors.

BZ#711987

This update adds the f_flags field to support the statvfs output received from kernel.

BZ#738763

The Linux kernel supports the UDP IP_MULTICAST_ALL socket option, which provides the ability to turn off IP Multicast multiplexing. This update adds the option to glibc.

Security Fixes

CVE-2009-5029

An integer overflow flaw, leading to a heap-based buffer overflow, was found in the way the glibc library read timezone files. If a carefully-crafted timezone file was loaded by an application linked against glibc, it could cause the application to crash or, potentially, execute arbitrary code with the privileges of the user running the application.

CVE-2011-4609

A denial of service flaw was found in the remote procedure call (RPC) implementation in glibc. A remote attacker able to open a large number of connections to an RPC service that is using the RPC implementation from glibc, could use this flaw to make that service use an excessive amount of CPU time.

BZ#754116

glibc had incorrect information for numeric separators and groupings for specific French, Spanish, and German locales. Therefore, applications utilizing glibc's locale support printed numbers with the wrong separators and groupings when those locales were in use. With this update, the separator and grouping information has been fixed.

BZ#766484

The RHBA-2011:1179 glibc update introduced a regression, causing glibc to incorrectly parse groups with more than 126 members, resulting in applications such as "id" failing to list all the groups a particular user was a member of. With this update, group parsing has been fixed.

BZ#769594

glibc incorrectly allocated too much memory due to a race condition within its own malloc routines. This could cause a multi-threaded application to allocate more memory than was expected. With this update, the race condition has been fixed, and malloc's behavior is now consistent with the documentation regarding the MALLOC_ARENA_TEST and MALLOC_ARENA_MAX environment variables.

Security Fix

CVE-2012-0864

An integer overflow flaw was found in the implementation of the printf functions family. This could allow an attacker to bypass FORTIFY_SOURCE protections and execute arbitrary code using a format string flaw in an application, even though these protections are expected to limit the impact of such flaws to an application abort.

BZ#783999

Previously, the dynamic loader generated an incorrect ordering for initialization according to the ELF specification. This could result in incorrect ordering of DSO constructors and destructors. With this update, dependency resolution has been fixed.

BZ#795328

Previously, locking of the main malloc arena was incorrect in the retry path. This could result in a deadlock if an sbrk request failed. With this update, locking of the main arena in the retry path has been fixed. This issue was exposed by a bug fix provided in the RHSA-2012:0058 update.

BZ#799259

Calling memcpy with overlapping arguments on certain processors would generate unexpected results. While such code is a clear violation of ANSI/ISO standards, this update restores prior memcpy behavior.

BZ#802855

Previously, glibc looked for an error condition in the wrong location and failed to process a second response buffer in the gaih_getanswer() function. As a consequence, the getaddrinfo() function could not properly return all addresses. This update fixes an incorrect error test condition in gaih_getanswer() so that glibc now correctly parses the second response buffer. The getaddrinfo() function now correctly returns all addresses.

BZ#813859

Previously, if the nscd daemon received a CNAME (Canonical Name) record as a response to a DNS (Domain Name System) query, the cached DNS entry adopted the TTL (Time to Live) value of the underlying "A" or "AAAA" response. This caused the nscd daemon to wait for an unexpectedly long time before reloading the DNS entry. With this update, nscd uses the shortest TTL from the response as the TTL value for the entire record. DNS entries are reloaded as expected in this scenario.

BZ#798771

Previously, the interface provided by the gmp library was changed. This resulted in one exported symbol being absent in Red Hat Enterprise Linux 6 (when compared to the Red Hat Enterprise Linux 5 system). In addition, the symbol could have been reported as missing under certain circumstances. To fix this problem, this update adds the missing symbol back to the library.

Bug Fix

BZ#822946

Previously, it was possible for the user to log out of the system or shut it down while the PackageKit update tool was running and writing to the RPM database (rpmdb). Consequently, rpmdb could become damaged and inconsistent due to the unexpected termination and cause various problems with subsequent operation of the rpm, yum, and PackageKit utilities. This update modifies PackageKit to not allow shutting down the system when a transaction writing to rpmdb is active, thus fixing this bug.

Bug Fix

BZ#800267

After resuming the system or re-enabling the display, an icon could appear in the notification area with an erroneous tooltip that read "Session active, not inhibited, screen idle. If you see this test, your display server is broken and you should notify your distributor." and included a URL to an external web page. This error message was incorrect, had no effect on the system and could be safely ignored. In addition, linking to an external URL from the notification and status area is unwanted. To prevent this, the icon is no longer used for debugging idle problems.

BZ#648850

When the user locked the screen and the X Window System did not support the X Resize, Rotate (XRandR) or XF86VM gamma fade extensions, then the gnome-screensaver utility terminated with a segmentation fault. With this update, additional checks are made before calling the fade_setup() function, and gnome-screensaver no longer terminates.

BZ#697892

Prior to this update, the Unlock dialog box arbitrarily changed between the monitors in dual head setups, based on the position of the mouse pointer. The Unlock dialog box is now placed on a consistent monitor instead of where the mouse is located.

BZ#719023

Previously, when docking a laptop and using an external monitor, parts of the background got cut off due to incorrect logic for determining monitor dimensions. With this update, the source code is modified and the login screen is now displayed correctly.

BZ#740892

Previously, in rare cases, the screen saver entered a deadlock if monitors were removed during the fade up. The screen was locked as a consequence. This update modifies gnome-screensaver so that the screen saver responds as expected.

BZ#677580

Previously, there was no indicator of the keyboard layout when the screen was locked. Users who used more than one layout did not know which layout was active. Consequently, users could be forced to type the password several times. This update adds the missing keyboard layout indicator.

BZ#664516

Prior to this update, the gnome-session utility may have improperly saved desktop sessions. As a consequence, when logging in, the running applications were incorrectly collapsed from multiple workspaces into the first workspace and their initial position was not restored. This has been fixed: applications are now restored in their original workspaces and correctly positionally placed.

Enhancement

BZ#622849

Prior to this update, users were not able to manage multiple custom GNOME sessions while being logged in. Now, multiple sessions can be managed under the Options tab of System -> Preferences -> Startup Applications.

BZ#571597

Previously, the CPU History graph could be hard to read if it displayed large numbers of CPUs. This update modifies the design: scrollbars were added for easier manipulation of the window and random color is now generated to each CPU.

BZ#655132

Previously, the regular expression used to find URLs in the text was missing a colon character. As a consequence, the URL containing a colon was not interpreted correctly. With this update, a colon character has been added to the regular expression so that the URL is now properly interpreted.

Security Fixes

CVE-2012-1573

A flaw was found in the way GnuTLS decrypted malformed TLS records. This could cause a TLS/SSL client or server to crash when processing a specially-crafted TLS record from a remote TLS/SSL connection peer.

CVE-2011-4128

A boundary error was found in the gnutls_session_get_data() function. A malicious TLS/SSL server could use this flaw to crash a TLS/SSL client or, possibly, execute arbitrary code as the client, if the client passed a fixed-sized buffer to gnutls_session_get_data() before checking the real size of the session data provided by the server.

BZ#684920

Prior to this update, it was not possible to build the gpm packages on the supported platforms if the emacs package was installed. This problem has been resolved with this update and no longer occurs.

BZ#743893

Prior to this update, PXE failed to boot a virtual machine which used the virtio network interface card (NIC). An upstream patch, which incorporates the latest upstream gPXE paravirtualized network adapter (virtio-net) driver and removes the legacy Etherboot virtio-net driver, has been applied to fix this problem. Now, PXE can successfully boot virtual machines that use virtio NIC.

BZ#624658

Several links in the Graphviz Documentation Index file led to nonexistent or incorrectly named files. This update fixes these links so that their targets resolve correctly.

BZ#624690

The graphviz test suite was disabled on the PowerPC, 64-bit PowerPC and SPARC64 architectures due to unexpected terminations with segmentation faults. The test code used in the test suite did not set the TextLayout plugin correctly, which led to the crash of the test suite. This has been fixed and the test suite passes on all architectures.

BZ#640247

Prior to this update, the About dialog box displayed "<unknown>" instead of the real name of the DotEdit utility. This has been fixed and the name is now displayed correctly.

BZ#679715

When using the graphviz utility with PHP, the gv.so module did not load and displayed the following error message:

/usr/lib64/php/modules/gv.so' - /usr/lib64/php/modules/gv.so: undefined symbol: zend_error_noreturn in Unknown on line 0

This was caused by the SWIG tool which used the zend_error_noreturn() function to build the PHP module. SWIG has been modified and the bug no longer occurs.

BZ#677468

Due to an error in the underlying source code, previous versions of GRUB may have failed to boot in Unified Extensible Firmware Interface (UEFI) mode. This happened, because GRUB was making UEFI calls without aligning the stack pointer to a 16-byte boundary. With this update, a patch has been applied to correct this error, and GRUB now boots in UEFI mode as expected.

BZ#736833

Prior to this update, an attempt to install GRUB on a CCISS device may have caused the grub-install utility to report the following error:

expr: non-numeric argument

When this happened, grub-install failed to install GRUB on this device, but incorrectly reported success and returned a zero exit status. This update applies a patch that ensures that GRUB can now be successfully installed on such devices.

BZ#746106

When looking for its configuration file, the previous versions of GRUB did not respect vendor-specific EFI device path. With this update, the underlying source code has been adapted to use the vendor-specific EFI-device path as expected.

BZ#629408

Prior to this update, the GRUB boot loader was unable to boot from boot drives that were larger than 2.2 TB. This update adds support for such devices on UEFI systems.

BZ#671355

On BIOS-based systems, previous versions of GRUB were only able to boot from first eight disk drives. This update allows GRUB to boot from up to 128 disk drives on these systems.

BZ#659674

Due to a problem in the build test suite, the guile package failed to build. The problem has been resolved in this update so that the guile package now builds properly.

Security Fix

CVE-2011-3639, CVE-2011-4317

It was discovered that the fix for CVE-2011-3368 (released via RHSA-2011:1391) did not completely address the problem. An attacker could bypass the fix and make a reverse proxy connect to an arbitrary server not directly accessible to the attacker by sending an HTTP version 0.9 request, or by using a specially-crafted URI.

CVE-2012-0053

The httpd server included the full HTTP header line in the default error page generated when receiving an excessively long or malformed header. Malicious JavaScript running in the server's domain context could use this flaw to gain access to httpOnly cookies.

CVE-2011-3607

An integer overflow flaw, leading to a heap-based buffer overflow, was found in the way httpd performed substitutions in regular expressions. An attacker able to set certain httpd settings, such as a user permitted to override the httpd configuration for a specific directory using a ".htaccess" file, could use this flaw to crash the httpd child process or, possibly, execute arbitrary code with the privileges of the "apache" user.

CVE-2012-0031

A flaw was found in the way httpd handled child process status information. A malicious program running with httpd child process privileges (such as a PHP or CGI script) could use this flaw to cause the parent httpd process to crash during httpd service shutdown.

BZ#694939

The Apache module "mod_proxy" implements a proxy or gateway for the Apache web server. The "ProxyErrorOverride On" option did not work if used with "mod_proxy_ajp", the AJP support module for mod_proxy. Consequently when accessing a 404 URL in the "/static" context, which was proxied with AJP, the 404 page from the proxy was displayed rather than the 404 page from Apache itself. This update corrects the code and accessing 404 URLs now works as intended, via Apache, as defined in "ErrorDocument".

BZ#700074

When a backend server sends data via SSL, and is using chunked transfer encoding, the backend splits the chunk between two different SSL blocks. Prior to this update, when transferring data via SSL through a reverse proxy implemented with Apache, "mod_proxy", and "mod_ssl", the end of the first SSL block was sometimes lost and the length of the next chunk was thus invalid. Consequently, files were sometimes corrupted during transfer via SSL. This updates implements a backported fix to this problem and the error no longer occurs.

BZ#700075

The "FilterProvider" directive of the "mod_filter" module was unable to match against non-standard HTTP response headers. Consequently, output content data was not filtered or processed as expected by httpd in certain configurations. With this update, a backported patch has been applied to address this issue, and the FilterProvider directive is now able to match against non-standard HTTP response headers as expected.

BZ#700393

In situations where httpd could not allocate memory, httpd sometimes terminated unexpectedly with a segmentation fault rather than terminating the process with an error message. With this update, a patch has been applied to correct this issue and httpd no longer crashes in the scenario described.

BZ#714704

Server Name Indication (SNI) sends the name of the virtual domain as part of the TLS negotiation. Prior to this enhancement, if a client sent the wrong SNI data the client would be rejected. With this update, in configurations where SNI is not required, "mod_ssl" can ignore the SNI hostname "hint".

BZ# 720980

Prior to this update, httpd terminated unexpectedly on startup with a segmentation fault when proxy client certificates were shared across multiple virtual hosts (using the SSLProxyMachineCertificateFile directive). With this update a patch has been applied and httpd no longer crashes in the scenario described.

BZ#729585

When the "SSLCryptoDevice" config variable in "ssl.conf" was set to an unknown or invalid value, the httpd daemon would terminate unexpectedly with a segmentation fault at startup. With this update the code has been corrected, httpd no longer crashes, and httpd will issue an appropriate error message in this scenario.

BZ#737960

If using mod_proxy_ftp, an httpd process could terminated unexpectedly with a segmentation fault when tests were made on an IPv6 localhost enabled machine. This update implements improvements to the code and the mod_proxy_ftp process no longer crashes in the scenario described.

BZ#740242

When using the "mod_cache" module, by default, the "CacheMaxExpire" directive is only applied to responses which do not specify their expiry date. Previously, it was not possible to limit the maximum expiry time for all resources. This update applies a patch which adapts the mod_cache module to provide support for "hard" as a second argument of the CacheMaxExpire directive, allowing a maximum expiry time to be enforced for all resources.

BZ#676634

The "mod_reqtimeout" module, when enabled, allows fine-grained timeouts to be applied during request parsing. The mod_reqtimeout module has been backported from upstream in this update.

BZ#682399

The pci.ids database has been updated with information about HP Laptop WiFi chipsets.

BZ#695798

The pci.ids database has been updated with information about future Intel PCH (Platform Controller Hub) devices.

BZ#712177

The pci.ids database has been updated with correct information about QLogic IBA7322 InfiniBand devices.

BZ#713070

The pci.ids database has been updated with information about future Atheros wireless devices.

BZ#739376

The pci.ids database has been updated with information about future Broadcom wireless devices.

BZ#728909

The pci.ids database has been updated according to the latest upstream changes.

BZ#667031

IBus did not work on a minimal installation of Red Hat Enterprise Linux 6 if no desktop environment, such as KDE or GNOME, was installed. This issue was caused by the missing dbus-x11 package, which IBus is dependent on. The dbus-x11 package is now included as a prerequisite for IBus in the IBus spec file, and IBus now works as expected.

BZ#661597

Previously, when changing the Candidate Window Page Size setting of Other under the General tab, the im-chooser application had to be restarted for the changes to take effect. This problem has been fixed and the changes made to Candidate Window Page Size now apply immediately.

BZ#712805

Prior to this update, the ibus-table-erbi spec file contained a redundant line which printed the debug message "/usr/share/ibus-table/tables" at the end of installation. The line indicated the working directory of the post-install script and has been removed to fix the problem.

BZ#729906

Previously, the table index was updated when running the post-install script of the ibus-table-erbi package. This modified the size of the files, the MD5 Message-Digest Algorithm checksum and the access time of database files. As a consequence, the "rpm -V" command failed with false positive warnings of the aforementioned changes due to the changes not matching the values in the package metadata. This has been fixed: files that are expected to be modified when running the post-install script are now specified with correct verify flags in the spec file.

BZ#683479

The Java Web Start window invoked by the "javaws -about" command contained out-of-date information and could not be closed correctly. The information was out-dated because the Java Network Launching Protocol (JNLP) XML file defined inadequate access permissions to access the about.jnlp file, which contained the update information. With this update, the about information has been moved to an accessible location. The window failed to close as the respective process thread became unresponsive. Now, the window contains up-to-date information and the thread closes correctly.

BZ#718693

MindTerm SSH Applet failed to work as it was using class netscape.security.PrivilegeManager, which was not present in icedtea-web. This update adds the class and the applet works as expected.

BZ#731345, BZ#731358

Java Web Start and IcedTea plug-in sometimes failed to run as they were calling a java binary with a JDK-based path instead of a JRE-based path. With this update, the package spec file contains the correct definition of the path construction and javaws and icedtea-plugin call the correct java binary.

BZ#734081

When running an application with javaws, javaws failed to use the proxy settings from Firefox even though the respective setting was enabled ("Use browser settings") and failed over to the "DIRECT" mode. This happened because javaws was looking for the DEFAULT profile in the Firefox configuration file to acquire the current proxy settings. If it failed to locate the section with the DEFAULT profile, the default "DIRECT" mode was applied. With this update, javaws uses the settings from the last section under these circumstances.

BZ#741796

Starting from version 10, Elluminate did not work with IcedTea-Web. This happened because Elluminate specified Class-Path elements in its manifest file which caused a conflict with the jnlp-specified JARs. With this update, the IcedTea-Web plug-in no longer honors the Class-Path elements (just as the Oracle implementation) and Elluminate works with IcedTea-Web as expected.

Security Fix

CVE-2011-4599

A stack-based buffer overflow flaw was found in the way ICU performed variant canonicalization for some locale identifiers. If a specially-crafted locale representation was opened in an application linked against ICU, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application.

Security Fix

CVE-2012-0247

A flaw was found in the way ImageMagick processed images with malformed Exchangeable image file format (Exif) metadata. An attacker could create a specially-crafted image file that, when opened by a victim, would cause ImageMagick to crash or, potentially, execute arbitrary code.

CVE-2012-0248

A denial of service flaw was found in the way ImageMagick processed images with malformed Exif metadata. An attacker could create a specially-crafted image file that, when opened by a victim, could cause ImageMagick to enter an infinite loop.

CVE-2010-4167

It was found that ImageMagick utilities tried to load ImageMagick configuration files from the current working directory. If a user ran an ImageMagick utility in an attacker-controlled directory containing a specially-crafted ImageMagick configuration file, it could cause the utility to execute arbitrary code.

CVE-2012-0259

An integer overflow flaw was found in the way ImageMagick processed certain Exif tags with a large components count. An attacker could create a specially-crafted image file that, when opened by a victim, could cause ImageMagick to access invalid memory and crash.

CVE-2012-0260

A denial of service flaw was found in the way ImageMagick decoded certain JPEG images. A remote attacker could provide a JPEG image with specially-crafted sequences of RST0 up to RST7 restart markers (used to indicate the input stream to be corrupted), which once processed by ImageMagick, would cause it to consume excessive amounts of memory and CPU time.

CVE-2012-1798

An out-of-bounds buffer read flaw was found in the way ImageMagick processed certain TIFF image files. A remote attacker could provide a TIFF image with a specially-crafted Exif IFD value (the set of tags for recording Exif-specific attribute information), which once opened by ImageMagick, would cause it to crash.

Bug Fixes

BZ#743222

Previously, the restorecon utility did not change MLS (multi-level security) levels unless the -F parameter was used. As a consequence, the /dev and /dev/pts filesystems were not correctly labelled after boot in systems with configured MLS policy. This bug has been fixed and the restorecon -F command is now used for /dev and /dev/pts by default.

BZ#734987

When an explicit configuration option, such as crashkernel=128M, was specified to reserve crash dump memory, the kexec-disable upstart job unconditionally freed up the memory if the kdump mechanism was not enabled. This action could not be reverted until a reboot. With this update, kexec-disable job has been changed to not free reserved memory, unless the crashkernel parameter is set to auto, thus fixing this bug.

BZ#675079

Previously, when the /etc/modprobe.d/bonding.conf file or the modprobe.conf file was used to set the bonding options, the bond0 interface never came up after a service restart because the arp_ip_target module was not restored. This bug has been fixed and arp_ip_target is now restored when configured in one of these files.

BZ#698520

Previously, there was a bug in the rc.sysinit script that allowed to properly set a hostname when more than one IP address was passed to the ipcalc utility. Even though it was difficult to emulate such a scenario, the rc.sysinit script has been fixed to prevent this bug, and ipcalc is now always passed only a single IP address.

BZ#700184

When a network interface was configured with the NetworkManager utility to statically assign an IP address or a prefix, then NetworkManager was stopped, and the interface was reset via the ifdown and ifup utilities, the interface lost its IP address. With this update, the network scripts have been fixed to properly read the IPADDR0 parameter in interface configuration files, and now IP addresses of such interfaces are preserved in the described scenario.

BZ#703475

Previously, when two VLAN interfaces were bonded together, the /etc/init.d/network script got into a loop and became unresponsive, trying to resolve MAC addresses of the interfaces. As a result, the server was prevented from completing its start-up sequence. With this update, /etc/init.d/network has been fixed, MAC addresses of VLAN interfaces are now resolved properly, and bonds between such interfaces now work as expected.

BZ#705367

Previously, when the PREFIX option was specified for the ifcfg utility while the NETMASK option was undefined, the netmask was calculated without regard to the PREFIX value. With this update, the expand_config() function has been fixed to use the PREFIX properly, and the netmask is now calculated correctly in the described scenario.

BZ#702814

When a system needed to be restarted after an unexpected termination, root password was not accepted to run the emergency shell. With this update, the rc.sysinit script has been fixed to run the /bin/plymouth command instead of /usr/bin/plymouth, thus fixing this bug. Additionally, other relevant scripts have been updated to properly work with the separated /usr/ directory.

BZ#703210

Due to a bug in the /etc/init.d/halt script, no mount point set up with the word nfs in its path could be unmounted at reboot or shut down. This bug has been fixed and such mount points are now unmounted properly.

BZ#681357

In Red Hat Entreprise Linux 6, when the emergency parameter was appended to the kernel command line, the system failed to invoke the sulogin command. With this update, the rcS-emergency task, which is run before the rc.sysinit script if emergency is passed to the kernel, has been added, and sulogin is now properly invoked in the described scenario.

BZ#729359

Due to a bug in the /etc/sysconfig/network-scripts/ifdown-eth script, the PID file name passed to the dhclient utility during a shutdown procedure did not include the IP version prefix. Consequently, leases for IPv6 addresses could not be released. This bug has been fixed and the shut down procedure now works properly both with the IPv4 and IPv6 clients.

Enhancements

BZ#692240

Previously, the ifup and ifdown scripts explicitly ignored IPv6 configuration files that contained an alias. With this update, clients properly utilize aliases on IPv6 devices in Red Hat Enterprise Linux.

BZ#653630, BZ#672202

There was a need to have a simple mechanism for troubleshooting network problems, integrated into existing log monitoring facilities. With this update, network scripts have been updated to report errors via the syslog utility, and the error messages now appear in configured syslog channels.

BZ#680527

Previously, configuration options for the sysctl utility could only be changed in the /etc/sysctl.conf file. With this update, several scripts have been updated to also recognize additional configuration files located in the /etc/sysctl.d/ directory.

BZ#692410

With this update, network start-up scripts have been enhanced to support all ethtool command options. These options can be set via the ETHTOOL_OPTS parameter in configuration files located in the /etc/sysconfig/network-scripts/ directory and take effect after reboot.

BZ#696788

With this update, start-up network scripts have been enhanced to set up static ARP (Address Resolution Protocol) entries located in the /etc/ethers file, allowing to load these entries early in the system startup.

BZ#789056

The previous version of initscripts did not support IPv6 routing in the same way as IPv4 routing. IPv6 addressing and routing could be achieved only by specifying the "ip" commands explicitly with the "-6" flag in the "/etc/sysconfig/network-scripts/rule-DEVICE_NAME" configuration file (where "DEVICE_NAME" is a name of the respective network interface). With this update, related network scripts have been modified to provide support for IPv6-based policy routing. IPv6 routing is now configured separately in the the "/etc/sysconfig/network-scripts/rule6-DEVICE_NAME" configuration file.

Security Fix

CVE-2011-3636

A Cross-Site Request Forgery (CSRF) flaw was found in Red Hat Identity Management. If a remote attacker could trick a user, who was logged into the management web interface, into visiting a specially-crafted URL, the attacker could perform Red Hat Identity Management configuration changes with the privileges of the logged in user.

Due to the changes required to fix CVE-2011-3636, client tools will need to be updated for client systems to communicate with updated Red Hat Identity Management servers. New client systems will need to have the updated ipa-client package installed to be enrolled. Already enrolled client systems will need to have the updated certmonger package installed to be able to renew their system certificate. Note that system certificates are valid for two years by default.

Updated ipa-client and certmonger packages for Red Hat Enterprise Linux 6 were released as part of Red Hat Enterprise Linux 6.2. Future updates will provide updated packages for Red Hat Enterprise Linux 5.

Bug Fixes

BZ#705800

When installation of Identity Management clients failed, the debugging information shown in the /var/log/ipaclient-install.log file did not provide enough information to determine the cause of the failure. With this update, the /var/log/ipaclient-install.log file contains improved debugging messages that make it easier to debug a possible installation failure.

BZ#705794

The Identity Management services were not started after a reboot when the server was installed with the ipa-replica-install command. With this update, after an installation of a replica with ipa-replica-install, the ipa service is enabled using the chkconfig utility so that the Identity Management services are started and available after a reboot.

BZ#704012

Prior to this update, installing an Identity Management replica in a new IP subnet with an Identity Management-controlled DNS server failed. With this update, such operation no longer fails, although, the bind service needs to be restarted when a new reverse zone is added over LDAP.

BZ#703869

Previously, Identity Management replication installations were missing configuration for managed entries. As a consequence, user-private groups and netgroups were not created for host groups if they were created on the replica. This update adds the missing configuration, and user and host group creation work as expected.

BZ#723662

Prior to this update, GSSAPI credential delegation was disabled in the curl utility due to a security issue. As a result, applications that rely on delegation did not work properly. This update utilizes a new constructor argument in the xmlrpc-c client API to set the new CURLOPT_GSSAPI_DELEGATION curl option. This option enables the credential delegation, thus fixing this bug.

BZ#698421

An Identity Management replica would occasionally fail to install while trying to initialize replication with the remote Identity Management server. With this update, the memberOf attribute is rebuilt during installation, thus fixing this issue. Note that the 389 Directory Server (389-ds) may crash if it is restarted while this task is running. Wait for this task to complete before requesting a restart.

BZ#743253

For NIS compatibility reasons, when a host group is created, a net group with the same name is created as well. However, when a host group is created, it was not checked whether there was a net group with the same name already existent. As a consequence, the host group was created, but the net group could not be created and the user was not notified of this. With this update, when a new host group is created, the Identity Management server checks whether a net group with the specified name exists already. If there is such a group, the operation is denied.

BZ#743936

Prior to this update, the Identity Management web user interface loaded the entire Identity Management API name space when it was being started. As a result, JSON requests returned large amount of data, which caused certain browsers to report the script stack space quota is exhausted message and prevent a user from accessing the Web UI. This update split the Web UI initialization to several smaller calls. Browsers no longer report errors and the Web UI works as expected.

BZ#719656

Running the ipa-nis-manage command disabled the NIS listener and also removed the netgroup compatibility suffix. If NIS was disabled, the automatic creation of net groups was disabled as well. Thus, creating a host group would fail to automatically create a net group. With this update, disabling NIS has no effect on the automatic creation of net groups when host groups are created.

BZ#725433

Adding an indirect automount map to a mount point that already exists returned an error, but created the map anyway. As a result, the map could not be removed with Identity Management tools. With this update, the addition of an indirect map requires the creation of a key to store the mount point. If the addition of a map fails because the key already exists, the map is removed.

BZ#744264

Prior to this update, the Web UI Password Policy interface was missing some of the password policy fields that are present in the command line version (specifically, Max failures, Failure reset interval, Lockout duration, and Priority). As a result, users could not set these parameters via the Web UI and had to use the CLI version. This update adds all the missing Password Policy fields to the Web UI.

BZ#696193

When an Identity Management server A was using a KDC on Identity Management server B, and server B does down, on server A it looked as if server B was still operational. This caused clients to fail to enroll. With this update, the underlying source code has been modified to address this issue, and client enrollment works as expected.

BZ#742327

Permission objects related to DNS were improperly formatted and added before the relevant DNS privileges (that they were members of) were added to LDAP. DNS related permissions contain just limited information. Additionally, the privilege objects, which they were members of, lacked memberof LDAP attributes pointing back to the permissions. Thus, a user could get an incorrect list of permissions that were members of a DNS related privilege. With this update, permission objects formatting has been fixed and the missing memberof LDAP attributes in the relevant DNS privileges are properly added. Users now get a valid list of permissions (containing all the needed information) when displaying a DNS related privilege.

BZ#691531

A certificate not signed by the Identity Management Certificate Authority (CA) imported into Identity Management could not be managed by Identity Management. Performing any operations on a service or a host that would cause Identity Management to attempt to revoke a certificate would fail (for example, disabling or deleting a host or service). With this update, certificates issued by other CAs cannot be imported into an Identity Management host or a service record. Disabling and deleting hosts and services works as expected and correctly revokes certificates.

BZ#741808

An LDAP object migrated using the migrate-ds command could contain a multi-valued RDN attribute. However, the migrate-ds process picked only the first value of the RDN attribute and did not respect the value that was present in the DN in the migrated LDAP object. With this update, the value that is used in the original LDAP object DN is used, rather than the first value of a multi-valued RDN. As a result, LDAP objects with a multi-valued RDN attribute are migrated without any errors.

BZ#741677

When the ipa-client-install was run with the --password option containing a bulk password for client enrollment, the password could be printed to Identity Management client install log in a plain-text format. This behavior has been fixed, and passwords are no longer logged in the install log file.

BZ#726943

By default, the Identity Management Web UI adds a redirect from the web root to /ipa/ui. This makes it look like no other web resources may be used. With this update, during the installation process, the --no-ui-redirect option can be used to disable the default Rewrite rule. This may also be commented out manually in the /etc/httpd/conf.d/ipa-rewrite.conf. As a result, the web server root can point to any specified place. However, /ipa must remain available to Identity Management.

BZ#745957

The Identity Management Web UI did not take into account when a non-admin user was a member of an administrative role, which has more privileges than just performing self-service actions. With this update, non-admin users with an administrative role are shown the full administrative tabset as expected.

BZ#746056

Identity Management Web UI did not allow addition of an external user (that is, user that is not managed by Identity Management) as a RunAs user for a Sudo rule. An external RunAs user could be added to a Sudo rule via the command line only. With this update, adding an external user as a RunAs user is possible in the Web UI.

BZ#726123

The automountkey-del command includes a --continue option which has no function and does not affect anything. With this update, the --continue has been hidden, and will be deprecated in the next major release.

BZ#723622

Prior to this update, the ipa-getkeytab command failed with Bind errors. If 32-bit packages were used on a 64-bit system, the 32-bit cyrus-sasl-gssapi package was required. This update adds architecture-specific Requires to the RPM spec file, and retrieving of keytabs no longer fails.

BZ#707009

Installing an Identity Management server signed by an external CA fails with the following error:

cannot concatenate 'str' and 'NoneType' objects

This was because the required information was not being passed so the installation failed when constructing the Kerberos principal name for the Dogtag 389-ds instance. This information is now provided by the installer, thus fixing this issue.

BZ#727282

In the Identity Management Web GUI, attempting to view a certificate of a host returned the unknown command u'show' error message. Users could only use the command-line to view host certificates. The certificate buttons including Get, View, Revoke, and Restore for hosts and services have been fixed to use the correct entity name, and viewing of certificates in the Web UI works as expected.

BZ#726526

The number of ports that needed to be open between Identity Management replicas was too high. Managing such a number of ports required planning because new rules were needed for each replication agreement. With this update, Dogtag is now proxied via the existing Apache web server on ports 80 and 443, which already need to be open. Ports 944[3-6] no longer need to be open in the firewall.

BZ#727921

It is possible to add a host group as a member of a net group; however, that relationship did not appear when viewing a host group. With this update, net group membership is displayed when viewing a host group.

BZ#726715

When importing automaster maps, the auto.direct mount mounted on /- was ignored because it was considered a duplicate. Consequently, direct maps needed to be added manually. This update adds an exception for the auto.direct map when importing so that its keys can be added, and importing direct maps works as expected.

BZ#728118

The output of adding or showing a sudo rule with a runAsGroup included a reference to a ipasudorunasgroup_group attribute, making the output unclear. A proper label was added for runAsGroup and the sudo option, which makes the output more understandable.

BZ#728614

Using the ipa-replica-install did not ensure that the dbus service was running. Consequently, tracking certificates with certmonger returned an error and the installation failed. With this update, prior to starting certmonger, it is checked whether the dbus-daemon is running.

BZ#733436

The Identity Management server installer and ipactl use two different methods to determine whether Identity Management is configured. If the Identity Management uninstallation was not complete, ipactl may have claimed that the Identity Management server is not configured while the Identity Management server installer refused to continue because Identity Management was configured. With this update, a common function that checks whether the Identity Management server is configured has been added. During the uninstallation process of the Identity Management server, checks are run that report left-over files so that users can manually resolve these.

BZ#714238

Prior to this update, the error message returned when setting an integer value that was too large on 64-bit systems was confusing. This update limits the integer values to 2147483647 on all platforms, making error messages consistent on 32 and 64-bit systems.

BZ#729245

Adding an option to a sudo rule with the sudurole-add-option command did not display a summary after the option was added. With this update, a summary is printed in the form of Added option 'x' to Sudo Rule 'y'.

BZ#730436

Under rare circumstances, certain operations may have caused the 389 Directory Server (389-ds) to crash or not function properly. This was because NSPR (Netscape Portable Runtime) read/write locks used by 389-ds were not re-entrant. These locks were replaced with POSIX thread read-write locks in the Identity Management 389-ds plugins, and the aforementioned crashes no longer occur.

BZ#729246

Removing an option from a sudo rule with the sudurole-remove-option command did not display a summary after the option was removed. With this update, a summary is printed in the form of Removed option 'x' to Sudo Rule 'y'.

BZ#729377

Installing an Identity Management server using the --no-host-dns option without a DNS resolvable host name caused the installation to fail with DNS errors. This update moves the no-host-dns test so that it is tested before any DNS lookups occur, and installations with the --no-host-dns option do not perform any DNS validation.

BZ#732468

When Identity Management client A/PTR DNS records did not match, the ipa-getkeytab and ipa-join commands did not operate properly, and the client could not be enrolled to the Identity Management server. As a result, client installations failed every time. With this update, matching client A/PTR DNS records are no longer a requirement for ipa-getkeytab and ipa-join, and client installations succeed even when the aforementioned records do not match.

BZ#730713

Selecting a check box for users, groups, hosts, or host groups when deleting a list of objects in an HBAC rule in the Identity Management Web UI left the check box checked even when the operation was complete and the entry was re-edited. With this update, the selection is cleared when the page is refreshed.

BZ#730751

When editing an HBAC rule in the Identity Management Web UI, the delete button was enabled even when no selection was made. This update disables the delete button when nothing is selected.

BZ#729089

Removing an external host value by checking the update dns check box rendered the action successful even though the host was not removed. With this update, the host is removed successfully in the aforementioned scenario.

BZ#728950

If an 389-ds certificate expired, the Identity Management services did not start .This update adds new options for 389-ds which allow to control how 389-ds reacts to an expired certificate. The default setting is to warn the user and start the services.

BZ#729665

Checking/unchecking the Hide already enrolled check box when adding/removing members from a group had no effect. This update removes this check box.

BZ#726725

Passing an empty map name to the automountmap or automountkey command returned the following error:

Map: 
ipa: ERROR: 'automountmapautomountmapname' is required

This was because Identity Management tries to hide the LDAP implementation and often provides a different value for options and errors than is actually used. It may also use contrived internal names for uniqueness. With this update, Identity Management returns the correct values depending on the context so that a more useful error message is returned. As a result, in the aforementioned scenario, the correct value, automountmap, is now returned.

BZ#714600

The default SSSD configuration did not store passwords if offline. Consequently, when a machine was disconnected from the network, SSSD was unable to authenticate any users. With this update, the krb5_store_password_if_offline parameter is set to True in the /etc/sssd/sssd.conf by default. Note that the --no-krb5-offline-passwords option of the ipa-client-install command may be used if storing passwords for offline use is not desired.

BZ#726722

Passing an empty location to the automountmap or automountkey command returned the following error:

Location: 
ipa: ERROR: 'automountlocationcn' is required

This was because Identity Management tries to hide the LDAP implementation and often provides a different value for options and errors than is actually used. It may also use contrived internal names for uniqueness. With this update, Identity Management returns the correct values depending on the context so that a more useful error message is returned. As a result, in the aforementioned scenario, the correct value, automountlocation, is now returned.

BZ#714919

Prior to this update, the ipa-client-install command did not configure a hostname in the /etc/sysconfig/network file. Consequently, when the --hostname value was passed to the client installer, that value was used during enrollment. However, the system hostname did not match the name of the machine. With this update, the /etc/sysconfig/network file is updated upon installation and /bin/hostname is executed with the hostname of the machine. The name used in the enrollment process now matches the hostname of the machine.

BZ#715112

Renaming users (via ipa user-mod --setattr) may have returned a Not Found error. Renaming the actual users was successful, but their user-private groups were not updated. With this update, the 389-ds plugin has been modified so that the ipa_modrdn plugin runs last. This plugin manages renaming of the Kerberos principal name of the user. Renaming a user now also renames the user-private group.

BZ#736684

If an Identity Management client was installed and there was a too large of a time difference between the client and the Identity Management server, a KDC running on the Identity Management server may have refused any Kerberos authentication request from the client. Consequently, the installation process could fail as it could not get a valid Kerberos ticket. With this update, time is always synchronized with the NTP servers configured for the client domain or the Identity Management server itself. If the time synchronization succeeds, the time on the client machine is fixed and Kerberos authentication and the installation itself successfully continue.

BZ#737048

The ipa-client-install command always ran /usr/sbin/authconfig to add the pam_krb5.so entry to PAM configuration files in the /etc/pam.d/ directory. However, this entry was not needed when an Identity Management client is installed with SSSD support, which is the default behavior. As a result, an unnecessary record was added to the PAM configuration. With this update, /usr/sbin/authconfig is not run if the Identity Management client is configured with SSSD support.

BZ#717724

The certificate subject base was editable post-install which caused the change to not be propagated to the CA. With this update, the certificate subject base is read-only and the value cannot be modified post installation.

BZ#737581

Prior to this update, a new host could be added to an Identity Management server without proper validation. For example, a host with an invalid hostname or a hostname containing a whitespace character could be created. With this update, proper validation of hostnames for any host has been added, and only hosts with valid hostnames can now be added to an Identity Management server.

BZ#717965

The Identity Management configuration stored a value for Password Expiration Notification but did not display it by default (when using the ipa config-show command). This update adds Password Expiration Notification to the default list of attributes to shown by default when running the ipa config-show command.

BZ#745698

Identity Management installation tools accepted invalid IP addresses in their --forwarder or --ip-address options. Consequently, installation could eventually fail, for example because of an invalid name server configuration. With this update, all IP addresses passed to the ipa-server-install, ipa-replica-install and ipa-dns-install commands are checked for validity.

BZ#739040

When the ipa-client-install command detected that the client hostname was not resolvable, it tried to add a DNS record to the Identity Management server. However, it did not expect that the client could have been using an IPv6 machine, and the installation process failed. This update adds a check to make sure that the process for adding a DNS record to the Identity Management server works for both IPv4 and IPv6, and the Identity Management client installation works as expected.

BZ#739640

When a new service was added via the Add New Service Web UI dialog box, the Web UI did not check if the service name field was filled in. When the dialog box was confirmed with the service name field empty, a new service named undefined was created. With this update, the service name field is required to be filled in.

BZ#693496

Prior to this update, the ipa-nis-manage tool crashed with a python exception when attempting to use an LDAPI connection only. With this update, ipa-nis-manage correctly falls back to GSSAPI or a password-based authentication if the LDAPI connection fails.

BZ#723233

An attempt to create a rule with an invalid type returned an error which informed users that only allow and deny are accepted as types:

ipa: ERROR: invalid 'type': must be one of (u'allow', u'deny')

However, rules of the type deny are not allowed. With this update, the deny type was deprecated because SSSD determined that properly enforcing the deny type was extremely difficult and dependent on how other libraries present host information.

BZ#743680

The ipa-server-install command did not update the system hostname when it was installed with a custom hostname. It passed the hostname to services using their own configurations. However, some services failed to function properly as they did not expect an Identity Management server to use a custom hostname and not a system hostname. With this update, the system hostname is updated to the value passed via ipa-server-install's --hostname option. The system hostname is also set in the system network configuration in /etc/sysconfig/network so that it is properly set after a system reboot. Refer to Section 2.8, “Authentication” for a known limitation regarding Identity Management server installations with custom hostnames.

BZ#707001

When installing an Identity Management server and using an external CA to sign it, the specified command line options were not properly validated. In such a case, the resulting CSR contained only the string null. This update adds better detection of whether the CA 389-ds instance has been installed to identify the current stage of the installation, thus fixing this issue.

BZ#723778

When deleting an automount location, the command appeared to be successful, but there was no feedback provided on the output. With this update, a summary of all automount commands is shown.

BZ#723781

When adding an automount location, the command appeared to be successful, but there was no feedback provided on the output. With this update, a summary of all automount commands is shown.

BZ#707133

Prior to this update, the ipa-nis-manage command did not return an exit status of 0 when successful. With this update, the underlying source code has been modified to address this issue, and correct exit codes are returned.

BZ#737997

When a new user was added, its login was normalized and lower-cased. However, its principal was not normalized and contained the original login. Consequently, if a new user with an uppercase letter in its login was added, a disconnect between a user login and its principal was created. The Identity Management server then refused to create a password for that user. This update normalizes both the new user long and its principal, thus fixing this issue.

BZ#737994

Certain Identity Management commands require a file to be passed. For example, a cert-request command requires a CSR file. If the command contains a validation rule for the required file, it needs to be executed before it can be processed. However, if the file was passed in the CLI command interactively (and not as a command option), the validation rule was applied to the file path and not the file contents. As a result, a validation rule could fail and the command then returned an error until the file was passed as a command option. With this update, a validation rule is applied to file contents only, and users can pass the required file on the command line both interactively and via a command option.

BZ#726454

Previously, there was no indicator in a host entry that a one-time password was set. This update adds a new output attribute for host entries, has_password, that is set when the host has a password set. If has_password is True, a password has been set on the host. However, there is no way to see what that password is once it has been set.

BZ#716287

When a host is enrolled, the user that does the enrollment is stored in the attribute enrolledBy on the host. Prior to this update, an administrator was able to change this value by using the ipa host-mod --setattr. This action should not be allowed. This update fixes this behavior and write permissions have been removed from the enrolledBy attribute.

BZ#714924

When configuring an Identity Management client to use SSSD, if an error occurred while looking up users, the following error message was displayed:

nss_ldap is not able to use DNS discovery

This update modifies this error message to be more specific.

BZ#736617

The ipa-client-install command did not configure /usr/sbin/ntpdate to use correct NTP servers in the /etc/ntp/step-tickers. Additionally, the ipa-client-install did not store the state of the ntpd service before installation. Consequently, when an Identity Management client is installed, ntpdate may have used incorrect servers to synchronize with. When the Identity Management client was uninstalled, the ntpd may have been set to an incorrect state. With this update ipa-client-install configures ntpdate to use the IPA NTP server for synchronization. When an IPA client is uninstalled, both ntpdate configuration and ntpd status are restored.

BZ#714597

The IPA-generated /etc/krb5.conf file contained values which were not present in the standard configuration file (specifically: ticket_lifetime, renew_lifetime, and forwardable in the [libdefaults] section, and the entire [appdefaults] section). This update removes these unnecessary values and sections.

BZ#680504

DNS forward and reverse entries are stored discretely. Removing one does not remove the other unless specifically requested. Previously, it was unclear how to remove the required entries. This update adds a new interactive mode (via ipa dnsrecord-del) to the command line application which guides the user through the process of removing the required entries.

BZ#725763

Summary data displayed when adding an automount key has been modified to include the map and the key.

BZ#717625

Updating values in the configuration tab in the Identity Management Web UI returned an error. This was because the Web UI was searching for a primary key configuration. With this update, it no longer searches for the key, and the configuration tab works as expected.

BZ#717020

When activating or deactivating a user in the Identity Management Web UI, the user is updated without having to click the Update button. With this update, a message box is displayed indicating that the change is going into effect immediately.

BZ#716432

If 389-ds debugging was enabled, superfluous content appeared in the ipactl output. With this update, the amount of information displayed in the ipactl output has been reduced. The previously reported data is not available in the 389-ds error log only.

BZ#714799

The ipa-client-install did not successfully run on a client when a one-time password was set on a host in the Identity Management Web UI. Consequently, clients could not be enrolled using a one-time password if it was set in the Web UI. With this update, the krbLastPwdChange value is no longer set in the host entry when setting a host one-time password, thus fixing this issue.

BZ#713798

Prior to this update, DNS lookups were not being forwarded if they originated in a subnet that was not managed by Identity Management. With this update, the Identity Management DNS is configured to allow recursion by default, thus fixing this issue.

BZ#713481

When removing a runAsGroup value from a sudo rule, the command appeared to be successful, but the group information data included in the output was not updated and did not show the proper membership. This update fixes this bug, and data is refreshed before being returned.

BZ#713380

When removing a runasuser (via ipa sudorule-remove-runasuser) and, consequently, defining a group, the RunAs Group value was not included in the output. This was because the label for the returned data was mislabeled and was not appearing in the output. With this update, the underlying source code has been modified to address this issue, and adding a group to runasuser is properly displayed.

BZ#713069

Comma-separated values were not handled properly when the --externaluser option was specified for the sudorule-mod command. As a result, erroneous values were stored in the entry. With this update, the --externaluser option was removed from the sudorule-mod command. It is advisable to use the sudorule-add-user command instead.

BZ#731804

Upgrading Identity Management from version 2.0.0-23 caused the 389-ds configuration to be modified to not accept requests. With this update, the upgrade process is more robust and always restores the 389-ds configuration. As a result, upgrading Identity Management no longer leaves the system in an inconsistent state.

BZ#731805

Different error types could cause various error messages to appear in the Identity Management Web UI. This update makes all error messages in the Web UI consistent.

BZ#732084

Disabling SELinux (SELINUX=disabled in /etc/selinux/config) and attempting to restart the ipa service caused the ipa service to fail to start. This update ignores the value returned by restorecon, and the ipa service now starts as expected whether SELinux is enabled or disabled.

BZ#712889

A request to set a certificate revocation reason to 7 would cause the request to fail and the certificate was not revoked. Reason 7 is not a valid revocation reason according to RFC 5280. With this update, an error message is returned to the user, informing of the fact that, when used, reason 7 is not a valid revocation reason.

BZ#726028

Previously, renaming an automount key did not work properly because DN of the key was being updated but not the value within the entry. Renaming an automount key now updates the DN and the stored key value, thus fixing this issue.

BZ#711786

When setting runAsGroup in a sudo role as a user, the name of that user is returned as the name of a group that may also be used as the runAsGroup. As a result, the sudo rule was erroneous and referred to a non-existent group. This was because the search filter for determining the CN value was too generic. This update adds a test which assures user names no longer appear as runAsGroup values.

BZ#711761

Prior to this update, removing a sudo rule option failed on the server because the code which handled sudo rule option removal was not robust enough and if the input did not exactly match the stored value, it failed. With this update, removing sudo rule options works as expected.

BZ#711671, BZ#711667

Previously, comma-separated values were not handled properly when using sudorule-mod's --runasexternaluser or --runasexternalgroup options. With this update, the aforementioned options have been deprecated. It is advisable to use the sudorule-add-runasuser or sudorule-runasgroup commands instead.

BZ#710601, BZ#710598, BZ#710592

Prior to this update, leading and trailing spaces were allowed in some parameter values. This update adds a validator that disallows the use of leading and trailing spaces.

BZ#710530

Passing an empty password when prompted to by the ipa-nis-manage command did not display an error and did not exit the command. With this update, passing an empty password causes an error to appear (No password supplied), and the command is exited with the status code 1.

BZ#710494

The ipa-nis-manage command has an option, -y, to specify the Directory Manager password in a file. This option caused the command to crash if the file did not exist. An exception handler around the password reader has been added, and a proper error message is displayed when the supplied password file is non-existent or is not readable.

BZ#710253

When adding a runasuser (via ipa sudorule-add-runasuser) and, consequently, defining a group, the RunAs Group value was not included in the output. This was because the label for the returned data was mislabeled and was not appearing in the output. With this update, the underlying source code has been modified to address this issue, and adding a group to runasuser is properly displayed.

BZ#738693

A user with a valid Kerberos ticket can change an IPA password with the ipa passwd command. Prior to this update, the command did not require entering the old password. Consequently, anyone with access to that user's shell could change his Identity Management password without knowing the old password. With this update, the old password is always required in order to change a user's password. The only exception is the administrator user.

BZ#710245

A removed sudorule option appeared in the output when that option was removed. With this update, option values are refreshed before being returned, and the output of the delete command is consistent with the actual data.

BZ#710240

Adding a duplicate sudorule option did not generate any errors messages. With this update, rather than ignoring duplicate values, an error is returned when a duplicate sudorule option is added.

BZ#739195

When attempting to unprovision a host keytab in the Identity Management Web UI Unprovisioning Host dialog, there was no option to cancel the process. This update adds the Cancel button to the Unprovisioning Host dialog.

BZ#709665, BZ#709645

When removing external hosts from a sudorule, the output shown after the command completed contained the hosts that were removed. With this update, external host information is refreshed before it is returned to the client.

BZ#707312

Previously, new DNS zones were not available until the bind service was restarted. With this update, an updated bind-dyndb-ldap package added a zone refresh option that Identity Management uses to refresh the zone list in DNS. The default setting is 30 seconds. As a result, new DNS zones are not immediately available, but the bind service does not have to be restarted anymore.

BZ#740320

When a new group was being created via the Identity Management Web UI, unchecking the Posix check box was not taken into account and a posix group was created every time. With this update, the underlying source code has been modified to address this issue, and creating non-posix groups works as expected.

BZ#707229

The --no-host-dns option of the ipa-server-install command still checked that the forward and reverse DNS entries existed and matched. Installation of an Identity Management server using a host name that could not be resolved would then fail. This update removes any DNS validation when the --no-host-dns option is used.

BZ#705804

The subject name of a CA agent certificate used by Identity Management was not very specific. This update changes the subject name from RA Subsystem to IPA RA.

BZ#702685

If a remote LDAP server that was being used while migrating to Identity Management contained an LDAP search reference, the migration failed. With this update, the migration process logs any search references and skips them, assuring a successful migration.

BZ#740885

For an HBAC rule, you can choose to add a host in the Accessing section of the Identity Management Web UI. Clicking on Enroll without selecting a host did not return an error indicating that a host was not selected. With this update, the Enroll button is disabled until a host is chosen.

BZ#740891

For an HBAC rule, you can choose to delete a host in the Accessing section of the Identity Management Web UI. Clicking on Enroll without selecting a host did not return an error indicating that a host was not selected. With this update, the Enroll button is disabled until a host is chosen.

BZ#741050

The ipa-client-install command always checked the specified server whether it was a valid Identity Management server. However, if the Identity Management server was configured to restrict access for anonymous binds (via the nsslapd-allow-anonymous-access option), the check failed and the installation processes returned an error and ended. With this update, when the ipa-client-install command detects that the chosen server does not allow anonymous binds, it skips server verification, reports a warning, and lets the user join the Identity Management server.

BZ#701325

The X509v3 certificate shown in a host or service record in the Identity Management Web UI was not properly formatted. This update converts the certificate from the base64 format to the PEM format.

BZ#698219

The Apache service communicates with 389-ds early on during the start-up (to attempt to retrieve the LDAP schema). Previously, if that communication failed, the Apache service would have to be restarted. This race condition could cause a restarted Identity Management server become unavailable. With this update, the communication between Apache and 389-ds is retried when it fails, thus fixing this issue.

BZ#697878

The Identity Management server installation could fail with an error informing of the fact that the LDAP server could not be reached. This was because the installation process did not wait for the 389-ds server to fully start after a restart. With this update, the installation process waits for the 389-ds server to be fully started.

BZ#742875

When an Identity Management server was installed, it did not properly check the system's static lookup table (/etc/hosts) for records which could interfere with its IP address or hostname, and cause forward or reverse DNS queries to be resolved to different values than expected. The installation process now always checks for any conflicting records in the /etc/hosts file.

BZ#696282

A certificate subject base with an incorrect format provided by the user could cause an installation process to fail in the CA step with a non-descriptive error. With this update, the subject base of a certificate is validated, and the installation no longer fails.

BZ#696268

Providing an IP address during the Identity Management server installation via the --ip-address option caused the installed server to not function properly. With this update, it is verified whether the provided IP address is a configured interface on the system. Providing an IP address that is not associated with a local network interface will return an error message.

BZ#743788

The IPA Web UI was missing a title on several pages. This update adds the missing titles.

BZ#693771

Including non-ASCII characters in the zonemgr email address could cause an installation to fail with an unclear message. This update adds a validator which requires the zonemgr to contain ASCII characters only.

BZ#681978

Uninstalling an Identity Management client on a machine which has the Identity Management server installed on it as well caused the server to break. The client uninstaller now detects the installation state of an installed server. An attempt to uninstall a client from a machine which also contains the server will result in an error message. The client can be uninstalled when the server is uninstalled.

BZ#744024

Prior to this update, the ipa-client-install command did not return an exit status of 0 when successful. With this update, the underlying source code has been modified to address this issue, and correct exit codes are returned.

BZ#744074

Prior to this update, the Identity Management Web UI allowed a user to delete a global Password Policy. If a global Password Policy is deleted, any attempt to add a user with a Kerberos password fails. Additionally, neither the CLI nor the Web UI version of Identity Management could be used to add this policy back. With this update, deleting the global Password Policy is denied.

BZ#692955

Attempting to set the manager value of a user resulted in the following error message:

value #0 invalid per syntax: Invalid syntax.

This was because the value required a full LDAP DN syntax. With this update, when storing or retrieving the manager value, the value is automatically translated between a login name and a DN. Setting the manager value now requires a login name only.

BZ#744422

During the installation of a Identity Management server, the ipa-server-install called kdb5_ldap_util to populate the directory with realm information. In the process of doing so, it passes the Kerberos master database password and the Kerberos directory password as parameters. As a result, a user could list all running processes during the IPA server installation and discover the aforementioned passwords. With this update, kdb5_ldap_util's interactive mode is used to pass the passwords instead of passing them via CLI parameters.

BZ#692950

When setting up DNS during an interactive installation, a reverse zone was always created regardless of the --no-reverse option. This update fixes this behavior, and a reverse zone is not created unless specified.

BZ#745392

When the ipa-client-install command attempted to auto-discover the Identity Management server in its domain, it did not use any timeout when a server was found and was being checked. If the found server was unresponsive during the auto-discovery, the ipa-client-install command got stuck and did not continue. This update adds a 30 second timeout to the ipa-client-install auto-discovery server check.

BZ#692144

Using the --no-sssd option of the ipa-client-install command did not properly back up and restore the existing /etc/sssd/sssd.conf file. With this update, the underlying source code has been modified to address this issue, and the --no-sssd option works as expected.

BZ#690473

Using the --hostname option to set a value outside an Identity Management-managed DNS domain did not return an error and did not add the host to DNS. The DNS updating utility, nsupdate, was modified to properly return an error when an update fails.

BZ#690185

Uninstalling an Identity Management client did not restore certain files when that client was previously installed with the --force option. This was because the --force option was able to re-install over an already installed system, causing the original saved files to be lost. This behavior is no longer permitted; the client must be first uninstalled and only then it can be re-installed.

BZ#689810

Adding a duplicate user resulted in a generic error message which was not specific enough to discover the reason of the error. With this update, the object type and the primary key are returned in the error message, making the error message more understandable.

BZ#689023

When adding a new password policy, the Identity Management Web UI did not prompt for a required field, priority. This update requires the priority field to be filled in.

BZ#688925

The process of setting up an Identity Management replica became unresponsive if the master could not be reached. This update adds a new utility, ipa-replica-conncheck, which verifies that the replica and the master can communicate in both directions.

BZ#688266

If the domain did not match the realm, enrolling a client could fail with the following error:

Cannot resolve network address for KDC

This was because a temporary /etc/krb5.conf file was used during enrollment to contact the Identity Management KDC. The process was always relying on DNS auto-discovery to find the correct KDC and not the values provided by the end-user. With this update, enrollment works even if the domain does not match the realm.

BZ#683641

If a one-time password was set on a host, an administrator was unable to enroll it and the following error message would be returned:

No permission to join this host to the IPA domain.

A delegated administrator did not have permissions to write the Kerberos principal name. This update adds permissions for the delegated administrator to be able to add a one-time password, but not change or remove an existing one.

BZ#681979

The --on-master lacked proper documentation. This update makes the option invisible and removes it from documentation entirely.

BZ#747443

Realm-Domain mapping was not specified in a client's Kerberos configuration when the client was outside of an Identity Management domain. In such a case, Certmonger would fail to issue a host certificate. Realm-Domain mapping is now properly configured when the client is outside of the Identity Management domain.

BZ#748754

Arguments for the Kerberos KDC, contained in the /etc/sysconfig/krb5kdc file, were not formatted properly on multi-CPU systems. As a consequence, the KDC could not use the intended number of CPUs and reported an error when it was (re)started. With this update, the aforementioned arguments are now properly formatted, fixing this issue.

BZ#749352

Prior to this update, the ypcat command's netgroup output did not show users in netgroup triples. Consequently, NIS-based authorization did not work as expected, and access was denied when it should have been allowed. This was caused by a syntax error in the triple rule. This update fixes this error, and users are now properly included in the netgroup triples.

BZ#736170

The ipa package has been upgraded to upstream version 2.1.3 which provides a number of bug fixes and enhancements over the previous version.