6.1 Technical Notes

Technical Release Documentation

Link to Original Document

Legal Notice

Copyright © 2011 Red Hat Inc.
The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version.
Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
All other trademarks are the property of their respective owners.


1801 Varsity Drive
 RaleighNC 27606-2072 USA
 Phone: +1 919 754 3700
 Phone: 888 733 4281
 Fax: +1 919 754 3701

Abstract
The Red Hat Enterprise Linux 6.1 Technical Notes list and document the changes made to the Red Hat Enterprise Linux 6 operating system and its accompanying applications between Red Hat Enterprise Linux 6.0 and minor release Red Hat Enterprise Linux 6.1.

1. Package Updates
1.1. abrt
1.2. acroread
1.3. anaconda
1.4. apr
1.5. apr-util
1.6. at
1.7. audit
1.8. augeas and virt-v2v
1.9. authconfig
1.10. autofs
1.11. avahi
1.12. bash
1.13. bfa-firmware
1.14. bind
1.15. bind-dyndb-ldap
1.16. binutils
1.17. blktrace
1.18. btrfs-progs
1.19. busybox
1.20. bzip2
1.21. certmonger
1.22. cifs-utils
1.23. cluster and gfs2-utils
1.24. compat-dapl
1.25. coolkey
1.26. coreutils
1.27. corosync
1.28. cracklib
1.29. crash
1.30. crda
1.31. cronie
1.32. cryptsetup-luks
1.33. cups
1.34. curl
1.35. cvs
1.36. dapl
1.37. dbus
1.38. device-mapper-multipath
1.39. dhcp
1.40. dovecot
1.41. dracut
1.42. e2fsprogs
1.43. ebtables
1.44. eclipse
1.45. edac-utils
1.46. efibootmgr
1.47. elfutils
1.48. emacs
1.49. epydoc
1.50. evince
1.51. evolution
1.52. evolution-data-server
1.53. evolution-mapi
1.54. fakechroot
1.55. fcoe-utils
1.56. febootstrap
1.57. fence-agents
1.58. fence-virt
1.59. file
1.60. fipscheck
1.61. firefox
1.62. firstaidkit
1.63. firstboot
1.64. freeradius
1.65. freetype
1.66. gcc
1.67. gdb
1.68. gdm
1.69. ghostscript
1.70. git
1.71. glib2
1.72. glibc
1.73. gnome-panel
1.74. gnome-power-manager
1.75. gnome-terminal
1.76. gpxe
1.77. grub
1.78. gtk2
1.79. gvfs
1.80. hal
1.81. hivex
1.82. hplip
1.83. httpd
1.84. hwdata
1.85. ibus
1.86. ibus-chewing
1.87. ibus-hangul
1.88. ibus-m17n
1.89. ibutils
1.90. im-chooser
1.91. imsettings
1.92. initscripts
1.93. iok
1.94. ipmitool
1.95. iproute
1.96. iprutils
1.97. iptables
1.98. iputils
1.99. irqbalance
1.100. iscsi-initiator-utils
1.101. iwl6000-firmware
1.102. iwl6050-firmware
1.103. java-1.6.0-openjdk
1.104. jss
1.105. kabi-whitelists
1.106. kdelibs
1.107. kdenetwork
1.108. kernel
1.109. kexec-tools
1.110. krb5
1.111. krb5-appl
1.112. ksh
1.113. ldapjdk
1.114. libcacard and spice-client
1.115. libcap-ng
1.116. libcgroup
1.117. libcmpiutil
1.118. libcxgb3
1.119. libdfp
1.120. libgcrypt
1.121. libgssglue
1.122. libguestfs
1.123. libguestfs-winsupport
1.124. libhbalinux
1.125. libica
1.126. libnl
1.127. libpciaccess
1.128. libselinux
1.129. libtdb
1.130. libtiff
1.131. libtirpc
1.132. libuser
1.133. libvirt
1.134. libvirt-cim
1.135. libvirt-java
1.136. libvirt-qpid
1.137. libvpd
1.138. libvpx
1.139. lldpad
1.140. logrotate
1.141. logwatch
1.142. lohit-devanagari-fonts
1.143. lohit-kannada-fonts
1.144. lohit-oriya-fonts
1.145. lohit-tamil-fonts
1.146. lsvpd
1.147. luci
1.148. lvm2
1.149. m17n-contrib
1.150. mailman
1.151. man-pages
1.152. man-pages-ja
1.153. man-pages-overrides
1.154. mcelog
1.155. mdadm
1.156. memtest86+
1.157. mesa
1.158. microcode_ctl
1.159. mipv6-daemon
1.160. mksh
1.161. mod_auth_mysql
1.162. mod_nss
1.163. mysql
1.164. net-snmp
1.165. net-tools
1.166. netcf
1.167. netlabel_tools
1.168. NetworkManager
1.169. NetworkManager-openswan
1.170. nfs-utils
1.171. nfs-utils-lib
1.172. nspr, nss, nss-softokn, and nss-util
1.173. nss
1.174. nss-pam-ldapd
1.175. oddjob
1.176. openais
1.177. opencryptoki
1.178. openldap
1.179. openmpi
1.180. openoffice.org
1.181. openscap
1.182. openssh
1.183. openssl
1.184. openswan
1.185. openwsman
1.186. oprofile
1.187. pacemaker
1.188. PackageKit
1.189. pam
1.190. pam_krb5
1.191. pam_ldap
1.192. pam_pkcs11
1.193. pango
1.194. papi
1.195. paps
1.196. parted
1.197. perl
1.198. perl-Mozilla-LDAP
1.199. perl-Sys-Virt
1.200. php
1.201. php-pecl-memcache
1.202. pidgin
1.203. pixman
1.204. plymouth
1.205. policycoreutils
1.206. polkit
1.207. poppler
1.208. postfix
1.209. postgresql
1.210. powerpc-utils
1.211. powertop
1.212. prelink
1.213. procps
1.214. psmisc
1.215. pykickstart
1.216. python
1.217. python-ethtool
1.218. python-gudev
1.219. python-meh
1.220. python-nss
1.221. python-pycurl
1.222. python-qpid
1.223. python-urlgrabber
1.224. python-virtinst
1.225. qemu-kvm
1.226. ql2400-firmware
1.227. ql2500-firmware
1.228. qpid-cpp
1.229. qpid-tests
1.230. qpid-tools
1.231. qt
1.232. quagga
1.233. quota
1.234. rdesktop
1.235. rds-tools
1.236. redhat-lsb
1.237. redhat-release
1.238. redhat-rpm-config
1.239. Release Notes
1.240. report
1.241. resource-agents
1.242. rgmanager
1.243. rhn-client-tools and yum-rhn-plugin
1.244. rhnlib
1.245. ricci
1.246. rpm
1.247. rsync
1.248. rsyslog
1.249. ruby
1.250. s390utils
1.251. samba
1.252. saslwrapper
1.253. screen
1.254. scsi-target-utils
1.255. seabios
1.256. selinux-policy
1.257. setup
1.258. shadow-utils
1.259. smartmontools
1.260. sos
1.261. spice-client
1.262. spice-server
1.263. spice-xpi
1.264. squashfs-tools
1.265. squid
1.266. srptools
1.267. sssd
1.268. strace
1.269. subversion
1.270. sudo
1.271. syslinux
1.272. sysstat
1.273. system-config-firewall
1.274. system-config-kickstart
1.275. system-config-users
1.276. systemtap
1.277. sysvinit-tools
1.278. tcsh
1.279. thunderbird
1.280. tigervnc
1.281. tomcat6
1.282. tuned
1.283. tzdata
1.284. udev
1.285. upstart
1.286. util-linux-ng
1.287. valgrind
1.288. vgabios
1.289. vim
1.290. virt-manager
1.291. virt-top
1.292. virt-viewer
1.293. virtio-win
1.294. volume_key
1.295. vsftpd
1.296. vte
1.297. watchdog
1.298. webkitgtk
1.299. wireshark
1.300. xguest
1.301. xinetd
1.302. xorg-x11-drv-intel
1.303. xorg-x11-drv-mga
1.304. xorg-x11-drv-nouveau
1.305. xorg-x11-drv-qxl
1.306. xorg-x11-drv-wacom and wacomcpl
1.307. xorg-x11-drv-xgi and xorg-x11-drivers
1.308. xorg-x11-server
1.309. xorg-x11-server-utils
1.310. yaboot
1.311. yum
1.312. yum-metadata-parser
1.313. yum-rhn-plugin and rhn-client-tools
1.314. yum-utils
2. New Packages
2.1. RHEA-2011:0533: 389-ds-base
2.2. RHEA-2011:0664: PyPAM
2.3. RHEA-2011:0644: biosdevname
2.4. RHEA-2011:0589: compat-openldap
2.5. RHEA-2011:0562: ding-libs
2.6. RHEA-2011:0635: foghorn
2.7. RHEA-2011:0579: hwloc
2.8. RHEA-2011:0658: icedtea-web
2.9. RHEA-2011:0631: ipa
2.10. RHEA-2011:0624: ipa-pki-theme
2.11. RHEA-2011:0811: iwl100-firmware
2.12. RHEA-2011:0552: iwl6000g2a-firmware
2.13. RHEA-2011:0553: iwl6000g2b-firmware
2.14. RHEA-2011:0660: kdewebdev
2.15. RHEA-2011:0431: kmod-hpwdt
2.16. RHEA-2011:0449: kmod-snd-hda
2.17. RHEA-2011:0777: libcxgb4
2.18. RHEA-2011:0656: libnes
2.19. RHEA-2011:0669: matahari
2.20. RHEA-2011:0629: mod_revocator
2.21. RHEA-2011:0625: netxen-firmware
2.22. RHEA-2011:0572: nuxwdog
2.23. RHEA-2011:0528: omping
2.24. RHEA-2011:0626: osutil
2.25. RHEA-2011:0623: perl-Class-MethodMaker
2.26. RHEA-2011:0709: perl-IO-Tty
2.27. RHEA-2011:0723: perl-IPC-Run
2.28. RHEA-2011:0617: perl-Parse-RecDescent
2.29. RHEA-2011:0640: perl-Term-ProgressBar
2.30. RHEA-2011:0605: perl-TermReadKey
2.31. RHEA-2011:0627: pki-core
2.32. RHEA-2011:0612: python-kerberos
2.33. RHEA-2011:0613: python-krbV
2.34. RHEA-2011:0622: python-netaddr
2.35. RHEA-2011:0630: python-pyasn1
2.36. RHEA-2011:0608: python-rhsm
2.37. RHEA-2011:0805: qpid-qmf
2.38. RHEA-2011:0654: ras-utils
2.39. RHEA-2011:0691: ruby-shadow
2.40. RHEA-2011:0671: scons
2.41. RHEA-2011:0670: sigar
2.42. RHEA-2011:0575: slapi-nis
2.43. RHEA-2011:0585: spice-protocol
2.44. RHEA-2011:0576: spice-vdagent
2.45. RHEA-2011:0611: subscription-manager
2.46. RHEA-2011:0532: svrcore
2.47. RHEA-2011:0727: system-switch-java
2.48. RHEA-2011:0657: tomcatjss
2.49. RHEA-2011:0604: virt-what
3. Technology Previews
4. Known Issues
4.1. Installer
4.2. Deployment
4.3. Virtualization
4.4. Storage and Filesystems
4.5. Networking
4.6. Clustering
4.7. Authentication
4.8. Devices
4.9. Kernel
4.10. Desktop
A. Revision History
The Red Hat Enterprise Linux 6.1 Technical Notes list and document the changes made to the Red Hat Enterprise Linux 6 operating system and its accompanying applications between Red Hat Enterprise Linux 6.0 and minor release Red Hat Enterprise Linux 6.1.
For system administrators and others planning Red Hat Enterprise Linux 6.1 upgrades and deployments, the Technical Notes provide a single, organized record of the bugs fixed in, features added to, and Technology Previews included with this new release of Red Hat Enterprise Linux.
For auditors and compliance officers, the Red Hat Enterprise Linux 6.1 Technical Notes provide a single, organized source for change tracking and compliance testing.
For every user, the Red Hat Enterprise Linux 6.1 Technical Notes provide details of what has changed in this new release.

Note

Previous versions of the Technical Notes contained a Package Manifest appendix. The Package Manifest is now available as a seperate document.

1. Package Updates

1.1. abrt

1.1.1. RHBA-2011:0619: bug fix update

Updated abrt packages that resolve several issues are now available.
The abrt package provides the Automatic Bug Reporting Tool.
These updated abrt packages provide fixes for the following bugs:
  • Prior to this update, the ABRT GUI did not warn the user when it could not connect to the Gnome keyring daemon (that is, could not save any of the user's settings). With this update, a warning message is displayed in such a case. (BZ#576866)
  • The previous version of ABRT did not properly restore the core_pattern parameter (which is used to specify a coredump file pattern name) if it was too long. This update restores the core_pattern parameter to its previous value when the abrt daemon is stopped. (BZ#614486)
  • If the TAINT_HARDWARE_UNSUPPORTED flag, which detecs hardware not officially supported by Red Hat, is set (in the /proc/sys/kernel/taint file), ABRT indicates that the flag is set in the created crash report. (BZ#623142)
  • The abrt-addon-ccpp plugin crashed due to a segmentation fault if the /proc/[PID]/ directory did not exist. With this update, ABRT no longer crashes in case the /proc/[PID]/ directory does not exist. (BZ#649309)
  • The abrt package has been upgraded to upstream version 1.1.16, which provides a number of bug fixes and enhancements over the previous version. (BZ#650975)
  • Content from various files in the /var/log/ directory is now included in the creation of an sosreport (which is created via the abrt-plugin-sosreport plugin). (BZ#665405)
  • Prior to this update, the "Help" button in the ABRT GUI displayed the "About" window. With this update, a proper help page is displayed. (BZ#666267)
  • Occasionally, ABRT did not send an attached core dump file along with a crash report. This was due to the large size of the core dump file which was consequently rejected by the server which was receiving the crash report. With this update, attachments and their sizes are listed in the crash report, making it easier to detect any problems caused by the large size of the attachments. (BZ#668875)
  • Previously, ABRT was using "Strata-Message:" headers in server responses. However, servers no longer use these headers. With this update, the aforementioned headers are no longer used by ABRT. (BZ#670492)
  • By default, in Red Hat Enterprise Linux 6, ABRT did not enable any reporters, causing environments which do not run an X server to not be notified of any crashes ABRT detected. With this update, the mailx plugin is enabled as the default reporter for every crash and the root user is now notified of any crashes via the root@localhost mailbox. (BZ#678724)
  • The duplicate hash of a crash was computed from the package NVR (Name, Version, Release), path of the executable and the backtrace hash. This caused the hash to be different for the same bug which occurred in two versions of the same package. With this update, the component name and the backtrace hash are used when computing the duplicate hash. (BZ#694410)
All users of abrt are advised to upgrade to these updated packages, which resolve these issues.

1.2. acroread

1.2.1. RHBA-2011:0813: bug fix update

Updated acroread packages that resolve an issue are now available.
Adobe Reader allows users to view and print documents in Portable Document Format (PDF).
These updated acroread packages fix the following bug:
  • With a recent update, the OpenLDAP libraries have been moved to different directory. This update changes the way Adobe Reader links to these libraries. (BZ#680202)
All users of acroread are advised to upgrade to these updated packages, which resolve this issue.

1.3. anaconda

1.3.1. RHBA-2011:0530: bug fix and enhancement update

An updated anaconda package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6.1.
The anaconda package contains portions of the Anaconda installation program that can be run by the user for reconfiguration and advanced installation options.
This updated anaconda package provides fixes for the following bugs:
  • Auto-partitioning no longer clears immutable partitions. (BZ#593642)
  • Anaconda no longer creates a new EFI system partition when one is not needed. (BZ#593984)
  • Anaconda now properly detects ext2's dirty/clean states. (BZ#601862, BZ#614812)
  • Anaconda no longer forgets IP method selection in the loader when returning to a previous menu. (BZ#609570)
  • The "Proxy password" field in stage 2 now correctly displays asterisks instead of plain text. (BZ#611825)
  • Text mode now allows IPv6 configuration. (BZ#612476)
  • Anaconda no longer displays free regions of less than 1MB in extended partitions. (BZ#626025)
  • Anaconda no longer loses focus on certain screens. (BZ#671017)
  • ".treeinfo" files are now properly fetched over a proxy. (BZ#634655)
  • Anaconda now writes correct NFS (Network File System) repository information into the summary Kickstart file. (BZ#635201)
  • The /boot/ directory can now reside on an ext4 partition. (BZ#638734)
  • Anaconda no longer fails to detect a disk if its size exceeds 1TB. (BZ#654360)
  • Anaconda is once again able to detect the file system on a previously-created RAID device. (BZ#678028)
  • Anaconda now generates the correct, FIPS-enabled initramfs (initial RAM file system) when the kernel option "fips=1" is provided on the kernel command line. (BZ#692350)
  • Anaconda incorrectly failed with a traceback when an attempt to unpack a driver disk to a pre-existing root partition did not succeed. (BZ#640260)
  • Fingerprint authentication has been disabled on IBM System z because it is not supported on that platform. (BZ#676854)
  • Static IPv4 configuration is now used when requested in stage 2: Anaconda no longer falls back to using DHCP. (BZ#641324)
  • Anaconda is now able to properly detect an md RAID array with a spare disk. (BZ#652874)
  • Anaconda now correctly reports an error when a network-based certificate is specified in Kickstart with no networking setup. (BZ#636533)
  • A custom value is now properly honored when shrinking a file system. (BZ#621490)
  • The "list-harddrives" command output for CCISS devices is now valid input for Kickstart files. (BZ#702430)
  • Anaconda now selects the new kernel after upgrade. (BZ#683891)
In addition, this updated package provides the following enhancements:
  • This update adds the cnic, bnx2i, and be2net drivers for better iSCSI support. (BZ#442980, BZ#529443)
  • This update adds drivers for the Emulex 10GbE PCI-E Gen2 and Chelsio T4 10GbE network adapters. (BZ#633307, 633319)
  • Algorithms from the SHA-2 hash function family can now be used to encrypt the boot loader password. (BZ#554874)
  • Anaconda now allows a username and password to be entered for iSCSI Discovery sessions. (BZ#607827)
  • The "rdate", "which", "tty" and "ntpdate" commands have been added to the install image. (BZ#354432, 614399)
  • The graphical installer now runs using the full display resolution. (BZ#663411)
  • Anaconda now features improved SSL certificate-handling. (BZ#667122, BZ#599042, BZ#678574)
  • It is now possible to specify additional packages when using the "@packages --default" Kickstart option. (BZ#621349)
  • On IBM System z, the /boot/ directory can now be placed on an LVM logical volume. (BZ#618376)
  • Anaconda now supports blacklisting to determine which modules can be loaded during installation. (BZ#644535)
Users are advised to upgrade to this updated anaconda package, which resolves these issues and adds these enhancements.

1.4. apr

1.4.1. RHSA-2011:0507: Moderate security update

The Apache Portable Runtime (APR) is a portability library used by the Apache HTTP Server and other projects. It provides a free library of C data structures and routines.
Updated apr packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
It was discovered that the apr_fnmatch() function used an unconstrained recursion when processing patterns with the '*' wildcard. An attacker could use this flaw to cause an application using this function, which also accepted untrusted input as a pattern for matching (such as an httpd server using the mod_autoindex module), to exhaust all stack memory or use an excessive amount of CPU time when performing matching. (CVE-2011-0419)
Red Hat would like to thank Maksymilian Arciemowicz for reporting this issue.
All apr users should upgrade to these updated packages, which contain a backported patch to correct this issue. Applications using the apr library, such as httpd, must be restarted for this update to take effect.

1.5. apr-util

1.5.1. RHSA-2010:0950: Moderate security update

Updated apr-util packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The Apache Portable Runtime (APR) is a portability library used by the Apache HTTP Server and other projects. apr-util is a library which provides additional utility interfaces for APR; including support for XML parsing, LDAP, database interfaces, URI parsing, and more.
It was found that certain input could cause the apr-util library to allocate more memory than intended in the apr_brigade_split_line() function. An attacker able to provide input in small chunks to an application using the apr-util library (such as httpd) could possibly use this flaw to trigger high memory consumption. (CVE-2010-1623)
All apr-util users should upgrade to these updated packages, which contain a backported patch to correct this issue. Applications using the apr-util library, such as httpd, must be restarted for this update to take effect.

1.6. at

1.6.1. RHBA-2011:0016: bug fix update

An updated at package that fixes bugs is now available for Red Hat Enterprise Linux 6.
At and batch read commands from standard input or from a specified file. At allows you to specify that a command will be run at a particular time. Batch will execute commands when the system load levels drop to a particular level. Both commands use /bin/sh.
This update fixes the following bugs:
  • Previously, the at daemon (atd) wrongly contained permissions 0755 for atd configuration. With this update, atd has the correct permissions 0644 as have all other such files. (BZ#589099)
  • Previously, the initscript caused the "OK" message to be printed twice. With this update, the initscript behaves as expected and no longer echoes duplicate messages. (BZ#615104)
  • Previously, the PIE label was not compiled with -fpie/-fPIE. This update adds a PIE compile option to specify secure Position-Independent Executables. (BZ#630019)
All users of at are advised to upgrade to this updated package, which resolves this issue.

1.7. audit

1.7.1. RHBA-2011:0653: bug fix and enhancement update

Updated audit packages that fix bugs and provide enhancements are now available for Red Hat Enterprise Linux 6.
The audit packages contain the user space utilities for storing and searching the audit records which have been generated by the audit subsystem in the Linux 2.6 kernel.
This update fixes the following bugs:
  • System processes — that is processes with an audit id (auid) of -1 — are logged by the audit subsystem. However, if the ausearch utility was used to locate events where the auid was -1, it would display all events. In this update, under these circumstances, ausearch only returns events with an auid of -1. (BZ#670938)
  • A value of 'syslog' for the 'disk_error_action' parameter in 'auditd.conf' instructs auditd to issue a warning to syslog if an error is encountered when writing audit events to disk. If 'disk_error_action' was set to 'syslog', auditd always attempted to exec() a child process. Consequently, if a disk error was encountered (ie. a disk full error), auditd would attempt to exec() a null child process, and logging would not resume after the disk error was reported to syslog. In this update the child process is not called when the 'syslog' option is used, and logging continues as expected. (BZ#688664)
  • Previously if an audispd plug-in was restarted, the plug-in was not marked as active. Consequently, the remote logging plug-in (audisp-remote) was unable to bind to a privileged port on reconnect because all privileges had been dropped. In these updated packages, audispd plug-ins are marked as active after being restarted, and the audisp-remote plug-in functions as expected. (BZ#695605)
  • Previously, the "autrace -r" command on the IBM System z architecture attempted to audit network syscalls not available on IBM System z. Consequently, an error similar to the following might have been returned:
    Error inserting audit rule for pid=13163
    With this update, "autrace -r" is now aware of system calls not available on this architecture, which resolves this issue. (BZ#697463)
  • When an ignore directive was included in an audit.rules configuration file, the auditctl utility became unresponsive when attempting to load those rules. With this update, the issue is resolved. (BZ#640948)
  • Previously, the audit_encode_nv_string() function was not checking if the memory allocation (malloc) it was performing succeeded. Consequently, if the malloc operation encountered an out of memory (OOM) error, audit_encode_nv_string() crashed attempting to reference a NULL pointer. With this update, audit_encode_nv_string() checks if the malloc is successful, which resolves this issue. (BZ#647128)
  • Previously, the man page for the "audit_encode_nv_string" function incorrectly documented the return value type as an "int". The man page for "audit_encode_nv_string" now correctly displays return value type for the "audit_encode_nv_string" function as a "char *" (BZ#647131)
Additionally, the audit packages are updated (rebased) to the upstream version 2.1-1. (BZ#584981) This rebase provides the following bugfixes and enhancements:
  • autrace now uses the correct syscalls on i386 systems
  • Added support for new event types related to virtualization, netfilter, the mmap syscall, key based authentication, and cryptographic session establishment.
  • Updated syscall tables for the 2.6.37 kernel.
  • Updated sample rules for new syscalls and packages.
  • The overflow_action configuration item was added to audisp-remote to allow configurable actions for remote logging queue overflows.
  • A new option in the audisp-syslog plug-in to send syslog audit events to local[0-7]
All audit users are advised to upgrade to these updated packages, which resolve these issues and add these enhancements.

1.8. augeas and virt-v2v

1.8.1. RHBA-2011:0650: bug fix update

Updated virt-v2v and augeas packages that fix multiple bugs are now available for Red Hat Enterprise Linux 6.
virt-v2v is a tool for converting virtual machines to use the KVM hypervisor. It modifies both the virtual machine image and its associated libvirt metadata. virt-v2v will also configure a guest to use VirtIO drivers if possible.
augeas is a library for programmatically editing configuration files. augeas parses configuration files as a tree structure, which it exposes through its public API.
Bug fixes:
BZ#609483
Red Hat Enterprise Linux guest conversion did not update /etc/sysconfig/kernel, which would lead to an incorrect kernel being set as the default in future updates. This would cause boot failure. /etc/sysconfig/kernel now updates correctly.
BZ#616720
Partially written guest images were not cleaned up if a conversion to a libvirt target failed or was interrupted. With this update, all created volumes are removed if a conversion is not successful.
BZ#618965
virt-v2v would not always update software in the transfer volume when updates were available because it relied on timestamps. The transfer volume is now updated whenever virt-v2v is used.
BZ#623571
virt-v2v could not detect VMware Tools to uninstall it if VMware Tools was installed via tarball. When VMware Tools detected that it was no longer running on a VMware platform and attempted to disable itself on the guest, it overwrote changes made by virt-v2v during conversion. This resulted in broken networking and initrd images containing unnecessary drivers. virt-v2v can now detect and uninstall VMware Tools even when VMware Tools is installed via tarball.
BZ#623579
If a Linux guest had an invalid default entry in the grub.conf file, virt-v2v assumed it was an i686 guest. This resulted in a converted guest that did not boot. virt-v2v now assumes an AMD64 or Intel 64 default architecture instead of i686.
BZ#642258
virt-v2v could not convert a Red Hat Enterprise Linux guest that did not have the /etc/securetty file. Conversion without this file is now possible.
BZ#643867
Conversion failed if conversion required updating the kernel and the guest had additional kernel modules installed. Conversion now succeeds and virt-v2v no longer attempts to uninstall old kernels.
BZ#644295
When performing an offline installation of the VirtIO block driver in a Windows guest, virt-v2v incorrectly assumed that ControlSet001 was always the current control set, even if ControlSet001 had been marked as failed. The correct control set is now detected, and the VirtIO block driver installed in the correct location.
BZ#656883
When creating a libvirt guest using block storage, virt-v2v incorrectly set the disk type to auto. This made libvirt unable to start the guest. Disk type is now set explicitly based on source metadata or other detection methods.
BZ#581421
In certain circumstances, virt-v2v exited with a return value of 0, even though conversion failed. The correct values are now returned.
BZ#609448
Red Hat Enterprise Linux guest conversion did not update /boot/grub/device.map with converted block device names in certain circumstances. device.map now updates as expected.
BZ#670778
virt-v2v failed to convert a guest to a Red Hat Enterprise Virtualization target if the current working directory was not universally readable. Universal readability is no longer required.
BZ#672521
virt-v2v failed to convert Windows guests that had a C:\Temp directory because it created a C:\temp directory without checking for file names that used alternative cases. virt-v2v now checks for case-sensitive file names before creating an appropriate temporary directory.
BZ#671300
virt-v2v failed to enable VirtIO support when converting a Xen guest that had both a paravirtualized Xen kernel and a fully virtualized kernel installed. The fully virtualized kernel is now made the default kernel and conversion succeeds as expected.
BZ#676323
It was not possible to create a Red Hat Enterprise Virtualization template from a guest that was converted by virt-v2v. Guests imported with this updated package can now be used to create templates.
BZ#679017
When converting a 64-bit Windows XP guest to run on Red Hat Enterprise Virtualization, virt-v2v incorrectly identified the guest as 64-bit Windows 2003. 64-bit Windows XP guests are now correctly identified as Windows XP when imported into Red Hat Enterprise Virtualization.
BZ#690286
augeas was not thread safe, and could leak file descriptors when multiple programs attempted to use the libvirt library simultaneously. This resulted in the failure of the calling program. augeas has been modified to remove the global variable that caused this threading issue.
BZ#620449
Sparse storage was not retained across conversion. Storage type is now retained across conversion, but can be modified with the -oa flag.
BZ#654531
virt-v2v used enum integers to populate the ovf:disk-interface field when converting for Red Hat Enterprise Virtualization. However, this produced an ovf file that was not intelligible to Red Hat Enterprise Virtualization Manager. The disk-interface is now populated with correct enum values (IDE, SCSI, or VirtIO), allowing Red Hat Enterprise Virtualization Manager to understand the ovf file.
BZ#664942
When converting a guest to run on Red Hat Enterprise Virtualization, virt-v2v identified created storage as sparse or raw. This combination is not supported when importing into a data center that uses block storage (fibre channel or iSCSI). virt-v2v can now convert storage format and allocation policy correctly. Additionally, customers can specify a format and allocation policy compatible with the target data center type by using the -of and -oa command line options.
BZ#671083
virt-v2v conversion would hang if its output was redirected at the command line. This bug was reported and corrected during development. It was not seen in production systems in the field.
BZ#678950
Conversion of a Red Hat Enterprise Linux Desktop virtual machine failed with the following error:
Can't locate object method "can_handle" via package
"Sys::VirtV2V::Converter::RedHat" at
/usr/share/perl5/vendor_perl/Sys/VirtV2V/Converter.pm line 121.
This issue has been resolved and conversion should now complete successfully
Enhancements:
BZ#581108
virt-v2v can now convert guests which use the qcow2 disk format.
BZ#615977
virt-v2v can now convert Microsoft Windows guests to run on a libvirt or Red Hat Enterprise Virtualization target without requiring the Guest Tools ISO.
BZ#671353
virt-v2v includes support for Windows XP guests with the latest version of virtio-win. New installations of Red Hat Enterprise Linux 6.1 will have this support automatically. Users upgrading from an earlier version of virt-v2v may need to manually alter /etc/virt-v2v.conf. If you see the following error message when attempting to convert a Windows XP guest:
virt-v2v: No app in config matches os='windows' name='virtio' major='5'
minor='1' arch='i386'
the following section must be added to /etc/virt-v2v.conf:
<app os='windows' major='5' minor='1' arch='i386' name='virtio'>
    <path>/usr/share/virtio-win/drivers/i386/WinXP</path>
  </app>
  <app os='windows' major='5' minor='1' arch='x86_64' name='virtio'>
    <path>/usr/share/virtio-win/drivers/amd64/WinXP</path>
</app>
BZ#676553
virt-v2v now enables the conversion of Windows guests which do not have available VirtIO drivers, although these guests are not guaranteed to operate correctly after conversion.
BZ#615182
virt-v2v requires root privileges to convert a guest to run on Red Hat Enterprise Virtualization. When run without these privileges, virt-v2v output an error to this effect but did not fail immediately. This resulted in a number of other error messages being printed, which obscured the primary error. virt-v2v now fails immediately after it outputs the primary privilege error.
BZ#672498
virt-v2v now relies on libvirt to detect volume metadata such as size and format. Guests with volumes that are not contained in a storage pool will therefore fail to be converted. The error message that results from such a failure has been updated to provide detailed information on how to create a storage pool to contain the target volume.
All users of virt-v2v and augeas are advised to upgrade to these updated packages, which correct these issues and add these enhancements.

1.9. authconfig

1.9.1. RHBA-2011:0595: bug fix and enhancement update

Updated authconfig packages that fix several bugs and add an enhancement are now available.
The authconfig package contains a command line utility and a GUI application that can configure a workstation to be a client for certain network user information and authentication schemes and other user information and authentication related options.
These updated authconfig packages provide fixes for the following bugs:
  • Prior to this update, authconfig unnecessarily restarted the user information and authentication services even though there were no configuration changes that would require the restart. With this update, services are no longer restarted unless explicitly required. (BZ#595261)
  • The authentication configuration utility did not keep the "Require smart card for login" check box set when Kerberos was also enabled. When the check box was checked and the configuration was saved with the "Apply" button, the system would correctly require smart card for login. However, on the subsequent run of the authentication configuration utility the check box would be unchecked again and it was necessary to check it again to keep the option switched on. With this update, the "Require smart card for login" stays checked even after subsequent runs of the authentication configuration utility. (BZ#620475)
  • The authentication configuration tool GUI incorrectly duplicated its window when the "Revert" button was pressed. This update fixes the duplicity problem. (BZ#621632)
  • In some cases, when multiple configuration files with the same configuration settings contained different configuration values for a setting, the configuration files contents were not properly synchronized with authconfig. With this update, the synchronization works as expected. (BZ#624159)
  • The authentication configuration tool GUI allowed to choose user identity and authentication schemes which require packages that are not installed on the system by default. With this update, certain identity and authentication schemes cannot be configured when they are not installed on the system. (BZ#639747)
  • The authconfig textual user interface incorrectly required the nss-pam-ldap package to be installed when the configuration used SSSD for LDAP user identification. With this update, the nss-pam-ldap package is not required in such a case. (BZ#663882)
  • Prior to this update, the authentication configuration tool overwrote the cache_credentials value to "True" in the SSSD configuration file (/etc/sssd/sssd.conf) if the configuration allowed using SSSD for the network user information and authentication services. With this update, the "cache_credentials" parameter is no longer overwritten in the aforementioned case. (BZ#674844)
  • The "system-config-authentication" command crashed when executed in an environment without the X server running. With this update, a proper error message is printed in the aforementioned case. (BZ#676333)
In addition, these updated authconfig packages provide the following enhancement:
  • The authconfig package has been upgraded to upstream version 6.1.12, which provides a number of bug fixes and enhancements over the previous version. This version also adds new options: "--enableforcelegacy" and "--disableforcelegacy". These options allow the user to use legacy LDAP and Kerberos user identity and authentication modules instead of the SSSD modules. (BZ#655910)
Users are advised to upgrade to these updated authconfig packages, which resolve these issues and add this enhancement.

1.10. autofs

1.10.1. RHBA-2011:0403: bug fix update

An updated autofs package that fixes one bug is now available for Red Hat Enterprise Linux 6.
The autofs utility controls the operation of the automount daemon. The automount daemon automatically mounts file systems when you use them, and unmounts them when they are not busy.
This update fixes the following bug:
  • Prior to this update, an attempt to restart the autofs service while a mounted file system was in use caused the service to stop responding upon its startup. This was due to inappropriate locking during the recursive reconstruction of mount trees of pre-existing mounted multi-mount map entries. With this update, the underlying source code has been adapted to avoid the deadlock during the mount tree reconstruction, so that autofs now starts as expected. Additionally, this update prevents autofs from occasionally terminating with a segmentation fault upon a map entry lookup. (BZ#689754)
All users of autofs are advised to upgrade to this updated package, which fixes this bug.

1.10.2. RHBA-2011:0753: bug fix update

An updated autofs package that fixes numerous bugs is now available for Red Hat Enterprise Linux 6.
The autofs utility controls the operation of the automount daemon. The automount daemon automatically mounts file systems when you use them, and unmounts them when they are not busy.
Bug fixes:
BZ#629480
When using client certificates with autofs, the certificate DN could not be used in LDAP ACLs. This prevented autofs from authenticating via SASL external. With this update, the SASL EXTERNAL authentication mechanism is used for mapping the certificate DN to an LDAP DN, allowing autofs to support SASL External authentication via TLS.
BZ#616426
The autfs initscript did not implement the functions force-reload and try-restart. Instead, the error try-restart and force-reload service action not supported was given and returned 3. This patch adds these initscript options so that the they are now implement and return appropriate values.
BZ#629359
Debugging output from autofs did not include IP addresses for mounts alongside hostname information which made it difficult to debug issues when using round-robin DNS. This update adds this feature, allowing logging output to show the IP address of a mount, rather than just the host name.
BZ#572608
Previously, automount woke up once per second to check for any scheduled tasks, despite the fact that adding a task triggered a wake up of that thread, which lead to a tight loop which used excessive CPU. This update removes these unnecessary wakeups.
BZ#520844
When an autofs map entry had multiple host names associated with it, there was no way to override the effect of the network proximity. This was a problem when a need existed to be able to rely on selection strictly by weight. With this patch, the server response time is also taken into consideration when selecting a server for the target of the mount. The pseudo option --use-weight-only was added that can only be used with master map entries or with individual map entries in order to provide this. For individual map entries, the option no-use-weight-only can also be used to override the master map option.
BZ#666340
If there were characters that matched isspace() (such as \t and \n) in a passed map entry key and there was no space in the key, these character were not properly preserved, which led to failed or incorrect mounts. This was caused by an incorrect attempt at optimization by using a check to see if a space was present in the passed key and only then processing each character of the key individually, escaping any isspace() characters. This patch adds a check for isspace() characters to the same check for a space, eliminating the problem.
BZ#630954
If the map type was explicitly specified for a map, then the map was not properly updated when a re-read was requested. This was because the map stale flag was incorrectly cleared after the lookup module read the map, instead of at the completion of the update procedure. In this patch, the map stale flag should only be cleared if the map read fails for some reason, otherwise it updates when the refresh is completed.
BZ#650009
Previously, when autofs was restarted with active mounts, due to a possible recursion when mounting multi-mount map entries, autofs would block indefinitely. This was caused by a cache readlock which was held when calling mount_subtree() from parse_mount () in parse_sun.c. This patch fixes remount locking which resolves the issue.
BZ#577099
The master map DN string parsing is quite strict and, previously, autofs could not use an automount LDAP DN using the l (localityName) attribute. This patch adds the allowable attribute 'l', the locality.
BZ#700691
A previous bug fix caused the state queue manager thread to stop processing events, and mounts expired and then stopped. This was caused when the state queue task manager transferred an automount point pending task to its task queue for execution. The state queue was then mistakenly being seen as empty when the completing task was the only task in the state queue. This patch adds a check to allow the queue manager thread to continue, resolving the issue.
BZ#700697
The autofs gave a segmentation fault on the next null cache look up in the auto.master file. This was due to a regression issue, where a function to clean the null map entry cache, added to avoid a race when re-reading the master map, mistakenly failed to clear the hash bracket array entries. This patch sets the hash bracket array entries to NULL, resolving the issue.
All users of autofs are advised to upgrade to these updated packages, which provide numerous bug fixes.

1.11. avahi

1.11.1. RHSA-2011:0779: Moderate security and bug fix update

Updated avahi packages that fix one security issue and one bug are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
Avahi is an implementation of the DNS Service Discovery and Multicast DNS specifications for Zero Configuration Networking. It facilitates service discovery on a local network. Avahi and Avahi-aware applications allow you to plug your computer into a network and, with no configuration, view other people to chat with, view printers to print to, and find shared files on other computers.
A flaw was found in the way the Avahi daemon (avahi-daemon) processed Multicast DNS (mDNS) packets with an empty payload. An attacker on the local network could use this flaw to cause avahi-daemon on a target system to enter an infinite loop via an empty mDNS UDP packet. (CVE-2011-1002)
This update also fixes the following bug:
  • Previously, the avahi packages in Red Hat Enterprise Linux 6 were not compiled with standard RPM CFLAGS; therefore, the Stack Protector and Fortify Source protections were not enabled, and the debuginfo packages did not contain the information required for debugging. This update corrects this issue by using proper CFLAGS when compiling the packages. (BZ#629954, BZ#684276)
All users are advised to upgrade to these updated packages, which contain a backported patch to correct these issues. After installing the update, avahi-daemon will be restarted automatically.

1.12. bash

1.12.1. RHBA-2011:0689: bug fix update

Updated bash packages that fix three bugs are now available for Red Hat Enterprise Linux 6.
Bash (Bourne-again shell) is the default shell for Red Hat Enterprise Linux.
This update fixes the following bugs:
  • When using arithmetic evaluation on an associative array with integer values, an attempt to provide an invalid subscript caused Bash to terminate unexpectedly with a segmentation fault. This update applies a patch that corrects this error, and providing an invalid subscript no longer causes the bash interpreter to crash. (BZ#618289)
  • Prior to this update, the Bash interpreter reported broken pipe errors for both external and built-in commands. Since these errors are only relevant for external commands, this update adapts the underlying source code to suppress the broken pipe error messages for built-in commands. As a result, only relevant messages are now presented to the users. (BZ#664468)
  • Previous version of the bash(1) manual page did not provide a clear description of the "break", "continue", and "suspend" built-in commands. This update corrects this error, and extends the manual page to provide accurate and complete descriptions of these commands. (BZ#619704)
All users are advised to upgrade to these updated packages, which fix these bugs.

1.13. bfa-firmware

1.13.1. RHBA-2011:0593: bug fix and enhancement update

An updated bfa-firmware package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6.
The bfa-firmware package contains the Brocade Fibre Channel Host Bus Adapter (HBA) Firmware to run Brocade Fibre Channel and CNA adapters. This package also supports the Brocade BNA network adapter.
The bfa-firmware package has been upgraded to upstream version 2.3.2.3, which provides a number of bug fixes and enhancements over the previous version. (BZ#617017)
All users of Brocade Fibre Channel and CNA adapters are advised to upgrade to this updated package, which fixes several bugs and adds various enhancements.

1.14. bind

1.14.1. RHSA-2010:0975: Important security update

Updated bind packages that fix two security issues are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols. BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating correctly.
It was discovered that named did not invalidate previously cached RRSIG records when adding an NCACHE record for the same entry to the cache. A remote attacker allowed to send recursive DNS queries to named could use this flaw to crash named. (CVE-2010-3613)
It was discovered that, in certain cases, named did not properly perform DNSSEC validation of an NS RRset for zones in the middle of a DNSKEY algorithm rollover. This flaw could cause the validator to incorrectly determine that the zone is insecure and not protected by DNSSEC. (CVE-2010-3614)
All BIND users are advised to upgrade to these updated packages, which contain a backported patch to resolve these issues. After installing the update, the BIND daemon (named) will be restarted automatically.

1.14.2. RHBA-2011:0541: bug fix and enhancement update

Updated bind packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6.
The Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols. BIND includes a DNS server (named), a resolver library (routines applications use when interfacing with DNS), and tools for verifying that the DNS server is operating correctly.
This update fixes the following bugs:
  • previously, bind on the 64-bit PowerPC architecture used emulated atomic operations rather than native instructions. In this updated package bind on the 64-bit PowerPC architecture uses the same native atomic operations as the PowerPC architecture. (BZ#623638)
  • previously, the bind package generated the /etc/rndc.key file. However, generating this file used entropy from /dev/random. Consequently, installation of the bind package might have hung. The rndc.key is used by the rndc utility for advanced administration commands and is no longer automatically generated during installation of the bind package. Users requiring the rndc utility should generate the key themselves, via the "rndc-confgen -a" command. (BZ#677381)
  • under certain circumstances, "named" was entering a deadlock. Consequently, "named" could not be stopped using the "/etc/init.d/named stop" command. In this updated package, the deadlock no longer occurs, resolving this issue. (BZ#623122)
  • previously, the named_sdb PostgreSQL database backend failed to reconnect to the database when the connection failed during named_sdb startup. With this update, named writes an error message to the system log and tries to reconnect during every lookup. (BZ#623190)
  • previously, file conflicts prevented the i686 and x86_64 versions of bind-devel from being installed on the same machine. In this update, the file conflict is resolved and both the i686 and x86_64 bind-devel packages can be installed on the same system. (BZ#658045)
  • previously, initscript killed all processes with the name "named" when stopping the named daemon. With this update, initscript kills only the selected one. (BZ#622785)
  • the return codes of the "dig" utility are documented in the dig man page. (BZ#640538)
  • previously the named.8 manpage mentioned the system-config-bind utility. This utility is not included with Red Hat Enterprise Linux 6. The man page is updated to remove the reference to the system-config-bind utility. (BZ#660676)
  • the "status" action of the named initscript would not complete when the bind-sdb package was installed. These updated packages resolve this issue. (BZ#661663, BZ#672777)
  • when resolv.conf contained the "search" keyword with no arguments, host/nslookup/dig utilities failed to parse it correctly. In these updated packages, such lines are ignored. (BZ#669163)
  • previously, the nsupdate man page incorrectly listed HMAC-MD5 as the only TSIG algorithm. In this updated package, the list of encryption algorithms was removed from the nsupdate man page. The dnssec-keygen man page contains a complete list of usable encryption algorithms. (BZ#672819)
In addition, this update adds the following enhancements:
  • the bind packages in this update are rebased to version 9.7.3. The References section of this erratum contains a link to the bind release notes. (BZ#653486)
  • the host utility now honors "debug", "attempts" and "timeout" options in resolv.conf. (BZ#622764)
  • a new option, called DISABLE_ZONE_CHECKING, has been added to /etc/sysconfig/named. This option adds the possibility to bypass zone validation via the named-checkzone utility in initscript and allows starting named with misconfigured zones. (BZ#623673)
  • with this update: size, MD5 and the modification time of the /etc/sysconfig/named configuration file are no longer checked via the "rpm -V bind" command. (BZ#646932)
  • Root zone DNSKEY is now included in the bind package, in the /etc/named.root.key file. (BZ#667375)
Users are advised to upgrade to these updated bind packages, which resolve these issues and add these enhancements.

1.15. bind-dyndb-ldap

1.15.1. RHBA-2011:0606: bug fix and enhancement update

An updated bind-dyndb-ldap package that fixes several bugs and adds several enhancements is now available for Red Hat Enterprise Linux 6.
The dynamic LDAP back-end is a plug-in for BIND that provides an LDAP database back-end capabilities. It features support for dynamic updates and internal caching, to lift the load off of your LDAP server.
This update fixes the following bugs:
  • the plugin didn't load child zones correctly. The plugin has been fixed and now loads child zones well. (BZ#658286)
  • named aborted when attempting to connect to a local LDAP server during boot. Now it does not abort but the administrator must call "rndc reload" when LDAP server starts to correctly fetch zones. (BZ#662930)
  • the plugin flooded logs with too many messages. Now those messages are logged only when named is started with the "-d" (debug) parameter. (BZ#666244)
  • the plugin was rebased to 0.2.0 bugfix release. (BZ#667704)
  • queries for ANY type were not handled correctly, only SOA records were returned. The plugin was fixed and now all records are returned when asked. (BZ#667727)
  • the plugin failed to reconnect to the LDAP server when SASL authentication was used. The plugin was fixed and reconnection now works. (BZ#667730)
  • the plugin failed to delete nodes from the LDAP database when all resource records associated with the node were removed. Now the plugin deletes the empty nodes. (BZ#667732)
  • the plugin did not emit enough information when it was configured to use invalid credentials. Now it emits enough details. (BZ#667733)
This update adds the following enhancements:
  • It is now possible to specify allow-query and allow-transfer ACLs for zones. (BZ#667729)
  • It is now possible to set timeout for queries to the LDAP server. (BZ#667734)
Users are advised to upgrade to this updated bind-dyndb-ldap package, which resolves these issues.

1.16. binutils

1.16.1. RHBA-2011:0614: bug fix and enhancement update

Updated binutils packages that fix bugs and add various enhancements are now available.
Binutils is a collection of binary utilities, including ar (for creating, modifying and extracting from archives), as (a family of GNU assemblers), gprof (for displaying call graph profile data), ld (the GNU linker), nm (for listing symbols from object files), objcopy (for copying and translating object files), objdump (for displaying information from object files), ranlib (for generating an index for the contents of an archive), readelf (for displaying detailed information about binary files), size (for listing the section sizes of an object or archive file), strings (for listing printable strings from files), strip (for discarding symbols), and addr2line (for converting addresses to file and line).
These updated binutils packages provide fixes for the following bugs:
  • fix strip to keep the address of an empty section consistent with its offset in the object (BZ#614443)
  • fix if one of the input files is of a non-ELF format the linker may crash (BZ#680143)
  • fix occasional crash in linker (BZ#697703)
This update also adds these enhancements:
  • add support for the large code model on PowerPC (BZ#663587)
  • add support for ELF core dump notes sections for extra s390 registers (BZ#633448)
  • add support for the new instructions in the System z196 processor (BZ#631540)
  • add support for ELF objects with more then 65535 program headers (BZ#578661)
Users are advised to upgrade to these updated binutils packages, which resolve these issues.

1.17. blktrace

1.17.1. RHBA-2011:0718: bug fix update

Updated blktrace packages that fix numerous bugs are now available for Red Hat Enterprise Linux 6.
The blktrace packages contain a number of utilities to record the I/O trace information for the kernel to user space, and utilities to analyze and view the trace information. This includes:
  • blktrace (to extract event traces from the kernel)
  • blkparse (to produce formatted output of event streams)
  • blkiomon (for i/o monitoring - periodically generating per-device request size and request latency statistics, and providing histograms)
  • btreplay (for recreating IO loads recorded by blktrace)
  • btt (to analyse block i/o traces produces by blktrace)
Bug fixes:
BZ#583615
When the device list contained the same device as supplied on the command line, blktrace stopped immediately and further I/O tracing was impossible. This occurred when an error returned in BLKTRACESETUP ioctl caused the program to terminate whenever a device was duplicated in the devpaths. This patch ensures devices are not duplicated in the devpaths pool, thus fixing the problem.
BZ#619201
When blktrace was run without parameters, it incorrectly included the version number in its usage message. This resulted in the false assumption that the version number was a required parameter. This update edits the usage message so that the version number is not printed when running blktrace, blkparce or btt without parameters, avoiding any confusion.
BZ#650229
Previously, btreplay would give a 'No such file or directory' error when attempting to execute with /dev/cciss/foo because of the long path name. This was caused by missing the back conversion of underscores to slashes. This update converts the underscores to slashes to restore the device names with longer paths.
BZ#583624
Running 'blktrace -d <device> -k' once did not kill a running background trace. Running it a second time resulted in a 'BLKTRACETEARDOWN: Invalid argument' message, after which any further attempt to run it returned 'BLKTRACESETUP: No such file or directory'. This was caused by the option -k clobbering information about running a trace by the kernel (that is, blk_trace_remove), while files opened in debugfs by blktrace running in the background were not released. In this patch, the documentation is updated to remove the faulty 'kill' option. It advices to send a SIGINT signal via kill(1) to the running background blktrace for its correct termination.
BZ#650243
The documentation falsely gave the impression that blkiomon was not giving the correct output when working with a logical volume device. When working on a logical volume device, blkiomon does not understand the output of blktrace,as a logical volume device is quiet. While working with a physical device, it prints I/O statistics as expected. This patch updates the documentation to reflect this.
BZ#583695
When blkparse was run with a non-existent file as an argument, it returned no errors and the exit-code was zero. This update provides a warning message when a non-existent file is used as an argument and exits with a non-zero status.
BZ#595356
Previously, blktrace would not end after 30 seconds. Instead it would remain running until the user killed it, after which any further attempts to run it failed with an error. This was because when open_ios() failed, tracer_wait_unblock() in thread_main() waits for an event that will never occur. Because the event never occurs, any future attempts to run blktrace failed with an error. This update makes sure that unblock_tracers() is also called when an unsuccessful event occurs, (that is, when nthreads_running != ncpus).
BZ#595413
There was a mistake in the man page for btrecord. It incorrectly documented the option --input-base, which is unsupported, and the supported --max-bunch-time was undocumented. This update replaces --input-base with --input-directory, and adds the option --max-bunch to the btrecord man page.
BZ#595419
The blkiomon man page was missing elements. The options -d and --dump-lldd were not recorded. This patch adds these and a drv_data mast description to the blktrace man page.
BZ#595615
The blkparce man page was missing six elements. These were -A, --set-mask, -a, --act-mask, -D, and --input-directory. These options are now added to the blkparce man page.
BZ#595620
The blktrace man page was missing sixteen elements. These were:
  • -d <dev> | --dev=<dev>
  • -r <debugfs path> | --relay=<debugfs path>
  • -o <file> | --output=<file>
  • -D <dir> | --output-dir=<dir>
  • -w <time> | --stopwatch=<time>
  • -a <action field> | --act-mask=<action field>
  • -A <action mask> | --set-mask=<action mask>
  • -b <size> | --buffer-size
  • -n <number> | --num-sub-buffers=<number>
  • -l | --listen
  • -h <hostname> | --host=<hostname>
  • -p <port number> | --port=<port number>
  • -s | --no-sendfile
  • -I <devs file> | --input-devs=<devs file>
  • -v <version> | --versio
  • -V <version> | --version
These options are now added to the blktrace man page.
BZ#595623
The btreplay man page was missing three elements. These were -t, -x, and --acc-factor. These options are now added to the btreplay man page.
BZ#595628
The btt man page was missing four elements. These were -X, -m, --easy-parse-avgs, and --seeks-per-second. These options are now added to the btt man page.
All users are advised to upgrade to these updated packages, which resolve these issues.

1.18. btrfs-progs

1.18.1. RHEA-2011:0567: enhancement update

An updated btrfs-progs package that adds an enhancement is now available for Red Hat Enterprise Linux 6.
The btrfs-progs package provides user-space programs to create, check, modify, and correct any inconsistencies in a Btrfs file system.
This update adds the following enhancement:
  • The btrfs-progs package has been updated to the latest upstream version, and newly includes the btrfs utility for easier administration of Btrfs file systems. (BZ#645741)
All users of Btrfs are advised to upgrade to this updated package, which adds this enhancement.

1.19. busybox

1.19.1. RHBA-2011:0559: bug fix update

Updated busybox packages that fixes several bugs are now available.
Busybox is a single binary containing a large number of system commands, including a shell. This package can be useful for recovering from certain types of system failures, particularly those involving broken shared libraries.
This update addresses the following issues:
  • Previously, the cpio applet included with busybox printed summary messages to stdout instead of stderr as the stand alone cpio does. Consequently nothing was returned to the shell when the busybox cpio applet ran. The updated applet include a patch that corrects this: the busybox cpio applet now prints summary messages to stderr, returning information to the shell as the standalone utility does. (BZ#615391)
  • As initially released, the "busybox hwclock" utility included with Red Hat Enterprise Linux 6 honored the current Filesystem Hierarchy Standard (FHS 2.3) and assumed the adjtime state file was at /var/lib/hwclock/adjtime. If kexec was invoked to load a second kernel over a crashed kernel, this caused "busybox hwclock" to return incorrect and inconsistent values when compared with the same command running in the first kernel prior to the crash. With this update, the config file for busybox hwclock was reverted to its old behavior. It now assumes the adjtime state file is at /etc/adjtime, as was the case in FHS 2.1, and "busybox hwclock" behaves as expected when run in an initial or reloaded kernel. (BZ#621853)
  • The "busybox awk" utility incorrectly treated all strings of digits with leading zeros as octal integer constants. This meant strings such as "0xffff" and "07777" were handled correctly but strings such as "0.531" were not. As a consequence, awk operations that correctly manipulated such strings as numbers were not handled correctly by busybox awk. With this update, the awk utility included with busybox correctly differentiates between hexadecimal and floating decimal strings and handles manipulations of the latter as expected. (BZ#633961)
All busybox users should install this update, which fixes these bugs.

1.20. bzip2

1.20.1. RHSA-2010:0858: Important security update

Updated bzip2 packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
bzip2 is a freely available, high-quality data compressor. It provides both standalone compression and decompression utilities, as well as a shared library for use with other programs.
An integer overflow flaw was discovered in the bzip2 decompression routine. This issue could, when decompressing malformed archives, cause bzip2, or an application linked against the libbz2 library, to crash or, potentially, execute arbitrary code. (CVE-2010-0405)
Users of bzip2 should upgrade to these updated packages, which contain a backported patch to resolve this issue. All running applications using the libbz2 library must be restarted for the update to take effect.

1.21. certmonger

1.21.1. RHBA-2011:0570: bug fix and enhancement update

An enhanced certmonger package that fixes various bugs and provides several enhancements is now available for Red Hat Enterprise Linux 6.
The certmonger utility monitors certificate expiration and can refresh certificates with the CAs (Certifying Authorities) in networks that use public-key infrastructure (PKI).
Bug fixes:
BZ#624142
If the certmonger service failed to contact a CA, the subprocess that submitted the request became defunct. This occurred because the parent process did not read the subprocess status. With this update, the parent process reads the subprocess status and there is no defunct process after a CA contact failure.
BZ#636894
Previously, after installing the certmonger utility, the certmonger service failed to start. This occurred because the package installation did not signal the system bus daemon that it needed to re-read its configuration as to allow the certmonger daemon to connect to the bus. This update fixes the bug and the certmonger service can be started right after the installation.
BZ#643561
The certmonger package has been upgraded to upstream version 0.34, which provides a number of bug fixes and enhancements over the previous version.
BZ#652047
Previously, the certmonger utility did not display a user-friendly error message when the user ran the ipa-getcert command with privileges that were insufficient for the system bus to allow it to communicate with the certmonger service. With this update, certmonger suppresses the original error message if a user-friendly message is available. The user can display both messages with the -v option.
BZ#652049
Prior to this update, the ipa-getcert list command did not return any output if certmonger was not tracking any certificates. With this update, the command returns a message that the certificate list is empty.
BZ#687899
Due to inappropriate SELinux policy settings, the certmonger daemon could not execute some of its helper processes. The updated policy now allows certmonger to run these processes and the certmonger libraries create temporary files in a location that certmonger can access.
BZ#688229
The certmonger service accepted a non-existent PIN (Personal Identification Number) file for the NSS (Network Security Services) database if the user ran the ipa-getcert request command with the -p option. This occurred because certmonger failed to detect reading errors in the file with the PIN and proceeded with an empty PIN value. With this update, such reading errors are logged and certmonger proceeded as if it had read an empty PIN value.
BZ#689776
Previously, the certmonger service terminated unexpectedly if the user attempted to use a certificate database stored in a non-existent directory. While preparing an error message to return to its client, the daemon attempted to use already-freed memory, which could have caused a segmentation fault. With this update, certmonger displays a message that the directory does not exist and remains stable in these circumstances.
BZ#690886
After installation of the ipa-client package, the ipa-client-install script runs the ipa-getcert command. As a consequence, the certmonger daemon runs its ipa-submit helper. The helper contacts the IPA server. Previously, if it received a fault message response from the server, it terminated with a segmentation fault and created a core dump; the installation failed. This happened because it attempted to dereference an uninitialized pointer while processing the fault message. With this update, the helper handles the fault message correctly and the enrollment process completes successfully.
BZ#691351
Previously, running the getcert command with an invalid Extended Key Usage parameter caused a segmentation fault. This happened because the command attempted to dereference a NULL pointer while attempting to report that the parameter value was not a valid OID (Object Identifier). With this update, certmonger reports that the OID validation failed and prints a message that the provided Extended Key Usage is invalid.
BZ#695672
Prior to this update, certmonger could have seemingly ignored the attempts to resubmit a certificate with changed Subject and Principal names. This occurred because the certificate changes were not saved if a certificate with the same nickname already existed in the certificate database. With this update, the certmonger utility removes the certificates with the respective nickname before storing the new certificate and the resubmit command works as expected.
BZ#695675
Previously, the certmonger service could have failed to resubmit certificates. This happened if the SELinux policy did not allow certmonger to write to the defined location for storing keys. With this update, the service reads information about the keys to verify that the keys had been generated and stored properly. If the reading fails, the keys are generated again.
BZ#696185
Previously, the getcert tool terminated unexpectedly with a segmentation fault if the user issued the getcert start-tracking command with changed values of the parameters Extended Key Usage, DNS, Email and Principal name. The command caused a buffer overflow in the getcert tool because the internal buffer in the getcert command was too small to hold four new values. This update enlarges the internal buffer of the command and the bug no longer occurs.
Enhancements:
BZ#624143
The ipa-getcert and getcert commands did not accept the location of a passphrase, which could provide the encrypted keying material and allow monitoring of an already-issued certificate or key pair. This update adds the -p and -P options to the getcert start-tracking command, which allows the user to pass the utility a PIN either in a file or directly.
BZ#683926
Previously, the certmonger service did not support a verbose mode for the ipa-getcert command. This update adds the --verbose option to the command.
All users of certmonger are advised to upgrade to this updated package, which resolves these issues and provides these enhancements.

1.22. cifs-utils

1.22.1. RHBA-2011:0380: bug fix update

An updated cifs-utils package that fixes a bug is now available for Red Hat Enterprise Linux 6.
The Server Message Block (SMB), also known as Common Internet File System (CIFS), is a standard file-sharing protocol widely deployed on Windows machines. The tools included in this package work in conjunction with support in the kernel to allow users to mount a SMB/CIFS share onto a client, and use it as if it were a standard Linux file system.
This update fixes the following bug:
  • Due to an error in the cifs.upcall utility, Generic Security Services Application Program Interface (GSSAPI) channel bindings in Kerberos authentication messages were not set properly. This would cause some servers to reject authentication requests. Consequent to this, an attempt to mount a CIFS share with the security mode set to "krb5" could fail with the following error:
    mount error(5): Input/output error
    
    This update corrects the cifs.upcall utility to set the GSSAPI channel bindings properly, and such CIFS shares can now be mounted as expected. (BZ#668366)
All users of cifs-utils are advised to upgrade to this updated package, which resolves this issue.

1.22.2. RHBA-2011:0569: bug fix update

An updated cifs-utils package that fixes five bugs is available.
The SMB/CIFS protocol is a standard file sharing protocol widely deployed on Microsoft Windows machines. This package contains tools for mounting shares on Linux using the SMB/CIFS protocol. The tools in this package work in conjunction with support in the kernel to allow one to mount a SMB/CIFS share onto a client and use it as if it were a standard Linux file system.
The cifs-utils package has been updated to the latest upstream version. Bugs fixed in this updated package include:
  • While trying to mount a share (DFS or 'classic') with Kerberos, a "mount error(5): Input/output error" occurred due to a problem with the MIT krb5 libraries. cifs.upcall now sets the GSSAPI checksum properly in SPNEGO blobs. This is necessary for proper interoperability with EMC servers when using krb5 authentication, and allows for a successful mount . (BZ#645127)
  • When mounting a share as root with kerberos, cifs.upcall used the ticket of root (/tmp/krb5cc_0) instead the one of the user specified with 'uid=' or 'user='. This was due to the --legacy-uid command line option for cifs.upcall not being properly implemented. This patch ensures that this option can be properly implemented, allowing successful mounting of a share as root with kerberos. (BZ#667382)
  • When two CIFS shares were mounted on the same server, each for a different user who had valid krb5 credentials, only the one mounted first could access the data. This was because cifs had a built in design limitation of a single set of credentials per mount. That limitation caused the implementation of a number of hacks to deal with it. With this patch mount.cifs now supports the 'cruid=' mount option, fixing this issue. (BZ#669377)
  • mount.cifs did not handle numeric uid=, gid=, or cuid= options correctly, and would often return an error when they were specified. With this patch, a check is run to see if any error occurred by setting errno to 0 before the conversion. If one did then it will attempt to treat the value as a name, allowing them to be correctly handled. (BZ#696951)
  • In order to update the man pages and include a couple small patches, cifs-utils has been rebased to 4.8.1. (BZ#658981)
All users who are using the cifs file system should update to this new package in order to take advantage of these bug fixes.

1.23. cluster and gfs2-utils

1.23.1. RHBA-2010:0844: bug fix update

Updated cluster and gfs2-utils packages that fix several bugs are now available for Red Hat Enterprise Linux 6.
The cluster packages contain the core clustering libraries for Red Hat High Availability as well as utilities to maintain GFS2 file systems for users of Red Hat Resilient Storage.
This update provides fixes for the following bugs:
  • The /proc/mounts file system is no longer updated with the wrong device. (BZ#634201)
  • A 'service cman stop remove' command no longer erroneously and permanently sets the 'remove' flag for a node for every subsequent stop/leave operation. (BZ#638954)
  • When two cluster nodes attempt to form a cluster with different configuration files, the one with the more recent version no longer gets killed. (BZ#639958)
  • The fsck.gfs2 utility no longer crashes if journals are missing. (BZ#637699)
All users of Red Hat High Availability and Red Hat Resilient Storage are advised to upgrade to these updated packages, which address these issues.

1.23.2. RHBA-2011:0361: bug fix update

Updated cluster and gfs2-utils packages that fix a bug are now available for Red Hat Enterprise Linux 6.
The cluster packages contain the core clustering libraries for Red Hat High Availability as well as utilities to maintain GFS2 file systems for users of Red Hat Resilient Storage.
This update provides fixes for the following bug:
  • Due to an incorrect conversion of directory inodes with the height larger than 1, running the gfs2_convert utility on a file system with extremely large directories may have caused the file system to become corrupted. With this update, the underlying source code has been modified to target this issue, and the gfs2_convert utility now works as expected. (BZ#643279)
All users of Red Hat High Availability and Red Hat Resilient Storage are advised to upgrade to these updated packages, which resolve this issue.

1.23.3. RHBA-2011:0537: bug fix update

Updated cluster and gfs2-utils packages that fix various defects are now available for Red Hat Enterprise Linux 6.
The cluster packages contain the core clustering libraries for Red Hat High Availability as well as utilities to maintain GFS2 file systems for users of Red Hat Resilient Storage.
This update provides fixes for the following defects:
  • CMAN init script race condition has been fixed (BZ#595725)
  • plock owner synchronization has been fixed (BZ#617306)
  • plocks are now ignored until they written to their checkpoint (BZ#623810)
  • plock signatures are now re-sent after a new totem ring forms (BZ#623816)
  • post_join_delay now works after a loss and subsequent regain of quorum (BZ#624844)
  • "service cman stop remove" now functions correctly (BZ#634718)
  • Active cluster nodes with higher configuration version numbers are no longer killed when they join the cluster (BZ#639018)
  • The ccs_tool man page no longer shows 'update' and 'upgrade' subcommands (BZ#577874)
  • ccs_tool cluster configuration editing has been dropped (BZ#614885)
  • The interaction between corosync and cman restarting independently of one another has been improved (BZ#617234)
  • reporting of corosync's exit code has been improved (BZ#617247)
  • cman_tool manual page no longer talks about "config version" as an argument to -r (BZ#619874)
  • Qdiskd now stops voting & exits if removed from the configuration (BZ#620679)
  • gfs_controld: fix plock owner in unmount (BZ#624822)
  • Qdiskd now reports to users when the quorumd "label" attribute overrides the "device" attribute (BZ#635413)
  • Qdiskd now has a hard limit on heuristic timeouts (BZ#636243)
  • Pacemaker-specific versions of dlm_controld and gfs_controld have been removed since they are no longer required (BZ#649021)
  • cman now allows users to select udpu (UDP unicast) corosync transport mechanism (BZ#657041)
  • Qdiskd now assumes votes for each cluster node are 1 when not specified in cluster.conf (BZ#663433)
  • The cman init script can no longer include an incorrect sysconf file (BZ#669340)
  • DLM recovery no longer hangs after fencing completion in some instances (BZ#678704)
  • The cluster.rng schema has been updated (BZ#645830, BZ#618705, BZ#684020, BZ#629017, BZ#680172)
  • A memory leak in the XML parser has been fixed (BZ#680155)
  • Heuristic checks are unreliable (BZ#688154)
  • cman quorum timeout is too short (BZ#688201)
  • The following issues have been addressed in the gfs2-utils package:
  • fsck.gfs2 was truncating directories with more than 100,000 entries (BZ#628013)
  • fsck.gfs2 was processing some files twice (BZ#621313)
  • fsck.gfs2 no longer crashes if journals are missing (BZ#622576)
  • When mounting a gfs2 file system, the same device requested on the command line now appears in /proc/mounts and /etc/mtab (BZ#632595)
  • gfs2_convert now resumes after an interrupted conversion (BZ#637913)
  • fsck.gfs2 can now repair rgrps resulting from gfs_grow->gfs2_convert (BZ#576640)
  • mkfs.gfs2 no longer segfaults with 18.55TB and -b512 (BZ#624535)
  • mkfs.gfs2 now supports discard request generation (BZ#656956)
  • fsck.gfs2: reports master/root inodes as unused and fixes the bitmap (BZ#663037)
  • gfs2_convert no longer corrupts the file system if the di_height is too large. (BZ#630005)
  • gfs2_convert no longer exits success without doing anything (BZ#688734)
In addition, this update provides the following enhancements:
  • gfs2_edit now outputs hexadecimal values in lower-case (BZ#634623)
  • gfs2_edit now prints continuation blocks (BZ#634623)
  • gfs2_edit's savemeta and restoremeta functions now report progress (BZ#634623)
  • gfs2_edit has improved handling of corrupt file systems and enhanced usability (BZ#674843)
  • It is now possible to prevent the cluster software from starting at boot using the kernel command line (BZ#563901)
  • The cluster now has a script which can be used with the watchdog daemon to reboot the host (BZ#560700)
  • Fenced now sends notifications over DBus (BZ#592964)
All users of Red Hat High Availability and Red Hat Resilient Storage are advised to upgrade to these updated packages, which resolve these issues.

1.24. compat-dapl

1.24.1. RHBA-2011:0343: bug fix update

Updated compat-dapl packages that fix a bug are now available.
The DAT programming API provides a means of utilizing high performance network technologies, such as InfiniBand and iWARP, without needing to write your program to use those technologies directly. This package contains the libraries that implement version 1.2 of the DAT API. The current (and recommended version for any new code) is 2.0. These 1.2 libraries are provided solely for backward compatibility.
This update fixes the following bug:
  • Under certain error conditions, an error in the code path in compat-dapl did not allow the cp_ptr entry to be cleaned up correctly in the internal link list. This could cause new connections to fail. This update includes a backported fix from uDAPL 2.0 which ensures the entry is cleaned up correctly and subsequent connections work as expected. (BZ#673992)
Users should upgrade to these updated packages, which resolve this issue.

1.24.2. RHBA-2011:0696: bug fix update

Updated compat-dapl packages that fix a bug are now available.
The DAT programming API provides a means of utilizing high performance network technologies, such as InfiniBand and iWARP, without needing to write your program to use those technologies directly. compat-dapl contains the libraries that implement version 1.2 of the DAT API. compat-dapl is provided solely for backward compatibility.
This update provides the following bug fix:
  • Fixes an issue in which, under certain error conditions, dapl could fail to properly clean up its internal state, potentially resulting in subsequent incorrect operation. (BZ#635155)
Users should upgrade to these updated packages, which resolve this issue.

1.25. coolkey

1.25.1. RHBA-2011:0765: bug fix update

An updated coolkey package that fixes a bug is now available.
The coolkey package contains driver support for CoolKey and Common Access Card (CAC) smart card products.
This updated coolkey package fixes the following bug:
  • Previous versions of coolkey would fail to operate correctly if the pcscd daemon in the pcsc-lite package was restarted. Proper operation could be restored by restarting the application which was using coolkey, for example, the Gnome screensaver or the Gnome login screen when used with a smart card login. With this update, applications no longer need to be restarted to function properly when the pcscd daemon is restarted. (BZ#210200)
All users of coolkey are advised to upgrade to this updated package, which resolves this issue.

1.26. coreutils

1.26.1. RHBA-2011:0646: bug fix update

Updated coreutils packages that fix several bugs are now available.
The coreutils package contains the core GNU utilities. It is the combination of the old GNU fileutils, sh-utils, and textutils packages.
These updated packages fix the following bugs:
  • The su utility was previously not built with PIE and RELRO enabled, as they were in Red Hat Enterprise Linux 5. In this update, it is built as a PIE executable and is using RELRO protection. (BZ#630017)
  • Previously, when reading a line longer than 16KiB, the tac utility reallocated its primary buffer. Before exiting, the tac utility tried to free the already freed original buffer, which caused a utility crash after a double free error displayed. This was fixed and the tac utility no longer frees an already freed buffer. (BZ#628212)
  • Previously, the hardware control flow, DTRDSR, was implemented via TC{SG}ETX. This was changed to TC{SG}ET ioctl, which caused the CDTRDSR support in stty to fail. This was fixed to allow stty to correctly handle CDTRDSR control flow. (BZ#598631)
  • Previously, the internalization patch for coreutils had an unsafe initialization of charbufops that left bufops uninitialized or initialized to NULL on the first usage. This behavior called memmove from an incorrect address, namely from address 0 and size 0. This is now fixed and bufops is correctly initialized for the first use. (BZ#683799)
  • Previously, when the multibyte LC_TIME differed from LC_CTYPE, an assertion failure caused the sort utility to crash irrespective of the parameters provided to it. This is fixed to prevent a crash when the sort utility is run and now works as expected. (BZ#649224)
  • Previously, the information page about 8-bit octal values did not mention checking if the value was lower than 256. Due to this, when a command like "/bin/echo -e '\0610'" was used, the results were not accurate. This is now fixed to provide more accurate information about the behavior of octal values. (BZ#660033)
  • Previously, when the dd utility used pipes, it read and wrote partial blocks. When the size of the block written was shorter than the specified maximum output block size, the "oflag=direct" would turn off, which resulted in degraded I/O performance. The workaround for this behavior, which involves the addition of "iflag=fullblock" is now available in the information documentation. (BZ#614605)
  • Previously, the coreutils information page was not sufficiently clear about behavior when multiple parent and leaf node directories are created. This is now fixed to incorporate additional information in the coreutils information page about the @option mode and its behavior when combined with the --parents option. (BZ609262)
  • Previously, documentation for tail command's --sleep-interval option did not outline the results of inotify support. This is now fixed and the documentation states that with inotify support, the --sleep-interval option is only relevant when the tail command reverts to the old polling-based method. (BZ#662900)
All coreutils users are advised to upgrade to these updated packages, which resolve these issues.

1.27. corosync

1.27.1. RHBA-2011:0360: bug fix update

Updated corosync packages that fix a bug are now available for Red Hat Enterprise Linux 6.
The corosync packages provide the Corosync Cluster Engine and C Application Programming Interfaces (APIs) for Red Hat Enterprise Linux cluster software.
This update fixes the following bug:
  • Compared to a unicast token, certain network switches add an extra delay to the transmission of a multicast packet. Consequent to this, multicast messages may have been retransmitted, even though the message was not lost and the retransmission was therefore not necessary. This update introduces the "miss_count_const" constant that allows a user to specify the maximum number of times a message is checked for retransmission before the retransmission is performed. (BZ#683592)
All users of corosync are advised to upgrade to these updated packages, which resolve this issue.

1.27.2. RHBA-2011:0764: bug fix update

Updated corosync packages that add features and fix bugs are now available for Red Hat Enterprise Linux 6.
The corosync packages provide the Corosync Cluster Engine and C Application Programming Interfaces (APIs) for Red Hat Enterprise Linux cluster software.
This update fixes the following bugs:
  • Multicast emulation caused an extra delay to the multicast packet transmission, causing unnecessary retransmission of the packet. This update adds the "miss_count_const" constant allowing the user to specify how many times a message is checked before retransmission occurs. (BZ#619496)
  • When denied permissions from SELinux, corosync failed with a segmentation fault. Corosync now passes an error back to the API user when it is unable to create a connection between the server and client instead of causing a segmentation fault. (BZ#619918)
  • When provided an invalid multicast address, corosync failed without errors. This is now fixed, thus corosync displays an error when given an invalid multicast address. (BZ#613836)
  • Corosync client libraries delayed for 2 seconds before they displayed an error on a shut down. This is now fixed, thus the exited flag value before and after sem_wait is checked. If the value is true, ERR_LIBRARY displays. (BZ#639023)
  • The default TTL value in multicast was 1, preventing use on a routed network. The TTL value is now configurable in the corosync configuration file, thus multicast can now be used on a routed network. (BZ#640311)
  • BZ#640311 introduced a regression. (BZ#684920) (BZ#684930)
  • Shared memory no longer is leaked if the corosync server unexpectedly exits while connected to corosync clients. (BZ#665165)
  • Running multiple instances of corosync simultaneously would succeed, causing local node errors. This is now fixed to prevent initialization of multiple instances of corosync. (BZ#626962)
  • If cman ran the corosync init script, it would cause the corosync init script to be blocked. This is now fixed to allow corosync to create a Pid file and to allow cman to run corosync. (BZ#614104)
  • Corosync was unable to capture system events and notify the user about them. With this fix, SNMP MIB and daemon are added for system event notification via DBUS and SNMP. (BZ#629380)
  • Member objects in corosync were not found due to validation failure. This is fixed with an addition to the objdb file, thus validation for SNMP/DBUS integration is now successful. (BZ#675859)
  • The corosync build contained invalid version information, which caused rpmdiff to warn the user about version information changes. This was fixed, thus pkgconfig files are now correctly configured to display version as 1.2.3. (BZ#675741)
  • Corosync rebuilds succeeded only on fresh installations due to a regression issue. This is now fixed, thus corosync now rebuilds on existing installations as well. (BZ#680258)
  • A ring id file smaller than 8 bytes caused corosync to abort. This was fixed by recreating the ring id file, thus corosync now does not abort due to the ring id file. (BZ#675099)
  • Inconsistent cluster.conf files amongst nodes caused a memory leak. This is now fixed, thus a configuration reload via cman_tool no longer causes a memory leak. (BZ#677975)
  • During the recovery phase, aisexec exited unexpectedly, resulting in a lost network token. This is now fixed, thus aisexec no longer exits due to a lost token. (BZ#675783)
  • UDPU transport is added, which simulates multicast via UDP unicast. This adds a third transport option to broadcast and multicast in a cluster. (BZ#568164)
  • Fix abort that happens in rare circumstances during shutdown. (BZ#688691)
All users of corosync are advised to upgrade to these updated packages, which resolve this issue.

1.28. cracklib

1.28.1. RHBA-2011:0202: bug fix update

Updated cracklib packages that fix two bugs are now available for Red Hat Enterprise Linux 6.
CrackLib is a password-checking library that is used to help enforce password quality controls.
This update fixes the following bugs:
  • Manual pages for the cracklib-check, cracklib-format, and create-cracklib-dict utilities have been added. (BZ#583932)
  • The Simplified Chinese (zh_CN) translation of one of the error messages the library can produce has been corrected, and no longer contains untranslated strings. (BZ#627449)
All users of cracklib are advised to upgrade to these updated packages, which resolve these issues.

1.29. crash

1.29.1. RHBA-2011:0561: bug fix and enhancement update

An updated crash package that fixes various bugs and adds two enhancements is now available for Red Hat Enterprise Linux 6.
The crash package provides a self-contained tool that can be used to investigate live systems, and kernel core dumps created from the netdump, diskdump, kdump, and Xen/KVM "virsh dump" facilities from Red Hat Enterprise Linux.
This update fixes the following bugs:
  • The crash package has been upgraded to upstream version 5.1.1, which provides a number of bug fixes over the previous version. (BZ#649070)
  • On 64-bit x86 architectures, using the "bt" command to analyze core dumps from kernel 2.6.27 or later caused it to display an invalid "vgettimeofday" frame above the topmost "system_call_fastpath" frame, followed by two read error messages similar to the following:
    bt: read error: kernel virtual address: ffffffffff600000  type:
    "gdb_readmem_callback"
    
    This error no longer occurs, and the "bt" command now produces correct results for these kernels. (BZ#637735)
  • When analyzing a KVM dump file from a 64-bit x86 guest system, the crash utility failed to determine the starting RIP and RSP hooks. This rendered it unable to produce a correct backtrace for tasks that were either running in user space when the "virsh dump" operation was performed on a live guest, or that were running on interrupt or exception stacks. With this update, the RIP and RSP hooks for a particular dump file are now determined by using the content of the per-CPU registers in the CPU device format. As a result, the "bt" command no longer produces incorrect backtraces for such dump files. (BZ#649050)
  • When analyzing a KVM dump file from an x86 guest system, the crash utility was unable to determine the starting EIP and ESP hooks, and produced an invalid backtrace. With this update, the crash utility has been updated to use the 64-bit CPU device format in x86 KVM dump files by default, and only use the 32-bit format when it is determined that the host machine was running a 32-bit kernel. As a result, running the "bt" command when analyzing such a dump file now produces a correct backtrace. (BZ#649051)
  • When creating a KVM dump file, the "virsh dump" operation marks all non-crashing CPUs as offline. Due to an incorrect use of the "cpu_online_map" mask to determine the CPU count, previous version of the crash utility may have reported a wrong number of CPUs when analyzing dumps created by the "virsh dump" command on x86 guest systems. With this update, the underlying source code has been adapted to use the "cpu_present_map" mask instead, so that the crash utility reports the correct number of CPUs. (BZ#649053)
  • Prior to this update, an attempt to display a backtrace of a non-active swapper task on a 32-bit x86 architecture could cause the crash utility to display the following message:
    bt: cannot resolve stack trace:
    #0 [c09f1ef4] ia32_sysenter_target at c08208ce
    
    This update applies a patch that resolves this issue, and the crash utility now resolves such backtraces as expected. Additionally, this update ensures that the crash utility is no longer negatively affected by the changes that were introduced in kernel 2.6.32-112. (BZ#682129)
As well, this update adds the following enhancements:
  • The crash utility has been updated to provide support for dump files created on the IBM System z architecture. (BZ#633449)
  • The crash utility now supports compressed and/or filtered dump files generated by the makedumpfile utility on IBM System z. (BZ#637197)
All users of crash are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

1.30. crda

1.30.1. RHEA-2011:0550: enhancement update

An updated crda package that adds one enhancement is now available for Red Hat Enterprise Linux 6.
The crda package contains the Central Regulatory Domain Agent, which provides the kernel with the wireless regulatory rules for a given jurisdiction.
This updated crda package enhances the kernel with the most current information with regard to wireless regulatory rules, and ensures that these updated rules are enforced. (BZ#654066)
All users are advised to upgrade to this updated package, which adds this enhancement.

1.31. cronie

1.31.1. RHBA-2011:0788: bug fix update

Updated cronie packages that fix various bugs are now available.
Cronie contains the standard UNIX daemon crond that runs specified programs at scheduled times and related tools. It is a fork of the original vixie-cron and has security and configuration enhancements like the ability to use pam and SELinux.
This update fixes the following bugs:
  • The initscript output written to /var/log/boot.log contained a double output of "OK", printed by /etc/init.d/crond and daemon. This error has been corrected: the echo from /etc/init.d/crond is removed, thus the output is now as expected. (BZ#615107)
  • Cronie didn't close file descriptor, which caused other applications such as anacron that are subsequently started by cronie to inherit the file descriptor. This caused SELinux to prevent /bin/bash access. With this update, the file descriptor is no longer inherited by other applications, thus SELinux no longer prevents /bin/bash access. (BZ#624043)
  • An incorrect option in the bash script caused anacron to run daily instead of hourly if the /var/spool/anacron/cron.daily file existed. The error has been corrected: the bash script option is fixed and anacron now runs once a day if the /var/spool/anacron/cron.daily file exists. (BZ#675077)
  • RELRO flags were previously not set by default from crond. This is now fixed so that cronie is compiled with RELRO protection enabled. (BZ#676040)
  • The /usr/bin/crontab was set to use both setuid and setgid permissions, but this was changed to use only setuid. (BZ#676081)
  • Multiple code quality improvements were made, which include:
    • In src/crontab.c, mkstemp expects six X's to be replaced with digits at the end of each filename. This fix removes the extra X's.
    • In src/security.c, ccon was not freed after a return. This is fixed and ccon is now freed using context_free.
    • In anacron/run_job.c, fdin was tested before being initialized. This is fixed to ensure that fdin is now initialized prior to testing.
All users of cronie are advised to upgrade to this updated package, which resolves these issues.

1.32. cryptsetup-luks

1.32.1. RHBA-2011:0597: bug fix and enhancement update

Updated cryptsetup-luks packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6.
The cryptsetup-luks packages provide the utility allowing users to set up encrypted devices with the Device Mapper and the dm-crypt target.
The cryptsetup-luks package has been upgraded to upstream version 1.2.0, which provides a number of bug fixes and enhancements over the previous version. (BZ#658817)
In addition, these updated cryptsetup-luks packages provide fixes for the following bugs:
  • Previously, cryptsetup printed twice the error message notifying the user that the queried device did not exist. With this update, the underlying code was changed and the error message is displayed once. (BZ#612963)
  • Prior to this update, when the user attempted to encrypt a device with the MD4 or MD5 hash algorithm, cryptsetup did not alert the user that the encryption with those algorithms was not supported, had failed, and that therefore the device could not be used. With this update, cryptsetup terminates the process and prints a message advising the user to check if the required encryption method is supported. (BZ#623121)
  • Previously, cryptsetup did not remove keys as soon as possible from device control buffers and therefore did not follow FIPS (Federal Information Processing Standard). With this update, the underlying code has been changed and the keys are removed from the buffers as soon as possible. (BZ#674825)
  • Previously, if the user issued the "cryptsetup luksRemoveKey" command with the "--key-file" parameter, the command removed the key defined in the standard input. With this update, such command removes the key defined in the "--key-file" parameter. (BZ#677634)
  • Prior to this update, when updating with the "yum update" command, the device-mapper-libs package was not updated. This occurred because the previous version of the cryptsetup package was compatible with any version of the package. This update adds the dependency to the cryptsetup package and the device-mapper-libs is updated to provide the compatible device-mapper-libs package. (BZ#692512)
  • Previously, when running in FIPS mode, the salt for PBKDF2 (Password-Based Key Derivation Function) was generated with the /dev/urandom device. According to NIST Special Publication 800-132, all or a portion of the salt must be generated with an approved random number generator. With this update, the salt is generated with the FIPS RNG (Random Number Generator) and the criterion is met. (BZ#693371)
These updated packages provide also the following enhancements:
  • With this update, cryptsetup uses a FIPS certified random number generator for generation of volume keys when running in FIPS mode. (BZ#663869)
  • This update adds the integrity check of the cryptsetup binary and library for FIPS mode. (BZ#663870)
Users are advised to upgrade to these updated cryptsetup-luks packages, which resolve these bugs and add these enhancements.

1.33. cups

1.33.1. RHSA-2010:0866: Important security update

Updated cups packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The Common UNIX Printing System (CUPS) provides a portable printing layer for UNIX operating systems.
An invalid free flaw was found in the way the CUPS server parsed Internet Printing Protocol (IPP) packets. A malicious user able to send IPP requests to the CUPS server could use this flaw to crash the CUPS server. (CVE-2010-2941)
Red Hat would like to thank Emmanuel Bouillon of NATO C3 Agency for reporting this issue.
Users of cups are advised to upgrade to these updated packages, which contain a backported patch to correct this issue. After installing this update, the cupsd daemon will be restarted automatically.

1.33.2. RHBA-2011:0715: bug fix update

Updated cups packages resolving several issues are now available for Red Hat Enterprise Linux 6.
The Common UNIX Printing System (CUPS) provides a portable printing layer for Linux, UNIX, and similar operating systems.
These updated cups packages provide fixes for the following bugs:
  • Some printers were incorrectly reporting ink and toner levels via SNMP backend. Support for an SNMP quirk has been added and enabled via the PPD file. (BZ#580604)
  • Previously, lpstat -p always reported job id as '-0'. This was because the jobstate was never IPP_JOB_PROCESSING due to an SVN revision upstream. This patch fixes this issue by adding the attributes needed for jobs. (BZ#614908)
  • The previous 8MB default RIP cache size was insufficient for modern high-resolution (color/photo) printing. This was because filters such as pstoraster could fail. This update increases the default RIP cache size to 128MB to fix this issue. (BZ#616864)
  • If the cupsd daemon was stopped while a job was being sent to a printer using a given backend, that backend was restarted multiple times before the CUPS scheduler actually terminated. In this updated package, the CUPS scheduler tracks whether it is shutting down and does not automatically start new jobs if so. (BZ#624441)
  • The 'restartlog' action was missing in Initscript usage output, preventing its usage. This update adds it. (BZ#632180)
  • Several rpmlint errors and warnings were fixed:
    • fixing the character encoding in CREDITS.txt
    • marking the D-Bus configuration file as config file
    • not marking MIME types and convs files as config files (overrides can be placed as new *.types/*.convs files in /etc/cups)
    • not marking banners as config files, instead new banners are provided
    • not marking initscript as a config file
    • not marking templates and www files as config files, instead a different ServerRoot setting is used to provide local overrides. Please note that a recent security fix required a change to template files
    • providing a versioned LPRng symbol for rpmlint
    • using mode 0755 for binaries and libraries where appropriate
    • moving /etc/cups/pstoraster.convs to /usr/share/cups/mime/
    • moving the cups-config man page to the devel sub-package
  • Red Hat Enterprise Linux 4 CUPS clients use the character set specified in LANG as the charset attribute in CUPS IPP requests, where Red Hat Enterprise Linux 5 and 6 ignore this, leading to incompatibilities. In these updated packages the CUPS server has been adjusted so that non-UTF-8 clients (e.g. Red Hat Enterprise Linux 4 clients) continue to be accepted. (BZ#642448)
  • The subpackage cups-php consumed library libcups.so2 from subpackage cups-libs even though it did not have an explicit package version requirement. In this update cups-php subpackage now explicitly requires cups-libs of the same version and release. (BZ#646814)
  • The ipp, socket and lpd backends were treating name resolution failures as a permanent error. Because these types of failures can be temporary, the tolerance for DNS failures has been added. (BZ#654667)
  • Previously, the CUPS service did not stop normally if it was running when halting the system or a reboot was performed. Instead, it had to be killed in the final stage of reboot or shut down. This update fixes Initscript so the service is correctly stopped on reboot or halt. (BZ#659692)
  • When the cupsd daemon was running with SELinux features enabled, the file descriptor count was increasing over time until its resources ran out. With this update, the resources are allocated only once so they do not leak file descriptors. (BZ#668010)
  • There was a small typo in sample snmp.conf file. It is fixed in this update. (BZ#672614)
All users of cups are advised to upgrade to these updated packages, which resolve these issues.

1.34. curl

1.34.1. RHBA-2011:0573: bug fix update

Updated curl packages that fix bugs in HTTPS, FTP, LDAP and proxy kerberos authentication are now available.
cURL is a tool for getting files from HTTP, FTP, FILE, LDAP, LDAPS, DICT, TELNET and TFTP servers, using any of the supported protocols. cURL is designed to work without user interaction or any kind of interactivity. cURL offers many useful capabilities, like proxy support, user authentication, FTP upload, HTTP post, and file transfer resume.
This update fixes the following bugs:
  • libcurl introduced a segfault where a RHEL 6.1 machine registered at RHN would result in a segmentation fault (core dumped) after running "yum clean all" and "yum update" respectively. "CERT_GetDefaultCertDB" is now used to prevent a segmentation fault after the "yum clean all" and "yum update" sequence. (BZ#690273)
  • libcurl HTTPS connections failed with a CURLE_OUT_OF_MEMORY error when given a certificate file name without a "/". This is now fixed to treat such a string as certificate nickname and if a file with the same name exists and libcurl runs in verbose mode, a warning is issued. The updated documentation now suggests to use the "./" prefix to load a file from the current directory. (BZ#623663)
  • A rebuild operation for curl failed if the libnih-devel package was installed. This is now fixed to allow a rebuild whether libnih-devel is installed, not installed or has a broken installation. (BZ#669048)
  • libcurl ignored the CA path provided in CURLOPT_CAPATH and consequently curl ignored the "--capath" argument provided. This is fixed so that libcurl now uses the value provided with the the "--capath" argument. (BZ#669702)
  • libcurl leaked memory and eventually resulted in a failed NSS shutdown when more than one CA certificate was loaded. This is now fixed so that libcurl works as expected when more than one CA certificates is loaded. (BZ#670802)
  • libcurl leaked memory when an SSL connection failed. This is now fixed to prevent the memory leak during an SSL connection failure. (BZ#678594)
  • libcurl's FTP protocol implementation was unable to handle server session timeouts correctly. This is now fixed so that libcurl drops the connection when a 421 timeout response is received. (BZ#651592)
  • libcurl failed when an LDAP request was sent using curl through a HTTP proxy in tunnel mode (curl option "-p" or "--proxytunnel"). Curl tried to connect directly to the LDAP server via the proxy port and consequently failed. This is now fixed to allow libcurl LDAP connections through HTTP proxies to work as expected. (BZ#655134)
  • libcurl was unable to authenticate http proxies via Kerberos. This is now fixed and libcurl can successfully authenticate http proxies via Kerberos. (BZ#625685)
  • When libcurl connected a second time to an SSL server with the same server certificate, the server's certificate was not re-authenticated because libcurl confirmed authenticity before the first connection to the server. This is fixed by disabling the SSL cache when it is not verifying a certificate to force the verification of the certificate on the second use. (BZ#678580)
  • Kerberos authentication was broken for reused curl handles, which prevented "git clone"' from working with Kerberos authenticated web servers. This is now fixed to allow "git clone" operations to successfully authenticate and carry out operations. (BZ#684892)
  • It was not possible to use two distinct client certificates to connect two times in a row to the same SSL server. This is now fixed to allow two different client certifications to connect to the same SSL server. (BZ#694294)
Users of curl should upgrade to these updated packages, which contain back-ported patches to correct these issues. All running applications using libcurl must be restarted for the update to take effect.

1.35. cvs

1.35.1. RHSA-2010:0918: Moderate security update

An updated cvs package that fixes one security issue is now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
Concurrent Version System (CVS) is a version control system that can record the history of your files.
An array index error, leading to a heap-based buffer overflow, was found in the way CVS applied certain delta fragment changes from input files in the RCS (Revision Control System file) format. If an attacker in control of a CVS repository stored a specially-crafted RCS file in that repository, and then tricked a remote victim into checking out (updating their CVS repository tree) a revision containing that file, it could lead to arbitrary code execution with the privileges of the CVS server process on the system hosting the CVS repository. (CVE-2010-3846)
Red Hat would like to thank Ralph Loader for reporting this issue.
All users of cvs are advised to upgrade to this updated package, which contains a backported patch to correct this issue.

1.36. dapl

1.36.1. RHBA-2011:0354: bug fix and enhancement update

Updated dapl packages that fix several bugs and add provider entries to the dat.conf are now available.
dapl provides a userspace implementation of the DAT 2.0 API and is built to natively support InfiniBand and iWARP network technology.
This update addresses the following bugs:
  • Under certain error conditions dapl did not allow the cp_ptr entry to be cleaned up correctly in the internal link list. This could cause new connections to fail. With this update, the entry is cleaned up correctly and subsequent connections work as expected. (BZ#673989)
  • Under certain error conditions dapl could fail to free allocated memory. The consequent memory leak could, potentially, result in an out of memory condition for the application. This update frees allocated memory correctly, closing the leak. (BZ#673993)
  • Under certain circumstances, when a thread was waiting on dapls_evd_dto_wait() and the thread received a signal, the function would return an incorrect error code, resulting in the application failing rather than retrying the request. (BZ#675198)
  • On systems with multiple InfiniBand (IB) adapters, especially if some were configured and some not, the dat_ia_open() function could hang when the driver queried the IB devices listed in /etc/dat.conf. This primarily presented as IBM DB2 installations hanging before they completed. With this update, the dat_ia_open() hang has been fixed and IBM DB2 installations, in particular, now succeed as expected. (BZ#675205)
This update also adds the following enhancement:
  • New provider entries for Mellanox RDMA over Converged Ethernet (RoCE) devices were added to the dat.conf file. (BZ#675202)
Users should upgrade to these updated packages, which fix these issues.

1.36.2. RHBA-2011:0695: bug fix update

Updated dapl packages that fix multiple bugs are now available for Red Hat Enterprise Linux 6.
The dapl package provides a user space implementation of the DAT 2.0 API, and is built to natively support InfiniBand/iWARP network technology.
This update fixes the following bugs:
  • Under certain circumstances, when a thread was waiting on dapls_evd_dto_wait() and the thread received a signal, the function would return an incorrect error code, resulting in the application failing rather than retrying the request. (BZ#626541)
  • Previously, the function dapls_evd_dto_wait() returned, under certain circumstances, an error code when a thread was waiting on the function and the thread received a signal. Due to this behavior, the application failed. With this update, the application retries the request. (BZ#626541)
  • Red Hat Enterprise Linux 6 already supports a feature called "RoCE" (RDMA over converged Ethernet). Previously, applications that utilize uDAPL could not use the RDMA over converged Ethernet (RoCE) feature. This update adds these additional entries to the dat.conf file. (BZ#636596)
  • The dat_ia_open() function could, under under certain circumstances, fail to return. With this update, the function returns as expected. (BZ#649360)
  • Under certain circumstances dapl could fail to clean up its internal state, resulting in subsequent usage of the library to fail. With this update, the internal state is cleaned up as expected and the library can be used without further problems. (BZ#667742)
  • Previously, dapl could, under certain circumstances, fail to free allocated memory, potentially causing the application to run out of memory and fail. Now, dapl frees all allocated memory. (BZ#637980)
All dapl users should upgrade to these updated packages, which fix these bugs.

1.37. dbus

1.37.1. RHSA-2011:0376: Moderate security update

Updated dbus packages that fix one security issue are now available for Red Hat Enterprise Linux 5 and 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
D-Bus is a system for sending messages between applications. It is used for the system-wide message bus service and as a per-user-login-session messaging facility.
A denial of service flaw was discovered in the system for sending messages between applications. A local user could send a message with an excessive number of nested variants to the system-wide message bus, causing the message bus (and, consequently, any process using libdbus to receive messages) to abort. (CVE-2010-4352)
All users are advised to upgrade to these updated packages, which contain a backported patch to correct this issue. For the update to take effect, all running instances of dbus-daemon and all running applications using the libdbus library must be restarted, or the system rebooted.

1.38. device-mapper-multipath

1.38.1. RHBA-2011:0173: bug fix update

Updated device-mapper-multipath packages that resolve an issue are now available for Red Hat Enterprise Linux 6.
The device-mapper-multipath packages provide tools to manage multipath devices by giving the "dm-multipath" kernel module instructions on what to do, as well as by managing the creation and removal of partitions for Device-Mapper devices.
These updated device-mapper-multipath packages fix the following bug:
  • When all paths of a pathgroup with set group_by_prio were restored after a failure, multipathd could place some paths into a wrong pathgroup. This issue occurred, because the daemon checked if pathgroups needed reconfiguration only if a path priority changed. When the original paths were restored, they could have been assigned the same priority as before the failure. In such case the paths were incorrectly left in a wrong pathgroup. With this update, when checking if it needs to recalculate the pathgroups, the multipathd daemon refreshes and checks all priorities once a new path becomes available and places recovered paths into the correct pathgroup. (BZ#658937)
All users of device-mapper-multipath are advised to upgrade to these updated packages, which resolve this issue.

1.38.2. RHBA-2011:0294: bug fix update

Updated device-mapper-multipath packages that resolve an issue are now available for Red Hat Enterprise Linux 6.
The device-mapper-multipath packages provide tools to manage multipath devices by giving the "dm-multipath" kernel module instructions on what to do, as well as by managing the creation and removal of partitions for Device-Mapper devices.
These updated device-mapper-multipath packages fix the following bug:
  • Multipathd caches the value of sysfs attribute lookups for the path devices that make up a multipath device. Previously, these weren't being removed when the path devices were removed. As well, in some cases the cache was not helpful and not used. This occasionally caused memory leaks when path devices were removed and restored. With this update, the unnecessary caching has been completely removed and the cached values are now removed when the corresponding path device is removed. Consequently, the occasional memory leaks no longer occur. (BZ#672151)
All device-mapper-multipath users are advised to upgrade to these updated packages, which resolve this issue.

1.38.3. RHBA-2011:0384: bug fix update

Updated device-mapper-multipath packages that resolve an issue are now available for Red Hat Enterprise Linux 6.
The device-mapper-multipath packages provide tools to manage multipath devices by giving the "dm-multipath" kernel module instructions on what to do, as well as by managing the creation and removal of partitions for Device-Mapper devices.
These updated device-mapper-multipath packages fix the following bug:
  • Prior to this update, multipathd did not always remove a path's sysfs device from cache when the path was removed. Also, multipathd searched the cache and created sysfs devices without the 'vecs' lock held. As a result, paths would occasionally have invalid sysfs devices, causing multipathd crashes and other errors. With this update, multipathd always removes the sysfs device from cache when deleting the path, and it only accesses the cache with the 'vecs' lock held. (BZ#684684)
All users of device-mapper-multipath are advised to upgrade to these updated packages, which resolve this issue.

1.38.4. RHBA-2011:0725: bug fix and enhancement update

Updated device-mapper-multipath packages that fix several bugs and add various enhancements are now available for Red Hat Linux 6.
The device-mapper-multipath packages provide tools for multipath device management with the device-mapper multipath kernel module.
Bug fixes:
BZ#611779
If you sent the multipathd daemon a command consisting only of spaces, the daemon terminated unexpectedly with a segmentation fault. With this update, the daemon is able to handle such commands and no longer crashes in this circumstance.
BZ#635088
Prior to this update, the daemon occasionally grouped paths incorrectly because the multipathd daemon did not recalculate path groups when restoring paths. Now, when a new path goes online, the multipathd daemon verifies whether it needs to recalculate path groups, and refreshes and reads all priorities.
BZ#636071
Previously, if the user edited configuration information with the mpathconf command, the process could have failed. This happened when the user ran the command without any additional arguments due to a conflict of the environment variable DISPLAY with the program variable DISPLAY. With this update, all variables are unset when the script is started and the DISPLAY program variable is renamed. The environment variable DISPLAY remains unchanged when the mpathconf is issued and the command works as expected.
BZ#645605
The DM-Multipath application marked paths as failed if it was unable to determine if a path was offline. With this update, multipath calls the path_checker function to determine the path state in such cases and the problem no longer occurs.
BZ#650797
Previously, multipathd displayed no tgt_node_name value for iSCI devices. This occurred because multipath used the FC (Fibre Channel) path from the sysfs file system to obtain tgt_node_name for iSCI devices. With this update, multipath first tries to acquire the FC path. If it fails, it uses the iSCI target name for the device.
BZ#651389
Previously, if you set dev_loss_tmo to a value greater than 600 in multipath.conf without setting the fast_io_fail_tmo value, the multipathd daemon failed to apply the setting. With this update, the multipathd daemon sets dev_loss_tmo for values over 600 correctly, as long as fast_io_fail_tmo is also set in the /etc/multipath.conf file.
BZ#662731
DM-Multipath could have terminated unexpectedly if the multipath.conf file contained parameters with no value. This occurred because it was trying to acquire the string length of an optional value before verifying that a value was actually defined. With this update, multipathd first checks if the value exists and the bug is fixed.
BZ#622569
On a non-disruptive upgrade (NDU), all paths to EMC Symmetrix arrays could have failed, which caused multipathd to fail all outstanding input/output. DM-Multipath now has a new default configuration for EMC Symmetrix arrays that queues input/output for up to 30 seconds if all paths are down and the problem no longer occurs.
BZ#623644
The multipathd daemon consumed excessive memory when iSCI devices were unloaded and reloaded. This occurred because the daemon was caching unnecessary sysfs data, which caused memory leaks. With this update, multipathd no longer caches these data; it frees the data when the associated device is removed.
BZ#680480
During a double path failure, the sysfs device file is removed and the sysdev path attribute is set to NULL. The sysfs device cache is indexed by the actual sysfs directory, and /sys/block/pathname is a symlink. Prior to this update, if the path was deleted, multipathd was not able to find the actual directory, which /sys/block/pathname pointed to, and searched the cache. With this update, multipathd verifies that sysdev has NULL value before updating it.
BZ#681144
When a path was removed, the multipathd daemon did not always remove the path sysfs device from its cache. The daemon kept searching the cache for the device and created sysfs devices without the vecs lock held. Because of this, paths could have pointed to invalid sysfs devices and caused multipathd to crash. The multipathd daemon now always removes the sysfs device from cache when deleting a path and accesses the cache only with the vecs lock held.
Enhancements:
BZ#576919
The log_checker_err option was added to the multipath.conf defaults section. By default, the option is set to always and a path checker error is logged continuously. If set to once, multipathd logs a path checker error once at logging level 2. Any later errors are logged at level 3 until the device is restored.
BZ#599690
Previously, the defaults section of the multipath.conf man page implied that the settings defined in the section became default and overrode the implied settings. Since the HWTABLE cannot be overridden, the wording of the man page has been changed.
BZ#628095
Previously, DM-Multipath did not print any messages when errors were detected in the multipath.conf file. With this update, multipath prints warning messages that inform the user that the configuration files contains invalid or duplicate options and the bug is fixed.
BZ#632734
This update adds the default configuration for Virtual SCSI disks.
BZ#633643
This update adds the default configuration for NEC Storage M .
BZ#636213
This update adds the default configuration for HP P2000 .
BZ#636246
This update adds the default configuration for HP OPEN devices.
BZ#644111
If the initramfs file system was not rebuilt when a new storage device was added to the system, the new device could have been assigned a user_friendly_names value that matched the user_friendly_names value already-assigned to another device. This device then stopped working correctly. The multipathd daemon now accepts a -B option, which makes the user_friendly_names bindings file read-only. When initramfs calls multipath with the -B option, devices without a binding to a user_friendly_names use their World Wide Identifier (WWID).
BZ#650664
Previously, the DM-Multipath did not prompt the user to increase the maximum number of open file descriptors (max_fds) if it failed to open a file descriptor due to receiving an EMFILE error. With this update, it prints out a message advising the user to do so.
BZ#602883
Previously, the multipathd deamon printed add map messages whenever it received a change uevent. In order not to clutter logs, multipathd now only prints add map messages for the change uevents of the devices that are not yet monitored.
BZ#639037
Previously, DM-Multipath did not set a default value for the no_path_retry parameter for Hitachi R700 devices. With this update, the parameter value for the devices is set to 6 by default.
BZ#696157
The multipathd daemon could have terminated unexpectedly with a segmentation fault on a multipath device with the path_grouping_policy option set to the group_by_prio value. This occurred when a device path came online after another device path failed because the multipath daemon did not manage to remove the restored path correctly. With this update multipath removes and restores such paths correctly.
Users are advised to upgrade to these updated device-mapper-multipath packages, which resolve these issues and add these enhancements.

1.39. dhcp

1.39.1. RHSA-2011:0428: Important security update

Updated dhcp packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6.
The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The Dynamic Host Configuration Protocol (DHCP) is a protocol that allows individual devices on an IP network to get their own network configuration information, including an IP address, a subnet mask, and a broadcast address.
It was discovered that the DHCP client daemon, dhclient, did not sufficiently sanitize certain options provided in DHCP server replies, such as the client hostname. A malicious DHCP server could send such an option with a specially-crafted value to a DHCP client. If this option's value was saved on the client system, and then later insecurely evaluated by a process that assumes the option is trusted, it could lead to arbitrary code execution with the privileges of that process. (CVE-2011-0997)
Red Hat would like to thank Sebastian Krahmer of the SuSE Security Team for reporting this issue.
All dhclient users should upgrade to these updated packages, which contain a backported patch to correct this issue.

1.39.2. RHSA-2010:0923: Moderate security update

Updated dhcp packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The Dynamic Host Configuration Protocol (DHCP) is a protocol that allows individual devices on an IP network to get their own network configuration information, including an IP address, a subnet mask, and a broadcast address. DHCPv6 is the DHCP protocol version for IPv6 networks.
A NULL pointer dereference flaw was discovered in the way the dhcpd daemon parsed DHCPv6 packets. A remote attacker could use this flaw to crash dhcpd via a specially-crafted DHCPv6 packet, if dhcpd was running as a DHCPv6 server. (CVE-2010-3611)
Users running dhcpd as a DHCPv6 server should upgrade to these updated packages, which contain a backported patch to correct this issue. After installing this update, all DHCP servers will be restarted automatically.

1.39.3. RHSA-2011:0256: Moderate security update

Updated dhcp packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The Dynamic Host Configuration Protocol (DHCP) is a protocol that allows individual devices on an IP network to get their own network configuration information, including an IP address, a subnet mask, and a broadcast address. DHCPv6 is the DHCP protocol version for IPv6 networks.
A flaw was found in the way the dhcpd daemon processed certain DHCPv6 messages for addresses that had previously been declined and marked as abandoned internally. If a remote attacker sent such messages to dhcpd, it could cause dhcpd to crash due to an assertion failure if it was running as a DHCPv6 server. (CVE-2011-0413)
Red Hat would like to thank Internet Systems Consortium for reporting this issue.
Users running dhcpd as a DHCPv6 server should upgrade to these updated packages, which contain a backported patch to correct this issue. After installing this update, all DHCP servers will be restarted automatically.

1.39.4. RHBA-2011:0697: bug fix and enhancement update

Updated dhcp packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6.
The Dynamic Host Configuration Protocol (DHCP) is a protocol that allows individual devices on an IP network to get their own network configuration information, including an IP address, a subnet mask, and a broadcast address. DHCPv6 is the DHCP protocol version for IPv6 networks.
This update fixes the following bugs:
  • Previously, it was impossible to configure the dhcrelay service to run the dhcrelay daemon with additional arguments. With this update, a DHCRELAYARGS variable is available for the /etc/sysconfig/dhcrelay configuration file, which allows additional arguments to be passed to the dhcrelay daemon properly. (BZ#625846)
  • Previously, the dhclient utility did not log its PID (process identifier) in syslog entries, making troubleshooting in systems with multiple running dhclients difficult. Now, the dhclient utility logs its PID properly. (BZ#627257)
  • Previously, the dhclient utility sometimes parsed date strings in lease files incorrectly, resulting in syntax error messages in its output. This bug has been fixed and the dates in the lease files are now parsed with no error messages given. (BZ#631071)
  • When the dhclient utility was updating a "search" entry in the /etc/resolv.conf file, it sometimes did not add a missing domain part. This was inconsistent with NetworkManager behavior. Now, while updating the "search" entry, the dhclient utility always adds the domain part of the host name given to the client if it is missing. (BZ#637763)
  • Previously, the dhcpd service with IPv6 support sometimes created a lease file that it was unable to parse. Consequently, once the service was restarted, it went into a loop and could not start. This bug has been fixed and now the service is able to properly parse all lease files it generates. (BZ#672551)
  • DHCP servers at some ISPs send to clients the "interface-mtu" option with the value of 576. Such a low MTU (Maximum Transmission Unit) can cause throughput problems with UDP traffic, among other things. With this update, the dhclient utility now sets the interface MTU only if the value obtained from the server is higher than 576. (BZ#681721)
  • Previously, the dhclient package was missing its LICENSE file. With this update, the file has been added. (BZ#613683)
This update adds the following enhancements:
  • The dhcp package now provides an implementation of Classless Static Route Options for DHCPv4 (RFC 3442). It can supply network route configuration to a large number of hosts without individual configuration of each one. (BZ#558641)
  • The dhcp package now provides support for IPoIB (IP over InfiniBand) interfaces. (BZ#660681)
Users of dhcp are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

1.40. dovecot

1.40.1. RHSA-2011:0600: Moderate security and enhancement update

Updated dovecot packages that fix two security issues and add one enhancement are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
Dovecot is an IMAP server for Linux, UNIX, and similar operating systems, primarily written with security in mind.
A flaw was found in the way Dovecot handled SIGCHLD signals. If a large amount of IMAP or POP3 session disconnects caused the Dovecot master process to receive these signals rapidly, it could cause the master process to crash. (CVE-2010-3780)
A flaw was found in the way Dovecot processed multiple Access Control Lists (ACL) defined for a mailbox. In some cases, Dovecot could fail to apply the more specific ACL entry, possibly resulting in more access being granted to the user than intended. (CVE-2010-3707)
This update also adds the following enhancement:
  • This erratum upgrades Dovecot to upstream version 2.0.9, providing multiple fixes for the "dsync" utility and improving overall performance. Refer to the "/usr/share/doc/dovecot-2.0.9/ChangeLog" file after installing this update for further information about the changes. (BZ#637056)
Users of dovecot are advised to upgrade to these updated packages, which resolve these issues and add this enhancement. After installing the updated packages, the dovecot service will be restarted automatically.

1.41. dracut

1.41.1. RHBA-2010:0877: bug fix update

Updated dracut packages that fix a bug are now available for Red Hat Enterprise Linux 6.
The dracut package is an event-driven initramfs generator infrastructure based around udev. The initramfs is loaded together with the kernel at boot time and initializes the system, so it can read and boot from the root partition.
This update fixes the following bug:
  • Prior to this update, the udev rules used by dracut may have caused the merged logical volume management (LVM) snapshots to be accessed. Consequent to this, I/O errors appeared in the log. With this update, dracut's internal udev rules have been updated to ignore those internal devices, and dracut now works as expected. (BZ#651402)
Users of dracut are advised to upgrade to these updated packages, which resolve this issue.

1.41.2. RHEA-2011:0141: enhancement update

Updated dracut packages that add an enhancement are now available for Red Hat Enterprise Linux 6.
The dracut packages provide an event-driven initramfs generator infrastructure based around udev. The initramfs is loaded together with the kernel at boot time and initializes the system, so it can read and boot from the root partition.
This update adds the following enhancement:
  • The dracut packages have been updated to support the new kernel boot option, "rdinsmodpost=[module]", which allows a user to specify a kernel module to be loaded after all device drivers are loaded automatically. (BZ#661298)
Users of dracut are advised to upgrade to these updated packages, which add this enhancement.

1.41.3. RHBA-2011:0523: bug fix and enhancement update

Updated dracut packages that fix several bugs and add some enhancements are now available for Red Hat Enterprise Linux 6.
The dracut package is an event-driven initramfs generator infrastructure based around udev. The initramfs is loaded together with the kernel at boot time and initializes the system, so it can read and boot from the root partition.
Bug fixes:
BZ#595096
When attempting to boot with MD RAID, udev issued error messages about a missing label because dracut was in the process of rewriting the udev rules files while udev attempted to parse them. dracut now creates temporary rules files, and creates a file for udev's use when the file is considered complete.
BZ#610466
Running mkinitrd alone does not override an existing initramfs image. When this is attempted, the message stated that the --force parameter should be used, but mkinitrd only supported the short version -f of this parameter. --force was added to mkinitrd as the long version.
BZ#626389
When booting an IMSM/ISW RAID with dmraid, the mdadm package must be added to a system that has a kickstart minimal install with the noiswmd or rd_NO_MDIMSM parameters specified.
BZ#630911
When multipath is configured to use user-friendly names, it stores the binding between the wwid and the alias in /etc/multipath/bindings. multipath uses this file in initramfs when creating devices during early boot, and in the root file system during normal operation. These files were not synchronized during initramfs creation, which resulted in naming conflicts that prevented new multipath devices from being created after boot. To work around this, the bindings for the devices in /etc/multipath/bindings must be included in the initramfs. This can be done by running dracut -f.
BZ#636668
dracut did not include all multipath configuration files needed for multipath to include the root device in the multipath listing. dracut now copies over the entire /etc/multipath directory to the initramfs.
BZ#640979
dracut used all network configuration parameters from the kernel command line, but did not honor any configuration settings in the iBFT. dracut now parses the iBFT settings to set up the network if the ip=ibft parameter is specified on the kernel command line.
BZ#642083
dracut did not include multipath in the generated generic initramfs, if the host on which it was running had no multipath root device. multipath support is now added to the initramfs unconditionally.
BZ#645799
Previously, dracut had a hard-wired dependency on vconfig; this dependency is no longer required, and has been removed.
BZ#650959
When operating with LVM snapshot volumes, I/O errors could occur because the udev rules in the initramfs did not exclude those volumes and kept them busy. The udev rules in the initramfs were updated to honor the DM_UDEV_DISABLE_OTHER_RULES_FLAG, which fixes this issue.
BZ#669438
cryptsetup was required to perform verification when a system attempted to run in FIPS mode. However, the verification check failed because several checksum files were missing from initramfs, which resulted in all encrypted devices not being activated. The missing checksum files have been replaced, and this issue no longer occurs. Note however that the dracut-fips must be installed at initramfs creation time.
BZ#674238
When multipath ran in the initramfs with user_friendly_names set, if it did not find existing mappings in /etc/multipath/bindings, it created new mappings. These mappings could conflict with the user_friendly_names set in the normal filesystem's /etc/multipath/bindings file. dracut now starts the multipathd daemon with the new -B option so that multipath treats the initial bindings file as read-only.
BZ#675118
The USE_BIOSDEVNAME variable in the parse-biosdevname.sh script was not initialized correctly, which caused an unexpected operator error. This issue was discovered and corrected during development, and did not occur in any production system in the field.
BZ#676018
If a user started dracut with the -l or --local parameter, or set the dracut base directory via the dracutbasedir environment variable, dracut wrote its log to /tmp/dracut.log, which could possibly allow local users to overwrite arbitrary files that were writable to the user running dracut, via a symlink attack. dracut now stores the logfile in $HOME/dracut.log, when in -l or --local mode, if /var/log/dracut.log is not writeable.
BZ#678294
The /var/log/dracut.log file was not created automatically, preventing dracut from writing its logs. dracut now creates its log files if they do not exist.
BZ#691419
The boot parameter did not work when the machine was booted in FIPS mode, resulting in numerous mount errors, failed FIPS integrity tests, and dracut refusing to continue. This issue has been corrected, and the boot parameter can now be used to specify a boot device, as expected.
BZ#692843
If FIPS mode is enabled and the root partition is encrypted, /boot must reside on a non-encrypted, plain (no LVM or RAID) partition, which can be specified with boot=<boot partition> as a boot option on the kernel command line.
BZ#692939
After installing to a remote logical unit via Fibre Channel over Ethernet (FCoE), the root device could not be found, resulting in kernel panic. This occurred because the MAC address and interface for the FCoE device was not defined correctly. Installing to a remote logical unit via FCoE now works.
BZ#696131
The fips.sh script did not wait for the boot drive to be created, which resulted in an error because the file system type did not exist yet. This has been corrected, and the script now waits for the boot drive to be identified.
Enhancements:
BZ#634013
Previously all information about the network interfaces to boot from was read from the kernel command line. dracut was extended to use network interface configuration from the OptionROM, if fcoe=edd:nodcb or fcoe=edd:dcb is specified on the kernel command line. ifname= is not needed in this case.
BZ#645648
dracut has been updated to support the new kernel boot option, rdinsmodpost=[module], which allows a user to specify a kernel module to be loaded after all device drivers are loaded automatically.
BZ#670925
dracut now includes the kernel module aes-xts in the initramfs, adding support for FIPS-140.
BZ#677340
A new module, dracut-caps has been added to let users omit selected dracut capabilities, and set one or more sysctl parameters.
BZ#689694
Support has been added for the Emulex Tiger Shark adapter for iSCSI.
BZ#692781
Support for several Broadcom drivers (bnx2, bnx2x and bnx2i) has been added to dracut-network.
All users of dracut are advised to upgrade to these updated packages, which resolve these issues.

1.42. e2fsprogs

1.42.1. RHBA-2011:0702: bug fix and enhancement update

Updated e2fsprogs packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6.
The e2fsprogs packages contain a number of utilities that create, check, modify, and correct inconsistencies in ext2, ext3, and ext4 file systems. This includes e2fsck (which repairs file system inconsistencies after an unclean shutdown), mke2fs (which initializes a partition to contain an empty file system), tune2fs (which modifies file system parameters), and most of the other core file system utilities.
Bug fixes:
BZ#489842
When lsattr or chattr was pointed at a non-existent file, an error was returned in that the exit code was always zero. This was because ls reported an error if any occurred, and lsattr did the same, reporting the last error encountered. This patch fixes this error, and lsattr and chattr provide the correct error.
BZ#491385
After using resize2fs to perform an offline resize of a file system, running e2fsck gave an error, stating the wrong block count for the resize inode. This was because the resize inode was not being properly cleared. This patch checks to see if the file system has grown to the point where the resize_inode is no longer needed, then cleans it so e2fsck does not have to. The correct block count is now given for the resize inode.
BZ#506643
Previously, e2fsprogs libblkid probe_all() could mismatch devices when scanning whole disks without partitions where the name ended in a number. This caused a mount failure. With this patch these disks are also scanned, so the devices are mounted correctly.
BZ#553216
When a host was re-kickstarted, mpath mounts with LABEL failed with the error “mount: /dev/sdk already mounted or /san/intf busy”. This was because the probe_one() function scanned /dev before /dev/mapper. This patch disables all calls from libdevmapper via #undef HAVE_DEVMAPPER, instead using the standard support for “normal” non-dm devices. This results in mpath can mount without errors.
BZ#562044
Running “e2fsck -y -f” on a corrupted file system printed errors even after “e2fsck -y” had previously reported the file system to be clean. This occurred when a file had its i_file_acl block cloned as a duplicate. This duplicate was then cleared because the file system did not have the xattr feature, and the inode was subsequently removed due to an invalid mode. The second e2fsck pass found the cloned xattr block in use but not owned by any file, so had to fix up the block bitmaps. This patch fixes an existing brace misalignment and skips the processing of the duplicat xattr blocks on a non-xattr file system, as these will be cleaned at a later point, allowing the clean to occur properly.
BZ#579836
On 64-bit systems, a sign extension bug in libcom_err caused incorrect error messages to be emitted. This was because an error code as an (int) was passed to error_message as an (unsigned int), especially when using libgssapi_krb5. This meant that error_message() failed to find a matching error table. To fix this, error_message() has been changed to follow the same method error_table_name() does when error_message() calls it. That is, it drops most of the higher bits of the parameter passed before continuing, so now correct error messages are emitted.
BZ#580671
A sparse journal (which indicates corruption) was not fixed by e2fsck, causing file system errors and a shut down after mount. This was because e2fsck marked the file system as clean so it would mount, but did not fix that block, so when the journal reached this point again it failed once more. This patch changes process_journal_block() to clear and recreate the journal inode if it is sparse, that is if it gets block 0, allowing e2fsck to correctly fix a sparse journal.
BZ#606757
Previously, chattr and lsattr would return “error code = 0” even when they have not done anything, which made error checking difficult in scripts. With this patch, if there are errors they will be reported with a non-zero exit code. It will give explicit errors when attempting to set files that are not files or directories (which are not currently supported under Linux). Also, the -f flag will suppress error messages from being printed even though the exit status will still be non-zero.
BZ#607843
When checking a particular volume, e2fsck exited with a signal 11 (segmentation fault). This was caused by floating point errors. This patch edits get_icount_el to prevent point precision errors on large file systems from causing the search interpolation algorithm from performing an infinite loop, allowing e2fsck to check the volume correctly.
BZ#618134
The fsck command returned a 0 status instead of an appropriate error code on an exec() failure, due to an error in the code. This patch fixes the error so that the appropriate error code is now returned.
BZ#637920
Previously, blkid cachine caused a tag search (blkid -l -t ...) to return empty results. This occurred mostly in debug code, where dev->bid_type is not-NULL before dereferencing the pointer. This has been edited and blkid cachine now returns proper results.
BZ#669676
Previously, e2fsprogs failed to build with newer gettext package. This was due to a problem in auto-fu. This patch fixes this allowing the packages to build correctly.
BZ#675694
If more than 128 devices were specified on the blkid command line, the devices[] array overflowed, resulting in a crash. This patch avoids the problem by dynamically allocating the devices[] array based on the number of arguments, resulting in more than 128 devices being able to be specified on the blkid command line.
BZ#696930
Running blkid on IBM System z caused a crash with a signal 11 (segmentation fault) error. This was due to an error in the code regarding floating points. This patch frees a pointer that was not initialized to null, allowing blkid to run correctly on IBM System z.
BZ#678304
It was possible for the UUIDD to generate duplicate UIDs under certain circumstances. This occurred when the socket backlog in the UUIDD daemon was full, therefore the connection was refused and uuid_generate_time() fell back to unsafe ways of generating a UUID, resulting in the duplicates. Also, fcntle(2) did not work for the synchronization of threads belonging to the same process, contributing to the problem. This patch introduces a safe variant of uuid_generate_time() and fixes the locking of the clock state counter file which prevents UUIDD from generating duplicate UIDs.
BZ#681071
Running e2fsck on a corrupted file system gave a “should never happen” error. This occurred when a directory with an htree index had an incorrect and too-large i_size field. This patch prevents e2fsck from crashing and prompts the user to remove the htree index so that it can be rebuilt after pass 3, allowing file systems with this error to be fixed.
Enhancements:
BZ#563909
When running blkid, stale mounts can occasionally be seen within the cache. While running blkid -c /dev/null gets around this, it can become a runtime issue when blkid is run against a machine with several hundred disks. As such this patch adds a garbage collection routine feature. This performs a garbage collection pass on the /etc/blkid.tab file by adding the -g option to the blkid program. The man page has also been updated with more information about what the -g garbge collection option does.
BZ#587778
The mkfs reserved blocks were originally set to 5% by default, with a 1% step size. This was considered excessive for large file systems. With this patch, the reserved blocks amount now accepts a floating point for better accuracy when setting the percent. Also, mke2fs and tune2fs now accept a floating point number from the user to improve the level of accuracy offered.
All users are advised to upgrade to these updated packages, which resolve these issues and include these enhancements.

1.43. ebtables

1.43.1. RHEA-2011:0556: enhancement update

An enhanced ebtables package is now available.
Ethernet bridge tables is a firewalling tool to transparently filter network traffic passing a bridge. The filtering possibilities are limited to link layer filtering and some basic filtering on higher network layers.
Auditing support is added to create a kernel audit record that records the information flow between a host, guest, and other network entities. (BZ#642394)
All users requiring firewalling for Ethernet bridge tables are advised to upgrade to this updated package, which adds this enhancement.

1.44. eclipse

1.44.1. RHSA-2011:0568: Low security, bug fix, and enhancement update

Updated eclipse packages that fix one security issue, several bugs, and add various enhancements are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having low security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The Eclipse software development environment provides a set of tools for C/C++ and Java development.
A cross-site scripting (XSS) flaw was found in the Eclipse Help Contents web application. An attacker could use this flaw to perform a cross-site scripting attack against victims by tricking them into visiting a specially-crafted Eclipse Help URL. (CVE-2010-4647)
The following Eclipse packages have been upgraded to the versions found in the official upstream Eclipse Helios SR1 release, providing a number of bug fixes and enhancements over the previous versions:
In addition, the following updates were made to the dependencies of the Eclipse packages above:
This update includes numerous upstream bug fixes and enhancements, such as:
  • The Eclipse IDE and Java Development Tools (JDT):
    • projects and folders can filter out resources in the workspace
    • new virtual folder and linked files support.
    • the full set of UNIX file permissions is now supported.
    • addition of the stop button to cancel long-running wizard tasks.
    • Java editor now shows multiple quick-fixes via problem hover.
    • new support for running JUnit version 4 tests.
    • over 200 upstream bug fixes.
  • The Eclipse C/C++ Development Tooling (CDT):
    • new Codan framework has been added for static code analysis.
    • refactoring improvements such as stored refactoring history.
    • compile and build errors now highlighted in the build console.
    • switch to the new DSF debugger framework.
    • new template view support.
    • over 600 upstream bug fixes.
This update also fixes the following bugs:
  • Incorrect URIs for GNU Tools in the "Help Contents" window have been fixed. (BZ#622713)
  • The profiling of binaries did not work if an Eclipse project was not in an Eclipse workspace. This update adds an automated test for external project profiling, which corrects this issue. (BZ#622867)
  • Running a C/C++ application in Eclipse successfully terminated, but returned an I/O exception not related to the application itself in the Error Log window. With this update, the exception is no longer returned. (BZ#668890)
  • The eclipse-mylyn package showed a "20100916-0100-e3x" qualifier. The qualifier has been modified to "v20100902-0100-e3x" to match the upstream version of eclipse-mylyn. (BZ#669819)
  • Installing the eclipse-mylyn package failed and returned a "Resource temporarily unavailable" error message due to a bug in the packaging. This update fixes this bug and installation now works as expected. (BZ#673174)
  • Building the eclipse-cdt package could fail due to an incorrect interaction with the local file system. Interaction with the local file system is now prevented and the build no longer fails. (BZ#678364)
  • The libhover plug-in, provided by the eclipse-cdt package, used binary data to search for hover topics. The data location was specified externally as a URL which could cause an exception to occur on a system with no Internet access. This update modifies the plug-in so that it pulls the needed data from a local location. (BZ#679543)
Users of eclipse should upgrade to these updated packages, which correct these issues and add these enhancements.

1.45. edac-utils

1.45.1. RHBA-2011:0768: bug fix and enhancement update

Updated edac-utils packages that fix one bug and add one enhancement are now available for Red Hat Enterprise 6.
EDAC is the current set of drivers in the Linux kernel that handles detection of ECC errors from memory controllers for most chipsets on the x86, AMD64, and Intel 64 architectures. The user-space component consists of an initscript which ensures that EDAC drivers and DIMM labels are loaded at system startup, as well as a library and utility for reporting current error counts from the EDAC sysfs files.
This update fixes the following bug:
  • Previously, the edac-utils initscript did not use the standard error codes of other initscripts because several mandatory actions were missing. This update implements the initscript actions "condrestart", "try-restart", "force-reload" and sets the return values for each action accordingly. Now, the initscript uses the standard error code. (BZ#632665)
This update also adds the following enhancement:
  • This update extends the maximum number of channels from 2 to 6, in order to allow it to work with some designs that have 4 channels on FB-DIMM motherboards, e.g. the ones with Intel 7300 chipset. By default, this update identifies the motherboard via BIOS DMI board information. If not available, it will fallback to use DMI system information. (BZ#640113)
Note: the improvements from upstream version 0.16 are now added to edac-utils, including new motherboard labels, an option to delay the motherboard write labels, and a better parser to retrieve memory and vendor information from the system.
All EDAC users are advised to upgrade to these updated packages, which fix this bug and add this enhancement.

1.46. efibootmgr

1.46.1. RHBA-2011:0674: bug fix update

An updated efibootmgr package that fixes one bug is now available for Red Hat Enterprise Linux 6.
The efibootmgr utility is responsible for the boot loader installation on Unified Extensible Firmware Interface (UEFI) systems.
This update fixes the following bug:
  • Due to missing support for 4KB disk sectors, an attempt to use the efibootmgr utility to create a boot option on such a device caused the utility to fail with the following error message:
    Error: no partition information on disk [device].
    Cowardly refusing to create a boot option.
    
    This update adapts the efibootmgr utility to provide support for 4KB disk sectors, resolving this issue. (BZ#612280)
All users of efibootmgr are advised to upgrade to this updated package, which fixes this bug.

1.47. elfutils

1.47.1. RHBA-2011:0578: bug fix update

Updated elfutils packages that resolve an issue are now available.
The elfutils package contains utilities and libraries for working with compiled binary files. Its libraries are used by the SystemTap instrumentation system found in the systemtap package.
These updated elfutils packages fix the following bug:
  • After prelink had been run on the system, using SystemTap user-space probes that targeted functions or statements in certain shared libraries, or executables based on a separate debuginfo file, caused resolution to the wrong PC location in a linked binary. As a result, the intended probes failed to fire at the correct place in the program, which could have caused the program to crash or misbehave due to a corrupted instruction sequence resulting from incorrect breakpoint insertions. With this update, the libdwfl library code (the libdw.so shared object library) was adjusted to use a more reliable method of compensating for prelink's effect on the address layout of a binary when aligning a runtime PC address with an address computed separately from the separated debuginfo file. SystemTap probes should now work the same on prelinked binaries as they would on binaries that have not been prelinked. (BZ#652858)
All users of SystemTap and elfutils are advised to upgrade to these updated packages, which resolve this issue.

1.48. emacs

1.48.1. RHBA-2011:0717: bug fix update

Updated emacs packages that fix two bugs are now available for Red Hat Enterprise Linux 6.
GNU Emacs is a powerful, customizable, self-documenting text editor. It provides special code editing features, a scripting language (elisp), and the capability to read email and news.
This update fixes the following bugs:
  • Prior to this update, Emacs incorrectly displayed Japanese documents using JIS X 0213:2004 (JIS2004) compliant fonts, even though other parts of the system prefer and use older fonts. This update lowers the priority of JIS X 0213:2004 to ensure the consistent use of fonts in the system. (BZ#612385)
  • Previously, the emacs packages required the aspell and hunspell spell checkers to be installed. Since the use of a spell checker is completely optional, this update removes aspell and hunspell from the list of dependencies, so that Emacs can now be installed without these packages. (BZ#613759)
All users of emacs are advised to upgrade to these updated packages, which fix these bugs.

1.49. epydoc

1.49.1. RHBA-2011:0316: bugfix update

An updated epydoc package that fixes a bug is now available for Red Hat Enterprise Linux 6.
Epydoc is a tool for generating API documentation for Python modules, based on their docstrings. A lightweight markup language called epytext can be used to format docstrings, and to add information about specific fields, such as parameters and instance variables. Epydoc also understands docstrings written in ReStructuredText, Javadoc and plaintext.
This update fixes the following bug:
  • Previously, the summary extractor of reStructuredText did not work properly and the documentation process failed. Due to this behavior, building packages could fail. This update resolves this problem. Packages now build successfully. (BZ#657567)
All users of epydoc are advised to upgrade to this updated package, which resolves this issue.

1.50. evince

1.50.1. RHSA-2011:0009: Moderate security update

Updated evince packages that fix multiple security issues are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
Evince is a document viewer.
An array index error was found in the DeVice Independent (DVI) renderer's PK and VF font file parsers. A DVI file that references a specially-crafted font file could, when opened, cause Evince to crash or, potentially, execute arbitrary code with the privileges of the user running Evince. (CVE-2010-2640, CVE-2010-2641)
A heap-based buffer overflow flaw was found in the DVI renderer's AFM font file parser. A DVI file that references a specially-crafted font file could, when opened, cause Evince to crash or, potentially, execute arbitrary code with the privileges of the user running Evince. (CVE-2010-2642)
An integer overflow flaw was found in the DVI renderer's TFM font file parser. A DVI file that references a specially-crafted font file could, when opened, cause Evince to crash or, potentially, execute arbitrary code with the privileges of the user running Evince. (CVE-2010-2643)
Note: The above issues are not exploitable unless an attacker can trick the user into installing a malicious font file.
Red Hat would like to thank the Evince development team for reporting these issues. Upstream acknowledges Jon Larimer of IBM X-Force as the original reporter of these issues.
Users are advised to upgrade to these updated packages, which contain a backported patch to correct these issues.

1.51. evolution

1.51.1. RHBA-2011:0714: bug fix update

Updated evolution packages that fix various bugs are now available for Red Hat Enterprise Linux 6.
Evolution is the GNOME email, calendar, contact management and communications application. The components which make up Evolution are tightly integrated with one another and act as a seamless personal information-management (PIM) tool.
This update fixes the following bugs:
  • When a user tried to migrate their mail folder settings after upgrading to Red Hat Enterprise Linux 6, or restore a backup from the previous version of Evolution, Evolution sometimes terminated unexpectedly. This bug has been fixed and no longer occurs during the migration process. (BZ#696881)
  • When a user created or edited a task in Evolution, the tooltip for the print icon in the toolbar was missing. This tooltip has been added and is now correctly displayed when hovering over the print icon. (BZ#585931)
  • When printing the "Day" view of a calendar in Evolution to a Postscript file, the selected day and month name overlapped the line below. The issue has been resolved; overlaps no longer take place. (BZ#628964)
  • When a user selected the "Submit bug report" option in the "Help" menu, a spurious "Bug Buddy is not installed" error message appeared. Because Bug Buddy is not a component of Red Hat Enterprise Linux 6, the menu option to submit a bug was removed. (BZ#632968)
  • When creating a mail account in the Evolution Account Assistant using the POP protocol, the keyboard shortcut for "Delete after 7 days" (Alt+D) did not work. With this update, the GUI widget accepts the keyboard shortcut for the "Delete after 7 days" functionality and entering the shortcut now works as expected. (BZ#633600)
  • The "Create a Memo" item from the "Message" menu was active when it was not supposed to be. As a consequence, Evolution terminated unexpectedly when the user selected this item. With this update, the "Create a Memo" item is deactivated when it is supposed to be, with the result that the user can no longer crash Evolution by selecting it. (BZ#633629)
  • When viewing an email message larger than the maximum value defined in the settings Edit -> Preferences -> Mail Preferences -> "Do not format messages when text size exceeds [n KB]" caused Evolution to terminate unexpectedly. This bug has been fixed and viewing a message larger than the set value no longer causes Evolution to crash. (BZ#666875)
  • When a user created a calendar meeting in Evolution with at least 16 attendees and right-clicked "Reply to all", the application terminated unexpectedly sometimes. The problem was with the reallocation of memory in glib2 and it has been fixed. Replying to all attendees of a calendar meeting now works as expected. (BZ#667083)
  • When a user clicked into the input field under the Summary header in Task or Memo section in Evolution, and switched its input method to any language managed by ibus (such as Chinese), foreign characters could not be entered. The fix involves calling some functions in the correct order so the events for the input method are registered properly. (BZ#633189)
  • When using one of four Asian locales (ml_IN, hi_IN, ta_IN, zh_TW), the following problems occurred in Evolution Assistant: differing translations for the label and button "Forward" and "Finish", a missing and erroneous translation for the "Forward" label, and the ZWJ/ZWNJ characters visible by mistake. With this update, corrected translations has been provided. (BZ#628882, BZ#630316, BZ#632998, BZ#638643)
  • In the "Evolution Appointment" dialog, when using the Chinese Simplified locale (zh_CN), there was an erroneous translation on the "for" button. The translation has been modified and Evolution now displays a proper button text translation. (BZ#633181)
Users are advised to upgrade to these updated packages, which fix these bugs and correct several localization issues.

1.52. evolution-data-server

1.52.1. RHBA-2011:0713: bug fix update

An updated evolution-data-server package that fixes several bugs is now available.
The evolution-data-server package provides a unified back end for applications which interact with contacts, task and calendar information. Evolution Data Server was originally developed as a back end for Evolution, but is now used by various other applications.
This updated evolution-data-server package provides fixes for the following bugs:
  • cannot enter date in New->Appointment dialog with or_IN language (BZ #629919)
  • crash when using Google address book (BZ #634949)
  • folder unread count doesn't update properly on search folders (BZ #657117)
  • crash when receiving On The Web calendar items (BZ #660356)
  • crash when adding contact to a contact list (BZ #666879)
Users are advised to upgrade to this updated evolution-data-server package, which resolves these issues.

1.53. evolution-mapi

1.53.1. RHBA-2011:0800: bug fix update

An updated evolution-mapi package that fixes a crash is now available.
The MAPI extension for Evolution (evolution-mapi) allows Evolution to interact with MS Exchange 2007 servers.
This package fixes the following bug:
  • When accessing an address book on an Exchange 2007 server, a flaw in the MAPI extension caused the evolution-data-server process to occasionally crash. This was because evolution-mapi mistook EDataBookView as a GObject, instead of a bonobo_object, and as a result was reffing/unreffing it with g_object_ref/g_object_unref. This patch uses the proper functions for ref/unref, resolving the issue. (BZ#66642)
Users are advised to upgrade to this updated evolution-mapi package, which resolves this.

1.54. fakechroot

1.54.1. RHBA-2011:0719: bug fix update

Updated fakechroot packages that fix one bug are now available for Red Hat Enterprise Linux 6.
The fakechroot utility allows a user to run programs in an environment that enables the use of the chroot command without the need for root privileges.
This update fixes the following bug:
  • Prior to this update, the fakechroot packages were marked as multilib, which allowed users to install these packages for multiple architectures at the same time. However, this feature is not fully supported by fakechroot. Since the 32-bit version is not actually needed, this update adds the "ExclusiveArch: x86-64" tag to the RPM spec file, so that the fakechroot packages are now available only for the 64-bit x86 architecture. (BZ#598451)
All users of fakechroot are advised to upgrade to these updated packages, which fix this bug.

1.55. fcoe-utils

1.55.1. RHBA-2011:0743: bug fix update

An updated fcoe-utils package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6.
The fcoe-utils package allows users to use Fibre Channel over Ethernet (FCoE). The package contains the fcoeadm command line tool for configuring FCoE interfaces, and the fcoemon service to configure DCB (Data Center Bridging) Ethernet QoS filters.
The fcoe-utils package has been upgraded to upstream version 1.0.18, which provides a number of bug fixes and enhancements over the previous version. (BZ#672453, BZ#691613)
This update fixes the following bugs:
  • Previously, in a particular setup with multipath and FCoE services, the system sometimes became unresponsive during shutdown or reboot, and a hard reboot was required to get the system back up. Now, an additional FCoE root filesystem check has been added to the init script and the system no longer hangs during reboot or shutdown in this scenario. (BZ#645917)
  • Sometimes, FCoE devices are not discovered immediately by the system. As a consequence, some FCoE partitions were previously not automounted after a boot. With this update, the FCoE init script waits for a certain amount of time (65 seconds by default), which is enough for most FCoE partitions to be discovered and mounted during the boot. (BZ#658076)
  • Running the fcoeadm tool without the FCoE stack loaded caused the fcoeadm tool to terminate with a backtrace when it tried to free an unallocated pointer. With this update, only successfully allocated pointers are freed and the fcoeadm tool returns a proper error message otherwise. (BZ#678487)
  • After VLAN discovery was tried unsuccessfully 10 times, the default FCoE driver for an interface was used instead of the preferred one. With this update, VLAN discovery is retried indefinitely and FCoE interfaces are now created only upon VLAN discovery, with proper drivers. (BZ#689631)
  • For several fcoe-utils executables, there were minor inconsistencies in the documentation between their command help output and their man pages. With this update, the documentation has been updated and the man pages and help output are now consistent. (BZ#623567)
  • The vconfig package had been marked for removal from the distribution, but the fcoe-utils package required it at runtime. With this update, this dependency has been removed in favor of the iproute package. (BZ#645796)
  • When an FCoE VLAN interface was restarted, the FCoE interface was not re-enabled after the VLAN interface was brought up again. This bug has been fixed and the FCoE interface is now automatically enabled after the VLAN interface is brought up. (BZ#680578)
This update adds the following enhancement:
  • With this update, the fcoe-utils package introduces a new SUPPORTED_DRIVERS configuration option to list all the low-level drivers that can potentially claim a network device. The package also uses the new sysfs module path introduced by the Red Hat Enterprise Linux 6.1 kernel update. (BZ#669211)
Users of fcoe-utils are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

1.56. febootstrap

1.56.1. RHEA-2011:0587: enhancement update

Updated febootstrap packages that add two enhancements are now available for Red Hat Enterprise Linux 6.
febootstrap is used to create a basic Red Hat Enterprise Linux or Fedora filesystem, and builds initramfs (initrd.img) or filesystem images.
This update adds the following enhancements:
  • The febootstrap packages have been upgraded to upstream version 2.11, which provides a number of bug fixes and one enhancement over the previous version. (BZ#628849)
  • This update provides the subpackage febootstrap-supermin-helper for the runtime helper program. Now, libguestfs runtime depends only on febootstrap-supermin-helper, which reduces the dependencies. (BZ#669839)
All febootstrap users are advised upgrade to these updated packages, which add these enhancements.

1.57. fence-agents

1.57.1. RHBA-2011:0363: bug fix update

An updated fence-agents package that fixes a bug is now available for Red Hat Enterprise Linux 6.
Red Hat fence agents are a collection of scripts to handle remote power management for several devices. They allow failed or unreachable nodes to be forcibly restarted and removed from the cluster.
This update fixes the following bug:
  • A bug fix for a previous advisory, the RHEA-2010:0904 enhancement update, stated that the Brocade 200E, Brocade 300, Brocade 4100, Brocade 4900, and Brocade 5100 fencing devices are now supported by the fence_brocade agent. However, the fence_brocade agent was not included in the updated package. This update corrects this error, and the fence_brocade agent is now included in the package as expected. (BZ#680522)
All users of fence-agents are advised to upgrade to this updated package, which resolves this issue.

1.57.2. RHBA-2011:0745: bug fix and enhancement update

An updated fence-agents package that fixes bugs, adds support for new hardware and Red Hat Enterprise Virtualization is now available.
Red Hat fence agents are a collection of scripts to handle remote power management for several devices. They allow failed or unreachable nodes to be forcibly restarted and removed from the cluster.
This update includes the following bug fixes:
  • Metadata generation has been corrected in order to provide information for all known parameters for each fencing agent. (BZ#618703, BZ#623266)
  • Port is now a synonym of module_name for fence_drac5, making it consistent with other fencing agents. (BZ#619096)
  • Information on how to use fence_ipmi with HP iLO version 3 has been added to the manual page. (BZ#648892)
  • The fence_egenera manual page has been improved. (BZ#635824)
  • fence_scsi now works when devices report "Unit Attention". (BZ#640343)
  • fence_scsi now verifies action results. (BZ#644385)
  • fence_scsi now correctly identifies device mapper multipath devices. (BZ#644389)
  • fence_scsi pattern matching has been improved. (BZ#670910)
  • fence_scsi now logs errors whenever a command fails. (BZ#672597)
This update adds the following enhancements:
  • Support for Cisco UCS blade systems is now provided. (BZ#580492, BZ#678904)
  • It is now possible for one node to delay fencing in a two-node cluster. (BZ#614046)
  • Fence_ipmilan can now use the "diag" option. (BZ#655764)
  • The package has been updated to provide a fencing agent that is able to communicate with Red Hat Enterprise Virtualization Manager, allowing virtual machines to be fenced. (BZ#595383)
  • For Intelligent Platform Management Interface (IPMI) devices, the "power_wait" delay can now be adjusted in order to support newer iLO 3 firmware. (BZ#642671)
  • Brocade 200E, Brocade 300, Brocade 4100, Brocade 4900, and Brocade 5100 fencing devices are now supported by the fence_brocade agent, and can be used with both Red Hat High Availability and Red Hat Resilient Storage. (BZ#642235, BZ#680170)
  • An issue with fence_scsi where the key was erroneously reported as 0 has been addressed. (BZ#653504)
  • fence_wti now correctly handles large (>20) port switches. (BZ#678522)
  • fence_rhevm has been updated to the current RHEVM development API. (BZ#681669, BZ#681674)
  • fence_cisco_ucs was missing from the fence-agents package, but is now included. (BZ#682715)
All users requiring any of the changes noted above should upgrade to this new package, which fixes these issues and adds these enhancements.

1.58. fence-virt

1.58.1. RHBA-2011:0731: bug fix and enhancement update

Updated fence-virt packages that provide a bug fix and an enhancement are now available.
The fence-virt packages provide a fencing agent for virtual machines as well as a host agent which processes fencing requests.
This update addresses the following bug:
  • The manual pages now correctly refer to "fence_virt.conf" instead of "fence_virtd.conf." (BZ#667170)
As well, this update adds the following enhancement:
  • Fence-virtd now operates with newer versions of QMF. (BZ#690582)
All users of fence-virt are advised to upgrade to these updated packages, which address these issues.

1.59. file

1.59.1. RHBA-2011:0204: bug fix update

Updated file packages that fix several bugs are now available for Red Hat Enterprise Linux 6.
The file command is used to identify a particular file according to the type of data contained in the file.
This update fixes the following bugs:
  • Prior to this update, the file utility could be unable to recognize Python scripts correctly. This update improves the file type recognition, and Python scripts are now identified as expected. (BZ#594083)
  • In accordance with POSIX standards, when the file utility is used on a file that does not exist, cannot be read, or is of an unknown type, it returns 0 exit code. This update extends the manual page to document this behavior. (BZ#608686)
  • The file utility has been updated to recognize the WebM media container. (BZ#610795)
  • The file utility has been updated to recognize the ZIP64 file format. (BZ#637782)
  • The file utility has been updated to recognize volume_key escrow packets. (BZ#643046)
  • Due to an error in a magic pattern, the file utility incorrectly identified GFS file systems as GFS2. With this update, the magic pattern has been corrected, and GFS file systems are now identified as expected. (BZ#670125)
All users of file are advised to upgrade to these updated packages, which resolve these issues.

1.60. fipscheck

1.60.1. RHEA-2011:0672: enhancement update

Updated fipscheck packages which relocate the library from /usr to /lib or /lib64 are now available.
FIPSCheck is a library used to verify the integrity of modules validated under FIPS-140-2. The fipscheck package provides helper binaries for creating and verifying HMAC-SHA256 checksum files.
These updated fipscheck packages add the following enhancement:
  • The fipscheck library can be linked to binaries (such as cryptsetup) which have to operate when /usr is not mounted. With this update, the fipscheck library relocates from /usr to /lib or /lib64 (depending on the underlying architecture) to allow linking to such binaries. (BZ#669077)
All fipscheck users are advised to upgrade to these updated packages, which add this enhancement.

1.61. firefox

1.61.1. RHSA-2010:0861: Critical security update

Updated firefox packages that fix several security issues are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
Mozilla Firefox is an open source web browser. XULRunner provides the XUL Runtime environment for Mozilla Firefox.
A race condition flaw was found in the way Firefox handled Document Object Model (DOM) element properties. Malicious HTML content could cause Firefox to crash or, potentially, execute arbitrary code with the privileges of the user running Firefox. (CVE-2010-3765)
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-2010-3175, CVE-2010-3176, CVE-2010-3179, CVE-2010-3183, CVE-2010-3180)
A flaw was found in the way the Gopher parser in Firefox converted text into HTML. A malformed file name on a Gopher server could, when accessed by a victim running Firefox, allow arbitrary JavaScript to be executed in the context of the Gopher domain. (CVE-2010-3177)
A same-origin policy bypass flaw was found in Firefox. An attacker could create a malicious web page that, when viewed by a victim, could steal private data from a different website the victim had loaded with Firefox. (CVE-2010-3178)
A flaw was found in the script that launches Firefox. The LD_LIBRARY_PATH variable was appending a "." character, which could allow a local attacker to execute arbitrary code with the privileges of a different user running Firefox, if that user ran Firefox from within an attacker-controlled directory. (CVE-2010-3182)
For technical details regarding these flaws, refer to the Mozilla security advisories for Firefox 3.6.11 and 3.6.12. You can find links to the Mozilla advisories in the References section of this erratum.
All Firefox users should upgrade to these updated packages, which contain Firefox version 3.6.12, which corrects these issues. After installing the update, Firefox must be restarted for the changes to take effect.

1.61.2. RHSA-2010:0966: Critical security update

Updated firefox packages that fix several security issues are now available for Red Hat Enterprise Linux 4, 5, and 6.
The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
Mozilla Firefox is an open source web browser.
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-2010-3766, CVE-2010-3767, CVE-2010-3772, CVE-2010-3776, CVE-2010-3777)
A flaw was found in the way Firefox handled malformed JavaScript. A website with an object containing malicious JavaScript could cause Firefox to execute that JavaScript with the privileges of the user running Firefox. (CVE-2010-3771)
This update adds support for the Sanitiser for OpenType (OTS) library to Firefox. This library helps prevent potential exploits in malformed OpenType fonts by verifying the font file prior to use. (CVE-2010-3768)
A flaw was found in the way Firefox loaded Java LiveConnect scripts. Malicious web content could load a Java LiveConnect script in a way that would result in the plug-in object having elevated privileges, allowing it to execute Java code with the privileges of the user running Firefox. (CVE-2010-3775)
It was found that the fix for CVE-2010-0179 was incomplete when the Firebug add-on was used. If a user visited a website containing malicious JavaScript while the Firebug add-on was enabled, it could cause Firefox to execute arbitrary JavaScript with the privileges of the user running Firefox. (CVE-2010-3773)
A flaw was found in the way Firefox presented the location bar to users. A malicious website could trick a user into thinking they are visiting the site reported by the location bar, when the page is actually content controlled by an attacker. (CVE-2010-3774)
A cross-site scripting (XSS) flaw was found in the Firefox x-mac-arabic, x-mac-farsi, and x-mac-hebrew character encodings. Certain characters were converted to angle brackets when displayed. If server-side script filtering missed these cases, it could result in Firefox executing JavaScript code with the permissions of a different website. (CVE-2010-3770)
For technical details regarding these flaws, refer to the Mozilla security advisories for Firefox 3.6.13. You can find a link to the Mozilla advisories in the References section of this erratum.
All Firefox users should upgrade to these updated packages, which contain Firefox version 3.6.13, which corrects these issues. After installing the update, Firefox must be restarted for the changes to take effect.

1.61.3. RHSA-2011:0310: Critical security and bug fix update

Updated firefox packages that fix several security issues and one bug are now available for Red Hat Enterprise Linux 4, 5, and 6.
The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
Mozilla Firefox is an open source web browser. XULRunner provides the XUL Runtime environment for Mozilla Firefox.
A flaw was found in the way Firefox sanitized HTML content in extensions. If an extension loaded or rendered malicious content using the ParanoidFragmentSink class, it could fail to safely display the content, causing Firefox to execute arbitrary JavaScript with the privileges of the user running Firefox. (CVE-2010-1585)
A flaw was found in the way Firefox handled dialog boxes. An attacker could use this flaw to create a malicious web page that would present a blank dialog box that has non-functioning buttons. If a user closes the dialog box window, it could unexpectedly grant the malicious web page elevated privileges. (CVE-2011-0051)
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-2011-0053, CVE-2011-0055, CVE-2011-0058, CVE-2011-0062)
Several flaws were found in the way Firefox handled malformed JavaScript. A website containing malicious JavaScript could cause Firefox to execute that JavaScript with the privileges of the user running Firefox. (CVE-2011-0054, CVE-2011-0056, CVE-2011-0057)
A flaw was found in the way Firefox handled malformed JPEG images. A website containing a malicious JPEG image could cause Firefox to crash or, potentially, execute arbitrary code with the privileges of the user running Firefox. (CVE-2011-0061)
A flaw was found in the way Firefox handled plug-ins that perform HTTP requests. If a plug-in performed an HTTP request, and the server sent a 307 redirect response, the plug-in was not notified, and the HTTP request was forwarded. The forwarded request could contain custom headers, which could result in a Cross Site Request Forgery attack. (CVE-2011-0059)
For technical details regarding these flaws, refer to the Mozilla security advisories for Firefox 3.6.14. You can find a link to the Mozilla advisories in the References section of this erratum.
This update also fixes the following bug:
  • On Red Hat Enterprise Linux 4 and 5, running the "firefox -setDefaultBrowser" command caused warnings such as the following:
    libgnomevfs-WARNING **: Deprecated function.  User modifications to the
    MIME database are no longer supported.
    
    This update disables the "setDefaultBrowser" option. Red Hat Enterprise Linux 4 users wishing to set a default web browser can use Applications -> Preferences -> More Preferences -> Preferred Applications. Red Hat Enterprise Linux 5 users can use System -> Preferences -> Preferred Applications. (BZ#463131, BZ#665031)
All Firefox users should upgrade to these updated packages, which contain Firefox version 3.6.14, which corrects these issues. After installing the update, Firefox must be restarted for the changes to take effect.

1.61.4. RHSA-2011:0471: Critical security update

Updated firefox packages that fix several security issues are now available for Red Hat Enterprise Linux 4, 5, and 6.
The Red Hat Security Response Team has rated this update as having critical security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
Mozilla Firefox is an open source web browser. XULRunner provides the XUL Runtime environment for Mozilla Firefox.
Several flaws were found in the processing of malformed web content. A web page containing malicious content could possibly lead to arbitrary code execution with the privileges of the user running Firefox. (CVE-2011-0080, CVE-2011-0081)
An arbitrary memory write flaw was found in the way Firefox handled out-of-memory conditions. If all memory was consumed when a user visited a malicious web page, it could possibly lead to arbitrary code execution with the privileges of the user running Firefox. (CVE-2011-0078)
An integer overflow flaw was found in the way Firefox handled the HTML frameset tag. A web page with a frameset tag containing large values for the "rows" and "cols" attributes could trigger this flaw, possibly leading to arbitrary code execution with the privileges of the user running Firefox. (CVE-2011-0077)
A flaw was found in the way Firefox handled the HTML iframe tag. A web page with an iframe tag containing a specially-crafted source address could trigger this flaw, possibly leading to arbitrary code execution with the privileges of the user running Firefox. (CVE-2011-0075)
A flaw was found in the way Firefox displayed multiple marquee elements. A malformed HTML document could cause Firefox to execute arbitrary code with the privileges of the user running Firefox. (CVE-2011-0074)
A flaw was found in the way Firefox handled the nsTreeSelection element. Malformed content could cause Firefox to execute arbitrary code with the privileges of the user running Firefox. (CVE-2011-0073)
A use-after-free flaw was found in the way Firefox appended frame and iframe elements to a DOM tree when the NoScript add-on was enabled. Malicious HTML content could cause Firefox to execute arbitrary code with the privileges of the user running Firefox. (CVE-2011-0072)
A directory traversal flaw was found in the Firefox resource:// protocol handler. Malicious content could cause Firefox to access arbitrary files accessible to the user running Firefox. (CVE-2011-0071)
A double free flaw was found in the way Firefox handled "application/http-index-format" documents. A malformed HTTP response could cause Firefox to execute arbitrary code with the privileges of the user running Firefox. (CVE-2011-0070)
A flaw was found in the way Firefox handled certain JavaScript cross-domain requests. If malicious content generated a large number of cross-domain JavaScript requests, it could cause Firefox to execute arbitrary code with the privileges of the user running Firefox. (CVE-2011-0069)
A flaw was found in the way Firefox displayed the autocomplete pop-up. Malicious content could use this flaw to steal form history information. (CVE-2011-0067)
Two use-after-free flaws were found in the Firefox mObserverList and mChannel objects. Malicious content could use these flaws to execute arbitrary code with the privileges of the user running Firefox. (CVE-2011-0066, CVE-2011-0065)
A flaw was found in the Firefox XSLT generate-id() function. This function returned the memory address of an object in memory, which could possibly be used by attackers to bypass address randomization protections. (CVE-2011-1202)
For technical details regarding these flaws, refer to the Mozilla security advisories for Firefox 3.6.17. You can find a link to the Mozilla advisories in the References section of this erratum.
All Firefox users should upgrade to these updated packages, which contain Firefox version 3.6.17, which corrects these issues. After installing the update, Firefox must be restarted for the changes to take effect.

1.61.5. RHSA-2011:0373: Important security update

Updated firefox packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6.
The Red Hat Security Response Team has rated this update as having important security impact.
Mozilla Firefox is an open source web browser. XULRunner provides the XUL Runtime environment for Mozilla Firefox.
This erratum blacklists a small number of HTTPS certificates. (BZ#689430)
All Firefox users should upgrade to these updated packages, which contain a backported patch. After installing the update, Firefox must be restarted for the changes to take effect.

1.61.6. RHBA-2011:0359: bug fix update

Updated firefox packages that resolve an issue are now available.
Mozilla Firefox is an open source Web browser.
These updated firefox packages fix the following bug:
  • Prior to this update, some Java applets would fail to load in the 3.6.14 version of Firefox. In this newly-released version (Firefox 3.6.15), Java applets no longer fail to load. (BZ#682251, BZ#682252, BZ#682253)
All users of firefox are advised to upgrade to these updated packages, which resolve this issue.

1.62. firstaidkit

1.62.1. RHEA-2011:0166: enhancement update

Updated firstaidkit packages that add an enhancement are now available for Red Hat Enterprise Linux 6.
FirstAidKit is a tool that runs automated diagnostics of an installed Red Hat Enterprise Linux system.
This update adds the following enhancement:
  • These updated packages introduce a new manual page with an outline of the basic concepts and format of the main configuration file (that is, /etc/firstaidkit/firstaidkit.conf by default). Note that this manual page does not replace a detailed description of available configuration options in the configuration file itself. (BZ#584677)
Users of firstaidkit are advised to upgrade to these updated packages, which add this enhancement.

1.63. firstboot

1.63.1. RHBA-2011:0742: bug fix and enhancement update

Updated firstboot packages that fix two bugs and add one enhancement are now available for Red Hat Enterprise Linux 6.
The firstboot utility runs after installation. It guides the user through a series of steps that allows for easier configuration of the machine.
This update fixes the following bugs:
  • Previously, no screen was provided to change the root password in firstboot. Due to this lack, users had to change the settings of system-config-users to the root password within the Advanced window of firstboot's create user screen. This update adds a module to change the root password. Now, users can view a set the root password in firstboot, if run with the option "the --reconfig". (BZ#658869)
  • Previously, users could not skip the user creation screen. Due to this lack, users had to create a user account with an UID number above or equal to 500 to continue to the next step of the first boot process. With this update, the check for valid user accounts in the system checks whether a user account with a valid login shell is present and not only user accounts with an UID number above or equal to 500. If there's no such user account present firstboot shows a warning, but allows the user to go to the next step. Now, users can skip the user creation part of firstboot. (BZ#659451)
This update also adds the following enhancement:
  • Previously, the firstboot utility did not run automatically after installation on IBM's System/390 architecture. Due to this issue, users had to run firstboot manually. This update adds automatic execution. Now, the firstboot utility runs automatically when the root user logs in to the system for the first time with a capable terminal. (BZ#463564)
All firstboot users are advised to upgrade to these updated packages, which fix these bugs and adds this enhancement.

1.64. freeradius

1.64.1. RHBA-2011:0610: bug fix and enhancement update

Updated freeradius packages that fix two bugs and add one enhancement are now available for Red Hat Enterprise Linux 6.
FreeRADIUS is an open source RADIUS server which allows RADIUS clients to perform authentication against the RADIUS server. The RADIUS server may optionally perform accounting of it's operations via the RADIUS protocol.
This update fixes the following bugs:
  • The FreeRADIUS packages have been upgraded to upstream version 2.1.10, which provides a number of bug fixes over the previous version. (BZ#644100)
  • Previously, the FreeRADIUS server failed to start when the rlm_perl or rlm_python modules were used due to unresolved symbols encountered by the dynamic loader. This update uses the dynamic loader option which must be explicitly turned on via lt_dladvise to allow loaded modules to globally export their symbols. Now, rlm_perl and rlm_python FreeRADIUS modules are successfully loaded and the FreeRADIUS server successfully starts in this configuration.(BZ#689045)
This update also adds the following enhancement:
  • This update makes the radtest script available for testing with IPv6. (BZ#599528)
All FreeRADIUS users are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

1.65. freetype

1.65.1. RHSA-2010:0864: Important security update

Updated freetype packages that fix multiple security issues are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
FreeType is a free, high-quality, portable font engine that can open and manage font files. It also loads, hints, and renders individual glyphs efficiently. These packages provide the FreeType 2 font engine.
It was found that the FreeType font rendering engine improperly validated certain position values when processing input streams. If a user loaded a specially-crafted font file with an application linked against FreeType, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. (CVE-2010-2805, CVE-2010-3311)
A stack-based buffer overflow flaw was found in the way the FreeType font rendering engine processed some PostScript Type 1 fonts. If a user loaded a specially-crafted font file with an application linked against FreeType, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. (CVE-2010-2808)
An array index error was found in the way the FreeType font rendering engine processed certain PostScript Type 42 font files. If a user loaded a specially-crafted font file with an application linked against FreeType, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. (CVE-2010-2806)
Note: All of the issues in this erratum only affect the FreeType 2 font engine.
Users are advised to upgrade to these updated packages, which contain backported patches to correct these issues. The X server must be restarted (log out, then log back in) for this update to take effect.

1.65.2. RHSA-2010:0889: Important security update

Updated freetype packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6.
The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
FreeType is a free, high-quality, portable font engine that can open and manage font files. It also loads, hints, and renders individual glyphs efficiently. The freetype packages for Red Hat Enterprise Linux 4 provide both the FreeType 1 and FreeType 2 font engines. The freetype packages for Red Hat Enterprise Linux 5 and 6 provide only the FreeType 2 font engine.
A heap-based buffer overflow flaw was found in the way the FreeType font rendering engine processed certain TrueType GX fonts. If a user loaded a specially-crafted font file with an application linked against FreeType, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. (CVE-2010-3855)
Note: This issue only affects the FreeType 2 font engine.
Users are advised to upgrade to these updated packages, which contain a backported patch to correct this issue. The X server must be restarted (log out, then log back in) for this update to take effect.

1.66. gcc

1.66.1. RHBA-2011:0663: bug fix update

A gcc update that resolves several compiler bugs is now available.
The gcc packages include C, C++, Java, Fortran, Objective C, Objective C++ and Ada 95 GNU compilers, along with related support libraries.
This update applies the following bug fixes:
  • These updated packages provide support for the "-mcmodel=medium" and "-mcmodel=large" options on the 64-bit PowerPC architecture. These new options provide the ability to extend the TOC addressing space up to 2GB. (BZ#630166)
  • gcc now has the ability to emit pre-fetch instructions for "memcmp", "memcpy" and "memset" in-line expansions when optimizing for IBM System z10 CPUs. (BZ#632366)
  • Previously, leaf functions that accessed TLS variables in the global or local dynamic model were not generating a large enough stack frame on PowerPC 64-bit. In this updated package, the generated stack frame is now larger than 112 bytes, resolving this issue. (BZ#624889)
  • Previously a regression in the gfortran compiler was causing the "-M" option to not be recognized. In these updated packages the "-M" option is now recognized and functions as expected. (BZ#675132)
  • Previously, the optimizations performed when calculating induction variables during the induction variable optimization (ivopts) pass were not as efficient as previous releases. In these updated packages, the optimizations performed during the the induction variable optimization (ivopts) pass is improved. (BZ#592502)
  • Previously, if a Java application built with gcj attempted to submit a print job to a print queue that was disabled, the process would enter a busy loop. This update fixes this issue by first checking if the print queue is null before attempting to send it a print job. (BZ#618258)
  • Previously, using "always_inline" on a function when compiling with "-g" without any "-O" options would cause the compiler to insert debugging annotations in unexpected locations. Consequently, the unexpected annotations caused the compiler to crash with an internal error. In these updated packages, the compiler is modified to properly handle attributes which change optimization levels, such as always_inline, properly. (BZ#659582)
  • This update provides code optimizations for the IBM System z architecture. (BZ#632370)
  • The mask operand for the AVX mask load/store is fixed. (BZ#635015)
In addition, the following enhancements are provided by this update
  • IBM z196 new instruction support and optimizations
  • IBM z10 prefetch instruction support and optimizations
All users of gcc are advised to upgrade to these updated packages which address these issues.

1.67. gdb

1.67.1. RHBA-2011:0145: bug fix update

Updated gdb packages that resolve an issue are now available.
The GNU debugger, gdb, allows the debugging of programs written in C, C++, and other languages by executing them in a controlled fashion and then printing out their data.
These updated gdb packages fix the following bug:
  • After you issued the command 'info program', GDB could have terminated unexpectedly, because a change of the shared library list corrupted the data in the internal GDB structure 'bpstat'. With this update, the 'bpstat' structure contains after a change in the shared library list the correct data and the command 'info program' works as expected. (BZ#662218)
All users of gdb are advised to upgrade to these updated packages, which resolve this issue.

1.67.2. RHBA-2011:0638: bug fix and enhancement update

Updated gdb packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6.
The GNU debugger, gdb, is a debugger for programs written in C, C++, and other languages.
This update fixes these bugs:
  • GDB crashed when reading a kernel core dump file because the value of temporary current inferior process was set to minus_one_ptid (all processes). The value is now set to null_ptid (no processes) and GDB displays the vmcore file. (BZ#611435)
  • When the gcore utility created a core file for an executable compiled with the "-Wl,-z,relro" parameter, GDB was unable to open it. This occurred because the file did not contain the list of shared libraries. Such core files now contain the shared library list and can be opened. (BZ#625239)
  • GDB Python's pretty-printing feature provides an easily-readable view on complex C++ STL data structures. GDB crashed when displaying such structures. This occurred when the pretty printer threw a Python exception and GDB crashed due to a NULL pointer dereference. GDB now displays the easily-readable view of any C++ STL data structure correctly. (BZ#629236)
  • GDB aborted unexpectedly if you set breakpoints on GNU-IFUNC functions and started the debugged program because the breakpoints could not resolve the target functions of the GNU-IFUNC functions at program startup. Breakpoints on GNU-IFUNC functions are now resolved when the program calls the target function. (BZ#632259)
  • With GDB, you can modify VSX registers on PowerPC platforms. Changing some VSX registers corrupted other VSX registers. GDB now sets VSX registers independently. (BZ#636298)
  • GDB aborted unexpectedly when an inferior shared library list changed during an inferior function call. This occurred because GDB reset all breakpoints including the temporary breakpoint, which was created by the call, and attempted to delete the breakpoint again after the call finished. The temporary breakpoint now remains valid during the entire inferior function call. (BZ#639645)
  • GDB could have hung when debugging multithreaded programs with the setuid() function because the siginfo_t information associated with a signal number got lost. GDB now no longer resubmits or reorders signals and the siginfo_t value is preserved. (BZ#639647)
  • GDB terminated unexpectedly after user run the "info program" command because a change of the shared library list corrupted the data in the internal GDB structure "bpstat". The structure now contains correct data even after a change in the shared library list and "info program" works as expected. (BZ#661773)
  • Test suite file break-interp.exp reported for PowerPC platforms several FAIL results. A number of fixes have been applied to address these issues and the test suite for PowerPC now runs successfully. (BZ#663449)
  • GDB crashed when attempting to access dynamic types, such as variable length arrays, using the GDB/MI interface. GDB now no longer crashes under these circumstances. (BZ#682891)
  • On the i686 architecture, the awatch and rwatch commands printed an error when entered before the program-to-be-debugged started. GDB now by default debugs on the native architecture and the commands can be used before the program-to-be-debugged starts. (BZ#688788)
This update adds these enhancements:
  • Debugged programs may use C++ templates. C++ templates provide template symbols for instantiation of classes and functions. GDB debugged the template instances but the template symbols were not accessible. GDB now displays the template symbols while debugging the template instances. (BZ#562758)
  • Fortran supports array slicing. GDB could not slice multidimensional arrays. GDB now supports slicing of such arrays. (BZ#609782)
  • The gdb package has been upgraded to upstream version 7.2, which provides a number of bug fixes and enhancements over the previous version. (BZ#649030)
  • GDB did not display pthread_t for threads found in the core. GDB now displays pthread_t for the threads. (BZ#673696)
Users are advised to upgrade to these packages, which resolve the bugs and add the enhancements.

1.68. gdm

1.68.1. RHSA-2011:0395: Moderate security update

Updated gdm packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The GNOME Display Manager (GDM) provides the graphical login screen, shown shortly after boot up, log out, and when user-switching.
A race condition flaw was found in the way GDM handled the cache directories used to store users' dmrc and face icon files. A local attacker could use this flaw to trick GDM into changing the ownership of an arbitrary file via a symbolic link attack, allowing them to escalate their privileges. (CVE-2011-0727)
Red Hat would like to thank Sebastian Krahmer of the SuSE Security Team for reporting this issue.
All users should upgrade to these updated packages, which contain a backported patch to correct this issue. GDM must be restarted for this update to take effect. Rebooting achieves this, but changing the runlevel from 5 to 3 and back to 5 also restarts GDM.

1.69. ghostscript

1.69.1. RHBA-2011:0527: bug fix update

Updated ghostscript packages that fix various bugs are now available for Red Hat Enterprise Linux 6.
The Ghostscript suite provides a PostScript interpreter, a set of C procedures (the Ghostscript library, which implements the graphics capabilities in the PostScript language), and an interpreter for PDF files. Ghostscript translates PostScript code into many common, bitmapped formats, like those understood by most printers and displays. This enables users to display PostScript files and print them on non-PostScript printers.
This update fixes the following bugs:
  • Previously, including a large JBIG2 compressed image in the PDF input file could cause the pdf2ps conversion utility to terminate unexpectedly with a segmentation fault. This was caused by the fact that the result of the "jbig2_image_new" function call was not always checked properly. This error has been fixed, and the inclusion of JBIG2 images no longer causes pdf2ps to crash. (BZ#621118)
  • Due to incorrect object management, Ghostscript could attempt to read from uninitialized memory, which could lead to a segmentation fault. This update applies a backported patch that addresses this issue, and Ghostscript no longer crashes. (BZ#629562)
  • The Fontmap.local file installed with the ghostscript package allows a system administrator to override font substitutions. However, previous versions of the Ghostscript suite did not use this file at all. This error has been fixed, and the file is now used as expected. (BZ#629941)
  • Previously, using the ps2pdf utility to convert a PostScript file to the PDF format caused the resulting document to be created without working hyperlinks. This update applies an upstream patch that resolves this issue, and ps2pdf now crates PDF files with correct hyperlinks. (BZ#675692)
All users of ghostscript are advised to upgrade to these updated packages, which fix these bugs.

1.70. git

1.70.1. RHSA-2010:1003: Moderate security update

Updated git packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
Git is a fast, scalable, distributed revision control system.
A cross-site scripting (XSS) flaw was found in gitweb, a simple web interface for Git repositories. A remote attacker could perform an XSS attack against victims by tricking them into visiting a specially-crafted gitweb URL. (CVE-2010-3906)
All gitweb users should upgrade to these updated packages, which contain a backported patch to correct this issue.

1.71. glib2

1.71.1. RHBA-2011:0535: bug fix update

Updated glib2 packages that fix one bug are now available for Red Hat Enterprise Linux 6.
GLib is a low-level core library that forms the basis for projects such as GTK+ and GNOME. It provides data structure handling for C, portability wrappers, and interfaces for such runtime functionality as an event loop, threads, dynamic loading, and an object system.
This update fixes the following bug:
  • Previously, snapshots from the Network File System (NFS) mounted home directories located on Network Appliance (NetApp) filers were treated as real mounts and were displayed on the desktop. Due to this behavior, users could not hide or unmount these items. By default, the GNOME desktop treated all mounts under user home directories as custom and put their icons on the desktop. This update follows common practice and hides mounts with path elements that start with a dot. (BZ#648498)
All users are advised to upgrade to these updated packages, which fix this bug.

1.72. glibc

1.72.1. RHSA-2010:0872: Important security and bug fix update

Updated glibc packages that fix two security issues and two bugs are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
The glibc packages contain the standard C libraries used by multiple programs on the system. These packages contain the standard C and the standard math libraries. Without these two libraries, a Linux system cannot function properly.
It was discovered that the glibc dynamic linker/loader did not handle the $ORIGIN dynamic string token set in the LD_AUDIT environment variable securely. A local attacker with write access to a file system containing setuid or setgid binaries could use this flaw to escalate their privileges. (CVE-2010-3847)
It was discovered that the glibc dynamic linker/loader did not perform sufficient safety checks when loading dynamic shared objects (DSOs) to provide callbacks for its auditing API during the execution of privileged programs. A local attacker could use this flaw to escalate their privileges via a carefully-chosen system DSO library containing unsafe constructors. (CVE-2010-3856)
Red Hat would like to thank Tavis Ormandy for reporting the CVE-2010-3847 issue, and Ben Hawkes and Tavis Ormandy for reporting the CVE-2010-3856 issue.
This update also fixes the following bugs:
  • Previously, the generic implementation of the strstr() and memmem() functions did not handle certain periodic patterns correctly and could find a false positive match. This error has been fixed, and both functions now work as expected. (BZ#643341)
  • The "TCB_ALIGNMENT" value has been increased to 32 bytes to prevent applications from crashing during symbol resolution on 64-bit systems with support for Intel AVX vector registers. (BZ#643343)
All users are advised to upgrade to these updated packages, which contain backported patches to correct these issues.

1.72.2. RHSA-2011:0413: Important security update

Updated glibc packages that fix three security issues are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
The glibc packages contain the standard C libraries used by multiple programs on the system. These packages contain the standard C and the standard math libraries. Without these two libraries, a Linux system cannot function properly.
The fix for CVE-2010-3847 introduced a regression in the way the dynamic loader expanded the $ORIGIN dynamic string token specified in the RPATH and RUNPATH entries in the ELF library header. A local attacker could use this flaw to escalate their privileges via a setuid or setgid program using such a library. (CVE-2011-0536)
It was discovered that the glibc fnmatch() function did not properly restrict the use of alloca(). If the function was called on sufficiently large inputs, it could cause an application using fnmatch() to crash or, possibly, execute arbitrary code with the privileges of the application. (CVE-2011-1071)
It was discovered that the locale command did not produce properly escaped output as required by the POSIX specification. If an attacker were able to set the locale environment variables in the environment of a script that performed shell evaluation on the output of the locale command, and that script were run with different privileges than the attacker's, it could execute arbitrary code with the privileges of the script. (CVE-2011-1095)
All users should upgrade to these updated packages, which contain backported patches to correct these issues.

1.72.3. RHBA-2011:0321: bug fix update

Updated glibc packages that fix a bug in the dynamic linker are now available for Red Hat Enterprise Linux 6.
The glibc packages contain the standard C libraries used by multiple programs on the system. These packages contain the standard C and the standard math libraries. Without these two libraries, a Linux system cannot function properly.
This update fixes the following bug:
  • Due to an error in glibc libraries, a race condition could occur when traversing a list of currently loaded shared libraries, causing an application to terminate with an error. This error has been fixed, the race condition no longer occurs, and the list of shared libraries can now be traversed as expected. (BZ#661396)
All users are advised to upgrade to these updated packages, which resolve this issue.

1.72.4. RHBA-2011:0584: bug fix and enhancement update

Updated glibc packages that fix numerous bugs and add various enhancements are now available for Red Hat Enterprise Linux 6.
The glibc packages contain the standard C libraries used by multiple programs on the system. These packages contain the standard C and the standard math libraries. Without these two libraries, a Linux system cannot function properly.
Bug fixes:
BZ#646954
Due to an error in glibc libraries, a race condition could occur when traversing a list of currently loaded shared libraries, causing an application to terminate with an error. This error has been fixed, the race condition no longer occurs, and the list of shared libraries can now be traversed as expected.
BZ#642584
On 64-bit x86 systems with support for AVX vector registers, an insufficient alignment of the thread descriptor could cause an application to crash during symbol resolution. With this update, the "TCB_ALIGNMENT" value has been increased to 32 bytes, and applications no longer crash.
BZ#641128
Previously, the generic implementation of the strstr() and memmem() functions did not handle certain periodic patterns correctly and could find a false positive match. This error has been fixed, and both functions now work as expected.
BZ#656530
The long double square root function, sqrtl, sometimes returned an incorrect result if the relative magnitude difference between the high and low halves of the long double exceeded a certain number. This occurred because one of the variables used in the calculation was an unsigned integer. The integer is now signed and the function works correctly.
BZ#623187
The futex(FUTEX_WAKE_OP) method did not default to futex(FUTEX_WAKE) when FUTEX_WAKE_OP was not supported by the kernel. This resulted in the method always failing on these systems. The code change in glibc pthread_cond_signal() that caused this issue has now been corrected.
BZ#661982
The memmove, wmemmove and wmemset operations contained incorrect "__restrict" qualifiers, even though their arguments could overlap. This issue has now been corrected.
BZ#656014
The name service cache daemon (nscd) cached the results of lookups for DNS records even when the DNS records had a time-to-live of 0. nscd now respects DNS time-to-live values, and does not cache the results in this situation.
BZ#653905
Attempting to build the glibc RPM failed when %_enable_debug_packages was either not set, or set to 0. This has been corrected so that debug packages need not be set or enabled in order to build the glibc RPM.
BZ#652661
An uninitialized variable prevented glibc from compiling with the G++ compiler when "sys/timex.h" was included. This has been corrected.
BZ#647448
strchr did not handle its second parameter correctly when %rdi was aligned to a 16-byte boundary and glibc was enabled for multiple architectures on AMD64 or Intel 64 systems with CPUs that supported Supplemental Streaming SIMD Extension (SSE) 4.2. The method would therefore output incorrect results. This has been corrected, and strchr now gives the expected output.
BZ#615701
glibc did not load nosegneg libraries in a 32-bit Xen domain U environment when hwcap 1 nosegneg was set in /etc/ld.so.conf.d/nosegneg.conf, causing the incorrect library to be used. This has been corrected so that the nosegneg libraries are loaded.
BZ#692177
Previously, the sysconf(_SC_*CACHE) method returned 0 for all caches on systems with Intel Xeon processors. This occurred because glibc used cpuid leaf 2 rather than cpuid leaf 4. This update uses cpuid leaf 4 where possible, resolving this issue.
BZ#689471
The strncmp method failed with a segmentation fault when used with Supplemental Streaming SIMD Extension 4 (SSE4). Several checks have been implemented to prevent this.
Enhancements:
BZ#601686
Several aspects of glibc code have been optimized for Supplemental Streaming SIMD Extension (SSE), including memcpy(), strcasecmp(), strnlen(), strcasestr() and strncasestr().
BZ#615090
Details about the MALLOC_PERTURB_ (M_PERTURB) operation, which can be used to debug the use of uninitialized or freed heap memory, have been added to the documentation.
BZ#676076
Support for forthcoming AMD processors has been added to glibc's memset operation.
All users of glibc are advised to upgrade to these updated packages, which resolve these issues.

1.73. gnome-panel

1.73.1. RHBA-2011:0710: bug fix and enhancement update

Updated gnome-panel and libwnck packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6.
The GNOME panel provides the window list, workspace switcher, menus, and other features for the GNOME desktop. libwnck allows applications to monitor information about open windows, workspaces, their names/icons, and so forth.
This update fixes the following bugs:
  • Previously, when a user connected two monitors to a computer and set the GNOME Panel to show hide buttons, the panel did not hide but moved to the adjacent monitor instead. This bug has been fixed, moving the panel to the adjacent monitor no longer takes place. (BZ#607665)
  • Previously, there was the untranslated text label "Top Panel" in the GNOME Panel's "Add to Panel" dialog. The problem applied to all non-English locales. The problem has been resolved so that the untranslated text label does not appear anymore in the "Add to Panel" dialog. (BZ#633853)
  • Previously, there was a conflicting accelerator key in the GNOME Panel's Date/Time context menu under the kn_IN locale. The fix for this bug has been provided so that there is no more a conflicting accelerator key in the Date/Time context menu. (BZ#633870)
In addition, the following enhancements have been made:
  • When windows were grouped by the GNOME Panel in the taskbar, they were grouped in an alphabetical order. Such behavior presented a problem when window title changed. This release introduces an option to disable grouping window alphabetically. The fix to enable the option has been applied both in the gnome-panel and the libwnck package. (BZ#509061, BZ#673231)
  • Previously, when an external monitor was connected to a computer, a user was able to move a panel between monitors by pressing the Alt key and dragging a blank area of the panel. This update introduces an enhancement in that the user can now change the settings with regard to moving the panel between monitors in the GNOME Panel "Properties" dialog. (BZ#585312)
All users requiring gnome-panel and libwnck should upgrade to these updated packages, which resolve these issues and add these enhancements.

1.74. gnome-power-manager

1.74.1. RHBA-2011:0722: bug fix update

Updated gnome-power-manager packages that fix several bugs are now available.
GNOME Power Manager uses the information and facilities provided by HAL to display icons and handle user callbacks in an interactive GNOME session.
These updated gnome-power-manager packages provide fixes for the following bugs:
  • Previously, the Help page for GNOME Power Manager was not displayed when users pressed F1 or selected Help from the menu bar. This has been corrected and the Help page now appears as expected. (BZ#581525)
  • The "do nothing" option, which allowed users to work on external monitors even when their laptop lid was closed, was removed. This prevented users from using external monitors while their laptop was closed. The "do nothing" option has been reinstated to allow this. (BZ#623674)
  • A bug in the docbook2man tool caused the GNOME Power Manager man page (man gnome-power-manager) to appear incorrectly. The man page has been manually corrected while this bug is in effect. (BZ#624422)
  • When an attempt to hibernate failed, an alert was displayed prompting users to check a help file. However, there was no link to the help file, which caused confusion. The alert no longer refers to the help file. (BZ#640296)
All users of GNOME Power Manager are advised to upgrade to these updated packages, which resolve these issues.

1.75. gnome-terminal

1.75.1. RHBA-2011:0700: bug fix update

Updated gnome-terminal packages that fix one bug are now available for Red Hat Enterprise Linux 6.
Gnome-terminal is a terminal emulator for GNOME. It supports translucent backgrounds, opening multiple terminals in a single window (tabs) and clickable URLs.
This update fixes the following bug:
  • Changes made to check boxes in the search dialog were not reflected in the terminal engine (vte). This led to confusion and wrong functionality. Problem has been fixed and users should get expected behaviour.(BZ#669113)
All gnome-terminal users are advised to upgrade to these updated packages, which resolve these issues.

1.76. gpxe

1.76.1. RHBA-2011:0415: bug fix update

Updated gpxe packages that fix one bug are now available for Red Hat Enterprise Linux 6.
The gpxe packages provide an open source Preboot Execution Environment (PXE) implementation and bootloader. gPXE also supports additional protocols such as DNS, HTTP, iSCSI and ATA over Ethernet.
This update fixes the following bug:
  • Previously, the virtIO gPXE driver padded all packets to maximum length. This could confuse some gateways because the Ethernet standard is to pad only packets of up to 64 bytes in length. Due to this issue, virtual machines with a virtIO NIC (network interface card) failed to connect to the PXE server behind a gateway. Subsequently, the PXE boot failed. This update pads only packets of up to 64 bytes in length. Now, virtual machines with a virtIO NIC connect to the same PXE server without further problems. (BZ#680148)
All gPXE users are advised to upgrade to these updated packages which fix this bug.

1.76.2. RHBA-2011:0694: bug fix update

Updated gpxe packages that fix two bugs are now available for Red Hat Enterprise Linux 6.
The gpxe packages provide an open source Preboot Execution Environment (PXE) implementation and bootloader. gPXE also supports additional protocols such as DNS, HTTP, iSCSI and ATA over Ethernet.
This update fixes the following bugs:
  • Devices that did not allow interrupts or required polling were not supported by gPXE UNDI code. This meant that booting did not work when using gPXE images on bare metal with some NICs, such as Emulex 10g. This patch allows the gPXE UNDI code to use polling for underlying devices that do not support interrupts. As a result it is now possible to use gPXE images to boot bare metal hosts using UNDI where it was not possible in some cases. (BZ#661840)
  • Virtual Machines (VM) with virtIO NIC could not access the PXE server, reaching a time out. This was because even though the VM could get an IP address from the DHCP server, it could not reach its own default gateway. The ARP requests that the VM sends were too large and thus not valid, so the default gateway did not answer those ARP requests. A patch has been added that sets the size of the transmitted Ethernet frame to header + data length, allowing the VM to boot via PXE. (BZ#672529)
All gPXE users are advised to upgrade to these updated packages, which fix these bugs.

1.77. grub

1.77.1. RHEA-2011:0633: enhancement update

An updated grub package that adds two enhancements is now available for Red Hat Enterprise Linux 6.
The GRUB utility is responsible for booting the operating system kernel.
This update adds the following enhancements:
  • Prior to this update, GRUB only supported the MD5 password encryption. This update introduces support for the SHA-2 cryptographic algorithms, allowing users to encrypt passwords using SHA-256 and SHA-512 hash functions as well. (BZ#553741)
  • GRUB has been updated to allow booting from disk drives with 4KB sector size on UEFI systems. (BZ#654869)
All users of grub are advised to upgrade to this updated package, which adds these enhancements.

1.78. gtk2

1.78.1. RHBA-2011:0693: bug fix update

Updated gtk2 packages that fix two file chooser bugs and two translation problems are now available for Red Hat Enterprise Linux 6.
GTK+ is a multi-platform toolkit for creating graphical user interfaces.
These updated packages fix the following bugs:
  • In the "Open Files" dialog box, the file selected by default failed to be opened upon hitting Enter if the "Location" field was displayed. Users had to select the file manually to actually open it. This update provides a fix to address this issue and the file selected by default now opens correctly. (BZ#647922)
  • The "Open Files" dialog box failed to show contents of the directory selected by default upon hitting Enter if the "Location" field was displayed. Users had to select the directory manually to actually show its contents. This update provides a fix for this issue and the directory selected by default now shows its contents correctly. (BZ#647923)
  • There was a typo in the Marathi (mr_IN) and Telugu (te_IN) translations. Erroneous "calender:MY" string was part of those translations. This update provides corrected translations. (BZ#625440)
  • There was an inconsistency in the Guarati (gu_IN) translation. In ibus's Language Selection Tab, titles for "Up" and "Down" buttons and help labels at the bottom of the dialog box did not match. This update provides an updated translation. (BZ#636476)
Users should upgrade to these updated packages, which resolve these issues.

1.79. gvfs

1.79.1. RHBA-2011:0536: bug fix and enhancement update

Updated gvfs packages that fix multiple bugs and add one enhancement are now available for Red Hat Enterprise Linux 6.
GVFS is the GNOME desktop's virtual file system layer, which allows users to easily access local and remote data, including via the FTP, SFTP, WebDAV, CIFS and SMB protocols, among others. GVFS integrates with the GIO (GNOME I/O) abstraction layer.
This update fixes the following bugs:
  • A flaw in the GVFS client code prevented D-Bus communications from being parsed correctly. Due to this problem, Nautilus became unresponsive when the user attempted to view Trash if a folder with an attached emblem was moved to Trash. This update corrects an error in the enumeration code which resolves this problem. Now, Nautilus no longer becomes unresponsive in such cases. (BZ#616145)
  • Previously, an unused file descriptor was not closed after a fork. Due to this behavior, SELinux prevented /usr/bin/ssh access to the leaked /dev/ptmx file descriptor. This update closes the leaked file descriptor. Now, SELinux alerts no longer appear. (BZ#616838)
  • Previously, the gnome-disk-utility packages did not reflect current version requirements. Due to this lack, potential problems could arise with custom compiled packages. This update requires the correct version of gnome-disk-utility packages. (BZ#636540)
  • Previously, the gvfsd-archive command was unexpectedly aborted when the user attempted to mount an archive file a second time. This update changes the way the gvfsd-archive backend is finalized. Now, gvfsd-archive no longer aborts when the same archive files are mounted for the second time. (BZ#645630)
  • Running the "gvfs-mkdir --help" command caused "--delete-files" to appear instead of "--create-directories". This update fixes the gvfs-mkdir command's help output so that the correct options are displayed. (BZ#667367)
This update also adds the following enhancement:
  • Previously, snapshots from the Network File System (NFS) mounted home directories located on Network Appliance (NetApp) filers were treated as real mounts and were displayed on the desktop. This behavior could cause confusion. This update checks and hides mounts with a path element starting with a dot. With this update, these mounts are hidden. Now, snapshot directories are no longer shown in the GUI. To apply this enhancement, the updated glib2 packages must be installed as well. (BZ#624795)
Users of GVFS are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

1.80. hal

1.80.1. RHBA-2011:0724: bug fix update

An updated hal package that fixes two bugs is now available for Red Hat Enterprise Linux 6.
HAL is daemon for collecting and maintaining information from several sources about the hardware on a system.
  • Previously, the init script for hald did not parse a config file in /etc/sysconfig. This meant that the only way to pass extra parameters to the hald was to start them manually without the init script, or to modify the line that launches hald in the init script itself. This update changes the startup script to parse a config file in /etc/sysconfig for extra configuration parameters. (BZ#576048)
  • When checking hal-device on a device that did not exist, an error in dbus/hal communication was displayed. In this update, hal no longer tries to close shared DBus connections, and therefore avoids printing a warning. (BZ#676618)
Users are advised to upgrade to this updated hal package, which resolves these issues.

1.81. hivex

1.81.1. RHBA-2011:0588: bug fix and enhancement update

Updated hivex packages that fix a bug and add an enhancement are now available for Red Hat Linux 6.
Hive files are undocumented binary blobs that Windows uses to store the Windows Registry on the disk. Hivex is a library that can read and write to these files.
These updated hivex packages provide the following enhancement:
  • The hivex package was updated to the upstream version 1.2.3. This enhancement provides several stability improvements. (BZ#642631)
In addition, these updated hivex packages fix the following bug:
  • Due to a problem with the Perl hivex bindings in the spec file, rebuilding of source packages could have failed if compiled from the source RPM. With this update, the issue no longer occurs. (BZ#657017)
All hivex users are advised to upgrade to these updated hivex packages, which resolve this issue and add this enhancement.

1.82. hplip

1.82.1. RHSA-2011:0154: Moderate security update

Updated hplip packages that fix one security issue are now available for Red Hat Enterprise Linux 5 and 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
Hewlett-Packard Linux Imaging and Printing (HPLIP) provides drivers for Hewlett-Packard printers and multifunction peripherals, and tools for installing, using, and configuring them.
A flaw was found in the way certain HPLIP tools discovered devices using the SNMP protocol. If a user ran certain HPLIP tools that search for supported devices using SNMP, and a malicious user is able to send specially-crafted SNMP responses, it could cause those HPLIP tools to crash or, possibly, execute arbitrary code with the privileges of the user running them. (CVE-2010-4267)
Red Hat would like to thank Sebastian Krahmer of the SuSE Security Team for reporting this issue.
Users of hplip should upgrade to these updated packages, which contain a backported patch to correct this issue.

1.82.2. RHBA-2011:0574: bug fix update

Updated hplip packages that fix multiple bugs are now available for Red Hat Enterprise Linux 6.
The hplip packages contain the Hewlett-Packard Linux Imaging and Printing Project (HPLIP) which provides drivers for Hewlett-Packard printers and multi-function peripherals.
This update fixes the following bugs:
  • Previously, certain Python scripts used the interpreter line "#!/usr/bin/env python". Due to this issue, these scripts used an incorrect version during the execution. With this update, the interpreter line is changed and uses the path /usr/bin/python. (BZ#608003)
  • Previously, the license text was missing. This update adds the license text to the hplip-common sub-package. (BZ#613707)
  • Previously, the hp-toolbox utility failed to add new printers due to incorrect handling of CUPS authentication in the cupsext Python extension. This update corrects the handling. Now, new printers can be added successfully. (BZ#616569)
  • Previously, the CUPS Web Interface button, displayed in hp-toolbox when no connected devices were shown, led to an incorrect URL. This update corrects this URL so that there is no error message shown. (BZ#633899)
  • This update upgrades HPLIP to the current version to allow support for a wider range of HP printers. (BZ#652255)
All HPLIP users are advised to upgrade to these updated packages, which fix these bugs.

1.83. httpd

1.83.1. RHBA-2011:0706: bug fix update

Updated httpd packages that fix multiple bugs are now available for Red Hat Enterprise Linux 6.
The Apache HTTP Server is a popular web server.
This update fixes the following bugs:
  • Due to a bug in the filter initialization process, filters configured using the mod_filter module were not handled correctly if a "sub-request" took place. For example, using the "FilterChain" directive to configure the "DEFLATE" compression filter with a Server-Side-Include page could result in pages which were only partially compressed. With this update, filters used with mod_filter operate correctly. (BZ#631849)
  • If arguments passed to the ab benchmarking program triggered a memory allocation failure, ab could terminate unexpectedly with a segmentation fault. With this update, the memory allocation failure is now trapped earlier, and the program exits gracefully with an error message. (BZ#645846)
  • * When executing the "service httpd stop" command, a 10-seconds timeout is used before terminating the httpd parent process in case of error. If this timeout was insufficient, resources did not allow the parent process to terminate cleanly and could be leaked. This update introduces the "STOP_TIMEOUT" environment variable, which can be used in the /etc/sysconfig/httpd configuration file to change the timeout. This can be used to allow a longer delay and fix resource leaks if the httpd parent is slow to terminate. (BZ#657480)
  • When configuring the httpd service, using a mod_ldap directive in the "VirtualHost" container caused the HTTP server to stop caching requests to a directory server. This update applies a patch that corrects this error, and the use of mod_ldap directives in the "VirtualHost" context no longer prevents the httpd service from caching LDAP requests. (BZ#676635)
  • Prior to this update, an attempt to use configuration with multiple virtual hosts sharing the same ID and private key file could prevent the httpd service from starting with an error message written to the error_log file. With this update, the underlying source code has been modified to address this issue, and the httpd service now starts as expected. (BZ#676831)
  • When using the prefork Multi-Processing Module (MPM), children processes with persistent connections (that is, with the "KeepAlive" directive set to "On") kept processing new requests even when a graceful restart had been issued. This update applies a patch that corrects this error, and children processes with the persistent connections no longer process new requests when a graceful restart is requested. (BZ#679476)
  • Previously, an attempt to start the httpd service with the mod_ssl module in FIPS mode failed. With this update, an upstream patch has been applied to implement support for the FIPS mode in the mod_ssl module, and httpd no longer fails to start. (BZ#684144)
All users of httpd are advised to upgrade to these updated packages, which fix these bugs.

1.84. hwdata

1.84.1. RHEA-2011:0701: enhancement update

An updated hwdata package that adds various enhancements is now available for Red Hat Enterprise Linux 6.1.
The hwdata package contains tools for accessing and displaying hardware identification and configuration data.
This update adds the following enhancements:
  • The pci.ids database has been updated to include the information about the MegaRAID SAS Thunderbolt device. (BZ#662673)
  • The pci.ids database has been updated to include the information about the Matrox IMMv2 management controller and integrated MatroxG200eR video controller. (BZ#633837)
Users of hwdata are advised to upgrade to this updated package, which adds these enhancements.

1.85. ibus

1.85.1. RHBA-2011:0518: bug fix update

Updated ibus packages that fix various bugs are now available.
The IBus (Intelligent Input Bus for Linux OS) package is an input method platform.
These updated packages provide fixes for the following bugs:
  • ibus-x11 displayed at the incorrect window position and did not follow xterm for X11 applications in big endian 64-bit machines such as ppc64 and s390x. This was caused by the call_data->ic_attr[i].value being able to support only CARD32 data (32-bit) while the problematic machines were 64-bit machines. The code was changed to support 64-bit machines, thus ibus now works as expected. (BZ#651915)
  • ibus displayed incorrect text for the "up" and "down" buttons for the Kannada translation. The translated text was corrected, thus now the buttons display the correct translated text. (BZ#633330)
  • ibus displayed inconsistent translations on "up" and "down" buttons compared to text at the bottom of the window referring to "up" and "down" buttons for the Gujarati translation. Translation was amended for consistency and the button text and descriptive text at the bottom of the window are now the same. (BZ#635541)
Users of ppc64, s390x machines, Gujarati, and Kannada, are advised to upgrade to these updated packages, which resolve these issues.

1.86. ibus-chewing

1.86.1. RHBA-2011:0737: bug fix update

An updated ibus-chewing package that fixes a bug is now available for Red Hat Enterprise Linux 6.
IBus-chewing is an IBus front-end of Chewing, an intelligent Chinese input method for Zhuyin (BoPoMoFo) users.
This updated ibus-chewing package fixes the following bug:
  • Previously, the IBus-chewing did not specify the rank parameter for the zh-TW locale in the input engine description file. This caused the IBus tool not to provide any default input method engine for the locale. This update adds the input method engines to the chewing.xml file and ibus-chewing is selected as the default input method for zh_TW users. (BZ#627794)
All users of ibus-chewing are advised to upgrade to this updated package, which resolves this issue.

1.87. ibus-hangul

1.87.1. RHBA-2011:0538: bug fix update

An updated ibus-hangul package that fixes one bug is now available for Red Hat Enterprise Linux 6.
The ibus-hangul package is a Korean language input engine platform for the IBus input method (IM).
This update fixes the following bug:
  • Previously, preedit was not restored when the candidate window was restored while focusing in. Due to this behavior, the candidate window remained open after focus changes. This update resolves this issue with a change in the code. Now, the candidate window is hidden as expected. (BZ#610075)
Users who require Korean language input are advised to upgrade to this updated package, which fixes this bug.

1.88. ibus-m17n

1.88.1. RHBA-2011:0539: bug fix update

An updated ibus-m17n package that resolves several bugs is now available.
The ibus-m17n is a multilingual input engine for the IBus input method platform.
This updated package provides fixes for the following bugs:
  • When a new user and language were selected during login, ibus-m17n did not load all input methods provided for that language; only one input method was loaded and marked for use as the default input method. The user had to manually search for and add any other input methods that they wanted to use. All input methods for a given language are now loaded upon login, and can be accessed from the ibus-m17n Preferences tab. (BZ#641243)
  • ibus-m17n did not recognize the AltGr (ISO Level 3 Shift) key as a virtual modifier key, making it impossible to input the Rupee Symbol (U+20B9) with an Indic Keyboard. The AltGr key is now recognized by ibus-m17n. (BZ#652201)
All users of ibus-m17n are advised to upgrade to this updated package, which resolves these issues.

1.89. ibutils

1.89.1. RHBA-2011:0814: bug fix update

Updated ibutils packages that resolve an issue are now available.
The ibutils package provides InfiniBand network and path diagnostics.
These updated ibutils packages fix the following bug:
  • Previous releases of the ibutils package were not built for the PowerPC 64-bit architecture. This has been fixed and the ibutils package is now built for the PowerPC 64-bit architecture as well. (BZ#695204)
All users of ibutils are advised to upgrade to these updated packages, which resolve this issue.

1.90. im-chooser

1.90.1. RHBA-2011:0666: bug fix update

An updated im-chooser package that fixes a bug is now available.
im-chooser is a GUI configuration tool to choose the Input Method to be used or disable Input Method usage on the desktop.
This updated package addresses the following issue:
  • The im-chooser window was not re-sizable. This caused the title bar text to run into the right-hand close box in some locales. With this update, the im-chooser window is now re-sizable, ensuring the title bar text displays properly no matter the current locale. (BZ#634146)
All im-chooser users are advised to upgrade to this updated package, which resolves this issue.

1.91. imsettings

1.91.1. RHBA-2011:0521: bug fix update

Updated imsettings packages that fix a bug are now available for Red Hat Enterprise Linux 6.
The imsettings packages provide a library and command line tools to configure and control input-methods settings. Users normally access it through the "im-chooser" GUI tool.
This update fixes the following bug:
  • It was not possible to turn off the GTK XIM input-method module from imsettings. As a consequence, users were unable to enter Unicode characters using the Ctrl+Shift+U shortcut. With this update, the default GTK input-method is restored to gtk-im-context-simple, which allows Unicode input with the shortcut. Now only desktop locales that normally need X locale compose default to using the GTK XIM input-method module. (BZ#616061)
Users of imsettings should upgrade to these updated packages, which fix this bug.

1.92. initscripts

1.92.1. RHBA-2010:1004: bug fix update

An updated initscripts package that fixes a bug is now available for Red Hat Enterprise Linux 6.
The initscripts package contains system scripts to boot your system, change runlevels, activate and deactivate most network interfaces, and shut the system down cleanly.
This update fixes the following bug:
  • Prior to this update, users were unable to set the VLAN tag to 0 when creating a logical network. With this update, the ifup script has been updated to permit this value, and the VLAN identification number can now be set to 0 as expected. (BZ#660327)
All users are advised to upgrade to this updated package, which resolves this issue.

1.92.2. RHBA-2011:0647: bug fix and enhancement update

An enhanced initscripts package that fixes various bugs and provides an enhancement is now available for Red Hat Enterprise Linux 6.
The initscripts package contains system scripts to boot your system, change runlevels, activate and deactivate most network interfaces, and shut the system down cleanly.
Bug fixes:
BZ#558575
Previously, initscripts used quoted strings as values following the =~ operators and the strings were thus matched as literal strings. However, they should be matched as regular expressions. With this update, the quotes were dropped and the strings are matched as regular expressions as expected.
BZ#598850
Previously, some systems failed to access the harware clock on system shutdown. This happened because the shutdown script ran the hwclock tool, which attempted to access the /dev/rtc device even if it did not exist. With this update, initscripts verifies if the /dev/rtc device exists before attempting to run the hwclock tool.
BZ#612934
The ifdown command could have failed to stop an NIC (Network Interface Controller) with a warning that the connection was unknown. This happened because, in some cases, the function, which verifies whether the NIC is managed by NetworkManager, returned an incorrect result. With this update, the function returns the correct result and the ifdown command stops the NIC correctly.
BZ#620461
Previously, if there was a bind mount for the / directory, the system could have failed to remount the root directory as a read-only file system on shutdown. This occurred because the script attempted to remount the defined bind mount instead of the root directory. With this update, the root directory is remounted successfully.
BZ#629257
Previously, a conflict between the sulogin tool and the login shell could have prevented the user from entering the root password in single-user mode. This occurred when switching from runlevel 3 because the login shell was not terminated and attempted to accept the input for the sulogin tool. With this update, the tty.conf and serial.conf files have been modified to have the login shell stopped when changing to runlevels S and the problem no longer occurs.
BZ#632584
On interactive startup, in some locals, the shortcut of the Continue key in the respective language did not work. This occurred due to an error in the local po files. With this update, the po files have been updated and the shortcuts work as expected.
BZ#633984
Previously, the network service did not support configurations with multiple IP addresses with the new syntax (IPADDRESSn/PREFIXn). This caused conflicts between network configurations set with the network service and network configurations set with the NetworkManager tool. With this update, the network service supports the configurations with multiple IP addresses with the new syntax and the conflicts no longer occur.
BZ#634996
Previously, the tty.conf file contained a comment with a typographical mistake ("sepcified"). With this update, the word is spelled correctly ("specified").
BZ#635360
Previously, the system was not able to create a logical network with the VLAN (virtual local area network) tag value 0. With this update, this tag value is allowed.
BZ#637058
Previously, the /etc/sysconfig/clock file did not document where the user can configure whether the hwclock tool should be using the local time or UTC (Coordinated Universal Time). This update adds comments documenting the setting location into the sysconfig.txt file.
BZ#645861
Previously, the /etc/ppp/ipv6-up and /etc/ppp/ip-up.ipv6to4 scripts used the incorrect alias ipv6_exec_ip and failed to bring up the routes. This update modifies the scripts so that they uses the ip command and the routes are now brought up as expected.
BZ#648966
For IPoIB (IP over InfiniBand) child interfaces, the value of the DEVICETYPE variable was calculated incorrectly. This happened because the calculation preserved the period (.) sign in the device name. This could have caused failure of the ifup-ib and ifdown-ib scripts. With this update, DEVICETYPE is resolved correctly.
BZ#654101
On shutdown, the system tried to deactivate the sit IPv6 over IPv4 tunnel device even though it was not active. With this update, the system verifies if the device is active before attempting to shut it down.
BZ#658138
Previously, the kexec-disable script was run when switching to runlevel 1. Because the kdump service is disabled in runlevel 1, the script freed the memory reserved for kdump. After the user changed from runlevel 1 to runlevel 3, which has kdump enabled, the system had set reserved memory size to 0 and kdump failed to start up. With this update, the kexec-disable job is no longer run in runlevel 1.
BZ#660036
Previously, all architectures used identical shmmax (maximum size of a shared memory segment) and shmall (maximum size of the total shared memory) values. However, the values vary depending on the system architecture. This update provides the settings of these values for various architectures.
BZ#664051
Previously, various errors occurred when some devices were inserted (for example, PCI network card). This happened because the biodevname tool assigned them interface names containing hash (#) signs, which were forbidden in such names. With this update, interface names can contain hash (#) signs and the problem no longer occurs.
BZ#667211
Previously, initscripts did not distinguish between the period (.) signs used by the sysctl device, which were delimiting the paths, and the period (.) signs used by VLANs, which were delimiting IDs. This caused that all sysctl calls to the VLAN interfaces failed. With this update, when calling a sysctl device, initscripts substitutes the periods in its name with forward slash (/) signs and the sysctl calls to a VLAN interface succeed.
BZ#669110
Previously, a slave network interface of a bonded interface failed to start if it defined the setting MASTER in double quotes (for example, as "bond0"). With this update, the respective scripts have been adapted to parse the value definition correctly even if double-quoted.
BZ#670154
The ifdown command could have failed to stop a bridge device with a warning that the connection was unknown. This happened because the function, which verified whether the device is managed by NetworkManager, returned an incorrect result. With this update, the function returns a correct result and the ifdown command stops the bridge device correctly.
BZ#674397
Section 8 of the sys-unconfig manual page contained various typographical mistakes. With this update, the man page is updated and the mistakes are corrected.
BZ#676708
Previously, a name of a VLAN interface had to start with the eth prefix followed by digits. If the user provided a name, which did not follow these requirements, the interface could not be started or stopped. With this update, the user can provide a custom name and the interface can be operated correctly.
BZ#696110
Previously, the netfs startup script attempted to run the mdadm tool always when the /etc/mdadm.conf file existed and could have failed if mdadm was not installed. With this update, the script first verifies if the mdadm tool is installed and only then runs its binary.
BZ#682879
The system could have failed to unmount the NFS (Network File System) shares on shutdown. This occurred because the system failed to unmount the NFS shares if they were in use. With this update, the unmouting of NFS shares on shutdown has been updated and the NFS shares are unmounted successfully even if in use.
Enhancement:
BZ#633323
With this update, the IBM System z profile was updated to allow an optimized performance setting for System z.
All users are advised to upgrade to this updated package, which fixes these bugs and provides this enhancement.

1.93. iok

1.93.1. RHBA-2011:0555: bug fix update

An updated iok package that fixes a bug is now available.
iok is an Indic on-screen virtual keyboard that supports the Assamese, Bengali, Gujarati, Hindi, Kannada, Marathi, Malayalam, Punjabi, Oriya, Sindhi, Tamil and Telugu languages. Currently, iok works with Inscript and xkb keymaps for Indian languages, and is able to parse and display non-Inscript keymaps as well.
The file that contains the Oriya translations for iok contained some entries with Latin text appended to the Oriya text. The Latin text caused the key size to increase, thus the keyboard became too large to fit in the display area.
The Latin text has now been removed from the Oriya translation, causing the Oriya keyboard and keys size to conform to other languages. (BZ#636756)
Users are advised to upgrade to this updated iok package, which resolves this issue.

1.94. ipmitool

1.94.1. RHEA-2011:0775: enhancement update

An enhanced ipmitool package is now available for Red Hat Enterprise Linux 6.
The ipmitool package contains a command line utility for interfacing with devices that support the Intelligent Platform Management Interface specification (IPMI). IPMI is an open standard for machine health, inventory, and remote power control.
This updated ipmitool package adds the following enhancements:
  • The update adds the "delloem" command extensions for Dell OEM hardware, which provide support for Peripheral Component Interconnect Express (PCIe) solutions, LCD setting on panel, NIC setting, and power monitoring. This update also provides manual pages for the "delloem" command extensions. (BZ#631649)
  • This update integrates the Linux Multiple Device (MD) driver with ipmitool to indicate SES (SCSI enclosure services) status and drive activities for PCIe SSD based solutions. (BZ#663793)
Users of ipmitool are advised to upgrade to this updated package, which adds these enhancements.

1.95. iproute

1.95.1. RHBA-2011:0757: bug fix and enhancement update

Updated iproute packages that fix several bugs and add one enhancement are now available.
The iproute packages contain networking utilities designed to use the advanced networking capabilities of the Linux kernel.
These updated packages contain the following bug fixes:
  • If the "ip" command was used to create a veth device pair, and the "peer" parameter was specified but the "name" parameter was not used, a segmentation fault occurred. The "name" parameter was an unnecessary requirement for this operation. The need for this parameter has been removed and the command now works as expected. (BZ#636943)
  • The ss man page contained a reference to a nonexistent file. This reference has been updated with the correct file location. (BZ#641918)
  • Previously, attempting to flush a secondary device with "ip secondary" would fail. This issue has now been corrected and secondary devices are flushed as expected. (BZ#678986)
These updated packages also provide the following enhancement:
  • Support for adding, deleting, and modifying security contexts or security labels in ipsec policies has been added to the "ip xfrm" command. (BZ#670295)
All users of iproute are advised to upgrade to these updated packages, which correct these issues and add this enhancement.

1.96. iprutils

1.96.1. RHEA-2011:0643: enhancement update

An updated iprutils package that adds an enhancement is now available for Red Hat Enterprise Linux 6.
The iprutils package provides utilities to manage and configure SCSI devices that are supported by the "ipr" SCSI storage device driver.
This update adds the following enhancement:
  • The iprutils package has been updated to provide support for the 6Gb SAS RAID storage controller on 64-bit IBM POWER7. (BZ#633328)
All users of iprutils are advised to upgrade to this updated package, which adds this enhancement.

1.97. iptables

1.97.1. RHBA-2011:0557: bug fix and enhancement update

Updated iptables packages that fix two bugs and add one enhancement are now available for Red Hat Enterprise Linux 6.
The iptables utility controls the network packet filtering code in the Linux kernel.
This update fixes the following bugs:
  • Previously, ip6tables did not support Portable Transparent Proxy Solution (TPROXY). Due to this lack, the IPv6 transparent proxy support was missing and IPv6 transparency was not available. This update adds this option. (BZ#590186)
  • Previously, the command "service iptables save" did not restore the context for the save file and the save backup file. It also used /tmp for the temporary file. Due to the wrong context of the save and save backup file, there could be an error the next time the save functionality is used. This update restores the context and also saves the temporary files correctly. (BZ#644273)
This update adds also the following enhancement:
  • Previously, iptables did not support auditing. Due to this issue, information for remote address/port, target address/port, protocol, and result (success/fail) could not be recorded as an audit event. This update adds the required audit support. This enhancement depends on the presence of auditing support in the kernel. (BZ#642393)
All iptables users are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

1.98. iputils

1.98.1. RHBA-2011:0546: bug fix update

An updated iputils package that fixes various bugs is now available for Red Hat Enterprise Linux 6.
The iputils package contains basic utilities for monitoring a network, including ping.
This update fixes the following bugs:
  • The ping and ping6 commands were previously not compiled as position independent executables (PIE). In this update, they are now built as PIE executables. (BZ#630022)
  • Previously, the tracepath6 program that is included in the iputils package failed to resolve a target when using the "-n" option and a hostname as the target. The fix for this problem has been provided so that tracepath6 now works as expected. (BZ#671579)
  • Previously, when the rdisc utility that is included in the iputils package was run on a system with an interface having two IP addresses assigned to the interface, an error was issued and rdisc failed to start. The bug has been fixed and the rdisc start failure no longer occurs. (BZ#688332)
All iputils users should upgrade to this updated package, which resolves these issues.

1.99. irqbalance

1.99.1. RHBA-2011:0804: bug fix update

An updated irqbalance package that fixes one bug is now available for Red Hat Enterprise Linux 6.
irqbalance is a daemon that evenly distributes IRQ load across multiple CPUs for enhanced performance.
This update fixes the following bug:
  • irqbalance was not previously built with PIE and RELRO enabled, as they were in Red Hat Enterprise Linux 5. In this update, irqbalance is built as a PIE executable and is using RELRO protection. (BZ#630023)
Users of irqbalance are advised to upgrade to this updated package, which fixes this bug.

1.100. iscsi-initiator-utils

1.100.1. RHBA-2011:0733: bug fix and enhancement update

Updated iscsi-initiator-utils packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6.
The iscsi package provides the server daemon for the Internet Small Computer System Interface (iSCSI) protocol, as well as the utility programs used to manage it. iSCSI is a protocol for distributed disk access using SCSI commands sent over Internet Protocol networks.
Bug fixes:
BZ#691902
When performing SendTargets discovery, the "iface" NIC binding was ignored. Instead, iscsiadm used the network device determined by the "route" command. SendTargets discovery now occurs through the NIC specified in the "iface" binding information.
BZ#631821
If SendTargets discovery required multiple TEXT commands because of a long target list, iscsiadm did not set the Initiator Task Tag in compliance with RFC-3720 as published by the Internet Engineering Task Force. This issue has been fixed, and iscsiadm now sets the Initiator Task Tag correctly.
BZ#634021
Attempting to reboot or shut down a system with a running iSCSI daemon caused the system to stop responding because iSCSI sessions remained running. All iSCSI sessions now shut down correctly, so no issues are encountered on shut down or reboot.
BZ#689359
Previously, iSCSI did not work on the Broadcom NetXtreme II 1GbE Quad Port Copper Adapter (BCM57712) when connected to a Data Center Bridging-enabled (DCB-enabled) switch over VLAN. This occurred because VLAN tagging was set twice, once by uIP and once by the DCB firmware. This update corrects this issue with VLAN tagging.
BZ#640115
The ISCSI_ERR_INVALID_HOST error event was not being handled correctly, leaving iSCSI sessions in memory when the iSCSI driver was attempting to shut down. This resulted in the driver failing to respond during shutdown of sessions that used the Broadcom NetXtreme II Network Adapter driver.
BZ#593269
The iscsiadm and iscsid commands depended on files in /usr, but did not require that /usr was mounted when they were used. This resulted in failures without useful error messages when the user attempted to use these commands when /usr was not mounted. This issue has been corrected, and these failures no longer occur.
BZ#658428
Starting or stopping the iSCSI service while accessing the root partition directly through an iSCSI disk could cause iSCSI to become unresponsive and incorrect status information to be reported. Attempting to stop the iSCSI service in this circumstance now warns that iSCSI cannot be shut down while Root is on an iSCSI disk, and all statuses are reported correctly.
BZ#599539
The brcm_iscsiuio usage message displayed in response to the brcm_iscsiuio --help command contained two unsupported options: --foreground and --pid. The man page omitted five supported options: --debug, --help, -h, -p and --version. The unsupported options have been removed from the usage message, and all supported options have been added to the brcm_iscsiuio man page.
BZ#599542
The iscsiadm usage message displayed in response to the iscsiadm --help command omitted 24 supported options. Additionally, the iscsiadm man page omitted one supported option (--host) and contained one unsupported option (--info). These errors have now been corrected.
BZ#624437
iscsiadm did not accept host names or aliases as valid values for the --portal argument when in "node" mode. This resulted in failure, because iscsiadm expected the value returned during discovery as the value for --portal. iscsiadm now attempts to match a host name to the IP address returned during discovery, so this issue no longer occurs.
BZ#688783
If debug message logging was disabled, the iSCSI daemon failed to set the socket priority according to the Data Center Bridging application priority setting, which resulted in packets being sent with the default priority incorrectly. Socket priority is now set based on the Data Center Bridging application priority setting in this situation.
Enhancements:
BZ#640340
When iscsiadm failed or exited incorrectly, it did not output useful error codes. Meaningful error codes now exist for these situations, and are described further in the iscsiadm man page.
BZ#523492
Support for Data Center Bridging has been added to the iSCSI driver.
BZ#635899
brcm_iscsiuio provides the ARP and DHCP functionality to offload iSCSI functionality. Support has been added for IPv6, VLAN, and several new Broadcom network cards.
All users of iscsi-initiator-utils are advised to upgrade to these updated packages, which provide these bug fixes and add these enhancements.

1.101. iwl6000-firmware

1.101.1. RHBA-2011:0549: bug fix update

An updated iwl6000-firmware package is now available for Red Hat Enterprise Linux 6.
The iwl6000-firmware package provides the iwlagn wireless driver with the firmware it requires to function correctly with Intel Wireless WiFi Link 6000 series adapters.
This update upgrades the iwl6000 firmware to upstream version 9.221.4.1, which provides a number of bug fixes over the previous version. (BZ#568034)
Users of wireless devices which use iwl6000 firmware are advised to upgrade to this updated package.

1.102. iwl6050-firmware

1.102.1. RHBA-2011:0551: bug fix update

An updated iwl6050-firmware package is now available for Red Hat Enterprise Linux 6.
The iwl6050-firmware package provides the iwlagn wireless driver with the firmware it requires to function correctly with Intel Wireless WiFi Link 6050 series adapters.
This update upgrades the iwl6050 firmware to upstream version 41.28.5.1, which provides a number of bug fixes over the previous version. (BZ#663748)
Users of wireless devices which use iwl6050 firmware are advised to upgrade to this updated package.

1.103. java-1.6.0-openjdk

1.103.1. RHSA-2010:0865: Important security and bug fix update

Updated java-1.6.0-openjdk packages that fix several security issues and two bugs are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
These packages provide the OpenJDK 6 Java Runtime Environment and the OpenJDK 6 Software Development Kit.
defaultReadObject of the Serialization API could be tricked into setting a volatile field multiple times, which could allow a remote attacker to execute arbitrary code with the privileges of the user running the applet or application. (CVE-2010-3569)
Race condition in the way objects were deserialized could allow an untrusted applet or application to misuse the privileges of the user running the applet or application. (CVE-2010-3568)
Miscalculation in the OpenType font rendering implementation caused out-of-bounds memory access, which could allow remote attackers to execute code with the privileges of the user running the java process. (CVE-2010-3567)
JPEGImageWriter.writeImage in the imageio API improperly checked certain image metadata, which could allow a remote attacker to execute arbitrary code in the context of the user running the applet or application. (CVE-2010-3565)
Double free in IndexColorModel could cause an untrusted applet or application to crash or, possibly, execute arbitrary code with the privileges of the user running the applet or application. (CVE-2010-3562)
The privileged accept method of the ServerSocket class in the Common Object Request Broker Architecture (CORBA) implementation in OpenJDK allowed it to receive connections from any host, instead of just the host of the current connection. An attacker could use this flaw to bypass restrictions defined by network permissions. (CVE-2010-3561)
Flaws in the Swing library could allow an untrusted application to modify the behavior and state of certain JDK classes. (CVE-2010-3557)
Flaws in the CORBA implementation could allow an attacker to execute arbitrary code by misusing permissions granted to certain system objects. (CVE-2010-3554)
UIDefault.ProxyLazyValue had unsafe reflection usage, allowing untrusted callers to create objects via ProxyLazyValue values. (CVE-2010-3553)
HttpURLConnection improperly handled the "chunked" transfer encoding method, which could allow remote attackers to conduct HTTP response splitting attacks. (CVE-2010-3549)
HttpURLConnection improperly checked whether the calling code was granted the "allowHttpTrace" permission, allowing untrusted code to create HTTP TRACE requests. (CVE-2010-3574)
HttpURLConnection did not validate request headers set by applets, which could allow remote attackers to trigger actions otherwise restricted to HTTP clients. (CVE-2010-3541, CVE-2010-3573)
The Kerberos implementation improperly checked the sanity of AP-REQ requests, which could cause a denial of service condition in the receiving Java Virtual Machine. (CVE-2010-3564)
The java-1.6.0-openjdk packages shipped with the GA release of Red Hat Enterprise Linux 6 mitigated a man-in-the-middle attack in the way the TLS/SSL protocols handle session renegotiation by disabling renegotiation. This update implements the TLS Renegotiation Indication Extension as defined in RFC 5746, allowing secure renegotiation between updated clients and servers. (CVE-2009-3555)
The NetworkInterface class improperly checked the network "connect" permissions for local network addresses, which could allow remote attackers to read local network addresses. (CVE-2010-3551)
Information leak flaw in the Java Naming and Directory Interface (JNDI) could allow a remote attacker to access information about otherwise-protected internal network names. (CVE-2010-3548)
Note: Flaws concerning applets in this advisory (CVE-2010-3568, CVE-2010-3554, CVE-2009-3555, CVE-2010-3562, CVE-2010-3557, CVE-2010-3548, CVE-2010-3564, CVE-2010-3565, CVE-2010-3569) can only be triggered in OpenJDK by calling the "appletviewer" application.
Bug fixes:
  • One defense in depth patch. (BZ#639922)
  • Problems for certain SSL connections. In a reported case, this prevented the JBoss JAAS modules from connecting over SSL to Microsoft Active Directory servers. (BZ#642779)

1.103.2. RHSA-2011:0281: Important security update

Updated java-1.6.0-openjdk packages that fix several security issues are now available for Red Hat Enterprise Linux 5 and 6.
The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
These packages provide the OpenJDK 6 Java Runtime Environment and the OpenJDK 6 Software Development Kit.
A flaw was found in the Swing library. Forged TimerEvents could be used to bypass SecurityManager checks, allowing access to otherwise blocked files and directories. (CVE-2010-4465)
A flaw was found in the HotSpot component in OpenJDK. Certain bytecode instructions confused the memory management within the Java Virtual Machine (JVM), which could lead to heap corruption. (CVE-2010-4469)
A flaw was found in the way JAXP (Java API for XML Processing) components were handled, allowing them to be manipulated by untrusted applets. This could be used to elevate privileges and bypass secure XML processing restrictions. (CVE-2010-4470)
It was found that untrusted applets could create and place cache entries in the name resolution cache. This could allow an attacker targeted manipulation over name resolution until the OpenJDK VM is restarted. (CVE-2010-4448)
It was found that the Java launcher provided by OpenJDK did not check the LD_LIBRARY_PATH environment variable for insecure empty path elements. A local attacker able to trick a user into running the Java launcher while working from an attacker-writable directory could use this flaw to load an untrusted library, subverting the Java security model. (CVE-2010-4450)
A flaw was found in the XML Digital Signature component in OpenJDK. Untrusted code could use this flaw to replace the Java Runtime Environment (JRE) XML Digital Signature Transform or C14N algorithm implementations to intercept digital signature operations. (CVE-2010-4472)
Note: All of the above flaws can only be remotely triggered in OpenJDK by calling the "appletviewer" application.
This update also provides one defense in depth patch. (BZ#676019)
All users of java-1.6.0-openjdk are advised to upgrade to these updated packages, which resolve these issues. All running instances of OpenJDK Java must be restarted for the update to take effect.

1.103.3. RHSA-2011:0214: Moderate security update

Updated java-1.6.0-openjdk packages that fix one security issue are now available for Red Hat Enterprise Linux 5 and 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
These packages provide the OpenJDK 6 Java Runtime Environment and the OpenJDK 6 Software Development Kit.
A denial of service flaw was found in the way certain strings were converted to Double objects. A remote attacker could use this flaw to cause Java-based applications to hang, for instance if they parse Double values in a specially-crafted HTTP request. (CVE-2010-4476)
All users of java-1.6.0-openjdk are advised to upgrade to these updated packages, which resolve this issue. All running instances of OpenJDK Java must be restarted for the update to take effect.

1.103.4. RHBA-2011:0632: bug fix and enhancement update

Updated java-1.6.0-openjdk packages that fix various bugs and provide several enhancements are now available for Red Hat Enterprise Linux 6.
These packages provide the OpenJDK 6 Java Runtime Environment and the OpenJDK 6 Software Development Kit.
The java-1.6.0-openjdk package has been upgraded to upstream version 1.9.7, which provides a number of bug fixes and enhancements over the previous version. (BZ#658208)
In addition, these updated java-1.6.0-openjdk packages fix the following bug:
  • In Java GUI (graphical user interface) applications, placeholder characters were displayed when run in the Japanese locale. This happened because the fontconfig file defined a mapping to an unavailable font. With this update, the IPA or VLGothic fonts are mapped instead and Japanese characters are displayed correctly. (BZ#659300)
All users of java-1.6.0-openjdk are advised to upgrade to these updated packages, which resolve these issues and add these enhancements.

1.104. jss

1.104.1. RHBA-2011:0621: bug fix update

Updated jss packages that fix two bugs are now available for Red Hat Enterprise 6.
JSS is a Java binding to Network Security Services (NSS), which provides SSL/TLS network protocols and other security services in the Public Key Infrastructure (PKI) suite. JSS is primarily utilized by the Certificate Server.
This update fixes the following bugs:
  • With this update, JSS has been upgraded to upstream version 4.2.6, which provides a number of bug fixes over the previous version. This rebase is necessary to support the Certificate Server. (BZ#656094)
  • Previously, JSS did not release a PK11 slot. Due to this problem, a resource leak occurred and prevented NSS from shutting down because NSS detected that resources were still in use. This update corrects the resource leak and allows NSS to shutdown. (BZ#676179)
All users of JSS are advised to upgrade to these updated packages, which fix these bugs.

1.105. kabi-whitelists

1.105.1. RHBA-2010:0856: bug fix update

An updated kabi-whitelists package that fixes a bug is now available.
The kabi-whitelists package contains reference files documenting interfaces provided by the Red Hat Enterprise Linux 6 kernel that are considered to be stable by Red Hat kernel engineering, and safe for longer term use by third party loadable device drivers, as well as for other purposes.
This update fixes the following bug:
  • Two exported kernel symbols were removed from the final version of the Kernel Application Binary Interface (kABI) whitelists package in Red Hat Enterprise Linux 6. (BZ#643570)
All users are advised to upgrade to this updated package, which resolves this issue.

1.105.2. RHEA-2011:0797: enhancement update

An updated kabi-whitelists package that adds two enhancements is now available for Red Hat Enterprise Linux 6.
The kabi-whitelists package contains reference files documenting interfaces provided by the Red Hat Enterprise Linux 6 kernel that are considered to be stable by Red Hat kernel engineering, and safe for longer term use by third party loadable device drivers, as well as for other purposes.
This update adds the following enhancements:
  • This update removes the "blk_queue_ordered" and the "blk_queue_physical_block_size" symbols from the Red Hat Enterprise Linux 6.0 kernel ABI whitelists. (BZ#636975)
  • This update adds several newly approved interfaces to the kernel ABI whitelists. (BZ#682967)
Note: It is not necessary to install the kabi-whitelists package in order to use Driver Updates. The kabi-whitelists package only provides reference files for use by those creating Driver Update packages, or for those who wish to enable support for verification of kernel ABI compatibility by installing the appropriate Yum plugin.
Users of kabi-whitelists are advised to upgrade to this updated package, which adds these enhancements.

1.106. kdelibs

1.106.1. RHSA-2011:0464: Moderate security update

Updated kdelibs packages that fix two security issues are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
The kdelibs packages provide libraries for the K Desktop Environment (KDE).
A cross-site scripting (XSS) flaw was found in the way KHTML, the HTML layout engine used by KDE applications such as the Konqueror web browser, displayed certain error pages. A remote attacker could use this flaw to perform a cross-site scripting attack against victims by tricking them into visiting a specially-crafted URL. (CVE-2011-1168)
A flaw was found in the way kdelibs checked the user specified hostname against the name in the server's SSL certificate. A man-in-the-middle attacker could use this flaw to trick an application using kdelibs into mistakenly accepting a certificate as if it was valid for the host, if that certificate was issued for an IP address to which the user specified hostname was resolved to. (CVE-2011-1094)
Note: As part of the fix for CVE-2011-1094, this update also introduces stricter handling for wildcards used in servers' SSL certificates.
Users should upgrade to these updated packages, which contain backported patches to correct these issues. The desktop must be restarted (log out, then log back in) for this update to take effect.

1.107. kdenetwork

1.107.1. RHSA-2011:0465: Important security update

Updated kdenetwork packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The kdenetwork packages contain networking applications for the K Desktop Environment (KDE).
A directory traversal flaw was found in the way KGet, a download manager, handled the "file" element in Metalink files. An attacker could use this flaw to create a specially-crafted Metalink file that, when opened, would cause KGet to overwrite arbitrary files accessible to the user running KGet. (CVE-2011-1586)
Users of kdenetwork should upgrade to these updated packages, which contain a backported patch to resolve this issue. The desktop must be restarted (log out, then log back in) for this update to take effect.

1.108. kernel

1.108.1. RHSA-2011:0928 – Important: kernel security and bug fix update

Important

This update has already been released as the security errata RHSA-2011:0928
Updated kernel packages that resolve several security issues and fix various bugs are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links after each description below.
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security fixes:
* It was found that the receive hook in the ipip_init() function in the ipip module, and in the ipgre_init() function in the ip_gre module, could be called before network namespaces setup is complete. If packets were received at the time the ipip or ip_gre module was still being loaded into the kernel, it could cause a denial of service. (CVE-2011-1767, CVE-2011-1768, Moderate)
* It was found that an mmap() call with the MAP_PRIVATE flag on /dev/zero would create transparent hugepages and trigger a certain robustness check. A local, unprivileged user could use this flaw to cause a denial of service. (CVE-2011-2479, Moderate)
Bug fixes:
BZ#712413
Deleting the lost+found directory on a file system with inodes of size greater than 128 bytes and reusing inode 11 for a different file caused the extended attributes for inode 11 (which were set before a umount operation) to not be saved after a file system remount. As a result, the extended attributes were lost after the remount. With this update, inodes store their extended attributes under all circumstances.
BZ#711540
Disk read operations on a memory constrained system could cause allocations to stall. As a result, the system performance would drop considerably. With this update, latencies seen in page reclaim operations have been reduced and their efficiency improved; thus, fixing this issue.
BZ#711528
Multiple GFS2 nodes attempted to unlink, rename, or manipulate files at the same time, causing various forms of file system corruption, panics, and withdraws. This update adds multiple checks for dinode's i_nlink value to assure inode operations such as link, unlink, or rename no longer cause the aforementioned problems.
BZ#711535
Migration of a Windows XP virtual guest during the early stage of a boot caused the virtual guest OS to fail to boot correctly. With this update, the underlying source code has been modified to address this issue, and the virtual guest OS no longer fails to boot.
BZ#713135
When using certain SELinux policies, such as the MLS policy, it was not possible to properly mount the cgroupfs file system due to the way security checks were applied to the new cgroupfs inodes during the mount operation. With this update, the security checks applied during the mount operation have been changed so that they always succeed, and the cgroupfs file system can now be successfully mounted and used with the MLS SELinux policy. This issue did not affect systems which used the default targeted policy.
BZ#711546
Prior to this update, Red Hat Enterprise Linux Xen (up to version 5.6) did not hide 1 GB pages and RDTSCP (enumeration features of CPUID), causing guest soft lock ups on AMD hosts when the guest's memory was greater than 8 GB. With this update, a Red Hat Enterprise Linux 6 HVM (Hardware Virtual Machine) guest is able to run on Red Hat Enterprise Linux Xen 5.6 and lower.
BZ#714190
A kernel panic in the mpt2sas driver could occur on an IBM system using a drive with SMART (Self-Monitoring, Analysis and Reporting Technology) issues. This was because the driver was sending an SEP request while the kernel was in the interrupt context, causing the driver to enter the sleep state. With this update, a fake event is not executed from the interrupt context, assuring the SEP request is properly issued.
BZ#713494
When VLANs stacked on top of multiqueue devices passed through these devices, the queue_mapping value was not properly decremented because the VLAN devices called the physical devices via the ndo_select_queue method. This update removes the multiqueue functionality, resolving this issue.
BZ#713492
Prior to this update, code was missing from the netif_set_real_num_tx_queues() function which prevented an increment of the real number of TX queues (the real_num_tx_queues value). This update adds the missing code; thus, resolving this issue.
BZ#711524
Prior to this update, interrupts were enabled before the dispatch log for the boot CPU was set up, causing kernel panic if a timer interrupt occurred before the log was set up. This update adds a check to the scan_dispatch_log function to ensure the dispatch log has been allocated.
BZ#712414
Prior to this update, in the __cache_alloc() function, the ac variable could be changed after cache_alloc_refill() and the following kmemleak_erase() function could receive an incorrect pointer, causing kernel panic. With this update, the ac variable is updated after the cache_alloc_refill() unconditionally.
BZ#711520
Due to an uninitialized variable (specifically, the isr_ack variable), a virtual guest could become unresponsive when migrated while being rebooted. With this update, the said variable is properly initialized, and virtual guests no longer hang in the aforementioned scenario.
BZ#713458
A previously introduced update intended to prevent IOMMU (I/O Memory Management Unit) domain exhaustion introduced two regressions. The first regression was a race where a domain pointer could be freed while a lazy flush algorithm still had a reference to it, eventually causing kernel panic. The second regression was an erroneous reference removal for identity mapped and VM IOMMU domains, causing I/O errors. Both of these regressions could only be triggered on Intel based platforms, supporting VT-d, booted with the intel_iommu=on boot option. With this update, the underlying source code of the intel-iommu driver has been modified to resolve both of these problems. A forced flush is now used to avoid the lazy use after free issue, and extra checks have been added to avoid the erroneous reference removal.
BZ#713831
Previously, auditing system calls used a simple check to determine whether a return value was positive or negative, which also determined the success of the system call. With an exception of few, this worked on most platforms and with most system calls. For example, the 32 bit mmap system call on the AMD64 architecture could return a pointer which appeared to be of value negative even though pointers are normally of unsigned values. This resulted in the success field being incorrect. This patch fixes the success field for all system calls on all architectures.
BZ#709381
A previously released patch for BZ#625487 introduced a kABI (Kernel Application Binary Interface) workaround that extended struct sock (the network layer representation of sockets) by putting the extension structure in the memory right after the original structure. As a result, the prot->obj_size pointer had to be adjusted in the proto_register function. Prior to this update, the adjustment was done only if the alloc_slab parameter of the proto_register function was not 0. When the alloc_slab parameter was 0, drivers performed allocations themselves using sk_alloc and as the allocated memory was lower than needed, a memory corruption could occur. With this update, the underlying source code has been modified to address this issue, and a memory corruption no longer occurs.
BZ#682989
Prior to this update, the /proc/diskstats file showed erroneous values. This occurred when the kernel merged two I/O operations for adjacent sectors which were located on different disk partitions. Two merge requests were submitted for the adjacent sectors, the first request for the second partition and the second request for the first partition, which was then merged to the first request. The first submission of the merge request incremented the in_flight value for the second partition. However, at the completion of the merge request, the in_flight value of a different partition (the first one) was decremented. This resulted in the erroneous values displayed in the /proc/diskstats file. With this update, the merging of two I/O operations which are located on different disk partitions has been fixed and works as expected.
Enhancements:
BZ#711550
This updates introduces a kernel module option that allows the disabling of the Flow Director.
BZ#711548
This update adds XTS (XEX-based Tweaked CodeBook) AES256 self-tests to meet the FIPS-140 requirements.
BZ#711545
This update reduces the overhead of probes provided by kprobe (a dynamic instrumentation system), and enhances the performance of SystemTap.
Users should upgrade to these updated packages, which contain backported patches to correct these issues and add the enhancement. The system must be rebooted for this update to take effect.

1.108.2. RHSA-2011:0836 – Important: kernel security and bug fix update

Important

This update has already been released as the security errata RHSA-2011:0836
Updated kernel packages that resolve several security issues and fix various bugs are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links after each description below.
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security fixes:
* An integer underflow flaw, leading to a buffer overflow, was found in the Linux kernel's Datagram Congestion Control Protocol (DCCP) implementation. This could allow a remote attacker to cause a denial of service. (CVE-2011-1770, Important)
* Missing sanity checks were found in setup_arg_pages() in the Linux kernel. When making the size of the argument and environment area on the stack very large, it could trigger a BUG_ON(), resulting in a local denial of service. (CVE-2010-3858, Moderate)
* A missing validation check was found in the bcm_release() and raw_release() functions in the Linux kernel's Controller Area Network (CAN) implementation. This could allow a local, unprivileged user to cause a denial of service. (CVE-2011-1598, CVE-2011-1748, Moderate)
* The fix for Red Hat Bugzilla bug 656461, as provided in RHSA-2011:0542, introduced a regression in the cifs_close() function in the Linux kernel's Common Internet File System (CIFS) implementation. A local, unprivileged user with write access to a CIFS file system could use this flaw to cause a denial of service. (CVE-2011-1771, Moderate)
Red Hat would like to thank Dan Rosenberg for reporting CVE-2011-1770; Brad Spengler for reporting CVE-2010-3858; and Oliver Hartkopp for reporting CVE-2011-1748.
Bug fixes:
BZ#704000
This update includes two fixes for the bna driver, specifically:
  • A memory leak was caused by an unintentional assignment of the NULL value to the RX path destroy callback function pointer after a correct initialization.
  • During a kernel crash, the bna driver control path state machine and firmware did not receive a notification of the crash, and, as a result, were not shut down cleanly.
BZ#704002
This update adds a missing patch to the ixgbe driver to use the kernel's generic routine to set and obtain the DCB (Data Center Bridging) priority. Without this fix, applications could not properly query the DCB priority.
BZ#704009
Prior to this update, the interrupt service routine was performing unnecessary MMIO operation during performance testing on IBM POWER7 machines. With this update, the logic of the routine has been modified so that there are fewer MMIO operations in the performance path of the code. Additionally, as a result of the aforementioned change, an existing condition was exposed where the IPR driver (the controller device driver) could return an unexpected HRRQ (Host Receive Request) interrupt. The original code flagged the interrupt as unexpected and then reset the adapter. After further analysis, it was confirmed that this condition could occasionally occur and the interrupt can be safely ignored. Additional code provided by this update detects this condition, clears the interrupt, and allows the driver to continue without resetting the adapter.
BZ#704011
After receiving an ABTS response, the FCoE (Fibre Channel over Ethernet) DDP error status was cleared. As a result, the FCoE DDP context invalidation was incorrectly bypassed and caused memory corruption. With this update, the underlying source code has been modified to address this issue, and memory corruption no longer occurs.
BZ#704014
The Brocade BFA FC/FCoE driver was previously selectively marked as a Technology Preview based on the type of the adapter. With this update, the Brocade BFA FC/FCoE driver is always marked as a Technology Preview.
BZ#704280
This update standardizes the printed format of UUIDs (Universally Unique Identifier)/GUIDs (Globally Unique Identifier) by using an additional extension to the %p format specifier (which is used to show the memory address value of a pointer).
BZ#704282
The Brocade BFA FC SCSI driver (bfa driver) has been upgraded to version 2.3.2.4. Additionally, this update provides the following two fixes:
  • A firmware download memory leak was caused by the release_firmware() function not being called after the request_firmware() function. Similarly, the firmware download interface has been fixed and now works as expected.
  • During a kernel crash, the bfa I/O control state machine and firmware did not receive a notification of the crash, and, as a result, were not shut down cleanly.
Users should upgrade to these updated packages, which contain backported patches to correct these issues. The system must be rebooted for this update to take effect.

1.108.3. RHSA-2011:0542: Important Red Hat Enterprise Linux 6.1 kernel security, bug fix and enhancement update

Important

This update has already been released as the security errata RHSA-2011:0542
Updated kernel packages that fix multiple security issues, address several hundred bugs, and add numerous enhancements are now available as part of the ongoing support and maintenance of Red Hat Enterprise Linux version 6. This is the first regular update.
The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links after each description below.
The kernel packages contain the Linux kernel, the core of any Linux operating system.
Security fixes:
* Multiple buffer overflow flaws were found in the Linux kernel's Management Module Support for Message Passing Technology (MPT) based controllers. A local, unprivileged user could use these flaws to cause a denial of service, an information leak, or escalate their privileges. (CVE-2011-1494, CVE-2011-1495, Important)
* A flaw was found in the Linux kernel's Ethernet bonding driver implementation. Packets coming in from network devices that have more than 16 receive queues to a bonding interface could cause a denial of service. (CVE-2011-1581, Important)
* A flaw was found in the Linux kernel's networking subsystem. If the number of packets received exceeded the receiver's buffer limit, they were queued in a backlog, consuming memory, instead of being discarded. A remote attacker could abuse this flaw to cause a denial of service (out-of-memory condition). (CVE-2010-4251, Moderate)
* A flaw was found in the Linux kernel's Transparent Huge Pages (THP) implementation. A local, unprivileged user could abuse this flaw to allow the user stack (when it is using huge pages) to grow and cause a denial of service. (CVE-2011-0999, Moderate)
* A flaw was found in the transmit methods (xmit) for the loopback and InfiniBand transports in the Linux kernel's Reliable Datagram Sockets (RDS) implementation. A local, unprivileged user could use this flaw to cause a denial of service. (CVE-2011-1023, Moderate)
* A flaw in the Linux kernel's Event Poll (epoll) implementation could allow a local, unprivileged user to cause a denial of service. (CVE-2011-1082, Moderate)
* An inconsistency was found in the interaction between the Linux kernel's method for allocating NFSv4 (Network File System version 4) ACL data and the method by which it was freed. This inconsistency led to a kernel panic which could be triggered by a local, unprivileged user with files owned by said user on an NFSv4 share. (CVE-2011-1090, Moderate)
* A missing validation check was found in the Linux kernel's mac_partition() implementation, used for supporting file systems created on Mac OS operating systems. A local attacker could use this flaw to cause a denial of service by mounting a disk that contains specially-crafted partitions. (CVE-2011-1010, Low)
* A buffer overflow flaw in the DEC Alpha OSF partition implementation in the Linux kernel could allow a local attacker to cause an information leak by mounting a disk that contains specially-crafted partition tables. (CVE-2011-1163, Low)
* Missing validations of null-terminated string data structure elements in the do_replace(), compat_do_replace(), do_ipt_get_ctl(), do_ip6t_get_ctl(), and do_arpt_get_ctl() functions could allow a local user who has the CAP_NET_ADMIN capability to cause an information leak. (CVE-2011-1170, CVE-2011-1171, CVE-2011-1172, Low)
Red Hat would like to thank Dan Rosenberg for reporting CVE-2011-1494 and CVE-2011-1495; Nelson Elhage for reporting CVE-2011-1082; Timo Warns for reporting CVE-2011-1010 and CVE-2011-1163; and Vasiliy Kulikov for reporting CVE-2011-1170, CVE-2011-1171, and CVE-2011-1172.
Bug fixes:
BZ#622327
Previously, an operation such as madvise(MADV_MERGEABLE) may have split VMAs (Virtual Memory Area) without checking if any huge page had to be split into regular pages, leading to huge pages to be still mapped in VMA ranges that would not be large enough to fit huge pages. With this update, huge pages are checked whether they have been split when any VMA is being truncated.
BZ#640576
Occasionally, the anon_vma variable could contain the value null in the page_address_in_vma function and cause kernel panic. With this update, kernel panic no longer occurs.
BZ#640579
Previously, building under memory pressure with KSM (Kernel Shared Memory) caused KSM to collapse with an internal compiler error indicating an error in swapping. With this update, data corruption during swapping no longer occurs.
BZ#640611
The fork() system call led to an rmap walk finding the parent huge-pmd twice instead of once, thus causing a discrepancy between the mapcount and page_mapcount check, which could have led to erratic page counts for subpages. This fix ensures that that the rmap walk is accurate when a process is forked, thus resolving the issue.
BZ#642570
The fork() system call led to an rmap walk finding the parent huge-pmd twice instead of once, thus causing a discrepancy between the mapcount and page_mapcount check, which could have led to erratic page counts for subpages. This fix ensures that that the rmap walk is accurate when a process is forked, thus resolving the issue.
BZ#646384
Running certain workload tests on a Non-Uniform Memory Architecture (NUMA) system could cause kernel panic at mm/migrate.c:113. This was due to a false positive BUG_ON. With this update, the false positive BUG_ON has been removed.
BZ#622640
If an Intel 82598 10 Gigabit Ethernet Controller was configured in a way that caused peer-to-peer traffic to be sent to the Intel X58 I/O hub (IOH), a PCIe credit starvation problem occurred. As a result, the system would hang. With this update, the system continues to work and does not hang.
BZ#637332
The ixgbe driver has been upgraded to upstream version 3.0.12, which provides a number of bug fixes and enhancements over the previous version.
BZ#696337
During light or no network traffic, the active-backup interface bond using ARP monitoring with validation could go down and return due to an overflow or underflow of system timer interrupt ticks (jiffies). With this update, the jiffies calculation issues problems have been fixed and a bond interface works as expected.
BZ#609516
Booting a system via the Extensible Firmware Interface (EFI) could result in a low resolution of the boot screen due to a VGA palette corruption. With this update, the VGA palette corruption no longer occurs and the boot screen is displayed in the correct resolution and colors.
BZ#626454
Systems with an updated Video BIOS for the AMD RS880 would not properly boot with KMS (Kernel mode-setting) enabled. With this update, the Video BIOS boots successfully when KMS is enabled.
BZ#640870
This update fixes the slow memory leak in the i915 module in DRM (Direct Rendering Manager) and GEM (Graphics Execution Manager).
BZ#640871
Previously, a race condition in the TTM (Translation Table Maps) module of the DRM (Direct Rendering Manager) between the object destruction thread and object eviction could result in a major loss of large objects reference counts. Consequently, this caused a major amount of memory leak. With this update, the race condition no longer occurs and any memory leaks are prevented.
BZ#644896
When booting the latest Red Hat Enterprise Linux 6 kernel (-78.el6), the system hanged shortly after the booting. Access to the file system died and the console started outputting soft lockup messages from the TTM code. With this update, the aforementioned behavior no longer occurs and the system boots as expected.
BZ#530618
Under some circumstances, a kernel panic on installation or boot may occur if the "Interrupt Remapping" feature is enabled in the BIOS. To work around this issue, disable interrupt remapping in the BIOS.
BZ#681017
Under some circumstances, faulty logic in the system BIOS could report that ASPM (Active State Power Management) was not supported on the system, but leave ASPM enabled on a device. This could lead to AER (Advanced Error Reporting) errors that the kernel was unable to handle. With this update, the kernel proactively disables ASPM on devices when the BIOS reports that ASPM is not supported, safely eliminating the aforementioned issues.
BZ#624628
Prior to this update, a guest could use the poll() function to find out whether the host-side connection was open or closed. However, with a SIGIO signal, this can be done asynchronously, without having to explicitly poll each port. With this update, a SIGIO signal is sent for any host connect/disconnect events. Once the SIGIO signal is received, the open/close status of virtio-serial ports can be obtained using the poll() system call.
BZ#628805
The virtio-console device did not handle the hot-unplug operation properly. As a result, virtio-console could access the memory outside the driver's memory area and cause kernel panic on the guest. With this update, multiple fixes to the virtio-console device resolved this issue and the hot-unplug operation works as expected.
BZ#634232
Applications and agents using virtio serial ports would block messages even though there were messages queued up and ready to be read in the virtqueue. This was due to virtio_console's poll function checking whether a port was NULL to determine if a read operation would result in a block of the port. However, in some cases, a port can be NULL even though there are buffers left in the virtqueue to be read. This update introduces a more sophisticated method of checking whether a port contains any data; thus, preventing queued up messages from being incorrectly blocked.
BZ#635535
Prior to this update, user space could submit (using the write() operation) a buffer with zero length to be written to the host, causing the qemu hypervisor instance running on that host to crash. This was caused by the write() operation triggering a virtqueue event on the host, causing a NULL buffer to be accessed. With this update, user space is no longer allowed to submit zero-sized buffers and the aforementioned crash no longer occur.
BZ#643750
Using a virtio serial port from an application, filling it until the write command returns -EAGAIN and then executing a select command for the write command, caused the select command to not return any values when using the virtio serial port in a non-blocking mode. When used in blocking mode, the write command waited until the host indicated it had used up the buffers. This was due to the fact that the poll operation waited for the port->waitqueue pointer; however, nothing woke the waitqueue when there was room again in the queue. With this update, the queue is woken via host notifications so that buffers consumed by the host can be reclaimed, the queue freed, and the application write operations may proceed again.
BZ#643751
If a host was slow in reading data or did not read data at all, blocking write() calls not only blocked the program that called the write() call but also the entire guest. This was caused by the write() calls waiting until an acknowledgment that the data consumed was received from the host. With this update, write() calls no longer wait for such acknowledgment: control is immediately returned to the user space application. This ensures that even if the host is busy processing other data or is not consuming data at all, the guest is not blocked.
BZ#605786
Please note that in future versions of Red Hat Enterprise Linux 6 (i.e. Red Hat Enterprise Linux 6.1 and later) the auto value setting of the crashkernel= parameter (i.e. crashkernel=auto) is deprecated.
BZ#675102
Prior to this update, the /usr/include/linux/fs.h file was broken, causing other packages to fail to build. With this update, the underlying source code has been modified to address this issue, and packages no longer fail to build.
BZ#629178
Prior to this update, the execve utility exhibited the following flaw. When an argument and any environment data were copied from an old task's user stack to the user stack of a newly-execve'd task, the kernel would not allow the process to be interrupted or rescheduled. Therefore, when the argument or environment string data was (abnormally) large, there was no "interactivity" with the process while the execve() function was transferring the data. With this update, fatal signals (like CTRL+c) can now be received and handled and a process is allowed to yield to higher priority processes during the data transfer.
BZ#616296
While not mandated by any specification, Linux systems rely on NMIs (Non-maskable Interrupts) being blocked by an IF-enabling (Interrupt Flag) STI instruction (an x86 instruction that enables interrupts; Set Interrupts); this is also the common behavior of all known hardware. Prior to this update, kernel panic could occur on guests using NMIs extensively (for example, a Linux system with the nmi_watchdog kernel parameter enabled). With this update, an NMI is disallowed when interrupts are blocked by an STI. This is done by checking for the condition and requesting an interrupt window exit if it occurs. As a result, kernel panic no longer occurs.
BZ#645898
Prior to this update, running context-switch intensive workloads on KVM guests resulted in a large number of exits (kvm_exit) due to control register (CR) accesses by the guest, thus, resulting in poor performance. This update includes a number of optimizations which allow the guest not to exit to the hypervisor in the aforementioned case and improve the overall performance.
BZ#626814
In some cases the NFS server fails to notify NFSv4 clients about renames and unlinks done by other clients, or by non-NFS users of the server. An application on a client may then be able to open the file at its old pathname (and read old cached data from it, and perform read locks on it), long after the file no longer exists at that pathname on the server. To work around this issue, use NFSv3 instead of NFSv4. Alternatively, turn off support for leases by writing 0 to /proc/sys/fs/leases-enable (ideally on boot, before the nfs server is started). This change prevents NFSv4 delegations from being given out, restoring correctness at the expense of some performance.
BZ#695488
In a four node cluster environment, a deadlock could occur on machines in the cluster when the nodes accessed a GFS2 file system. This resulted in memory fragmentation which caused the number of network packet fragments in requests to exceed the network hardware limit. The network hardware firmware dropped the network packets exceeding this limit. With this update, the network packet fragmentation was reduced to the limit of the network hardware, no longer causing problems during memory fragmentation.
BZ#627741
The zfcpdump (kdump) kernel on IBM System z could not be debugged using the dump analysis tool crash, because the vmlinux file in the kernel-kdump-debuginfo RPM did not contain DWARF debug information. With this update, the CONFIG_DEBUG_KERNEL parameter is set to yes and the needed debug information is provided.
BZ#647365
On IBM System z systems, user space programs could access the /dev/mem file (which contains an image of main memory), where an accidental memory (write) access could potentially be harmful. To restrict access to memory from user space through the /dev/mem file, the CONFIG_STRICT_DEVMEM configuration option has been enabled for the default kernel. The kdump and debug kernels have this option switched off by default.
BZ#668470
If a CPU is set offline, the nohz_load_balancer CPU is updated. However, under certain circumstances, the nohz_load_balancer CPU would not be updated, causing the offlined CPU to be enqueued with various timers which never expired. As a result, the system could become unresponsive. With this update, the nohz_load_balancer CPU is always updated; systems no longer become unresponsive.
BZ#636678
Previously, in order to install Snapshot 13, boot parameter nomodeset xforcevesa had to be added to the kernel command line, otherwise, the screen turned black and and prevented the installation. With this update, the aforementioned boot parameter no longer has to be specified and the installation works as expected.
BZ#635710
The qla2xxx driver for QLogic Fibre Channel Host Bus Adapters (HBAs) has been updated to upstream version 8.03.05.01.06.1-k0, which provides a number of bug fixes and enhancements over the previous version.
BZ#695478
The driver for the NetXen NX3031 network adapter did not support more than 14 fragments for a non-TSO (TCP Segmentation Offload) packet, which could have caused network failures. This update corrects the driver.
BZ#641764
Previously, accounting of reclaimable inodes did not work correctly. When an inode was reclaimed it was only deleted from the per-AG (per Allocation Group) tree. Neither the counter was decreased, nor was the parent tree's AG entry untagged properly. This caused the system to hang indefinitely. With this update, the accounting of reclaimable inodes works properly and the system remains responsive.
BZ#632021
If a Xen guest which specifies a physical path such as /dev/sda1 in its /etc/fstab configuration file, instead of a labeled path, then the following workaround procedure should be followed:
  1. The "xen_emul_unplug=never" option should be added to the guest's kernel boot line.
  2. The /etc/fstab entry should be modified to specify a partition such as /dev/xvda1 for the /boot partition, or a proper partition label should be used for the file systems on the emulated block device.
  3. Finally, if the Xen guest configuration spec uses a line similar to the following:
    disk = [ 'file:/var/lib/xen/images/rhel6-guest.dsk,hda,w', ]
    …then that line should be changed to:
    disk = [ 'tap:aio:/var/lib/xen/images/rhel6-guest.dsk,hda,w', ]
    This line needs to be changed because the Xen para-virtualized disk driver is not supported with file-backed I/O.
BZ#680126
Using the pam_tty_audit.so module (which enables or disables TTY auditing for specified users) in the /etc/pam.d/sudo file and in the /etc/pam.d/system-auth file when the audit package is not installed resulted in soft lock-ups on CPUs. As a result, the kernel became unresponsive. This was due to the kernel exiting immediately after TTY auditing was disabled, without emptying the buffer, which caused the kernel to spin in a loop, copying 0 bytes at each iteration and attempting to push each time without any effect. With this update, a locking mechanism is introduced to prevent the aforementioned behavior.
BZ#625914
Previously, a kernel module not shipped by Red Hat was successfully loaded when the FIPS boot option was enabled. With this update, kernel self-integrity is improved by rejecting to load kernel modules which are not shipped by Red Hat when the FIPS boot option is enabled.
BZ#631547
Previously the cxgb3 (Chelsio Communications T3 10Gb Ethernet) adapter experienced parity errors. With this update, the parity errors are correctly detected and the cxgb3 adapter successfully recovers from them.
BZ#698016
When the iscsi driver detected the platform option-rom, it bypassed its local defaults and used the platform-provided parameters. With this update, if the platform specifies invalid OEM parameters, a warning message is printed, and the iSCSI driver falls back on its sensible internal default parameters rather than failing to load the driver altogether.
BZ#694106
After a raid45->raid0 takeover operation, another takeover operation (for example, raid0->raid5) resulted in kernel panic. This was due to the 'degraded' and 'plug' variables from the mddev structure not being cleared after the raid4->raid0 takeover. With this update, aforementioned variables are properly cleared, and no longer cause kernel panic.
BZ#550724
In some cases, under a small system load involve some I/O operation, processes started to lock up in the D state (that is, became unresponsive). The system load could in some cases climb steadily. This was due to the way the event channel IRQ (Interrupt Request) was set up. Xen events behave like edge-triggered IRQs, however, the kernel was setting them up as level-triggered IRQs. As a result, any action using Xen event channels could lock up a process in the D state. With this update, the handling has been changed from edge-triggered IRQs to level-triggered IRQs and process no longer lock up in the D state.
BZ#643371
A race condition occurred when Xen was presented with an inconsistent page type resulting in the crash of the kernel. With this update, the race condition is prevented and kernel crashes no longer occur.
BZ#645198
The Red Hat Enterprise Linux kernel can now be tainted with a "tech preview" status. If a kernel module causes the tainted status, then running the command "cat /proc/modules" will display a "(T)" next to any module that is tainting the kernel.
For more information about Technology Previews, refer to:

Important

Running a kernel with the tainted flag set may limit the amount of support that Red Hat can provide for the system.
BZ#694913
The "perf" subsystem failed to load on HP ProLiant servers, and messages similar to the following were logged to the console at boot time:
NMI watchdog disabled for cpu1: unable to create perf event: -2
This update includes a patch that allows the "perf" subsystem to load when using these servers, but only using the same counter that the BIOS uses. The implications of this are that "perf" statistics could be corrupted.
BZ#643667
Previously, Red Hat Enterprise Linux 6 enabled the CONFIG_IMA option in the kernel. This caused the kernel to track all inodes in the system in a radix tree, leading to a huge waste of memory. With this update, an optimized version of a tree (rbtree) is used and memory is no longer wasted.
BZ#615309
Direct Asynchronous I/O (AIO) which is not issued on file system block boundaries, and falls into a hole in a sparse file on ext4 or xfs file systems, may corrupt file data if multiple I/O operations modify the same file system block. Specifically, if qemu-kvm is used with the aio=native I/O mode over a sparse device image hosted on the ext4 or xfs filesystem, guest file system corruption will occur if partitions are not aligned with the host file system block size. This issue can be avoided by using one of the following techniques:
  1. Align AIOs on file system block boundaries, or do not write to sparse files using AIO on xfs or ext4 filesystems.
  2. KVM: Use a non-sparse system image file or allocate the space by zeroing out the entire file.
  3. KVM: Create the image using an ext3 host filesystem instead of ext4.
  4. KVM: Invoke qemu-kvm with aio=threads (this is the default).
  5. KVM: Align all partitions within the guest image to the host's file system block boundary (default 4k).
BZ#624909
Running a fsstress test which issues various operations on a ext4 filesystem when usrquota is enabled, the following JBD (Journaling Block Device) error was output in /var/log/messages:
JBD: Spotted dirty metadata buffer (dev = sda10, blocknr = 17635). There's a risk of filesystem corruption in case of system crash.
With this update, by always journaling the quota file modification in an ext4 file system the aforementioned message no longer appears in the logs.
BZ#593766
The /var/log/messages file could have slowly filled up with error messages similar to the following:
ACPI Error: Illegal I/O port address/length above 64K: 0x0000000000400020/4 (20090903/hwvalid-154)
ACPI Exception: AE_LIMIT, Returned by Handler for [SystemIO] (20090903/evregion-424)
ACPI Error (psparse-0537): Method parse/execution failed [\_GPE._L09] (Node ffff8800797cd298), AE_LIMIT
ACPI Exception: AE_LIMIT, while evaluating GPE method [_L09] (20090903/evgpe-568)
This error message no longer occurs with this update.
BZ#653245
The kernel syslog contains debugging information that is often useful during exploitation of other vulnerabilities such as kernel heap addresses. With this update, a new CONFIG_SECURITY_DMESG_RESTRICT option has been added to config-generic-rhel which prevents unprivileged users from reading the kernel syslog. This option is by default turned off (0), which means no restrictions.
BZ#627653
A regression was discovered that caused kernel panic during the booting of any SGI UV100 and UV1000 system unless the virtefi command line option was passed to the kernel by GRUB. With this update, the need for the virtefi command line option is removed and the kernel will boots as expected without it.
BZ#659480
Prior to this update, running the hwclock --systohc command could halt a running system. This was due to the interrupt transactions being looped back from a local IOH (Input/Output Hub), through the IOH to a local CPU (erroneously), which caused a conflict with I/O port operations and other transactions. With this update, the conflicts are avoided and the system continues to run after executing the hwclock --systohc command.
BZ#621304
The RELEASE_LOCKOWNER operation has been implemented for the NFSv4 client in order to avoid an exhaustion of NFS server state IDs, which could result in an NFS4ERR_RESOURCE error. Additionally, this update introduces NFSv4 lock state tracking in read/write requests and lock owners labeling.
BZ#626515
An implementation of the SHA (Secure Hash Algorithm) hashing algorithm for the IBM System z architecture did not produce correct hashes and could potentially cause memory corruption due to broken partial block handling. A partial block could break when it was followed by an update which filled it with leftover bytes. Instead of storing the new leftover bytes at the start of the buffer, they were stored immediately after the previous partial block. With this update, the index pointer is reset, thus resolving the aforementioned partial block handling issue.
BZ#661113
Outgoing packets were not fragmented after receiving the icmpv6 pkt-too-big message when using the IPSecv6 tunnel mode. This was due to the lack of IPv6 fragmentation support over an IPsec tunnel. With this update, IPv6 fragmentation is fully supported and works as expected when using the IPSecv6 tunnel mode.
BZ#630810
Prior to this update, performing live migration back and forth during guest installation with network adapters based on the 8168c chipset or the 8111c chipset triggered an rtl8169_interrupt hang due to a RxFIFO overflow. With this update, infinite loops in the IRQ (Interrupt Request) handler caused by RxFIFO overflows are prevented and the aforementioned hang no longer occurs.
BZ#629066
When booting a Red Hat Enterprise Linux 5.5 kernel on a guest on an AMD host system running Red Hat Enterprise Linux 6, the guest kernel crashes due to an unsupported MSR (Model Specific Registers) read of the MSR_K7_CLK_CTL model. With this update, KVM support was added for the MSR_K7_CLK_CTL model specific register used in the AMD K7 CPU models, thus, the kernel crashes no longer occur.
BZ#629836
Previously, a Windows XP host experienced the stop error screen (i.e. the "Blue Screen Of Death" error) when booted with the CPU mode name. With this update, a Windows XP host no longer experiences the aforementioned error due to added KVM (Kernel-based Virtual Machine) support for the MSR_EBC_FREQUENCY_ID model specific register.
BZ#629085
Under certain circumstances, a kernel thread that handles incoming messages from a server could unexpectedly exit by itself. As a result, the kernel thread would free some data structures which could then be referenced by another data structure, resulting in a kernel panic. With this update, kernel threads no longer unexpectedly exit; thus, kernel panic no longer occurs in the aforementioned case.
BZ#641408
Previously, calling the elevator_change function immediately after the blk_init_queue function resulted in a null pointer dereference. With this update, the null pointer dereference no longer occurs.
BZ#623199
In certain network setups (specifically, using VLAN on certain NICs where packets are sent through the VLAN GRO rx path), sending packets from an active ethernet port to another inactive ethernet port could affect the network's bridge and cause the bridge to acquire a wrong bridge port. This resulted in all packets not being passed along in the network. With this update, the underlying source code has been modified to address this issue, and network traffic works as expected.
BZ#683496
Prior to this update, adding a bond over a bridge inside a virtual guest caused the kernel to crash due to a NULL dereference. This update improves the tests for the presence of VLANs configured above bonding (additionally, this update fixes a regression introduced by the patch for BZ#633571) . The new logic determines whether a registration has occurred, instead of testing that the internal vlan_list of a bond is empty. Previously, the system panicked and crashed when vlan_list was not empty, but the vlgrp pointer was still NULL.
BZ#592879
The memory cgroup controller has its own Out of Memory routine (OOM killer) and kills a process at an OOM event. However, a race condition could cause the pagefault_out_of_memory function to be called after the memory cgroup's OOM. This invoked the generic OOM killer and a panic_on_oom could occur. With this update, only the memory cgroup's OOM killer is invoked and used to kill a process should an OOM occur.
BZ#613812
This update provides a number of patches that resolve a mutual exclusion fault which could cause the kernel to become unresponsive.
BZ#634500
Previously, MADV_HUGEPAGE was missing in the include/asm-generic/mman-common.h file which caused madvise to fail to utilize TPH. With this update, the madvise option was removed from /sys/kernel/mm/redhat_transparent_hugepage/enabled since MADV_HUGEPAGE was removed from the madvise system call.
BZ#619818
If device-mapper-multipath is used, and the default path failure timeout value (/sys/class/fc_remote_ports/rport-xxx/dev_loss_tmo) is changed, that the timeout value will revert to the default value after a path fails, and later restored. Note that this issue will present the lpfc, qla2xxx, ibmfc or fnic Fibre Channel drivers. To work around this issue the dev_loss_tmo value must be adjusted after each path fail/restore event
BZ#633907
During an installation through Cisco NPV (N port virtualization) to Brocade, adding a LUN (Logical Unit Number) through Add Advanced Target did not work properly. This was caused by the faulty resending of FLOGI (Fabric Login) when a Fibre Channel switch in the NPV mode rejected requests with zero Destination ID. With this update, the LUN is seen and able to be selected for installation.
BZ#633915
An I/O operation could fast fail when using Device Mapper Multipathing (dm-multipath) if the I/O operation could be retried by the scsi layer. This prevented the multipath layer from starting its error recovery procedure and resulted in unnecessary log messages in the appropriate log files. This update includes a number of optimizations that resolve the aforementioned issue.
BZ#636233
Previously, timing issues could cause the FIP (FCoE Initialization Protocol) FLOGIs to timeout even if there were no problems. This caused the kernel to go into a non-FIP mode even though it should have been in the FIP mode. With this update, the timing issues no longer occur and the kernel no longer switches to the non-FIP mode when logging to the Fibre Channel Switch/Forwarder.
BZ#636771
A Red Hat Enterprise Linux 6.0 host (with root on a local disk) with dm-multipath configured on multiple LUNs (Logical Unit Number) hit kernel panic (at scsi_error_handler) with target controller faults during an I/O operation on the dm-multipath devices. This was caused by multipath using the blk_abort_queue() function to allow lower latency path deactivation. The call to blk_abort_queue proved to be unsafe due to a race (between blk_abort_queue and scsi_request_fn). With this update, the race has been resolved and kernel panic no longer occurs on Red Hat Enterprise Linux 6.0 hosts.
BZ#638297
When an scsi command timed out and the fcoe/libfc driver aborted the command, a race could occur during the clean-up of the command which could result in kernel panic. With this update, the locking mechanism in the clean-up and abort paths was modified, thus, fixing the aforementioned issue.
BZ#643237
Prior to this update, when using Red Hat Enterprise Linux 6 with a qla4xxx driver and FC (Fibre Channel) drivers using the fc class, a device might have been put in the offline state due to a transport problem. Once the transport problem was resolved, the device was not usable until a user manually corrected the state. This update enables the transition from the offline state to the running state, thus, fixing the problem.
BZ#668114
Operating in the FIP (FCoE Initialization Protocol) mode and performing operations that bring up ports could cause the fcoe.ko and fnic.ko modules to not be able to re-login when a port was brought back up. This was due to a bug in the FCoE (Fiber Channel over Ethernet) layer causing improper handling of FCoE LOGO frames while in the FIP mode. With this update, FCoE LOGO frames are properly handled when in the FIP mode and the fcoe.ko and fnic.ko modules no longer fail to re-login.
BZ#632631
Previously, the s390 tape block driver crashed whenever it tried to switch the I/O scheduler. With this update, an official in-kernel API (elevator_change()) is used to switch the I/O scheduler safely; thus, the crashes no longer occurs.
BZ#635199
The barrier implementation in the Red Hat Enterprise Linux 6 kernel works by completely draining the I/O scheduler's queue, then issuing a preflush, a barrier, and finally a postflush request. However, since the supported file systems in Red Hat Enterprise Linux 6 all implement their own ordering guarantees, the block layer need only provide a mechanism to ensure that a barrier request is ordered with respect to other I/O already in the disk cache. This mechanism avoids I/O stalls experienced by queue draining. The block layer will be updated in future kernels to provide this more efficient mechanism of ensuring ordering.
Workloads that include heavy fsync or metadata activity will see an overall improvement in disk performance. Users taking advantage of the proportional weight I/O controller will also see a boost in performance. In preparation for the block layer updates, third party file system developers need to ensure that data ordering surrounding journal commits are handled within the file system itself, since the block layer will no longer provide this functionality.
These future block layer improvements will change some kernel interfaces such that symbols which are not on the kABI whitelist shall be modified. This may result in the need to recompile third party file system or storage drivers.
BZ#636994
Handling ALUA (Asymmetric Logical Unit Access) transitioning states did not work properly due to a faulty SCSI (Small Computer System Interface) ALUA handler. With this update, optimized state transitioning prevents the aforementioned behavior.
BZ#637805
Previously, a write request may have merged with a discard request. This could have posed a potential risk for 3rd party drivers which could possibly issue a discard without waiting properly. With this update, discarding of write block I/O requests by preventing merges of discard and write requests in one block I/O has been introduced, resolving the possible risks.
BZ#638525
Previously, the /proc/maps file which is read by LVM2 (Logical Volume Manager) contained inconsistencies.
BZ#644380
Running the Virtual Desktop Server Manager (VDSM) and performing an lvextend during an intensive Virtual Guest power up caused this operation to fail. Since lvextend was blocked, all components became non-responsive: vgs and lvs commands froze the session, Virtual Guests became Paused or Not Responding. This was caused by a faulty use of a lock. With this update, performing an lvextend operation works as expected.
BZ#658293
The lack of synchronization between the clearing of the QUEUE_FLAG_CLUSTER flag and the setting of the no_cluster flag in the queue_limits variable caused corruption of data. Note that this issue only occurred on hardware that did not support segment merging (that is, clustering). With this update, the synchronization between the aforementioned flags works as expected, thus, corruption of data no longer occurs.
BZ#669411
Deleting an SCSI (Small Computer System Interface) device attached to a device handler caused applications running in user space, which were performing I/O operations on that device, to become unresponsive. This was due to the fact that the SCSI device handler's activation did not propagate the SCSI device deletion via an error code and a callback to the Device-Mapper Multipath. With this update, deletion of an SCSI device attached to a device handler is properly handled and no longer causes certain applications to become unresponsive.
BZ#670572
For a device that used a Target Portal Group (TPG) ID which occupied the full 2 bytes in the RTPG (Report Target Port Groups) response (with either byte exceeding the maximum value that may be stored in a signed char), the kernel's calculated TPG ID would never match the group_id that it should. As a result, this signed char overflow also caused the ALUA handler to incorrectly identify the Asymmetric Access State (AAS) of the specified device as well as incorrectly interpret the supported AAS of the target. With this update, the aforementioned issue has been addressed and no longer occurs.
BZ#680140
Deleting an SCSI (Small Computer System Interface) device attached to a device handler caused applications running in user space, which were performing I/O operations on that device, to become unresponsive. This was due to the fact that the SCSI device handler's activation did not propagate the SCSI device deletion via an error code and a callback to the Device-Mapper Multipath. With this update, deletion of an SCSI device attached to a device handler is properly handled and no longer causes certain applications to become unresponsive.
BZ#647367
Migrating a guest could have resulted in dirty values for the guest being retained in memory, which could have caused both the guest and qemu to crash. The trigger for this was memory pages being both write-protected and dirty simultaneously. With this update, memory pages in the current bitmap are either dirty or write-protected when migrating a guest, with the result that neither qemu nor guest operating systems crash following a migration.
BZ#676579
Intensive usage of resources on a guest lead to a failure of networking on that guest: packets could no longer be received. The failure occurred when a DMA (Direct Memory Access) ring was consumed before NAPI (New API; an interface for networking devices which makes use of interrupt mitigation techniques) was enabled which resulted in a failure to receive the next interrupt request. The regular interrupt handler was not affected in this situation (because it can process packets in-place), however, the OOM (Out Of Memory) handler did not detect the aforementioned situation and caused networking to fail. With this update, NAPI is subsequently scheduled for each napi_enable operation; thus, networking no longer fails under the aforementioned circumstances.
BZ#626956
The kernel panicked when booting the kdump kernel on a s390 system with an initramfs that contained an odd number of bytes. With this update, an initramfs with sufficient padding such that it contains an even number of bytes is generated; thus, the kernel no longer panics.
BZ#631246
Previously, the destination MAC address validation was not checking for NPIV (N_Port ID Virtualization) addresses, which results in FCoE (Fibre Channel over Ethernet) frames being dropped. With this update, the destination MAC address check for FCoE frames has been modified so that multiple N_port IDs can be multiplexed on a single physical N_port.
BZ#641315
Reading the /proc/vmcore file on a Red Hat Enterprise Linux 6 system was not optimal because it did not always take advantage of reading through the cached memory. With this update, access to the /dev/oldmem device in the /proc/vmcore file is cached, resulting in faster copying to user space.
BZ#665110
Bonding, when operating in the ARP monitoring mode, made erroneous assumptions regarding the ownership of ARP frames when it received them for processing. Specifically, it was assumed that the the bonding driver code was the only execution context which had access to the ARP frames network buffer data. As a result, an operation was attempted on the said buffer (specifically, to modify the size of the data buffer) which was forbidden by the kernel when a buffer was shared among several execution contexts. The result of such an operation on a shared buffer could lead to data corruption. Consequently, trying to prevent the corruption, the kernel panicked. This shared state in the network buffer could be forced to occur, for example, when running the tcpdump utility to monitor traffic on the bonding interface. Every buffer the bond interface received would be shared between the driver and the tcpdump process, thus, resulting in the aforementioned kernel panic. With this update, for the particular affected path in the bonding driver, each inbound frame is checked whether it is in the shared state. In case a buffer is shared, a private copy is made for exclusive use by the bonding driver, thus, preventing the kernel panic.
BZ#672937
Reading the /proc/vmcore file was previously significantly slower on a Red Hat Enterprise Linux 6 system when compared to a Red Hat Enterprise Linux 5 system. This update enables caching of memory accesses; reading of the /proc/vmcore file is now noticeably faster.
BZ#680478
The kdump kernel (the second kernel) could in some cases become unresponsive due to a pending IPI (Inter-processor Interrupt) from the first kernel. The kernel tries to handle the IPI, but fails to do so due to a NULL pointer dereference. With this update, the underlying source code has been modified to address this issue, and kdump no longer hangs.
BZ#625585
Physical CPU Hotplug is not supported on Red Hat Enterprise Linux 6 i686.
BZ#681870
A Peripheral Component Interconnect Express (PCIe) Active State Power Management (ASPM) was not being properly enabled on some platforms. This resulted in the system becoming unresponsive and followed by a Non-Maskable Interrupt (NMI) on some HP ProLiant systems in the Hewlett Packard Smart Array (HPSA) or on some network cards. With this update, the underlying source code has been modified to address this issue.
BZ#694891
Intel Xeon processor E7 family processors have an issue in which some c-state transitions can cause false correctable Machine Check Exception (MCE) errors to be reported from MCE bank 6 to the user. On some E7 processor family systems, this resulted in "floods" of MCE errors. This patch disables MCE error reporting for bank 6.
BZ#634703
Systems that have an Emulex FC controller (with SLI-3 based firmware) installed could return a kernel panic during installation. With this update, kernel panic no longer occurs during installation.
BZ#651584
Kernel panic could occur when the gfs2_glock_hold function was called within the gfs2_process_unlinked_inode function. This was due to the fact that gfs2_glock_hold was being called without a reference already held on the inode in question. This update, resolves this problem by changing the order in which it acquires references to match that of the NFS code; thus, kernel panic no longer occurs.
BZ#695751
A previously applied patch accidentally removed a check that handled invalid EEPROM (Electrically Erasable Programmable Read-Only Memory) sizes. Without this check the EEPROM validation failed if the EEPROM size was invalid, causing the NIC (Network Interface Controller) to not function properly. This update reintroduces the aforementioned patch, fixing the problem.
BZ#628951
PowerPC systems having more than 1 TB of RAM could randomly crash or become unresponsive due to an incorrect setup of the Segment Lookaside Buffer (SLB) entry for the kernel stack. With this update, the SLB entry is properly set up.
BZ#636978
Previously, the vmstat (virtual memory statistics) tool incorrectly reported the disk I/O as swap-in on ppc64 and other architectures that do not support the TRANSPARENT_HUGEPAGE configuration option in the kernel. With this update, the vmstat tool no longer reports incorrect statistics and works as expected.
BZ#676640
The bnx2i driver could cause a system crash on IBM POWER7 systems. The driver's page tables were not set up properly on Big Endian machines, causing extended error handling (EEH) errors on PowerPC machines. With this update, the page tables are properly set up and a system crash no longer occurs in the aforementioned case.
BZ#678099
A race condition could occur during a threaded coredump causing some threads to not have a full register set. With this update, the underlying source code has been modified to address this issue and prevent the aforementioned race condition.
BZ#681668
If an EEH (Enhanced I/O Error Handling) error occurred too early in the boot process, the kernel panicked with an error message similar to the following:
Unable to handle kernel paging request for data at address 0x00000468
Oops: Kernel access of bad area, sig: 11 [#1]
This situation is detected and avoided with this update, with the result that the machine continues to boot normally.
BZ#683115
A race condition caused by a missing mutual exclusion lock in the device_pm_pre_add() function and the device_pm_pre_add_cleanup() function could occur during the booting of an IBM Power system. As a result, error diagnostic messages were displayed in dmesg. This update adds the missing mutual exclusion lock, resolving this issue.
BZ#684961
On the PowerPC architecture, a PCI adapter with two functions, one of which uses MSI (Message Signaled Interrupts), and one of which uses MSI-X (an extended version of MSI), could have triggered an EEH (Enhanced I/O Error Handling) from an MSI-X signal when MSI was disabled using an older interface. With this update, the newer interface is used to disable MSI, with the result that the adapter no longer signals a stray MSI-X interrupt, and no EEH is registered.
BZ#694327
A previously released patch added a spin_unlock into the dtl_disable function for the virtual processor dispatch trace log file. However, the dtl_function did not include a spin_unlock which could cause a deadlock to occur. With this update, the missing spin_unlock has been added, and a deadlock no longer occurs.
BZ#695678
Section 14.11.3.2 "H_REGISTER_VPA" in the POWER Architecture Platform Reference (PAPR) specified that Dispatch Trace Log (DTL) buffers could not cross Active Memory Sharing (AMS) environments and memory entitlement granule boundaries (of size 4kB). However, kmalloc (a method for allocating memory in the kernel) did not guarantee an alignment of the allocation beyond 8 bytes. This update adds a special kmem cache for DLT buffers with the aforementioned alignment requirement.
BZ#593566
Certain scan requests failed to complete before the network interface was brought down. As a result, a warning will appear in the kernel log regarding wdev_cleanup_work. In some cases connectivity may be lost until the next reboot. If connectivity is restored, then the warning may be safely ignored. In other cases, the driver module may need to be reloaded or the system may need to be rebooted.
BZ#633836
Installing a debug kernel caused the PERC (Dell PowerEdge RAID Controller) 700 adapter to enter an undefined state and produce incorrect error messages. This has been corrected so that installing the debug kernel no longer causes the PERC 700 adapter to enter an undefined state and display erroneous RAID DIMM error messages.
BZ#664832
Systems Management Applications using the libsmbios package could become unresponsive on Dell PowerEdge servers (specifically, Dell PowerEdge 2970 and Dell PowerEdge SC1435). The dcdbas driver can perform an I/O write operation which causes an SMI (System Management Interrupt) to occur. However, the SMI handler processed the SMI well after the outb function was processed, which caused random failures resulting in the aforementioned hang. With this update, the underlying source code has been modified to address this issue, and systems management applications using the libsmbios package no longer become unresponsive.
BZ#692673
If an error occurred during an I/O operation, the SCSI driver reset the megaraid_sas controller to restore it to normal state. However, on Red Hat Enterprise Linux 6, the waiting time to allow a full reset completion for the megaraid_sas controller was too short. The driver incorrectly recognized the controller as stalled, and, as a result, the system stalled as well. With this update, more time is given to the controller to properly restart, thus, the controller operates as expected after being reset.
BZ#638269
The lock reclaim operation on a Red Hat Enterprise Linux 6 NFSv4 client did not work properly when, after a server reboot, an I/O operation which resulted in a STALE_STATEID response was performed before the RENEW call was sent to the server. This behavior was caused due to the improper use of the state flags. While investigating this bug, a different bug was discovered in the state recovery operation which resulted in a reclaim thread looping in the nfs4_reclaim_open_state() function. With this update, both operations have been fixed and work as expected.
BZ#680549
Previously, the UDP (User Datagram Protocol) transmit path ran under a socket lock due to the corking feature, which limited scalability due to having to transmit to the same socket in multiple threads. With this update, the transmit path has been made lockless when corking is not used, which greatly increases UDP transmit speed.
BZ#630060
On a system configured with an HP Smart Array controller, during the kdump process, the capturing kernel could have become unresponsive and the following error message logged:
NMI: IOCK error (debug interrupt?)
As a workaround, the system can be configured by blacklisting the hpsa module in a configuration file such as /etc/modules.d/blacklist.conf, and specifying the disk_timeout option so that saving the vmcore over the network is possible.
BZ#700430
Under certain circumstances, a command could be left unprocessed when using either the cciss or the hpsa driver. This was because the HP Smart Array controller considered all commands to be completed when, in fact, some commands were still left in the completion queue. This could cause the file system to become read-only or panic and the whole system to become unstable. With this update, an extra read operation has been added to both of the aforementioned drivers, fixing this issue.
BZ#617137
On platforms using an Intel 7500 or an Intel 5500 chipset (or their derivatives), occasionally, a VT-d specification defined error occurred in the kdump kernel (the second kernel). As a result of the VT-d error, on some platforms, an SMI (System Management Interrupt) was issued and the system became unresponsive. With this update, a VT-d error is properly handled so that an SMI is no longer issued, and the system no longer hangs.
BZ#664364
Invocating an EFI (Extensible Firmware Interface) call caused a restart or a failure to boot to occur on a system with more than 512GB of memory because the EFI page tables did not map the whole kernel space. EFI page tables used only one PGD (Page Global Directory) entry to map the kernel space; thus, virtual addresses higher than PAGE_OFFSET + 512GB could not be accessed. With this update, EFI page tables map the whole kernel space.
BZ#655231
A previously introduced patch that prevented kbuild to attempt to sign an out-of-the-tree module only fixed this issue for cases when a full kernel tree was used for compiling. Using the kernel-devel package for compilation remained broken. This update allows out-of-the-tree modules to compile using the kernel-devel package only.
BZ#703504
Prior to this update, external modules could be built using the "-Werr" option, which resulted in a failure to build any major third party module. This update, disables the "-Werr" option for external modules, fixing the issue.
Enhancements:
BZ#628676
The zfcpdump tool was not able to mount ext4 file systems. Because ext4 is the default file system on Red Hat Enterprise Linux 6, with this update, ext4 file system support was added for the zfcpdump tool.
BZ#629205
The zfcpdump tool was not able to mount ext2 file systems. With this update, ext2 file system support was added for the zfcpdump tool.
BZ#636922
The ALSA HDA audio driver has been updated to improve support for new chipsets and HDA audio codecs.
BZ#693050
The perf subsystem's trace command has been replaced with the script command. Users should now use the script command.
BZ#633571
This update provides VLAN null tagging support (VLAN ID 0 can be used in tags).
BZ#591796, BZ#591797, BZ#624615, BZ#637237
USB 3.0 support has been changed from Technology Preview to full support, and supports Power Management as well as other chips other than NEC.
Users should upgrade to these updated packages, which contain backported patches to correct these issues, fix these bugs, and add these enhancement. The system must be rebooted for this update to take effect.

1.108.4. RHSA-2011:0498: Important security, bug fix, and enhancement update

The kernel packages contain the Linux kernel, the core of any Linux operating system.
Updated kernel packages that fix several security issues, various bugs, and add an enhancement are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
Security fixes:
  • An integer overflow flaw in ib_uverbs_poll_cq() could allow a local, unprivileged user to cause a denial of service or escalate their privileges. (CVE-2010-4649, Important)
  • An integer signedness flaw in drm_modeset_ctl() could allow a local, unprivileged user to cause a denial of service or escalate their privileges. (CVE-2011-1013, Important)
  • The Radeon GPU drivers in the Linux kernel were missing sanity checks for the Anti Aliasing (AA) resolve register values which could allow a local, unprivileged user to cause a denial of service or escalate their privileges on systems using a graphics card from the ATI Radeon R300, R400, or R500 family of cards. (CVE-2011-1016, Important)
  • A flaw in dccp_rcv_state_process() could allow a remote attacker to cause a denial of service, even when the socket was already closed. (CVE-2011-1093, Important)
  • A flaw in the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation could allow a remote attacker to cause a denial of service if the sysctl "net.sctp.addip_enable" and "auth_enable" variables were turned on (they are off by default). (CVE-2011-1573, Important)
  • A memory leak in the inotify_init() system call. In some cases, it could leak a group, which could allow a local, unprivileged user to eventually cause a denial of service. (CVE-2010-4250, Moderate)
  • A missing validation of a null-terminated string data structure element in bnep_sock_ioctl() could allow a local user to cause an information leak or a denial of service. (CVE-2011-1079, Moderate)
  • An information leak in bcm_connect() in the Controller Area Network (CAN) Broadcast Manager implementation could allow a local, unprivileged user to leak kernel mode addresses in "/proc/net/can-bcm". (CVE-2010-4565, Low)
  • A flaw was found in the Linux kernel's Integrity Measurement Architecture (IMA) implementation. When SELinux was disabled, adding an IMA rule which was supposed to be processed by SELinux would cause ima_match_rules() to always succeed, ignoring any remaining rules. (CVE-2011-0006, Low)
  • A missing initialization flaw in the XFS file system implementation could lead to an information leak. (CVE-2011-0711, Low)
  • Buffer overflow flaws in snd_usb_caiaq_audio_init() and snd_usb_caiaq_midi_init() could allow a local, unprivileged user with access to a Native Instruments USB audio device to cause a denial of service or escalate their privileges. (CVE-2011-0712, Low)
  • The start_code and end_code values in "/proc/[pid]/stat" were not protected. In certain scenarios, this flaw could be used to defeat Address Space Layout Randomization (ASLR). (CVE-2011-0726, Low)
  • A flaw in dev_load() could allow a local user who has the CAP_NET_ADMIN capability to load arbitrary modules from "/lib/modules/", instead of only netdev modules. (CVE-2011-1019, Low)
  • A flaw in ib_uverbs_poll_cq() could allow a local, unprivileged user to cause an information leak. (CVE-2011-1044, Low)
  • A missing validation of a null-terminated string data structure element in do_replace() could allow a local user who has the CAP_NET_ADMIN capability to cause an information leak. (CVE-2011-1080, Low)
Red Hat would like to thank Vegard Nossum for reporting CVE-2010-4250; Vasiliy Kulikov for reporting CVE-2011-1079, CVE-2011-1019, and CVE-2011-1080; Dan Rosenberg for reporting CVE-2010-4565 and CVE-2011-0711; Rafael Dominguez Vega for reporting CVE-2011-0712; and Kees Cook for reporting CVE-2011-0726.
This update also fixes several bugs and adds various enhancements. Documentation for these bug fixes and enhancements is available in the Red Hat Enterprise Linux 6.0 Technical Notes document:
Users should upgrade to these updated packages, which contain backported patches to correct these issues, and fix the bugs and add the enhancements noted in the Technical Notes. The system must be rebooted for this update to take effect.

1.108.5. RHSA-2011:0421: Important security and bug fix update

Updated kernel packages that fix multiple security issues and several bugs are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
The kernel packages contain the Linux kernel, the core of any Linux operating system.
This update fixes the following security issues:
  • A flaw was found in the sctp_icmp_proto_unreachable() function in the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation. A remote attacker could use this flaw to cause a denial of service. (CVE-2010-4526, Important)
  • A missing boundary check was found in the dvb_ca_ioctl() function in the Linux kernel's av7110 module. On systems that use old DVB cards that require the av7110 module, a local, unprivileged user could use this flaw to cause a denial of service or escalate their privileges. (CVE-2011-0521, Important)
  • A race condition was found in the way the Linux kernel's InfiniBand implementation set up new connections. This could allow a remote user to cause a denial of service. (CVE-2011-0695, Important)
  • A heap overflow flaw in the iowarrior_write() function could allow a user with access to an IO-Warrior USB device, that supports more than 8 bytes per report, to cause a denial of service or escalate their privileges. (CVE-2010-4656, Moderate)
  • A flaw was found in the way the Linux Ethernet bridge implementation handled certain IGMP (Internet Group Management Protocol) packets. A local, unprivileged user on a system that has a network interface in an Ethernet bridge could use this flaw to crash that system. (CVE-2011-0716, Moderate)
  • A NULL pointer dereference flaw was found in the Generic Receive Offload (GRO) functionality in the Linux kernel's networking implementation. If both GRO and promiscuous mode were enabled on an interface in a virtual LAN (VLAN), it could result in a denial of service when a malformed VLAN frame is received on that interface. (CVE-2011-1478, Moderate)
  • A missing initialization flaw in the Linux kernel could lead to an information leak. (CVE-2010-3296, Low)
  • A missing security check in the Linux kernel's implementation of the install_special_mapping() function could allow a local, unprivileged user to bypass the mmap_min_addr protection mechanism. (CVE-2010-4346, Low)
  • A logic error in the orinoco_ioctl_set_auth() function in the Linux kernel's ORiNOCO wireless extensions support implementation could render TKIP countermeasures ineffective when it is enabled, as it enabled the card instead of shutting it down. (CVE-2010-4648, Low)
  • A missing initialization flaw was found in the ethtool_get_regs() function in the Linux kernel's ethtool IOCTL handler. A local user who has the CAP_NET_ADMIN capability could use this flaw to cause an information leak. (CVE-2010-4655, Low)
  • An information leak was found in the Linux kernel's task_show_regs() implementation. On IBM S/390 systems, a local, unprivileged user could use this flaw to read /proc/[PID]/status files, allowing them to discover the CPU register values of processes. (CVE-2011-0710, Low)
Red Hat would like to thank Jens Kuehnel for reporting CVE-2011-0695; Kees Cook for reporting CVE-2010-4656 and CVE-2010-4655; Dan Rosenberg for reporting CVE-2010-3296; and Tavis Ormandy for reporting CVE-2010-4346.
This update also fixes several bugs. Documentation for these bug fixes is available in the Red Hat Enterprise Linux 6.0 Technical Notes document:
Users should upgrade to these updated packages, which contain backported patches to correct these issues, and fix the bugs noted in the Technical Notes. The system must be rebooted for this update to take effect.

1.108.6. RHSA-2011:0329: Important security update

Updated kernel packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The kernel packages contain the Linux kernel, the core of any Linux operating system.
This update fixes the following security issue:
  • A use-after-free flaw was found in the Linux kernel's RPC server sockets implementation. A remote attacker could use this flaw to trigger a denial of service by sending a corrupted packet to a target system. (CVE-2011-0714, Important)
Red Hat would like to thank Adam Prince for reporting this issue.
Users should upgrade to these updated packages, which contain a backported patch to correct this issue. The system must be rebooted for this update to take effect.

1.108.7. RHSA-2011:0283: Moderate security, bug fix, and enhancement update

Updated kernel packages that fix three security issues, several bugs, and add two enhancements are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
The kernel packages contain the Linux kernel, the core of any Linux operating system.
This update fixes the following security issues:
  • A divide-by-zero flaw was found in the tcp_select_initial_window() function in the Linux kernel's TCP/IP protocol suite implementation. A local, unprivileged user could use this flaw to trigger a denial of service by calling setsockopt() with certain options. (CVE-2010-4165, Moderate)
  • A use-after-free flaw in the mprotect() system call in the Linux kernel could allow a local, unprivileged user to cause a local denial of service. (CVE-2010-4169, Moderate)
  • A flaw was found in the Linux kernel execve() system call implementation. A local, unprivileged user could cause large amounts of memory to be allocated but not visible to the OOM (Out of Memory) killer, triggering a denial of service. (CVE-2010-4243, Moderate)
Red Hat would like to thank Steve Chen for reporting CVE-2010-4165, and Brad Spengler for reporting CVE-2010-4243.
This update also fixes several bugs and adds two enhancements. Documentation for these bug fixes and enhancements is available in the Red Hat Enterprise Linux 6.0 Technical Notes document:
Users should upgrade to these updated packages, which contain backported patches to correct these issues, and fix the bugs and add the enhancements noted in the Technical Notes. The system must be rebooted for this update to take effect.

1.108.8. RHSA-2011:0007: Important security and bug fix update

Updated kernel packages that fix multiple security issues and several bugs are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
  • Buffer overflow in eCryptfs. When /dev/ecryptfs has world writable permissions (which it does not, by default, on Red Hat Enterprise Linux 6), a local, unprivileged user could use this flaw to cause a denial of service or possibly escalate their privileges. (CVE-2010-2492, Important)
  • Integer overflow in the RDS protocol implementation could allow a local, unprivileged user to cause a denial of service or escalate their privileges. (CVE-2010-3865, Important)
  • Missing boundary checks in the PPP over L2TP sockets implementation could allow a local, unprivileged user to cause a denial of service or escalate their privileges. (CVE-2010-4160, Important)
  • NULL pointer dereference in the igb driver. If both Single Root I/O Virtualization (SR-IOV) and promiscuous mode were enabled on an interface using igb, it could result in a denial of service when a tagged VLAN packet is received on that interface. (CVE-2010-4263, Important)
  • Missing initialization flaw in the XFS file system implementation, and in the network traffic policing implementation, could allow a local, unprivileged user to cause an information leak. (CVE-2010-3078, CVE-2010-3477, Moderate)
  • NULL pointer dereference in the Open Sound System compatible sequencer driver could allow a local, unprivileged user with access to /dev/sequencer to cause a denial of service. /dev/sequencer is only accessible to root and users in the audio group by default. (CVE-2010-3080, Moderate)
  • Flaw in the ethtool IOCTL handler could allow a local user to cause an information leak. (CVE-2010-3861, Moderate)
  • Flaw in bcm_connect() in the Controller Area Network (CAN) Broadcast Manager. On 64-bit systems, writing the socket address may overflow the procname character array. (CVE-2010-3874, Moderate)
  • Flaw in the module for monitoring the sockets of INET transport protocols could allow a local, unprivileged user to cause a denial of service. (CVE-2010-3880, Moderate)
  • Missing boundary checks in the block layer implementation could allow a local, unprivileged user to cause a denial of service. (CVE-2010-4162, CVE-2010-4163, CVE-2010-4668, Moderate)
  • NULL pointer dereference in the Bluetooth HCI UART driver could allow a local, unprivileged user to cause a denial of service. (CVE-2010-4242, Moderate)
  • Flaw in the Linux kernel CPU time clocks implementation for the POSIX clock interface could allow a local, unprivileged user to cause a denial of service. (CVE-2010-4248, Moderate)
  • Flaw in the garbage collector for AF_UNIX sockets could allow a local, unprivileged user to trigger a denial of service. (CVE-2010-4249, Moderate)
  • Missing upper bound integer check in the AIO implementation could allow a local, unprivileged user to cause an information leak. (CVE-2010-3067, Low)
  • Missing initialization flaws could lead to information leaks. (CVE-2010-3298, CVE-2010-3876, CVE-2010-4072, CVE-2010-4073, CVE-2010-4074, CVE-2010-4075, CVE-2010-4077, CVE-2010-4079, CVE-2010-4080, CVE-2010-4081, CVE-2010-4082, CVE-2010-4083, CVE-2010-4158, Low)
  • Missing initialization flaw in KVM could allow a privileged host user with access to /dev/kvm to cause an information leak. (CVE-2010-4525, Low)
Red Hat would like to thank Andre Osterhues for reporting CVE-2010-2492; Thomas Pollet for reporting CVE-2010-3865; Dan Rosenberg for reporting CVE-2010-4160, CVE-2010-3078, CVE-2010-3874, CVE-2010-4162, CVE-2010-4163, CVE-2010-3298, CVE-2010-4073, CVE-2010-4074, CVE-2010-4075, CVE-2010-4077, CVE-2010-4079, CVE-2010-4080, CVE-2010-4081, CVE-2010-4082, CVE-2010-4083, and CVE-2010-4158; Kosuke Tatsukawa for reporting CVE-2010-4263; Tavis Ormandy for reporting CVE-2010-3080 and CVE-2010-3067; Kees Cook for reporting CVE-2010-3861 and CVE-2010-4072; Nelson Elhage for reporting CVE-2010-3880; Alan Cox for reporting CVE-2010-4242; Vegard Nossum for reporting CVE-2010-4249; Vasiliy Kulikov for reporting CVE-2010-3876; and Stephan Mueller of atsec information security for reporting CVE-2010-4525.
This update also fixes several bugs. Documentation for these bug fixes is available in the Red Hat Enterprise Linux 6.0 Technical Notes document:
Users should upgrade to these updated packages, which contain backported patches to correct these issues, and fix the bugs noted in the Technical Notes. The system must be rebooted for this update to take effect.

1.108.9. RHSA-2010:0842: Important security and bug fix update

Updated kernel packages that fix multiple security issues and several bugs are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
[Updated 22 November 2010] The packages list in this erratum has been updated to include four missing debuginfo-common packages (one per architecture). No changes have been made to the original packages.
The kernel packages contain the Linux kernel, the core of any Linux operating system.
This update fixes the following security issues:
  • Missing sanity checks in the Intel i915 driver in the Linux kernel could allow a local, unprivileged user to escalate their privileges. (CVE-2010-2962, Important)
  • compat_alloc_user_space() in the Linux kernel 32/64-bit compatibility layer implementation was missing sanity checks. This function could be abused in other areas of the Linux kernel if its length argument can be controlled from user-space. On 64-bit systems, a local, unprivileged user could use this flaw to escalate their privileges. (CVE-2010-3081, Important)
  • A buffer overflow flaw in niu_get_ethtool_tcam_all() in the niu Ethernet driver in the Linux kernel, could allow a local user to cause a denial of service or escalate their privileges. (CVE-2010-3084, Important)
  • A flaw in the IA32 system call emulation provided in 64-bit Linux kernels could allow a local user to escalate their privileges. (CVE-2010-3301, Important)
  • A flaw in sctp_packet_config() in the Linux kernel's Stream Control Transmission Protocol (SCTP) implementation could allow a remote attacker to cause a denial of service. (CVE-2010-3432, Important)
  • A missing integer overflow check in snd_ctl_new() in the Linux kernel's sound subsystem could allow a local, unprivileged user on a 32-bit system to cause a denial of service or escalate their privileges. (CVE-2010-3442, Important)
  • A flaw was found in sctp_auth_asoc_get_hmac() in the Linux kernel's SCTP implementation. When iterating through the hmac_ids array, it did not reset the last id element if it was out of range. This could allow a remote attacker to cause a denial of service. (CVE-2010-3705, Important)
  • A function in the Linux kernel's Reliable Datagram Sockets (RDS) protocol implementation was missing sanity checks, which could allow a local, unprivileged user to escalate their privileges. (CVE-2010-3904, Important)
  • A flaw in drm_ioctl() in the Linux kernel's Direct Rendering Manager (DRM) implementation could allow a local, unprivileged user to cause an information leak. (CVE-2010-2803, Moderate)
  • It was found that wireless drivers might not always clear allocated buffers when handling a driver-specific IOCTL information request. A local user could trigger this flaw to cause an information leak. (CVE-2010-2955, Moderate)
  • A NULL pointer dereference flaw in ftrace_regex_lseek() in the Linux kernel's ftrace implementation could allow a local, unprivileged user to cause a denial of service. Note: The debugfs file system must be mounted locally to exploit this issue. It is not mounted by default. (CVE-2010-3079, Moderate)
  • A flaw in the Linux kernel's packet writing driver could be triggered via the PKT_CTRL_CMD_STATUS IOCTL request, possibly allowing a local, unprivileged user with access to "/dev/pktcdvd/control" to cause an information leak. Note: By default, only users in the cdrom group have access to "/dev/pktcdvd/control". (CVE-2010-3437, Moderate)
  • A flaw was found in the way KVM (Kernel-based Virtual Machine) handled the reloading of fs and gs segment registers when they had invalid selectors. A privileged host user with access to "/dev/kvm" could use this flaw to crash the host. (CVE-2010-3698, Moderate)
Red Hat would like to thank Kees Cook for reporting CVE-2010-2962 and CVE-2010-2803; Ben Hawkes for reporting CVE-2010-3081 and CVE-2010-3301; Dan Rosenberg for reporting CVE-2010-3442, CVE-2010-3705, CVE-2010-3904, and CVE-2010-3437; and Robert Swiecki for reporting CVE-2010-3079.
This update also fixes several bugs. Documentation for these bug fixes is available in the Red Hat Enterprise Linux 6.0 Technical Notes document:
Users should upgrade to these updated packages, which contain backported patches to correct these issues, and fix the bugs noted in the Technical Notes. The system must be rebooted for this update to take effect.

1.109. kexec-tools

1.109.1. RHBA-2011:0736: bug fix update

The kexec fastboot mechanism allows booting a Linux kernel from the context of an already running kernel. The kexec-tools package provides the /sbin/kexec binary and ancillary utilities that form the user-space component of the kernel's kexec feature.
This update fixes the following bugs:
BZ#605411
The kdump crash recovery service allows users to specify a raw device (that is, a raw disk or partition) as a target location for core dumps. Previously, when a kernel crash occurred and a core dump was written to such a raw device, kdump was unable to retrieve it after a reboot. With this update, the corresponding init script has been updated to search the configured raw device for the presence of a core dump upon the service startup. Now, when the kdump service is started and a core dump is found on the raw device, the init script retrieves it and creates a proper vmcore file in a local file system.
BZ#607400
Due to various unrelated errors in the underlying source code, the kexec utility may not have worked properly on the SGI Altix UV architecture. This update applies a set of patches to address these issues, and kexec now works on this architecture as expected.
BZ#619682
Prior to this update, the kdump.conf(5) manual page did not provide a description of the blacklist directive. This update corrects this error, and the blacklist directive is now included in the OPTIONS section of the kdump.conf(5) manual page as expected.
BZ#626318
When running the firstboot application in a language other than English, certain messages regarding the configuration of the kdump crash recovery service were presented to a user in the original English version. This update corrects this error, and the Kdump section of the firstboot application no longer contains untranslated strings.
BZ#626606
Prior to this update, an attempt to run the mkdumprd utility on a system without the /etc/modprobe.d/modprobe.conf file caused the utility to stop responding. With this update, this error no longer occurs, and mkdumprd now works as expected.
BZ#626746
Due to an error in the init script, the kdump service did not take into account the value of the path option in the /etc/kdump.conf configuration file, and always saved the vmcore file to the /var/crash/ directory. This update adapts the corresponding init script to ensure that kdump uses the directory specified in the configuration.
BZ#627118
In accordance with the current version of the Filesystem Hierarchy Standard (FHS), the makedumpfile utility is now installed in the /usr/sbin/ directory.
BZ#627834
Previously, configuring the kdump service to store core dumps over a network on a system that used channel bonding or bridging caused the mkdumprd utility to display the following error message on the service startup:
Netmask is missed!
With this update, the underlying source code has been adapted to address this issue, and makedumpfile no longer displays this message when channel bonding or bridging is in use.
BZ#628817
The kdump crash recovery service is unable to operate in Xen environment. With this update, an attempt to start kdump in such an environment fails with the Kdump is not supported on this kernel message.
BZ#628827
The commented section of the /etc/kdump.conf configuration file contains the following line:
#core_collector cp --sparse=always
However, uncommenting this line without including /bin/cp in the initial RAM disk (that is, by using the extra_bins directive) would cause the kdump crash recovery service to fail. This update corrects this error, and the above line is now followed by #extra_bins /bin/cp.
BZ#630305
Due to an error in the translation, when running the firstboot application in the Malayalam language (that is, the ml_IN language code), certain keyboard shortcuts on the Kdump screen did not work. This update corrects the Malayalam translation of the firstboot application, and all shortcuts can now be used as expected.
BZ#630309
When running the firstboot application in the Malayalam language (that is, the ml_IN language code), the first paragraph on the Kdump screen contained an incorrect string. This update adapts the Malayalam translation of the firstboot application, and the Kdump screen is now translated correctly.
BZ#642735
Prior to this update, an attempt to start the kdump service on a system with a large amount of memory (that is, 1TB and more) caused kdump to terminate unexpectedly with a segmentation fault. With this update, the underlying source code has been adapted to address this issue, and kdump no longer crashes
BZ#642855
Due to an error in DHCP NAK handling, previous versions of kdump may have failed to resolve an IP address when storing a core dump to a remote server. This update corrects this error, and kdump no longer fails.
BZ#645441
Prior to this update, the kdump crash recovery service failed to start on IBM System x3850 X5 machines. This update applies an upstream patch that extends the size of kcore ELF headers. Now, kdump can be started on such machines as expected.
BZ#652191
Previously, configuring the kdump service to store core dumps to a remote machine over the SSH protocol and changing the core collector to cp caused it to name core dump files vmcore.flat, even when the SCP (Secure Copy) protocol was used. This update corrects this error, and kdump now only uses the .flat file extension when the makedumpfile utility is used as the core collector.
BZ#652724
Previously, when a system did not have enough memory to use kdump, the Kdump screen of the firstboot application incorrectly displayed the Enable kdump? check box as selected, but did not allow a user to change it. This error has been fixed, and the Enable kdump? check box is no longer displayed when the kdump service cannot be configured.
BZ#654245
When the kdump crash recovery service was already enabled, an attempt to use the firstboot application to change its configuration may have failed with the following message:
Insufficient memory to configure kdump!
This update adapts the underlying source code to verify that kdump is not running before displaying this message.
BZ#669655
Previously, when the root partition was mounted as a read-only file system, the mkdumprd utility was unable to create a temporary directory and failed to build an initial RAM disk (that is, initrd). This update adapts mkdumprd to use the /boot/ directory in this case. As a result, mounting the root partition as a read-only file system no longer renders mkdumprd unable to create an initial RAM disk.
BZ#671013
Due to an error in the mkdumprd utility, updating a disk drive firmware could render the kdump crash recovery service unable to recognize the disk drive. This update adapts the mkdumprd utility to ignore disk drive firmware revisions, and kdump now works as expected.
BZ#674893
Due to known issues with the hpsa and cciss drivers, kdump is unable to save core dumps to certain HP Smart Array Controllers that use these drivers. This update ensures that the kdump service is disabled on such controllers.
BZ#676758
Prior to this update, an attempt to boot a system with the new syntax of the crashkernel kernel parameter (such as crashkernel=4G-:256M) caused the firstboot application to terminate unexpectedly during the configuration of kdump. This update applies a patch to address this issue, and firstboot no longer crashes.
BZ#679310
When using the Russian translation (that is, the ru_RU language code) of the firstboot application, the first paragraph on the Kdump screen incorrectly contained the string. This update corrects this error, and the Kdump section of the firstboot application is now translated correctly.
BZ#680741
Prior to this update, running the makedumpfile -V command caused the makedumpfile utility to terminate unexpectedly with a segmentation fault. This update applies an upstream patch that removes -V from the list of supported command line options, and running the above command no longer causes makedumpfile to crash.
BZ#683713
Due to a typing error in the underlying source code of the mkdumprd utility, configuring the kdump service to store core dumps to a raw device caused it to display a message similar to the following when a kernel crash occurred:
kill: cannot kill pid 887: No such process
This update corrects this error, and kdump no longer display the above error message upon a kernel crash.
BZ#683735
When configured to use a raw device as a target location for core dumps, the kdump service recovers the dump file at next startup. Previously, an attempt to use this configuration without the core_collector option specified in the configuration file caused kdump to fail to recover the core dump. With this update, the underlying source code has been adapted to use the makedumpfile utility by default, and kdump is now able to recover core dumps as expected.
BZ#688150
When the firstboot application is used to configure the kdump crash recovery service, a dialog box appears and prompts a user to reboot the system in order for the changes to take effect. Previously, closing this dialog box by clicking the Close button had the same effect as clicking Yes, and incorrectly initiated the system restart. This error no longer occurs, and clicking the Close button now only closes the dialog box as expected.
BZ#691632
Under certain circumstances, the kdump service may have failed to create a core dump with the following error:
readmem: Can't read the dump memory(/proc/vmcore). Cannot allocate memory
This update fixes this regression, and kdump no longer fails to store the core dump.
BZ#692264
Prior to this update, the mkdumprd utility was not allowed to create temporary files in the tmpfs file system, rendering the kdump service unable to start in a diskless environment. With this update, the underlying source code has been adapted to allow the use of the tmpfs file system, so that kdump is now able to start on diskless nodes as expected.
BZ#692449
Previously, running the makedumpfile utility with the dump level (that is, the -d option) set to 16 or 31 may have caused the utility to fail. This update applies a patch that addresses this issue, and makedumpfile now works as expected.
BZ#692685
With this update, the mkdumprd utility has been adapted to provide support for the --override-resettable option. This allows system administrators to start the kdump service on otherwise unsupported devices, such as HP Smart Array Controllers that use the hpsa or cciss driver.
BZ#693015
Prior to this update, the kdump crash recovery service was unable to find an LVM device identified by a universally unique identifier (UUID). Consequent to this, when a system crashed, kdump may have failed to write a core dump to such a device. This update fixes this error, and kdump now locates LVM devices according to their UUIDs as expected.
As well, this update adds the following enhancements:
BZ#598064
After the installation of Red Hat Enterprise Linux 6, the firstboot application now allows users to edit the content of the /etc/kdump.conf configuration file.
BZ#632709
Support for IBM System z has been added.
BZ#672109
Previously, when the makedumpfile utility was used to translate a core dump file to the kdump-compressed format, it removed the ELF note section. Since this section contains potentially important information, this update adapts makedumpfile preserve this section in the kdump-compressed core dump files.
All users of kexec-tools are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

1.110. krb5

1.110.1. RHSA-2010:0863: Important security update

Updated krb5 packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
Kerberos is a network authentication system which allows clients and servers to authenticate to each other using symmetric encryption and a trusted third party, the Key Distribution Center (KDC).
An uninitialized pointer use flaw was found in the way the MIT Kerberos KDC handled TGS (Ticket-granting Server) request messages. A remote, authenticated attacker could use this flaw to crash the KDC or, possibly, disclose KDC memory or execute arbitrary code with the privileges of the KDC (krb5kdc). (CVE-2010-1322)
Red Hat would like to thank the MIT Kerberos Team for reporting this issue. Upstream acknowledges Mike Roszkowski as the original reporter.
All krb5 users should upgrade to these updated packages, which contain a backported patch to correct this issue. After installing the updated packages, the krb5kdc daemon will be restarted automatically.

1.110.2. RHSA-2010:0925: Important security and bug fix update

Updated krb5 packages that fix multiple security issues and one bug are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
Kerberos is a network authentication system which allows clients and servers to authenticate to each other using symmetric encryption and a trusted third party, the Key Distribution Center (KDC).
Multiple checksum validation flaws were discovered in the MIT Kerberos implementation. A remote attacker could use these flaws to tamper with certain Kerberos protocol packets and, possibly, bypass authentication or authorization mechanisms and escalate their privileges. (CVE-2010-1323, CVE-2010-1324, CVE-2010-4020)
Red Hat would like to thank the MIT Kerberos Team for reporting these issues.
This update also fixes the following bug:
* When attempting to perform PKINIT pre-authentication, if the client had more than one possible candidate certificate the client could fail to select the certificate and key to use. This usually occurred if certificate selection was configured to use the value of the keyUsage extension, or if any of the candidate certificates did not contain a subjectAltName extension. Consequently, the client attempted to perform pre-authentication using a different (usually password-based) mechanism. (BZ#644825)
All krb5 users should upgrade to these updated packages, which contain backported patches to correct these issues. After installing the updated packages, the krb5kdc daemon will be restarted automatically.

1.110.3. RHSA-2011:0200: Important security update

Updated krb5 packages that fix three security issues are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
Kerberos is a network authentication system which allows clients and servers to authenticate to each other using symmetric encryption and a trusted third-party, the Key Distribution Center (KDC).
A NULL pointer dereference flaw was found in the way the MIT Kerberos KDC processed principal names that were not null terminated, when the KDC was configured to use an LDAP back end. A remote attacker could use this flaw to crash the KDC via a specially-crafted request. (CVE-2011-0282)
A denial of service flaw was found in the way the MIT Kerberos KDC processed certain principal names when the KDC was configured to use an LDAP back end. A remote attacker could use this flaw to cause the KDC to hang via a specially-crafted request. (CVE-2011-0281)
A denial of service flaw was found in the way the MIT Kerberos V5 slave KDC update server (kpropd) processed certain update requests for KDC database propagation. A remote attacker could use this flaw to terminate the kpropd daemon via a specially-crafted update request. (CVE-2010-4022)
Red Hat would like to thank the MIT Kerberos Team for reporting the CVE-2011-0282 and CVE-2011-0281 issues. Upstream acknowledges Kevin Longfellow of Oracle Corporation as the original reporter of the CVE-2011-0281 issue.
All krb5 users should upgrade to these updated packages, which contain backported patches to correct these issues. After installing the updated packages, the krb5kdc daemon will be restarted automatically.

1.110.4. RHSA-2011:0356: Important security update

Updated krb5 packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
Kerberos is a network authentication system which allows clients and servers to authenticate to each other using symmetric encryption and a trusted third-party, the Key Distribution Center (KDC). The Public Key Cryptography for Initial Authentication in Kerberos (PKINIT) capability provides support for using public-key authentication with Kerberos.
A double-free flaw was found in the way the MIT Kerberos KDC handled initial authentication requests (AS-REQ), when the KDC was configured to provide the PKINIT capability. A remote attacker could use this flaw to cause the KDC daemon to abort by using a specially-crafted AS-REQ request. (CVE-2011-0284)
All krb5 users should upgrade to these updated packages, which contain a backported patch to correct this issue. After installing the updated packages, the krb5kdc daemon will be restarted automatically.

1.110.5. RHSA-2011:0447: Moderate security update

Updated krb5 packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
Kerberos is a network authentication system which allows clients and servers to authenticate to each other using symmetric encryption and a trusted third-party, the Key Distribution Center (KDC).
An invalid free flaw was found in the password-changing capability of the MIT Kerberos administration daemon, kadmind. A remote, unauthenticated attacker could use this flaw to cause kadmind to abort via a specially-crafted request. (CVE-2011-0285)
All krb5 users should upgrade to these updated packages, which contain a backported patch to correct this issue. After installing the updated packages, the kadmind daemon will be restarted automatically.

1.110.6. RHBA-2011:0571: bugfix update

Updated krb5 packages that fix multiple bugs are now available for Red Hat Enterprise Linux 6.
Kerberos is a network authentication system which allows clients and servers to authenticate to each other using symmetric encryption and a trusted third-party, the Key Distribution Center (KDC).
Kerberos has been upgraded to version 1.9, which provides a number of bug fixes over the previous version. (BZ#642417)
This update fixes the following bugs:
  • Previously, no IPv6 suport was available for kprop, kpropd, kadmin and kadmind. This update adds IPv6 support to these utilities. (BZ#595841, BZ#595842)
  • Previously, the krbPwdExpiration attribute in the principal's entry would often be ignored when the realm database was stored in a directory server. This update fixes this problem and this attribute is no longer ignored. (BZ#627039)
  • Previously, kinit with smart card login did not authenticate to the KDC correctly if the certificate on the smart card did not contain a subjectAltName extension or multiple certificates were available and krb5.conf was configured to select according to the value of the keyUsage extension in the certificates. This update continues to look for certificates with the right extension and corrects the valuation. (BZ#629022)
  • Previously, the init script for the kpropd was not Linux Standards Base (LSB) compliant. With this update, this init script is LSB compliant. (BZ#630587)
  • Previously, the KDC log files were not rotated by default. This update corrects this problem. Now these log files are rotated correctly. (BZ#630968)
  • Previously, logins failed if the user had a .k5login file which did not explicitly contain the user's principal name. With this update, this check can be disabled using the "k5login_authoritative" setting in krb5.conf. (BZ#646499)
  • Previously, GSSAPI authentication from Windows clients using cross-realm authentication failed if the client's ticket included a Privilege Attribute Certificate (PAC) with a failed signature check. Failed signature checks are now ignored. (BZ#679612)
All krb5 users are advised to upgrade to these updated packages, which fix these bugs.

1.111. krb5-appl

1.111.1. RHBA-2011:0687: bug fix update

Updated krb5-appl packages are now available for Red Hat Enterprise Linux 6.
The krb5-appl package contains Kerberos-aware versions of telnet, ftp, rcp, rsh, and rlogin clients and servers. While these have been replaced by tools such as OpenSSH in most environments, they remain in use in others.
This update corrects the following bug:
  • kshd, the Kerberos-aware version of rshd, unnecessarily failed if the name of the local user account being accessed was more than 16 characters long. This occurred despite the user name being accepted by klogind, the Kerberos-aware version of rlogind. In this update, kshd was modified to accept user names with the length of up to 32 characters as accepted by klogind. (BZ#632442)
Users are advised to upgrade to these updated krb5-appl packages, which resolve this issue.

1.112. ksh

1.112.1. RHBA-2011:0645: bug fix and enhancement update

An updated ksh package that fixes several bugs and adds various enhancements is now available.
KSH-93 is the most recent version of the KornShell by David Korn of AT&T Bell Laboratories -- a shell programming language upwards-compatible with "sh" (the Bourne Shell).
This updated ksh package provides fixes for the following bugs:
  • When a ksh script contained the "trap" command to capture a "SIGPIPE" signal, sending this signal via the built-in "echo" command could cause its output to be incorrectly added to the redirected output of an external command. With this update, ksh now flushes the output buffer before redirecting any output streams. (BZ#616684)
  • Due to incorrect signal handling, receiving a signal while still processing the same one caused ksh to terminate unexpectedly with a segmentation fault. With this update, the subsequent signals are deferred until the current one is processed; thus, ksh no longer crashes. (BZ#616691)
  • The previous version of the ksh man page contained an unavailable "-m" option and an insufficient description of the "-R" option. In this updated version of the man page, the section mentioning the unavailable option is removed and the description of the "-R" option is extended. (BZ#619692)
  • Assigning a value to an array variable during the execution of the "typeset" command could cause ksh to terminate unexpectedly with a segmentation fault. This update corrects the array handling in this command and ksh no longer crashes. (BZ#637052)
  • Prior to this update, ksh did not close a file containing an auto-loaded function definition. After loading several functions, ksh could have easily exceeded the system's limit on the number of open files. With this update, files containing auto-loaded functions are properly closed, thus, the number of opened files no longer increases with usage. (BZ#643811)
  • If a here document (heredoc — specifies a string literal in command line shells) was combined with an auto-loaded function, interference with the here document processing could occur causing output to be truncated to 8 kB. This update improves the here document processing logic and auto-loaded functions no longer have a negative side effect on here documents. (BZ#644362)
  • Previously, ksh did not restore file handles after executing a sourced script. If an output stream or an error stream was redirected in the sourced script, the respective stream remained redirected in the parent script as well. With this update, file handles are restored after execution of sourced scripts so a parent script is not affected by sourced script redirections. (BZ#651888)
  • When a ksh script created a file and immediately opened it after the creation, the operation failed. This happened because the created file, in some cases, did not exist yet. With this update, this race condition has been fixed and once a file is created, it is immediately available for any following commands. (BZ#660319)
  • Previously, a ( ) compound list did not always use a copy of the environment which caused the original environment to be altered. Scripts could behave unexpectedly because their variables could be changed. With this update, a copy of the environment is always used for a ( ) compound list; thus, the original environment is not affected by commands from the ( ) compound list. (BZ#681478)
In addition, this updated package provides the following enhancements:
  • The ksh built-in "ulimit" command now provides the ability to read and set the "RLIMIT_RTPRIO" and "RLIMIT_NICE" resource limiters. (BZ#582690)
  • The ksh package now includes an "alternatives" command which allows ksh to be switched with mksh (MirBSD Korn Shell). This enhancement allows users to switch between the ksh-93 and ksh-88 (provided by mksh) shells and to port ksh-88 scripts to ksh-93. (BZ#659658)
Users are advised to upgrade to this updated ksh package, which resolves these issues and adds these enhancements.

1.113. ldapjdk

1.113.1. RHBA-2011:0803: bug fix update

An updated ldapjdk package that fixes one bug is now available.
The Mozilla LDAP SDKs enable you to write applications which access, manage, and update the information stored in an LDAP directory.
When parsing an attribute definition from a directory server schema entry, the ldapjdk parser did not properly handle the ORDERING and SUBSTR matching rule specifications.
This bug was being encountered by:
  1. RHDS customers using the 389-ds-console code; or
  2. Custom applications while using the LDAPSchemaElement.getOptionalValues() or LDAPAttributeSchema.getValue() methods to get a string representation of an LDAP attribute that has multiple matching rule types present.
The offending method in ldapjdk was fixed so that new attributes with multiple matching rule types are created properly. (BZ#684028)
An updated package that fixes this bug is now available.

1.114. libcacard and spice-client

1.114.1. RHBA-2011:0583: bug and enhancement update

New libcacard packages, and an updated spice-client package that fixes number of bugs and adds various enhancements, are now available for Red Hat Enterprise Linux 6.
The Simple Protocol for Independent Computing Environments (SPICE) is a remote display protocol designed for virtual environments which allows users to view a computing 'desktop' environment not only on the machine where it is running, but from anywhere on the Internet. The spice-client package contains the spicec program, which renders a virtual desktop using the SPICE protocol.
The new libcacard package contains Common Access Card (CAC) emulation library.
The spice-client package has been upgraded to upstream version 0.8.0, which provides a number of bug fixes and enhancements over the previous version. (BZ#671383)
Bug fixes:
BZ#630825, BZ#626975
When a kernel panic occurred on a guest, spice-client blinked the LED lights for the Num lock and Caps Lock keys even when it did not have keyboard focus, making it virtually impossible to type in another window. This bug has been fixed and both keys now work as expected.
BZ#628573
The X Window Server occasionally used over 80% of CPU time while the client was in full-screen mode, which caused the user's desktop session to become very unresponsive. This bug has been fixed and the undesired overhead no longer occurs.
BZ#642149
When switching to full-screen mode using the Shift+F11 shortcut, spice-client did not work properly with certain window managers such as Compiz. This bug has been fixed and the full-screen mode now works as expected in modern window managers.
BZ#644292
When running the "spicec --controller" command without having set the SPICE_XPI_SOCKET environment variable, users could experience unexpected termination caused by a segmentation fault. This bug has been fixed and spicec now exits cleanly with an error message in this particular scenario.
BZ#653535
Using the Red Hat Enterprise Virtualization Manager, when a guest connected to a virtual machine (VM) via spicec, the window received title that differed from the VM name. This bug has been fixed and the user window's title now matches the name of the VM.
BZ#655029
A watermark banner was visible during the whole session and it obstructed the user's view. This update disables the banner so that it no longer obstructs the view.
BZ#670238
When spice-client was set to use JPEG compression for images, the client sometimes terminated unexpectedly. This bug has been fixed and the spice-client now handles JPEG images properly.
BZ#670274
If the client failed verification because of a subject mismatch between the supplied host and the actual host, the error message given was too short to be useful. With this update, the error message is now sufficiently informative.
BZ#670276
The spicec program incorrectly parsed long arguments when an equal sign ("=") was used. As a result, an error message was given and the client did not start. This bug has been fixed and the client now behaves as expected.
BZ#675767
When a spice-client hotkey was set to Ctrl+Alt, users were unable to send, using Sticky-Alt, a Ctrl+Alt+key key sequence to a guest. That prevented various functionality such as switching focus to the console or setting keyboard shortcuts. This bug has been fixed and users can send the client a key sequence with Ctrl and Alt keys using Sticky-Alt even if a spice-client hotkey is set to Ctrl+Alt.
BZ#679467
Status changes of the Caps Lock and Num Lock key were not synchronized from the guest to the client. With this update a guest and a client always synchronize their status of the Caps Lock and Num Lock keys.
BZ#680763
Sometimes, spicec became stuck when exiting from full-screen mode if it received an asynchronous X Window system error. With this update, spicec now correctly calls the appropriate "_exit()" function in this rare circumstance so that spicec does not become stuck if this situation occurs.
Enhancements:
BZ#644258
With an appropriate spice-server installed and a spice-agent running, users of spice-client can now copy-and-paste between the guest and the client.
BZ#545936
With this update, the following features have been added to the spice-client package to support a WAN (wide area network) environment: lossy compression for RGBA images on WAN connections, zlib compression (over GLZ) on WAN connections, an option to disable guest display effects such as animations, and an option to set guest color-depth.
BZ#675085
The spice-server and spice-client packages use common libraries in Red Hat Enterprise Linux 6.1. This renders the following packages obsolete: cairo-spice version 1.8.7.2 and earlier, ffmpeg-spice version 0.4.9-1 and earlier, pixman-spice version 0.13.3-6 and earlier, and spice-common version 0.4.2-8 and earlier. These removed and obsoleted packages are now recorded in the spice-server.spec file.

Note

Note that if both spice-client and spice-server are installed on a system, upgrading one of them will also cause the other to be upgraded.
BZ#641829
The spice-client package now supports Common Access Cards (CACs), allowing single sign-on and other card services such as encryption.
BZ#641831
The spice-client package now supports Red Hat Enterprise Linux Single Sign-On (SSO) functionality with properly-configured smart card readers.
Users of spice-client should upgrade to these updated packages, which fix these bugs and add these enhancements.

1.115. libcap-ng

1.115.1. RHBA-2010:0906: bug fix update

Updated libcap-ng packages that fix a bug are now available for Red Hat Enterprise Linux 6.
The libcap-ng library is designed to make programming with POSIX capabilities easier. It is shipped with utilities to analyze the POSIX capabilities of all running applications, as well as tools to set the file system-based capabilities.
This update fixes the following bug:
  • Previously, when listing the file system based capabilities of a single file with the "filecap" utility, it would terminate with a segmentation fault. This error has been fixed, and "filecap" no longer crashes when attempting to list the capabilities of a single file. (BZ#650131)
Users are advised to upgrade to these updated packages, which resolve this issue.

1.116. libcgroup

1.116.1. RHSA-2011:0320: Important security update

Updated libcgroup packages that fix two security issues are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
The libcgroup packages provide tools and libraries to control and monitor control groups.
A heap-based buffer overflow flaw was found in the way libcgroup converted a list of user-provided controllers for a particular task into an array of strings. A local attacker could use this flaw to escalate their privileges via a specially-crafted list of controllers. (CVE-2011-1006)
It was discovered that libcgroup did not properly check the origin of Netlink messages. A local attacker could use this flaw to send crafted Netlink messages to the cgrulesengd daemon, causing it to put processes into one or more existing control groups, based on the attacker's choosing, possibly allowing the particular tasks to run with more resources (memory, CPU, etc.) than originally intended. (CVE-2011-1022)
Red Hat would like to thank Nelson Elhage for reporting the CVE-2011-1006 issue.
All libcgroup users should upgrade to these updated packages, which contain backported patches to correct these issues.

1.116.2. RHBA-2011:0577: bug fix and enhancement update

Updated libcgroup packages that fix several bugs and add an enhancement are now available for Red Hat Enterprise Linux 6.
The libcgroup packages provide tools and libraries to control and monitor control groups.
These updated libcgroup packages provide fixes for the following bugs:
  • With this update, the cgred and cgconfig services return proper exit codes when an error occurs. (BZ#620368)
  • The cgconfig service was erroneously setting values of configured parameters in the reverse order as they were written in the /etc/cgconfig.conf file. With this update, the cgconfig service now correctly sets parameter values in the same order as they appear in the configuration file. (BZ#622462)
  • The cgget command (which prints parameters of given cgroups) did not correctly display information about resource controllers due to a small buffer size. With this update, the buffer is no longer limited in size and the cgget command displays correct information. (BZ#626127)
  • The cgcreate command changed the current working directory when creating a cgroup. The command restored the working directory to the previous location, however, some directory changes could have been refused (for example, SELinux; resulting in cryptic security denials). With this update, the cgcreate command no longer changes the current working directory and therefore no longer incurs any SELinux denials. (BZ#628895)
  • After re-mounting a hierarchy of cgroups, the lssubsys command displayed incorrect information about the mounted hierarchies. This update fixes the faulty parsing of mounted hierarchies which are now correctly displayed. (BZ#635984)
  • The cgred service failed to start if the cgconfig service was not running and returned the following error: "libcgroup initialization failed, 50001". With this update, a more human-readable error message is returned when the cgred service is started before the cgconfig service. (BZ#650984)
  • The cgclassify command returned exit code 1 even if no errors occurred. With this update, exit code 0 is returned in the aforementioned case. (BZ#667957)
  • The /etc/cgconfig.conf file could not contain parameter values with special characters such as commas. Therefore, it was not possible to set certain values for some parameters (for example, cpuset.cpus=0,2). With this update, the cgconfig.conf parser allows enclosing the parameter values inside double quotes which allow special characters to be defined inside them (for example, cpuset.cpus="0,2"). (BZ#679698)
In addition, these updated packages provide the following enhancement:
  • The libcgroup package now includes the cgsnapshot tool which is used to write the current state of control groups to a configuration file. (BZ#649195)
Users are advised to upgrade to these updated libcgroup packages, which resolve these issues and add this enhancement.

1.117. libcmpiutil

1.117.1. RHEA-2011:0641: enhancement update

An enhanced libcmpiutil package is now available for Red Hat Enterprise Linux 6.
The libcmpiutil library provides an API for performing common tasks with various Common Manageability Programming Interface (CMPI) providers.
This updated libcmpiutil package adds the following enhancement:
  • The libcmpiutil package has been upgraded to upstream version 8.5.4, which improves performance and is a prerequisite for the new interfaces provided by the libvirt-cim package update as the package depends on the libcmpiutil library. (BZ#633332)
Users of libcmpiutil are advised to upgrade to this updated package, which adds this enhancement.

1.118. libcxgb3

1.118.1. RHBA-2011:0758: bug fix and enhancement update

Updated libcxgb3 packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6.
libcxgb3 is a device-specific driver for use with the libibverbs InfiniBand/iWARP verbs library. This driver enables Chelsio Internet Wide Area RDMA Protocol (iWARP) capable ethernet devices.
  • This update upgrades libcxgb3 to upstream version 7.10, which provides multiple bug fixes and enhancements over the previous version. (BZ#675025)
All users of libcxgb3 are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

1.119. libdfp

1.119.1. RHBA-2011:0659: bugfix update

Updated libdfp packages that fix various bugs are now available for Red Hat Enterprise Linux 6.
The libdfp packages contain the Decimal Floating Point C Library, which is inter alia used for converting strings into decimal floating point numbers.
The libdfp packages have been upgraded to upstream version 1.0.6, which provides a number of bug fixes over the previous version. (BZ#642693)
Additionally, this update fixes the following bugs:
  • Previously, converting a string into a decimal floating point number greater than zero and less than one caused an error. During this conversion, the first decimal digit disappeared; consequently all following computations were done with wrong numbers. This bug has been fixed so that the conversion into the decimal floating point number now works as expected. (BZ#625495)
  • Under some circumstances, libdfp encountered an issue while converting a value from a string into a decimal floating point number with the conversion command "strtod32". The "strtod64" and "strtod128" commands, which are also included in libdfp, did work correctly. The problem has been resolved so that the conversion now proceeds properly. (BZ#628670)
  • Previously, there were several testsuite failures encountered when building the libdfp packages for the IBM S/390 architecture. These testsuite failures have been corrected with this update and thus no longer occur. (BZ#673222)
All users requiring libdfp should upgrade to these updated packages, which fix these bugs.

1.120. libgcrypt

1.120.1. RHBA-2011:0726: bug fix update

An updated libgcrypt package that fixes various bugs is now available for Red Hat Enterprise Linux 6.
The libgcrypt library provides general-purpose implementations of various cryptographic algorithms.
This updated libgcrypt package includes fixes for the following bugs:
  • Previously, the build time test did not support FIPS (Federal Information Processing Standard) mode and failed in this mode. This update modifies the test so that it passes successfully on machines set to use FIPS mode. (BZ#576549)
  • In FIPS mode, libgcrypt used the /dev/random device as the source for the RNG (Random Number Generator) seed. This caused the RNG initialization in FIPS mode to take several minutes. With this update, libgcrypt uses the /dev/urandom device for the RNG seed and RNG initialization no longer causes any delays. (BZ#669084)
All users of libgcrypt are advised to upgrade to this updated package, which resolves these issues.

1.121. libgssglue

1.121.1. RHBA-2011:0789: bug fix update

Updated libgssglue packages that fix two bugs are now available.
The libgssglue packages provide a library required by programs in the rpcbind package. This library exports a GSSAPI interface that calls GSSAPI routines in other libraries.
This update fixes the following bugs:
  • Previously, the libgssglue library files were placed in the "/usr/lib/" or "/usr/lib64/" directory, depending on the architecture. As the library is required by rpcbind which is installed in "/sbin/", this update moves the libgssglue library files to "/lib/" or "/lib64/". (BZ#558941)
  • Previously, it was not possible to install both the 32-bit and 64-bit -devel packages simultaneously. This update resolves this multi-arch conflict. (BZ#681660)
All libgssglue and rpcbind users should install these updated packages, which address these issues.

1.122. libguestfs

1.122.1. RHSA-2011:0586: Low security, bug fix, and enhancement update

libguestfs is a library for accessing and modifying guest disk images.
Updated libguestfs packages that fix one security issue and several bugs, and add a number of enhancements, are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having low security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are linked to from the security descriptions below.
Security fix:
libguestfs relied on the format auto-detection in QEMU rather than allowing the guest image file format to be specified. A privileged guest user could potentially use this flaw to read arbitrary files on the host that were accessible to the user on that host by running a program that utilized the libguestfs library. (CVE-2010-3851)
Libguestfs has been rebased to upstream version 1.7.17, which includes the following bug fixes and enhancement (BZ#613593):
BZ#600144
The guestfish mkmountpoint and umount-all commands are considered incompatible. Mount points created with the mkmountpoint command become invalid after the umount-all command is used. This is now documented in the guestfish man page. Customers should note that it is possible to safely unmount devices that were mounted with mkmountpoint by using the umount command.
BZ#612308
The -net and vlan=... options in the qemu package are deprecated. To avoid relying on these deprecated options, libguestfs now uses the -netdev option instead.
BZ#615223
The guestfish vfs-type command could not determine the type of a file system newly created by guestfish. This occurred because the vfs-type command tried to read the type from a cache file (blkid.c) that had not yet been updated. The cache file is now deleted between file system creation and attempting to read the file system type, resulting in updated file system information for vfs-type to read.
BZ#617440
If the $HOME variable was not set, guestfish did not expand a path containing ~ (tilde) into a path to the user's home directory. Guestfish now examines the current user's passwd file for the location of the user's home directory so that a path containing ~ can be expanded correctly.
Additionally, an off-by-one error was discovered in the same path-expansion algorithm. This error could potentially cause a crash. The off-by-one error has been corrected so that this crash is no longer possible.
BZ#627468
The virt-inspector and virt-v2v tools did not work for Windows guests if an additional package, libguestfs-winsupport, was not installed. The error message did not explicitly state that this missing package could be responsible for the error. An additional note has been added to make the error output more useful when attempting to use these tools with Windows guests.
BZ#627832
Some guestfish commands print integer results. In some cases, namely for file permissions, the natural radix for these results is octal. Instead, guestfish returned decimal integer results for commands such as umask. This has been corrected, and guestfish commands that return integers now return them in the natural radix for that number.
BZ#627833
The get-e2uuid command retrieved file system UUIDs via tune2fs -l. This failed on journaling block devices (JBDs) and other devices that were not second, third or fourth extended file systems (ext2, ext3 or ext4). get-e2uuid has been reimplemented so that it retrieves UUIDs via blkid instead of tune2fs -l, resolving this issue. However, since the get-e2uuid command has been deprecated, customers are advised to retrieve UUIDs with the vfs-uuid command instead.
BZ#633174
Some guestfish commands would hang when applied to non-regular files. This had some security implications in that a guest could replace regular configuration files with, for example, character devices, and cause virt-inspector and other programs to hang. guestfish commands have been modified and can now handle non-regular files.
Additionally, virt-inspector has been rewritten as virt-inspector2, which is both more powerful, and more careful about untrusted files from the guest.
BZ#639601
libguestfs documentation did not specify that special characters should be surrounded by quotes or otherwise "escaped" when used with the virt-ls at the command line. The following has been added to the libguestfs documentation:
Libvirt guest names can contain arbitrary characters, some of which have meaning to the shell such as # and space. You may need to quote or escape these characters on the command line. See the shell manual page sh(1) for details.
BZ#639602
libguestfs documentation did not specify that special characters should be surrounded by quotes or otherwise "escaped" when used with the virt-list-filesystems at the command line. The following has been added to the libguestfs documentation:
Libvirt guest names can contain arbitrary characters, some of which have meaning to the shell such as # and space. You may need to quote or escape these characters on the command line. See the shell manual page sh(1) for details.
BZ#657472
The guestfish checksum command contained a file descriptor that was not closed properly in an error path. If the checksum command resulted in an error, this would later prevent the file system from being unmounted with either umount or umount-all. The file descriptor is now closed properly on the error path, so an error in checksum no longer causes problems unmounting file systems.
BZ#657502
The virt-inspector package had an unnecessary dependency on the perl-String-ShellQuote package. This superfluous dependency has been removed.
Note that this bug was reported and corrected during development. It was not seen in production systems in the field.
BZ#666577
If the /etc/fstab of a guest machine contained a reference to a floppy disk (/dev/fd0), both virt-inspector and virt-v2v printed the following harmless warning during inspection or conversion:
unknown filesystem /dev/fd0
This warning has been suppressed to avoid confusion, and should no longer appear even if the guest machine refers to floppy disks in /etc/fstab.
BZ#666579
If the /etc/fstab of a guest machine contained a reference to a CD-ROM drive (/dev/hdc), both virt-inspector and virt-v2v printed the following harmless warning during inspection or conversion:
unknown filesystem /dev/hdc
This warning has been suppressed to avoid confusion, and should no longer appear even if the guest machine refers to CD-ROM drives in /etc/fstab.
BZ#668115
The virt-filesystems command failed when used against a guest which had a missing or corrupt file system label. This command has been updated to handle guest file systems with missing or corrupt file system labels.
Note that this bug was reported and corrected during development. It was not seen in production systems in the field.
BZ#668611
When a device in /etc/fstab did not exist, the guestfish -i command failed with a "No such file or directory" error. In the event of missing devices, guestfish now completes, and reports that some file systems could not be mounted.
Note that this bug was reported and corrected during development. It was not seen in production systems in the field.
BZ#669840
The febootstrap package contained tools required to both build and run libguestfs. This package has now been split into two parts: febootstrap and febootstrap-supermin-helper. febootstrap now contains only tools used to create supermin appliances. A new package, febootstrap-supermin-helper, is a helper tool used to rebuild supermin appliances on the fly. libguestfs now depends only on the smaller febootstrap-supermin-helper package. Fresh libguestfs installations to Red Hat Enterprise Linux 6.1 now require less space because of this smaller dependency.
BZ#673477
Separating libguestfs trace output from debug output was difficult. A string (libguestfs: trace:) is now added to the beginning of each line of the trace output so that it can be easily distinguished and filtered out of logs with the grep command or similar.
BZ#673721
The virt-make-fs man page referred to the non-existent tool virt-make-resize. This reference should have been to the virt-make-fs tool. The man page has been corrected.
BZ#676788
The guestfish set-trace command was not prepared to handle all possible error conditions. This resulted in a segmentation fault when attempting to handle several conditions. The command now handles trace errors separately, so the segmentation fault no longer occurs.
Note that this bug was reported and corrected during development. It was not seen in production systems in the field.
BZ#691724
If the /etc/fstab of a guest machine contained a reference to a virtio disk (/dev/vda1), virt-inspector printed a warning and ignored the virtio disk. The warning has been suppressed, and virtio disks are now recognized by virt-inspector.
BZ#695138
A superfluous dependency on the gfs2-utils package has been removed.
All libguestfs users are advised to upgrade to these updated packages, which correct these issues and add these enhancements.

1.123. libguestfs-winsupport

1.123.1. RHEA-2011:0792: enhancement update

An enhanced libguestfs-winsupport package is now available for Red Hat Enterprise Linux 6.
The libguestfs-winsupport package adds support for Windows guests to libguestfs, a set of tools and libraries allowing users to access and modify virtual machine (VM) disk images.
This updated libguestfs-winsupport package adds the following enhancement:
  • The libguest-winsupport package depended on the entire febootstrap package. Since the febootstrap package was split into the febootstrap package and febootstrap-supermin-helper packages, libguest-winsupport now depends only on the febootstrap-supermin-helper package, which contains the runtime part of the original febootstrap package. (BZ#670299)
In addition, this update fixes the following bug:
  • The debuginfo subpackage contained no data and has been removed. (BZ#691555)
Users of libguestfs-winsupport are advised to upgrade to this updated package, which adds this enhancement and fixes this bug.

1.124. libhbalinux

1.124.1. RHBA-2011:0799: bug fix update

An updated libhbalinux package that fixes various bugs is now available for Red Hat Enterprise Linux 6.
The libhbalinux library is a vendor library utilized by fcoe-utils. The libhbaapi library provides programmatic access to the libhbalinux library. This library can retrieve adapter information with the assistance of libpciaaccess.
This updated libhbalinux package includes fixes for the following bugs:
  • Creating an FCoE (Fibre Channel over Ethernet) interface, by executing the "fceoadm -c [interface]" command, and shortly after the creation executing the "fcoeadm -i" command (which displays information about FCoE instances), resulted in a segmentation fault due to a NULL pointer dereference. This update fixes this issue and a segmentation fault no longer occurs in the aforementioned case. (BZ#690014)
  • After upgrading the libhbalinux package, the "fcoeadm -i" command (which shows information about FCoE instances) printed an error message. With this update, the "fcoeadm -i" command has been fixed, and no longer returns an error message.
All users of libhbalinux are advised to upgrade to this updated package, which resolves these issues.

1.125. libica

1.125.1. RHBA-2011:0676: bug fix update

Updated libica packages that fix various bugs are now available.
A library of functions and utilities for accessing ICA hardware crypto on IBM zSeries.
This updated libica packages fix the following bugs:
  • Previously, when the libica library ran in 31-bit mode, the STCK buffer length was smaller than required, which caused corrupted memory and application crashes. This is now fixed to ensure that the libica library allocates an appropriately sized STCK buffer in 31-bit mode to prevent corrupted memory and application crashes. (BZ#640035)
  • Previously, a SIGILL handler wrapped all cryptographic operations and caught crashes caused by invalid CPU instructions. This SIGILL handler prevented crashes but caused significant performance regression in the system. This is now fixed so that the CPU correctly reports the availability of individual cryptographics algorithms, therefore the SIGILL wrappers are removed. (BZ#665401)
  • The libica testsuite failed for libica_keygen_test and libica_sha1_test. The test failed for libica_sha1_test because "return to zero" was missing for the old_api_sha_test() function. The libica_keygen_test test failed because the openSSL powered RSA exponent only handles the values 3 or 65537 and libica_keygen_test provided a default random value. This is now fixed so that libica_sha1_test's old_api_sha_test includes "return to zero" and libica_keygen_test runs with parameters, "libica_keygen_test <keylength> <3|65537>". Due to this, the libica testsuite no longer fails for libica_keygen_test and libica_sha1_test. (BZ#624005)
Users are advised to upgrade to these updated packages, which resolves these issues.

1.126. libnl

1.126.1. RHBA-2011:0325: bug fix update

Updated libnl packages that plug a memory leak when libnl reported some error conditions are now available for Red Hat Enterprise Linux 6.
The libnl package contains a convenience library to simplify using the Linux kernel netlink sockets interface for network manipulation.
This update addresses the following issue:
  • Some nl_send_auto_complete() callers did not free the allocated message when errors were reported, resulting in libnl leaking memory. A problem in its own right, these small leaks also made it more work to detect memory leaks in other processes. With this update, allocated messages are freed correctly when nl_send_auto_complete() is called, and libnl no longer leaks memory in this circumstance. (BZ#676327)
All libnl users should upgrade to these updated packages, which resolve this issue.

1.126.2. RHBA-2011:0795: bug fix update

An updated libnl package that fixes various bugs is now available.
This package contains a convenience library to simplify using the Linux kernel's netlink sockets interface for network manipulation.
This update addresses the following issues:
  • When a domain started under libvirt, a memory leak was triggered from the libnl library because libnl continued to use memory no longer in use. Memory leaks in libnl are now fixed and libnl releases memory after it completes usage. (BZ#620345)
  • The port allocation/de-allocation was not safe in multi-threaded applications and the logic was incorrect, which resulted in some applications and other libraries being unable to initialize libnl. Port allocation/de-allocation and logic is now fixed, and libnl can now be initialized. (BZ#677724) (BZ#677725)
All libnl users should upgrade to this updated package, which resolves these issues.

1.127. libpciaccess

1.127.1. RHBA-2011:0806: bug fix update

Updated libpciaccess packages that fix two bugs are now available for Red Hat Enterprise Linux 6.
libpciaccess is a low level system library used to access PCI devices. It provides this functionality for X.Org and virtualization layers.
This update fixes the following bugs:
  • If pci_system_init/pci_system_cleanup was run twice (or more) in a row within the one process, a double close() could occur on the config_fd variable. This caused an error, as the FD associated with nullfd was closed by the second pci_get_strings() call. That was because the pci_device_linux_sysfs_destroy() failed to re-initialize the global 'config_fd' variable to -1 after closing it. This patch adds a line to set config_fd to -1 after the closure, fixing the issue. (BZ#675756)
  • When the pci_system_init() function opened the /proc/mtrr file and saved its file descriptor, then pci_system_cleanup() would fail to close the file descriptor. This resulted in a leak of the FD. With this update, added to the above bug's patch, the file descriptor is closed as expected. (BZ#675758)
All users of libpciaccess are advised to upgrade to these updated packages which resolve these issues.

1.128. libselinux

1.128.1. RHBA-2011:0751: bug fix update

Updated libselinux packages that fix various bugs are now available.
libselinux is the core library of an SELinux system. It provides an API for SELinux applications to get and set process and file security contexts and to obtain security policy decisions. It is required for any applications that use the SELinux API and used by all applications that are SELinux-aware.
These updated packages contain fixes for the following bugs:
  • libselinux used __thread variables to store malloc() data in order to minimize computation. Destructors cannot be associated with __thread variables, so malloc() data stored in a __thread void* variable could potentially cause memory leaks upon thread exit. For example, repeatedly starting and stopping domains with libvirt could trigger out-of-memory exceptions, since libvirt starts one thread per domain, and each thread uses libselinux calls such as fgetfilecon. libselinux has been updated to be thread-safe, preventing these potential memory leaks. (BZ#658571)
  • An update to libselinux added global destructors, which deleted thread-specific keys without checking that they had been initialized. Since the keys were not always initialized with the pthread_key_create() method and their default value was 0, it was possible that key 0 would be removed by these destructors. This resulted in segmentation faults in programs using active threads whose keys were removed, specifically in OpenJDK. Keys now receive a default value of -1, protecting uninitialized keys from attempts by global destructor to delete them. Note that this issue was discovered and corrected during development, and was not seen in production systems in the field. (BZ#693600)
  • An update to libselinux caused a segmentation fault to appear in the multi-threaded pam_chauthtok() test program. If a shared library attempted to call pthread_key_create(), the associated destructors were registered with that library. The segmentation fault occurred when pthread_key_delete() was called, if that library was dereferenced with dlclose() before the destructors were removed with pthread_key_delete(). This issue has now been corrected. Note: this issue was discovered and corrected during development, and was not seen in production systems in the field. (BZ#680887)
All users of libselinux are advised to upgrade to these updated packages, which resolve these issues.

1.129. libtdb

1.129.1. RHBA-2011:0808: bug fix update

Updated libtdb packages that resolve an issue are now available for Red Hat Enterprise Linux 6.
The libtdb package contains a library that implements a trivial database.
These updated libtdb packages fix the following bug:
  • When processing very large database updates, occasionally, tdb incorrectly allocated unnecessarily large amounts of memory. As a result, an OOM (Out Of Memory) situation occurred. This was caused by libtdb calling the tdb_expand() function to increase its size by creating space to store an extra hundred records of the size of the largest record it currently has. With this update, this behavior has been removed and tdb no longer allocates unnecessarily large amounts of memory. (BZ#692251)
All users of libtdb are advised to upgrade to these updated packages, which resolve this issue.

1.130. libtiff

1.130.1. RHSA-2011:0318: Important security update

Updated libtiff packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6.
The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The libtiff packages contain a library of functions for manipulating Tagged Image File Format (TIFF) files.
A heap-based buffer overflow flaw was found in the way libtiff processed certain TIFF Internet Fax image files, compressed with the CCITT Group 4 compression algorithm. An attacker could use this flaw to create a specially-crafted TIFF file that, when opened, would cause an application linked against libtiff to crash or, possibly, execute arbitrary code. (CVE-2011-0192)
Red Hat would like to thank Apple Product Security for reporting this issue.
All libtiff users should upgrade to these updated packages, which contain a backported patch to resolve this issue. All running applications linked against libtiff must be restarted for this update to take effect.

1.130.2. RHSA-2011:0392: Important security and bug fix update

Updated libtiff packages that fix one security issue and one bug are now available for Red Hat Enterprise Linux 4, 5, and 6.
The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The libtiff packages contain a library of functions for manipulating Tagged Image File Format (TIFF) files.
A heap-based buffer overflow flaw was found in the way libtiff processed certain TIFF files encoded with a 4-bit run-length encoding scheme from ThunderScan. An attacker could use this flaw to create a specially-crafted TIFF file that, when opened, would cause an application linked against libtiff to crash or, possibly, execute arbitrary code. (CVE-2011-1167)
This update also fixes the following bug:
  • The RHSA-2011:0318 libtiff update introduced a regression that prevented certain TIFF Internet Fax image files, compressed with the CCITT Group 4 compression algorithm, from being read. (BZ#688825)
All libtiff users should upgrade to these updated packages, which contain a backported patch to resolve these issues. All running applications linked against libtiff must be restarted for this update to take effect.

1.130.3. RHSA-2011:0452: Important security update

Updated libtiff packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The libtiff packages contain a library of functions for manipulating Tagged Image File Format (TIFF) files.
A heap-based buffer overflow flaw was found in the way libtiff processed certain TIFF image files that were compressed with the JPEG compression algorithm. An attacker could use this flaw to create a specially-crafted TIFF file that, when opened, would cause an application linked against libtiff to crash or, possibly, execute arbitrary code. (CVE-2009-5022)
All libtiff users should upgrade to these updated packages, which contain a backported patch to resolve this issue. All running applications linked against libtiff must be restarted for this update to take effect.

1.131. libtirpc

1.131.1. RHBA-2011:0747: bug fix update

An updated libtirpc package that fixes various bugs is now available.
The libtirpc package contains SunLib's implementation of transport independent RPC (TI-RPC) documentation. This includes a library required by programs in the nfs-utils and rpcbind packages.
This update fixes the following bugs:
  • Binaries in the nfs-utils package located in /sbin relied on shared libraries located in /usr. This has been fixed so that nfs-utils binaries installed in /sbin no longer rely on shared libraries in /usr/lib. (BZ#558937)
  • Previously certain files were under SISSL license. These files are now under the BSD license and are marked with the "Copyright (c) 2010, Oracle America, Inc." license text. (BZ#628682)
  • In a multi-homed NFS server with two IP addresses on the same subnet, mount operations sent to one IP address would result in a reply from the other IP address. This is now fixed to ensure that a mount request to one IP address elicits a response from the same IP address. (BZ#676234)
Users are advised to upgrade to these updated packages, which resolve this issue.

1.132. libuser

1.132.1. RHSA-2011:0170: Moderate security update

Updated libuser packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The libuser library implements a standardized interface for manipulating and administering user and group accounts. Sample applications that are modeled after applications from the shadow password suite (shadow-utils) are included in these packages.
It was discovered that libuser did not set the password entry correctly when creating LDAP (Lightweight Directory Access Protocol) users. If an administrator did not assign a password to an LDAP based user account, either at account creation with luseradd, or with lpasswd after account creation, an attacker could use this flaw to log into that account with a default password string that should have been rejected. (CVE-2011-0002)
Note: LDAP administrators that have used libuser tools to add users should check existing user accounts for plain text passwords, and reset them as necessary.
Users of libuser should upgrade to these updated packages, which contain a backported patch to correct this issue.

1.133. libvirt

1.133.1. RHSA-2011:0391: Important security update

Updated libvirt packages that fix one security issue are now available for Red Hat Enterprise Linux 5 and 6.
The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The libvirt library is a C API for managing and interacting with the virtualization capabilities of Linux and other operating systems. In addition, libvirt provides tools for remotely managing virtualized systems.
It was found that several libvirt API calls did not honor the read-only permission for connections. A local attacker able to establish a read-only connection to libvirtd on a server could use this flaw to execute commands that should be restricted to read-write connections, possibly leading to a denial of service or privilege escalation. (CVE-2011-1146)
Note: Previously, using rpmbuild without the '--define "rhel 5"' option to build the libvirt source RPM on Red Hat Enterprise Linux 5 failed with a "Failed build dependencies" error for the device-mapper-devel package, as this -devel sub-package is not available on Red Hat Enterprise Linux 5. With this update, the -devel sub-package is no longer checked by default as a dependency when building on Red Hat Enterprise Linux 5, allowing the libvirt source RPM to build as expected.
All libvirt users are advised to upgrade to these updated packages, which contain a backported patch to resolve this issue. After installing the updated packages, libvirtd must be restarted ("service libvirtd restart") for this update to take effect.

1.133.2. RHSA-2011:0479: Moderate security and bug fix update

Updated libvirt packages that fix one security issue and one bug are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The libvirt library is a C API for managing and interacting with the virtualization capabilities of Linux and other operating systems. In addition, libvirt provides tools for remotely managing virtualized systems.
A flaw was found in the way libvirtd handled error reporting for concurrent connections. A remote attacker able to establish read-only connections to libvirtd on a server could use this flaw to crash libvirtd. (CVE-2011-1486)
This update also fixes the following bug:
  • Previously, running qemu under a different UID prevented it from accessing files with mode 0660 permissions that were owned by a different user, but by a group that qemu was a member of. (BZ#668692)
All libvirt users are advised to upgrade to these updated packages, which contain backported patches to resolve these issues. After installing the updated packages, libvirtd must be restarted ("service libvirtd restart") for this update to take effect.

1.133.3. RHBA-2011:0446: bug fix update

Updated libvirt packages that resolve several issues are now available for Red Hat Enterprise Linux 6.
The libvirt library is a C API for managing and interacting with the virtualization capabilities of Linux and other operating systems. In addition, libvirt provides tools for remotely managing virtualized systems.
These updated libvirt packages provide fixes for the following bugs:
  • When a root-squashing export of a domain was owned by a group to which the qemu user belonged, but was not owned by the qemu user, libvirt could not create a file to save the domain's state. This was because the save operation was invoked by the user who did not have the needed group permissions. With this update, libvirt first acquires all the needed group permissions and only then attempts to perform the aforementioned save operation. (BZ#656355)
  • Members of the qemu group did not have read/write permissions for the "[localstatedir]/[cache/lib]/libvirt/qemu/" directory in which XML files which define sockets are placed. Permissions are now updated to allow the qemu group read/write permissions. (BZ#656972)
  • A race condition where an application could query block information on a virtual guest that had just been migrated away could occur when migrating a guest. As a result, the libvirt service crashed. The libvirt application now verifies that a guest exists before attempting to start any monitoring operations. (BZ#658141)
  • Live migration of a guest could take an exceptionally long time to converge to the switchover point if the guest was very busy. By allowing to increase the downtime setting of a guest, migration is more likely to complete. However, libvirt was sending an incorrectly formatted request to increase the downtime setting of a guest. With this update, libvirt correctly sends the downtime setting request. (BZ#658143)
  • The "addrToString" methods did not work properly with UNIX domain sockets which did not have a normal "host:port" address. As a result SASL (Simple Authentication and Security Layer) could not be used over UNIX domain sockets. With this update, the "addrToString" methods are fixed and SASL is no longer restricted to TCP connections. (BZ#658144)
  • Prior to this update, libvirt was not able to recognize whether a domain crashed or was properly shut down. With this update, a SHUTDOWN event sent by qemu is recognized by libvirt when a domain is properly shut down. If the SHUTDOWN event is not received, the domain is declared to have crashed. (BZ#662042)
  • A deadlock occurred in the libvirt service when running concurrent bidirectional migration because certain calls did not release their local driver lock before issuing an RPC (Remote Procedure Call) call on a remote libvirt daemon. A deadlock no longer occurs between two communicating libvirt daemons. (BZ#662043)
  • A specification file bug caused permissions on the /var/lib/libvirt directory to change when upgrading a system. With this update, correct permissions are assigned to the aforementioned directory. (BZ#662045)
  • An off-by-one error in a clock variable caused a virtual guest to show incorrect date and time information. This update addresses this error. Date and time information is now correctly displayed. (BZ#662046)
  • The %post script (part of the libvirt-client package) started the libvirt-guests service even when the service was explicitly turned off. With this update, the libvirt-guests service is no longer started when explicitly turned off. (BZ#668694)
  • Starting and shutting down a domain led to a memory leak due to the memory buffer not being freed properly. With this update, starting and shutting down a domain no longer leads to a memory leak. (BZ#672549)
  • Starting and shutting down a domain led to a memory leak due to the use of a thread-unfriendly "matchpathcon" (which gets the default security context for the specified path) SELinux API. With this update, libvirt uses improved SELinux APIs and a memory leak no longer occurs.(BZ#672554)
All users of libvirt are advised to upgrade to these updated packages, which resolve these issues.

1.133.4. RHBA-2011:0596: bug fix and enhancement update

Updated libvirt packages that upgrade the libvirt library to upstream version 0.8.7, fix a number of bugs, and add various enhancements and new features are now available for Red Hat Enterprise Linux 6.
The libvirt library is a C API for managing and interacting with the virtualization capabilities of Linux and other operating systems. In addition, libvirt provides tools for remotely managing virtualized systems.
These updated packages upgrade the libvirt library for Red Hat Enterprise Linux 6 to upstream version 0.8.7, which contains many enhancements and bug fixes over the previous version. This section contains detailed information about a subset of bug fixes and enhancements that are likely to affect customers only. For a short summary of all changes see the CHANGELOG file installed to /usr/share/doc/libvirt-0.8.7 when the updated package is installed.
Bug fixes:
BZ#515692
Guests were not required to honour the virDomainSetMemory() setting, making it impossible to set a hard limit on guest memory consumption. New virDomainGetMemoryParameters and virDomainSetMemoryParameters methods have been introduced to allow users to fine-tune and enforce memory limits.
BZ#561935
Live migration of a guest could take an exceptionally long time to converge to the switchover point if the guest was very busy. Migration is more likely to complete if a guest's downtime setting is increased. However, libvirt was sending an incorrectly formatted request to increase the downtime setting of a guest. This update corrects the format of this request to assist in live migration completion.
BZ#672226
Using SASL authentication with a single libvirt connection for multiple threads could result in libvirt hanging while waiting for a response from the libvirt daemon. SASL decoding has been fixed such that clients do not wait for further data while already decoded SASL data remains unprocessed, so libvirt no longer hangs in this situation.
BZ#688774
libvirt was not careful about object locking rules when managing KVM guests, which resulted in a number of unexpected actions. If a guest shut down without notice, libvirt could crash or loop indefinitely. Locking code in libvirt has been improved to avoid accessing data outside locks, and to avoid deadlocks when multiple threads are interacting with the same domain, so libvirt no longer hangs or crashes when a guest shuts down.
BZ#677729
The port allocation/de-allocation of the libnl library, which is used by libvirt for macvtap (for example, vepa and vnlink) interfaces, was not threadsafe and the logic was incorrect. This resulted in a failure to initialize libnl, and a subsequent failure of the associated libvirt functionality. In particular, the first guest vepa interface started on a host would work, but all subsequent vepa interfaces would fail. Port allocation/de-allocation and logic is now fixed in libnl, and the failures in libvirt no longer occur.
BZ#687551
In previous releases, libvirt set a maximum lease limit for DHCP leases on each virtual network according to the number of addresses available on that network. However, all networks shared the same lease file, so the maximum lease limit was reached long before all networks had given out all of their addresses. This meant that some guests were unable to obtain IP addresses. With this release of libvirt, each virtual network uses its own lease file, so there is sufficient space for all configured addresses to be allocated.
BZ#691514
When creating virtual machines via remote protocol, the client hung because the list of remote procedure calls to execute was not traversed correctly. Traversal has been corrected so that creating virtual machines remotely no longer causes libvirt to hang.
BZ#692998
libvirt removed the managed state file (created by virsh managedsave dom) even if it failed to restore and start the domain using that file. This caused data loss. The managed state file is now removed only if the restore operation succeeds.
BZ#638285
During migration, an application could query block information on the virtual guest being migrated. This resulted in a race condition that crashed libvirt. libvirt now verifies that a guest exists before attempting to start monitoring operations.
BZ#656795
Memory buffer was not freed properly on domain startup and shutdown, which led to a memory leak that increased each time the domain was started or shut down. This update removes this memory leak.
BZ#660706
The %post script (part of the libvirt-client package) started the libvirt-guests service even when the service was explicitly turned off. The libvirt-guests service is no longer started when explicitly turned off.
BZ#659310
A deadlock occurred in the libvirt service when running concurrent bidirectional migration because certain calls did not release their local driver lock before issuing an RPC (Remote Procedure Call) call on a remote libvirt daemon. A deadlock no longer occurs between two communicating libvirt daemons.
BZ#653293
When running virsh vcpuinfo or setting up virtual CPU pinning on a host machine that used NUMA, virsh vcpuinfo showed the incorrect number of virtual CPUs. Virtual CPU pinning could also fail because libvirt reported an incorrect number of CPU sockets per NUMA node. Virtual CPUs are now counted correctly.
BZ#660194
An off-by-one error in a clock variable caused a virtual guest to show incorrect date and time information. This update corrects this error so that date and time information is correctly displayed.
BZ#649523
A specification file bug caused permissions on the /var/lib/libvirt directory to change when a system was upgraded. With this update, correct permissions are assigned to the aforementioned directory.
BZ#658657
libvirt used a non-thread friendly SELinux API (matchpathcon) to get the default security context for a specified path. This led to a memory leak upon domain startup and shutdown. libvirt now uses improved SELinux APIs, so this memory leak no longer occurs.
BZ#646895
Device boot order could not be set more explicitly than Network, Disk, CD ROM, or Floppy. This meant that users could not select the exact boot device that they wished to use. A per-device <boot> element has been introduced, which can be used to specify the exact order of boot devices.
BZ#609463
The MAC address of libvirt's bridges could change over time depending on which guests were currently running and connected. This caused problems in some Windows guests, which assumed that the changed MAC address indicated a new network connection, and automatically launched a configuration wizard. libvirt now creates a dummy tap device with a guaranteed lowest MAC address that will not change. This address is stored as part of network configuration so that it will persist across host reboots.
BZ#611793
If the configuration for a virtual network only contained static address definitions, dnsmasq (the DHCP server used by libvirt) was started incorrectly and would not respond to any DHCP requests. Any guests with MAC address/IP address pairs listed in static address definitions were then unable to acquire their IP addresses. libvirt now starts up dnsmasq with the correct options so that these statically configured addresses are properly served to the guests.
BZ#639587
The virsh freecell command could be run with an invalid (non-integer) argument without error, and the free memory for node 0 would still be printed. The validity of the argument is now checked, and an error message is now printed when an invalid value is detected.
BZ#671050
If the virsh detach-interface command was used on a domain with multiple NICs, but a particular MAC address was not specified with --mac, virsh detached the first interface without error. The --mac option is now required where a domain has multiple NICs, and an appropriate error message has been added.
BZ#627143
If the user did not specify a disk driver when hot-plugging a disk with virsh attach-disk, virsh set phy as the driver value by default. Because this value is not supported everywhere, the disk did not persist over domain shutdown, and could prevent domain startup. This update corrects virsh behavior such that the driver value is not set if it is not provided by the user.
BZ#667091
libvirt incorrectly identified the virtual IB700 device (an ISA device) as a PCI device, resulting in the device being misconfigured, and preventing the virtual machine from booting until the virtual IB700 device was removed. libvirt now identifies the IB700 device correctly.
BZ#605660
Invalid setvcpus commands resulted in unknown errors. More useful error messages have been added to this command.
BZ#676374
A typographical error in source code that parsed and wrote SPICE auth data caused unrelated data to be overwritten, which caused a crash in libvirt. The error has been corrected, and auth can now be set without issue.
BZ#696660
The string containing the name of libvirt's "dummy" tap interface was freed before network startup was guaranteed. This caused a segmentation fault if a problem occurred while setting the forward-delay or stp-enable parameters. The string is no longer freed prematurely, and in the event of a problem with these parameters, users receive a specific error message.
BZ#689001
When a problem occurred while starting up a guest that used direct interfaces, an uninformative error message ("unspecified error") was printed to the log. These failures now have specific, more informative log messages.
BZ#611822
When the certificate used for TLS authentication was rejected, libvirt displayed a log message containing a command that had misleading output (openssl x509 -in clientcert.pem -text). This command has been replaced with the following command, which gives more helpful, accurate output:
certtool -i --infile /etc/pki/libvirt/clientcert.pem
Enhancements:
BZ#586124
The virtual networks created and used by libvirt for virtual guest connectivity were previously limited to only IPv4 connectivity; IPv6 traffic was explicitly disallowed. Full IPv6 connectivity is now supported on libvirt's virtual networks, including autoconf address/route discovery and a DNS server listening on an IPv6 address on the network. Note, however, that because autoconf is supported, there is no support for DHCPv6.
BZ#656845
libvirt could not determine whether a domain had crashed or been correctly shut down. This update adds recognition of the SHUTDOWN event sent by qemu when a server is shut down correctly. If this event is not received, the domain is now declared to have crashed.
BZ#653530
An --all option has been added to the virsh freecell command to allow the command to iterate across all nodes instead of forcing users to run the command manually on each node. virsh freecell --all will list the free memory on all available nodes.
BZ#635419
Users can now disable memory merging (KSM) on guest machines. Note however that this requires support for the underlying qemu-kvm -redhat-disable-KSM flag.
BZ#641187
The virsh documentation has been updated to clarify usage of the cpu_shares parameter.
BZ#639603
The virsh documentation has been updated to remove references to the deprecated virt-mem command.
BZ#605660
The virsh documentation for the setvcpus, setmem, and setmaxmem sub-commands has been updated to correct and expand the information available for these sub-commands.
BZ#595350
A man page is now available for libvirtd. Access it with the man libvirtd command.
All users of libvirt are advised to upgrade to these updated packages, which correct these issues and add these enhancements.

1.134. libvirt-cim

1.134.1. RHEA-2011:0648: enhancement update

An enhanced libvirt-cim package is now available for Red Hat Enterprise Linux 6.
The libvirt-cim package contains a Common Information Model (CIM) provider based on Common Manageability Programming Interface (CMPI). It supports most libvirt virtualization features and allows management of multiple libvirt-based platforms.
This updated libvirt-cim package adds the following enhancements:
  • Previously, the libvirt-cim migration indications did not contain any UUID (universally unique identifier) values. This update adds the UUID values to migration indications and improves the ability of the management software to track migrated virtual machines. (BZ#633331)
  • Previously, Virtual Ethernet Port Aggregator (VEPA) and VSI (Virtual Station Interface) networking capabilities were not supported. This update provides support for both VEPA and VSI. (BZ#633336)
All libvirt-cim users are advised to upgrade to this updated package, which adds these enhancements.

1.135. libvirt-java

1.135.1. RHBA-2011:0761: bug fix and enhancement update

Updated libvirt-java packages that provide a new API, fix several bugs, and add various enhancements are now available for Red Hat Enterprise Linux 6.
The libvirt-java package provides a base framework to use libvirt, which is the virtualization API to manage and interact with the virtualization capabilities.
The libvirt-java package has been upgraded to upstream version 0.4.7, which provides a new API, improved error-handling, and enhancements over the previous version. (BZ#675044)
Users are advised to upgrade to these updated libvirt-java packages, which resolve these issues and add these enhancements.

1.136. libvirt-qpid

1.136.1. RHBA-2011:0762: bug fix update

An updated libvirt-qpid package that fixes one bug is now available for Red Hat Enterprise Linux 6.
The libvirt-qpid package provides an interface with libvirt using the qpid modeling framework (QMF), which utilizes the Advanced Message Queuing Protocol (AMQP), an open standard application layer protocol providing reliable transport of messages.
  • Previously, libvirt-qpid did not correctly connect to qpid due to an authentication conflict. This update rebuilds libvirt-qpid to match the qpid-cpp package. Now, libvirt-qpid runs as expected. (BZ#618876)
Users of libvirt-qpid are advised to upgrade to this updated package, which fixes this bug.

1.137. libvpd

1.137.1. RHEA-2011:0548: enhancement update

An updated libvpd package that adds an enhancement is now available for Red Hat Enterprise Linux 6.
The libvpd package contains the classes that are used to access Vital Product Data (VPD) created by vpdupdate in the lsvpd package.
This update introduces the following enhancement:
  • This update provides the latest API by which external serviceability and diagnostics tools can access VPD, consisting of hardware present on a system, the characteristics of that hardware, or hardware state. (BZ#632738)
Users of libvpd are advised to install this package, which adds this enhancement.

1.138. libvpx

1.138.1. RHSA-2010:0999: Moderate security update

Updated libvpx packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The libvpx packages provide the VP8 SDK, which allows the encoding and decoding of the VP8 video codec, commonly used with the WebM multimedia container file format.
An integer overflow flaw, leading to arbitrary memory writes, was found in libvpx. An attacker could create a specially-crafted video encoded using the VP8 codec that, when played by a victim with an application using libvpx (such as Totem), would cause the application to crash or, potentially, execute arbitrary code. (CVE-2010-4203)
All users of libvpx are advised to upgrade to these updated packages, which contain a backported patch to correct this issue. After installing the update, all applications using libvpx must be restarted for the changes to take effect.

1.139. lldpad

1.139.1. RHBA-2010:0857: bug fix update

An updated lldpad package that fixes dcbx negotiation issues is now available for Red Hat Enterprise Linux 6.
The lldpad package adds Link Layer Discovery Protocol (LLDP) support for all ports.
This update fixes the following bug:
  • Previously, lldpad failed to initiate a dcbx negotiation when a "link down" netlink event message was dropped or lost. As a result, a boot failure occurred and the system got suspended. With this update, lldpad dcbx negotiation works as expected. (BZ#639414)
All lldpad users are advised to upgrade to this updated package, which resolves this issue.

1.139.2. RHBA-2011:0520: bug fix and enhancement update

An updated lldpad package that fixes multiple bugs and adds one enhancement is now available for Red Hat Enterprise Linux 6.
The lldpad package provides the Linux user space daemon and configuration tool for Intel's Link Layer Discovery Protocol (LLDP) agent with Enhanced Ethernet support.
This update fixes the following bugs:
  • Previously, lldpad did not initiate a Data Center Bridging Exchange (DCBX) negotiation if a link down netlink event message (nlmsg) was dropped or lost. Due to this lack, DCBX could not negotiate and Fibre Channel over Ethernet (FCoE) did not login to the fabric in this case. This update resolves this problem. Now, lldpad successfully initiates a Data Center Bridging Exchange (DCBX). (BZ#631587)
  • Previously, lldpad could not be upgraded or removed on systems which had lldpad packages for both Intel P6 and Intel 64 simultaneously installed. As a workaround, this update removes such packages with the command rpm -e --noscripts. (BZ#647833)
  • Previously, non-default priorities for FCoE did not correctly work, because lldpad handled application type-length-values (TLV) incorrectly. With this update, non-default priorities work as expected. (BZ#694671)
  • Previously, lldpad did under certain circumstances not correctly synchronize with peers on link events. Due to this issue, users had to manually reset the link or lldpad. This update resolves the synchronization issue. Now, synchronization with peers on link events works as expected. (BZ#694925)
This update also adds the following enhancement:
  • The lldpad package has been upgraded to upstream version 0.9.41, which builds on the new kernel interface and adds support for 802.1Qbg Edge Virtual Bridging, netlink, and libvirt, as well as a new, flexible build process. (BZ#675076)
All lldpad users are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

1.140. logrotate

1.140.1. RHSA-2011:0407: Moderate security update

An updated logrotate package that fixes multiple security issues is now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
The logrotate utility simplifies the administration of multiple log files, allowing the automatic rotation, compression, removal, and mailing of log files.
A shell command injection flaw was found in the way logrotate handled the shred directive. A specially-crafted log file could cause logrotate to execute arbitrary commands with the privileges of the user running logrotate (root, by default). Note: The shred directive is not enabled by default. (CVE-2011-1154)
A race condition flaw was found in the way logrotate applied permissions when creating new log files. In some specific configurations, a local attacker could use this flaw to open new log files before logrotate applies the final permissions, possibly leading to the disclosure of sensitive information. (CVE-2011-1098)
An input sanitization flaw was found in logrotate. A log file with a specially-crafted file name could cause logrotate to abort when attempting to process that file a subsequent time. (CVE-2011-1155)
All logrotate users should upgrade to this updated package, which contains backported patches to resolve these issues.

1.141. logwatch

1.141.1. RHSA-2011:0324: Important security update

An updated logwatch package that fixes one security issue is now available for Red Hat Enterprise Linux 5 and 6.
The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
Logwatch is a customizable log analysis system. Logwatch parses through your system's logs for a given period of time and creates a report analyzing areas that you specify, in as much detail as you require.
A flaw was found in the way Logwatch processed log files. If an attacker were able to create a log file with a malicious file name, it could result in arbitrary code execution with the privileges of the root user when that log file is analyzed by Logwatch. (CVE-2011-1018)
Users of logwatch should upgrade to this updated package, which contains a backported patch to resolve this issue.

1.142. lohit-devanagari-fonts

1.142.1. RHEA-2011:0203: enhancement update

An updated lohit-devanagari-fonts package that adds an enhancement is now available for Red Hat Enterprise Linux 6.
The lohit-devanagari-fonts package provides a free Devanagari Script TrueType and OpenType font.
This update adds the following enhancement:
  • A glyph for the Indian rupee sign (U+20B9) defined in version 6.0 of the Unicode standard has been added to the font. (BZ#651713)
All users requiring the Indian rupee sign should install this updated package, which adds this enhancement.

1.143. lohit-kannada-fonts

1.143.1. RHBA-2011:0667: bug fix and enhancement update

An updated lohit-kannada-fonts package that corrects display problems and adds Latin punctuation glyphs is now available.
lohit-kannada-fonts provides a free TrueType and OpenType typeface for writing and displaying Kannada script.
This update corrects the following display issue:
  • * Previously, Lohit Kannada did not include Latin punctuation glyphs (such as opening and closing parentheses). When these characters were required while using the Kannada script, they were drawn from a system's default Latin script. With this update, these characters have been added to the Kannada character set, improving the look of text which mixes Kannada characters and Latin punctuation glyphs.
    As well, the right-side bearing rules for Kannada conjuncts that immediately follow a Latin parenthesis character have been corrected to ensure these glyphs no longer kern so close as to overlap. (BZ#577127)

1.144. lohit-oriya-fonts

1.144.1. RHBA-2011:0707: bug fix update

An updated lohit-oriya-fonts package that fixes OpenType rules for presenting conjunction characters in Qt-based applications is now available for Red Hat Enterprise Linux 6.
The lohit-oriya-fonts package provides a free Oriya script TrueType and OpenType font.
This update addresses the following issue:
  • Oriya script is an abugida or alphasyllabic writing system and, when certain consonant glyphs would otherwise be written adjacent, applies rules for replacing the glyphs with a single, ligatured conjunction character. The OpenType version of Lohit Oriya did not, previously, apply these rules correctly when the typeface was used in an application built using the Qt application framework (eg OpenOffice or KWrite). With this update, these rules act as expected, and conjunct symbols appear properly when the OpenType face is used in Qt-based applications.
    Note: this bug did not present if the TrueType face was used in Qt-based applications, nor did it present in applications built with the GTK+ framework (eg AbiWord and gedit) if the OpenType face was used. (BZ#623990)
Users should upgrade to this updated package, which resolves this issue.

1.145. lohit-tamil-fonts

1.145.1. RHBA-2011:0704: bug fix update

An updated lohit-tamil-fonts package that fixes a display issue in the asterisk glyph ('*' -- Unicode U+002A) is now available for Red Hat Enterprise Linux 6.
The lohit-tamil-fonts package provides a free Tamil script TrueType and OpenType font.
This update addresses the following display issue:
  • The Latin asterisk glyph ('*' -- ASCII 0x2A; Unicode U+002A) was over-sized relative to the same glyph as presented in other non-Latin scripts which include Latin glyphs (eg Lohit Devanagari). With this update, the asterisk has been re-drawn to match the glyph included with Lohit Devanagari. This re-drawing also ensures the asterisk matches the typographic 'color' of the Tamil script characters and the other Latin glyphs included with this typeface. (BZ#629813)
Users should upgrade to this updated package, which resolves this issue.

1.146. lsvpd

1.146.1. RHEA-2011:0547: enhancement update

An updated lsvpd package that adds an enhancement is now available available for Red Hat Enterprise Linux 6.
The lsvpd package contains all of the lsvpd, lscfg and lsmcode commands.
This update upgrades the lsvpd package to upstream version 1.6.9, which provides an enhancement over the previous version. (BZ#632737)
Users of lsvpd are advised to upgrade to this updated package, which adds this enhancement.

1.147. luci

1.147.1. RHBA-2011:0655: bug fix update

An updated luci package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6.
The luci package provides a web-based high-availability cluster configuration application.
This update fixes the following bugs:
BZ#536841
Previous versions of luci did not allow users to change the number of votes for a particular node. With this update, the underlying source code has been adapted to provide this functionality, and users are now allowed to change the number of votes for a node as expected.
BZ#600057
Under certain circumstances, the list of nodes may not have included uptime information for all nodes. This error has been fixed, and the uptime is now displayed for all listed nodes as expected.
BZ#600078
Prior to this update, the user interface of the luci application did not inform users about possible issues with using the Quorum Disk on certain configurations. This update corrects this error, and the user interface now informs users that Quorum Disk cannot be used unless each node has exactly 1 vote, and advises them not to use this feature for clusters with more than 8 nodes.
BZ#605932
When configuring the Quorum Disk, previous version of luci did not allow users to reset input fields to their default values. To address this issue, this update adds the Reset values to defaults button to the user interface.
BZ#613155
Previously, when a user other than root or luci attempted to run the luci init script, the service failed to start and a traceback was written to standard error. With this update, the init script has been corrected to terminate with exit code 4 in this case.
BZ#613871
When a user attempted to view a cluster that contained an unknown or unsupported fence device, luci displayed error 500, and a traceback was written to the luci.log log file. This error has been fixed, and luci now correctly displays Unknown fence device type when an unknown or unsupported fence device is encountered.
BZ#614963
Due to an incorrect use of a deprecated Python feature, the following message may have been occasionally written to the luci.log log file:
DeprecationWarning: BaseException.message has been deprecated as of Python 2.6
This update corrects the underlying source code not to use deprecated features, so that the above message no longer appears in the log file.
BZ#616239
Previously, deleting a cluster from the user interface only removed the cluster from luci, but did not remove the cluster.conf configuration file or shut down the clustering on the nodes. This update corrects this error, and users are now allowed to completely destroy a whole cluster by selecting all of its nodes and clicking the Delete button.
BZ#617586
Prior to this update, certain actions, such as the creation of a new cluster, required users to manually refresh the user interface. This update introduces a progress dialog that informs users about the current status of long-running operations and automatically refreshes the user interface when such an operation completes.
BZ#617587
When the ricci daemon encountered an error, previous version of luci did not present this error to a user and displayed a generic error message instead. In order to make it easier to determine the cause of such errors, this update adapts luci to display the error messages reported by ricci.
BZ#618701
When a user created a cluster with a name that contained spaces, clicking the cluster name in the user interface caused luci to display error 404. This error has been fixed, and luci is now able to work with clusters with spaces in their names as expected.
BZ#620377
Prior to this update, various drop-down menus in the user interface of luci did not remember their selection. With this update, this error no longer occurs, and all drop-down menus now remember their selection as expected.
BZ#622562
Previous versions of luci did not allow users to configure unfencing, and thus prevented the SAN fencing agents and fence_scsi from being unfenced at boot time. With this update, the underlying source code has been adapted to provide this functionality, and users are now allowed to configure unfencing from the user interface.
BZ#624716
When a user configured a cluster for the first time, the Services, Resources, Failover Domains, and Devices tabs contained the following error message:
No nodes from this cluster could be contacted. The status of this cluster is unknown.
Since this message may have been misleading, luci has been adapted to display a more comprehensive message, such as No items to display.
BZ#633983
Prior to this update, luci did not handle the nodename parameter for the fence_scsi fence agent correctly. This update corrects this error, and the nodename parameter is now handled properly.
BZ#636267
Prior to this update, the Fence Devices tab contained two Update buttons. However, these buttons are no longer required, and clicking them did not trigger any action. With this update, the Update buttons have been removed from the Fence Devices tab.
BZ#636300
Previously, luci did not handle the username for the fence_egenera fence agent correctly. With this update, the underlying source code has been modified to address this issue, and the username for fence_egenera is now handled correctly.
BZ#639123
Prior to this update, action buttons such as those for starting, stopping, deleting, or rebooting nodes were active even if no node was selected. Consequent to this, clicking such a button caused luci to display an error message. This update addresses this issue, and the action buttons are no longer active when no node is selected.
BZ#639124
When changes to a cluster were made outside of luci, previous versions of luci did not update the local database to reflect the current cluster membership. This update corrects this error, and in response to such changes to cluster membership, luci now updates its local database as expected.
BZ#659014
Previously, when a user attempted to configure a node with a fully qualified domain name (FQDN) that did not match the cluster node name, luci incorrectly displayed error 500, and a traceback was written to the luci.log log file. This error no longer occurs, and users are now allowed to configure such nodes as expected.
BZ#678366
Under certain circumstances, an attempt to remove existing fence methods from a device, or add new fence instances may have failed. This update corrects the fence management in luci, and removing existing fence methods from a device or adding new fence instances no longer fails.
BZ#678424
Under certain circumstances, an attempt to add a node to an existing cluster could fail with the following message written to the luci.log log file:
AttributeError: 'ClusterNode' object has no attribute 'getID'
With this update, the underlying source code has been modified to address this issue, and luci no longer fails with the above error when adding a new node to a cluster.
BZ#682843
Previously, when configuring the Samba resource agent, the user interface of luci contained the Workgroup input box. Since, this option is not used by the resource agent, this update removes it from the user interface.
As well, this update adds the following enhancements:
BZ#472972
Support for the OracleListener and OracleInstance resource agents has been added.
BZ#557234
This update allows luci to communicate with the ricci daemon on an interface different from the one that is used for the cluster communication.
BZ#620343
To make the distinction between services and resources more obvious, the Services label in the user interface of luci has been replaced with more comprehensive Service Groups.
BZ#620373
The user interface of luci has been adjusted to present tabs to a user in more logical order.
BZ#624558
The Use UDP unicast (UDPU) option has been added to the Network Configuration page. Note that unless expert mode is enabled, the Use broadcast option is no longer presented to a user.
BZ#632344
This update introduces the Logging Configuration page, which allows users to configure centralized logging.
BZ#637223
Support for the fence_cisco_ucs fence agent has been added.
BZ#639107
Support for the fence_rhev fence agent has been added.
BZ#639111
This update adds support for configuring non-critical cluster resources.
BZ#639120
An expert user mode has been added. When enabled, this mode allows users to edit most of the properties that are defined by the cluster schema.
BZ#666971
This update adds the Disable updates to static routes check box to the user interface, allowing users to disable updates to static routes in the IP resource agent.
BZ#680173
Support for the Distributed Replicated Block Device (DRBD) resource type has been added.
BZ#681506
This update re-includes fence_brocade to the list of supported fence agents.
All users of luci are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

1.148. lvm2

1.148.1. RHBA-2010:0849: bug fix update

Updated lvm2 packages that resolve several issues are now available.
The lvm2 packages contain support for Logical Volume Management (LVM).
These updated lvm2 packages provide fixes for the following bugs:
  • This update avoids data corruption caused by a failure to detect that a filesystem being resized with 'fsadm' (or lvresize/lvreduce --resizefs) is mounted. The update also fixes various other problems in 'fsadm' including incorrect handling of user's break action, inconsistent processing of the '--dry-run' option, missing support for correctly passing the '--yes' option, and incorrect handling of the 'LVM_BINARY' environment variable. (BZ#641461)
  • Under some circumstances, creating cluster mirrors with the '--nosync' option could cause I/O to become extremely slow. Note that this issue only effected I/O immediately after the creation of the mirror, and only when '--nosync' was used. With this update, I/O no longer runs slow in the aforementioned case. (BZ#641812)
  • Previously, the limit for tags section in metadata was 4096 characters. When this limit was exceeded, the VG metadata were corrupted. With this update, the limitation has been removed and the limit is given by metadata size only. (BZ#641896)
  • Previously, a limit for maximum output length in reporting functions (vgs, lvs) caused problems while using a large set of tags. With this update, the output lines in these reports are now limited by available memory only. (BZ#648554)
All users of lvm2 are advised to upgrade to these updated packages, which resolve these issues.

1.148.2. RHBA-2010:0951: bug fix update and enhancement

Updated lvm2 packages that fix several bugs and add an enhancement are now available.
The lvm2 packages contain support for Logical Volume Management (LVM).
These updated lvm2 packages provide fixes for the following bugs:
  • Merging of a snapshot volume caused I/O errors to be issued during a reboot. After the reboot the snapshot volume (snapshot of an LV where the root file system resides) was still present and it appeared as if the merge operation was still in progress. With this update, the errors no longer occur and the snapshot merge completes cleanly. (BZ#651007)
  • The optimizer for the regex filter defined in the LVM2 configuration (the 'devices/filter' setting) did not work correctly when using the 'or' operator. This resulted in improper filtering of devices. With this update, the application of the regex filter works as expected. (BZ#652185)
  • Previously, the 'vgchange' command did not allow the '--addtag' and '--deltag' arguments to be used simultaneously. With this update, this restriction is removed. (BZ#652186)
  • Prior to this update, the 'fsadm' script issued an error message about not being able to resize the just unmounted file system because it required the 'force' option to be used. With this update, the 'force' option is not needed anymore and the script proceeds and successfully resizes the file system. (BZ#652638)
In addition, these updated lvm2 packages provide the following enhancement:
  • This update adds support for using multiple "--addtag" and "--deltag" arguments within a single command. (BZ#652662)
Users are advised to upgrade to these updated lvm2 packages, which resolve these issues and add this enhancement.

1.148.3. RHEA-2010:0994: enhancement update

Updated lvm2 packages that add various enhancements are now available for Red Hat Enterprise Linux 6.
The lvm2 packages contain support for Logical Volume Management (LVM).
This update adds the following enhancements:
  • Previously, the maximum length of a tag was limited to 128 characters. However, in certain cases, this may have been too restrictive. To remove this restriction, the lvm2 packages have been updated to support tags that are up to 1024 characters long. (BZ#661741)
  • Due to technical limitations, a valid tag can consist of a limited range of characters only. With this update, the list of allowed characters has been extended, and tags can newly contain "/", "=", "!", ":", "#", and "&". (BZ#661742)
Users are advised to upgrade to these updated lvm2 packages, which add these enhancements.

1.148.4. RHBA-2011:0772: bug fix and enhancement update

Updated lvm2 packages that fix several bugs and add enhancements are now available.
The lvm2 packages contain support for Logical Volume Management (LVM).
This update applies the following bug fixes:
  • Fixes a possible endless loop in cache. (BZ#683689)
  • Fixes a deadlock while removing last exclusive snapshot in cluster. (BZ#677739)
  • Fixes a boot failure on big-endian architectures. (BZ#675744)
  • Adds device-mapper library support for wiping ioctl buffers in kernel. (BZ#674823, BZ#687857)
  • Improves insufficient free space message for lvcreate. (BZ#672617)
  • Fixes the use of --addtag --deltag arguments for pvchange in cluster. (BZ#660471)
  • Adds support for multiple --addtag or multiple --deltag arguments for pvchange. (BZ#660467)
  • Adds lvm2app support for querying float attributes. (BZ#654441)
  • Fixes lvcreate to not exit incorrectly with a failure if --test option is used. (BZ#649334)
  • Fixes vgs to not limit the number of tags displayed. (BZ#648219)
  • Adds a possibility to use --addtag and --deltag arguments in one command. (BZ#647167)
  • Fixes I/O errors for merged snapshots on boot. (BZ#645488)
  • Adds a new global/metadata_read_only configuration option to disallow any operations changing metadata. (BZ#642938)
  • Fixes a possible error in processing a regular expression used in device filter. (BZ#642575)
  • Fixes incorrect detection of mounted filesystem in fsadm script. (BZ#638052, BZ#652200)
  • Adds scalability improvements. (BZ#636006)
  • Clarifies the description in lvconvert man page. (BZ#635949)
  • Adds support for /, =, !, :, #, & in tags. (BZ#634349)
  • Fixes an issue where adding VG tags left metadata corrupted. (BZ#633033)
  • Adds support for multiple --addtag and --deltag arguments within a single command. (BZ#633018)
  • Adds support for up to 1024 characters in LV tags. (BZ#633013)
  • Fixes cmirrord init script to not fail if it is already started. (BZ#632681)
  • Fixes a failure in mirror log allocation if a device failure in the log is encountered. (BZ#625192)
  • Fixes an issue that caused a mirror log to be removed while replacing the failed mirror image. (BZ#625135)
  • Fixes pvremove to not show 'No physical volume label read' message when removing PVs with no metadata copies in one pvremove command. (BZ#623218)
  • Fixes lvconvert to honour the --yes and --force options. (BZ#621281)
  • Fixes a regression where a non-root user could not view LVM2 devices. (BZ#620571)
  • Fixes a failure in rename during metadata archive and backup handling. (BZ#615907)
  • Includes hooks for querying and setting pvs, vgs and lvs report fields in lvm2app. (BZ#614049)
  • Fixes an issue where a mirror containing snapshot volumes could end up with I/O hung if there was a failed device. (BZ#613829)
  • Fixes clvmd to clean up dlm lockspace if clvmd restart is invoked. (BZ#612862)
  • Adds a possibility to use the allocate fault policy for mirrored logs. (BZ#607334)
  • Disallows adding a mirror log and removing mirror images (or vice versa) in one step while specifying PVs.(BZ#603912, BZ#602748)
  • Clarifies a message about pvmove operation if another process finishes or aborts it. (BZ#602389)
  • Improves lvscan man page to describe possible output values. (BZ#601740)
  • Disallows converting a mirrored log to core log along with image conversion while specifying PVs. (BZ#601383)
  • Fixes an issue with clustered mirrors and very slow I/O. (BZ#595507)
  • Adds support for exclusively activating snapshots of clustered logical volumes. (BZ#527186)
  • Adds new -f option to clvmd to run it in foreground. (BZ#596352)
  • Fixes clvmd init script to comply with LSB and Red Hat init script guidelines. (BZ#553381)
  • Reduces delays by avoiding scans on failed devices (devices/disable_after_error_count configuration option). (BZ#525972)
  • Adds support for snapshots of a mirror. (BZ#525957)
  • Adds support for striped mirrors. (BZ#510292)
  • Adds 'cling by tags' allocation policy. (BZ#504871)
Users are advised to upgrade to these updated lvm2 packages, which resolve these issues and add these enhancements.

1.149. m17n-contrib

1.149.1. RHBA-2011:0544: bug fix and enhancement update

An updated m17n-contrib package that includes two corrected keymap files and two improved keymap files, each back ported from upstream, is now available.
This package contains contributed internationalization files for m17n-lib.
This update includes the following fixes to keymap files:
  • Previously, when using the Devanagari script keymap -- hi-remington.mim -- the key combination to produce "आप" (the respectful form of the second person pronoun) on qwerty keyboards was "Shift-h backspace w [ backspace". The widely used sequence for this pronoun, however, is "Shift-h k w [ k" (with "k" used rather than the backspace). With this update the more common key sequence is now used by the hi-remington.mim keymap file. (BZ#653782)
  • The Malayalam script keymap -- ml-inscript.mim -- was missing the 20th letter, ച (ca). This is mapped to the semi-colon (;) on qwerty keyboards. Previously, when the Malayalam input system was active, pressing that key (either physically or using the on-screen keyboard) produced no output. The on-screen keyboard also displayed a blank keycap. This update corrects the typo in the ml-inscript.mim keymap file. When the Malayalam input method is used "ca" displays on the on-screen keyboard and appears in documents when typed, as expected. (BZ#653783)
As well, this update includes the following improvements to keymap files:
  • The Telugu script keymap -- te-inscript.mim -- now maps three further Telugu script characters to English-language keyboard keys. The specific changes are as follows: the vowel character U0c60 ("ౠ") is now mapped to the pipe symbol ("|"); the dependent vowel character U0c44 ('ౄ') is now mapped to the back slash ("\"); and the dependent vowel character U0c01 ("ఁ") is now mapped to the capital X ("X"). (BZ#642138)
  • The Tamil script keymap -- ta-tamil99.mim -- now maps seventeen further input options for generating both Tamil and English script glyphs on English-language keyboards. With the updated keymap file installed and active, the "f" key now generates a question mark ("?"). The other sixteen added options are Control+[key] inputs. They include new input options to generate several English characters such as the copyright symbol (using Control+c), the bullet character (Control+.) and single and double typographer's quote marks (using Control+7 through Control+9). As well, eight further Tamil script glyphs can now be generated, using Control+q +s +w +d +e +g +t and +r. (BZ#653781)
All users, especially those inputting Devanagari, Malayalam, Telugu or Tamil script characters, should install this update, which addresses these issues and adds these enhancements.

1.150. mailman

1.150.1. RHSA-2011:0308: Moderate security update

An updated mailman package that fixes multiple security issues is now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
Mailman is a program used to help manage email discussion lists.
Multiple input sanitization flaws were found in the way Mailman displayed usernames of subscribed users on certain pages. If a user who is subscribed to a mailing list were able to trick a victim into visiting one of those pages, they could perform a cross-site scripting (XSS) attack against the victim. (CVE-2011-0707)
Multiple input sanitization flaws were found in the way Mailman displayed mailing list information. A mailing list administrator could use this flaw to conduct a cross-site scripting (XSS) attack against victims viewing a list's "listinfo" page. (CVE-2010-3089)
Red Hat would like to thank Mark Sapiro for reporting these issues.
Users of mailman should upgrade to this updated package, which contains backported patches to correct these issues.

1.151. man-pages

1.151.1. RHBA-2011:0679: bug fix and enhancement update

An updated man-pages package that corrects several documentation errors and omissions and adds several improved man pages is now available for Red Hat Enterprise Linux 6.
The man-pages package provides man (manual) pages from the Linux Documentation Project (LDP).
This updated man-pages package addresses the following issues:
  • The sd man page had an invalid link referring to the scsi man page. With this update, all references to the scsi man page were removed from the sd man page. (BZ#634626)
  • The "getent --help" command output mentioned a "-s" switch which was not explained anywhere in the getent man page. Since the getent man page is outdated, the entire page was removed for this update. (BZ#669768)
  • The man page for clock_gettime had references to the CLOCK_REALTIME_HR and CLOCK_MONOTONIC_HR constants, that were used in clock_getres.2, clock_gettime.2, clock_nanosleep.2, clock_settime.2, and timer_create.2. These constants are no longer present in the Linux kernel and clock_gettime was corrected to remove all references to these constants. (BZ#678376)
  • A typographical error in the SHA, MD5, and DES algorithms on crypt(3) man page, meant key significance in passwords was presented incorrectly. The typo was fixed for this update. (BZ#679530)
  • Information about a new keyword -- scopev4 -- was missing from the "gai.conf" man page. As of this update, "gai.conf(5)" now documents the scopev4 keyword. (BZ#679894)
  • The example code demonstrating how to use the getifaddrs() API in the getifaddrs man page contained a bug capable of crashing getifaddrs if used. The previous example code did not check for a NULL pointer under certain conditions which would cause a segmentation fault. With this update the example code tests for this condition, as expected, thereby avoiding the segfault. (BZ#683039)
This update also adds the following enhancements:
  • The man pages for "pwrite(v)" and "pread(v)" were previously not included in the man page package. With this update, they are. (BZ#528546)
  • The "get_mempolicy" man page was updated to be more contemporaneous with the version of the Linux kernel (version 2.6.32) used by Red Hat Enterprise Linux 6.(BZ#613777)
  • The "pthread_attr_setguardsize" man page was updated to include information about glibc 2.8 changes. (BZ#634986)
All users of manual pages are advised to upgrade to this updated package, which resolves these issues.

1.152. man-pages-ja

1.152.1. RHBA-2011:0192: bug fix update

An updated man-pages-ja package that fixes three bugs is now available for Red Hat Enterprise Linux 6.
The man-pages-ja package contains Japanese translations of the Linux Documentation Project man pages.
This update fixes the following bugs:
  • Previously, the man-pages-ja package contained the outdated Japanese manual pages based on SysVinit which is not shipped in Red Hat Enterprise Linux 6. This update drops those redundant manual pages to avoid a confusion. (BZ#579647)
  • Previously, the Japanese manual page of the 'snmpd.conf' did not mention the deprecated notice for the listening port specifier in the sink directives.This update adds the deprecated notice. (BZ#600324)
  • Previously, the Japanese manual page of the 'echo' command did not mention the format of '\e' and '\xHH' in the -e option. The updated package adds the description of '\e' and '\xHH'. (BZ#618934)
  • Previously, the Japanese manual page of the 'pmap' command did not mention the "extended and device format fields". This update adds the description of it. (BZ#628891)
All man-pages-ja users are advised to upgrade to this updated package, which resolves these issues.

1.153. man-pages-overrides

1.153.1. RHBA-2011:0780: bug fix and enhancement update

An updated man-pages-overrides package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6.
A collection of manual ("man") pages to complement other packages or update those contained therein.
This updated man-pages-overrides package provides fixes for the following bugs:
  • The semanage(8) manual page has been rewritten. (BZ#540492, BZ#636785)
  • Several typographical errors have been fixed in the yum-verify(1) manual page. (BZ#604626)
  • The release tag has been fixed in the w3m(1) manual page. (BZ#615873)
  • The missing description for the auto-rename option has been added to the lftp(1) manual page. (BZ#619779)
  • The logrotate(8) manual page has been updated, fixing multiple issues such as missing options, typographical errors, an incorrect author tag, and a faulty description of the "size" parameter. (BZ#622451, BZ#638625, BZ#644308, BZ#673968)
  • The Japanese version of the man(1) manual page no longer contains a duplicate line in the specification of the "-p pager" option (BZ#632081)
  • Several syntax errors and typographical errors have been fixed in the expect(1) manual page. (BZ#633701)
  • The information on home directories in the useradd(8) manual page has been fixed. (BZ#650162)
  • The "-v" option in the parametersetfattr(1) manual page is now described more extensively to prevent possible confusion. (BZ#651120)
  • The find(1) manual page has been rewritten. (BZ#657563)
  • The setfacl(1) manual page has been update to address various issues. (BZ#658734)
  • A typographical error has been fixed in the userpasswd(1) manual page. (BZ#675213)
  • Several typographical errors have been fixed in the locate(1) manual page (BZ#675223)
  • Several typographical errors have been fixed in the pcregrep(1) manual page. (BZ#675682)
  • Several typographical errors have been fixed in the pcretest(1) manual page. (BZ#675688)
  • Several typographical errors have been fixed in the magic(5) manual page. (BZ#676540)
    In addition, this updated package provides the following enhancements:
  • The dftest(1) and randpkt(1) manual pages are now available. (BZ#613979)
  • The ospfclient(8) and watchquagga(8) manual pages are now available. (BZ#615905)
Users are advised to upgrade to this updated man-pages-overrides package, which resolves these issues and adds these enhancements.

1.154. mcelog

1.154.1. RHBA-2011:0519: bug fix update

An updated mcelog package that fixes various bugs is now available.
mcelog is a daemon that collects and decodes Machine Check Exception data on AMD64 and Intel 64 machines.
This update includes the following bug fixes:
  • The mcelog service did not check whether another instance of mcelog was running, which could result in multiple mcelog service instances on a single system. This could result in lost or over-reported Machine Check Exceptions. mcelog now detects whether another instance is already running, preventing multiple instances from being launched on a single system simultaneously. (BZ#614874)
  • When a Machine Check Error occurs, a message indicating that the issue is not a software problem is output to the console. This incorrectly implies that a hardware problem exists. The message has now been corrected to indicate that a Hardware Event has occurred, instead. (BZ#646568)
  • No configuration file was provided for mcelog, preventing users from configuring mcelog daemon and its actions. A default configuration file (/etc/mcelog/mcelog.conf), which can be used to modify the behavior of mcelog at runtime, is now provided. (BZ#647066)
  • Support for future Intel processors has been added to mcelog, enabling mcelog to decode Machine Check Exceptions for these processors when they become available. (BZ#664016)
  • The default mcelog configuration file contained references to files that did not exist in the default package installation. This caused mcelog to attempt to execute files that did not exist. The mcelog configuration file has been corrected. Note that this bug was reported and corrected during development, and was not seen in production systems in the field. (BZ#682753)
All users of mcelog are advised to upgrade to this updated mcelog package, which resolves these issues.

1.155. mdadm

1.155.1. RHBA-2011:0759: bug fix and enhancement update

An updated mdadm package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6.
mdadm is a utility for creating, managing, and monitoring Linux MD (multiple disk) devices.
This update fixes the following bugs:
  • Previously, the "noiswmd" kernel command line option did not set the rd_NO_MDIMSM variable to 1 and the udev rules thus failed to match the option. This update removes the rule for the rd_NO_MDIMSM variable and adds the "noiswmd" and "nodmraid" command line options, which substitute the rule for rd_NO_MDIMSM. (BZ#605710)
  • The md kernel module stopped responding when attempting to stop a RAID device. This occurred due to a mutex deadlock. With this update, the underlying code was changed and the issue no longer occurs. (BZ#626762)
  • Previously, mdadm did not accept the short version of the "--export" (that is "-Y") and "--name" (that is "-N") options. This was due to missing entries in the list of short options. With this update, the missing entries have been added and the short versions of the options now work as expected. (BZ#636883)
This update also adds the following enhancements:
  • Previously, mdadm was not able to rebuild newly-connected drives automatically. This update adds the array auto-rebuild feature and allows a RAID stack to automatically rebuild newly-connected drives. (BZ#633306)
  • RAID migration is now supported: mdadm is now able to change the RAID level of an already-existing device. (BZ#633667)
  • Previously, mdadm could not add a new disk to an already-existing volume. This update adds the OLCE (On Line Capacity Expansion) feature, which allows mdadm to add new disks to an array and allocate their resources to existing volumes. (BZ#633671)
  • Previously, mdadm did not track the progress of the rebuild and level-migration operations and therefore was not able to recover their progress after a system failure. This update adds the check-pointing feature, which tracks their progress and allows mdadm to resume these operations after a system failure from the last check point. (BZ#633688)
  • This update adds SAS-SATA feature, which allows the user to disconnect a set of SATA (Serial Advanced Technology Attachment) drives from a SCSI Controller Unit (SCU) and connect it to an Advanced Host Controller Interface (AHCI) and vice versa. (BZ#633690)
  • This update limits the RAID-5 support for volumes on drives attached to the SCU on systems with the X79 chipset (code-named "Patsburg"). It inhibits the creation, assembly, activation, and level migration of RAID 5 volumes on drives attached to the SCU on these systems. (BZ#633692)
Users are advised to upgrade to this updated mdadm package, which resolves these issues and adds these enhancements.

1.156. memtest86+

1.156.1. RHBA-2011:0683: bug fix and enhancement update

An updated memtest86+ package that fixes one bug and adds an enhancement is now available for Red Hat Enterprise Linux 6.
The memtest86+ package contains an advanced memory diagnostic tool for x86, AMD64 and Intel 64 computers. BIOS-based memory tests are only a quick check and often miss many of the failures that are detected by memtest86+.
This update fixes the following bug:
  • The memtest86+ tool failed to start on AMD64 and Intel 64 computers with the "--type=netbsd /elf-memtest86+-4.00" kernel parameter, and the "Error 13: Invalid or unsupported executable format" error message was given. This option now works as expected, and no error message is displayed. (BZ#607006)
This update adds the following enhancement:
  • With this update, memtest86+ supports the latest Intel processors, including those based on the Intel Xeon Processor E56XX, L56XX, W36XX and X56XX families, and the Intel Xeon Processor E7 family. (BZ#640731)
Users of memtest86+ are advised to upgrade to this updated package, which fixes this bug and adds this enhancement.

1.157. mesa

1.157.1. RHEA-2011:0628: enhancement update

Updated mesa packages that add one enhancement are now available for Red Hat Enterprise Linux 6.
Mesa provides a 3D graphics application programming interface (API) that is compatible with OpenGL (Open Graphics Library). It also provides hardware-accelerated drivers for many popular graphics chips.
This update adds the following enhancement:
  • This update adds accelerated 3D support for systems based on the 2nd Generation Intel Core Processor Family to the mesa packages and provides updated drivers for all other supported 3D hardware. (BZ#667563)
All Mesa users are advised to update to these upgraded packages, which add this enhancement.

1.158. microcode_ctl

1.158.1. RHEA-2011:0712: enhancement update

An updated microcode_ctl package that provides several enhancements is now available for Red Hat Enterprise Linux 6.
The microcode_ctl package provides microcode updates for Intel processors.
This updated microcode_ctl package adds the following enhancements:
  • The Intel CPU microcode file is updated to version 20101123. This is the most recent version of the microcode available from Intel. (BZ#638286)
  • microcode_ctl is now udev-driven and the previously delivered init.d script is no longer needed. (BZ#578107)
Note that the system must be rebooted in order for these changes to take effect.
All users of Intel processors are advised to upgrade to this updated package, which adds these enhancements.

1.159. mipv6-daemon

1.159.1. RHBA-2011:0741: bug fix and enhancement update

An updated mipv6-daemon package that fixes several bugs and adds various enhancements is now available.
The mipv6-daemon package contains a mobile IPv6 service for clients, which allows them to relocate within an IPv6-enabled network yet remain reachable
The mipv6-daemon package has been upgraded to upstream version 2.0.2.20110203b, which provides numerous bug fixes and enhancements over the previous version. (BZ#612007)
Users are advised to upgrade to this updated mipv6-daemon package, which resolves these issues and adds these enhancements.

1.160. mksh

1.160.1. RHBA-2011:0580: bug fix and enhancement update

An updated mksh package that fixes three bugs and adds one enhancement is now available for Red Hat Enterprise Linux 6.
The mksh package provides the MirBSD version of the Korn Shell which implements the ksh-88 programming language for both interactive and shell script use.
This update fixes the following bugs:
  • Previously, mksh did not handle trace output correctly. Due to this problem, mksh aborted unexpectedly when the tracing was enabled and a long string was to be reported, This update improves the long trace output handling. Now, long trace output is successfully printed without interruption. (BZ#616771)
  • Previously, mksh did not handle aliases that contained aliases correctly. Due to this problem, mksh aborted when double aliases were used. This update corrects the alias handling code. Double aliases are handled as expected. (BZ#616777)
  • Previously, bad substitution could abort mksh unexpectedly because of a conflict between acceptable code for ksh-88 and ksh-93. This update recognizes both code types and prints errors as expected. (BZ#618274)
This update also adds the following enhancement:
  • Previously, users had to change the shebang in their ksh-88 scripts or port their scripts to ksh-93. This update adds the "alternatives" switching method that allows to switch between ksh-93 provided by the ksh package and ksh-88 provided by the mksh package for /bin/ksh. Now, users can apply their scripts without modification or porting them to ksh-93 one by one. (BZ#659668)
All users of mksh are advised to upgrade to this updated package, which fixes these bugs and adds this enhancement.

1.161. mod_auth_mysql

1.161.1. RHSA-2010:1002: Moderate security update

An updated mod_auth_mysql package that fixes one security issue is now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The mod_auth_mysql package includes an extension module for the Apache HTTP Server, which can be used to implement web user authentication against a MySQL database.
A flaw was found in the way mod_auth_mysql escaped certain multibyte-encoded strings. If mod_auth_mysql was configured to use a multibyte character set that allowed a backslash ("\") as part of the character encodings, a remote attacker could inject arbitrary SQL commands into a login request. (CVE-2008-2384)
Note: This flaw only affected non-default installations where AuthMySQLCharacterSet is configured to use one of the affected multibyte character sets. Installations that did not use the AuthMySQLCharacterSet configuration option were not vulnerable to this flaw.
All mod_auth_mysql users are advised to upgrade to this updated package, which contains a backported patch to correct this issue. After installing the updated package, the httpd daemon must be restarted for the update to take effect.

1.162. mod_nss

1.162.1. RHBA-2011:0735: bug fix update

An updated mod_nss package that fixes various bugs is now available for Red Hat Enterprise Linux 6.
The mod_nss module provides strong cryptography for the Apache HTTP Server via the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, using the Network Security Services (NSS) security library.
This update fixes the following bugs:
  • During the Apache HTTP Server startup, a race condition could prevent one or more child processes from receiving the token PIN, rendering such processes unable to use SSL. With this update, the race condition no longer occurs, and all child processes of the Apache HTTP Server can enable SSL as expected. (BZ#677700)
  • Due to an incorrect use of the memcpy() function in the mod_nss module, running the Apache HTTP Server with this module enabled could cause some requests to fail with the following message written to the error_log file:
    request failed: error reading the headers
    This update applies a patch to ensure that the memcpy() function is now used in accordance with the current specification, and using the mod_nss module no longer causes HTTP requests to fail. (BZ#682326)
  • Under certain circumstances, a large "POST" request could cause the mod_nss module to enter an infinite loop. With this update, the underlying source code has been adapted to address this issue, and mod_nss now works as expected. (BZ#634687)
  • The mod_nss module is shipped with the gencert utility that generates the default NSS database. Prior to this update, this utility was installed without any documentation on its usage. This error has been fixed, and a manual page for gencert is now included as expected. (BZ#605376)
All users of mod_nss are advised to upgrade to this updated package, which fixes these bugs.

1.163. mysql

1.163.1. RHSA-2011:0164: Moderate security update

Updated mysql packages that fix multiple security issues are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
MySQL is a multi-user, multi-threaded SQL database server. It consists of the MySQL server daemon (mysqld) and many client programs and libraries.
The MySQL PolyFromWKB() function did not sanity check Well-Known Binary (WKB) data, which could allow a remote, authenticated attacker to crash mysqld. (CVE-2010-3840)
A flaw in the way MySQL processed certain JOIN queries could allow a remote, authenticated attacker to cause excessive CPU use (up to 100%), if a stored procedure contained JOIN queries, and that procedure was executed twice in sequence. (CVE-2010-3839)
A flaw in the way MySQL processed queries that provide a mixture of numeric and longblob data types to the LEAST or GREATEST function, could allow a remote, authenticated attacker to crash mysqld. (CVE-2010-3838)
A flaw in the way MySQL processed PREPARE statements containing both GROUP_CONCAT and the WITH ROLLUP modifier could allow a remote, authenticated attacker to crash mysqld. (CVE-2010-3837)
MySQL did not properly pre-evaluate LIKE arguments in view prepare mode, possibly allowing a remote, authenticated attacker to crash mysqld. (CVE-2010-3836)
A flaw in the way MySQL processed statements that assign a value to a user-defined variable and that also contain a logical value evaluation could allow a remote, authenticated attacker to crash mysqld. (CVE-2010-3835)
A flaw in the way MySQL evaluated the arguments of extreme-value functions, such as LEAST and GREATEST, could allow a remote, authenticated attacker to crash mysqld. (CVE-2010-3833)
A flaw in the way MySQL handled LOAD DATA INFILE requests allowed MySQL to send OK packets even when there were errors. (CVE-2010-3683)
A flaw in the way MySQL processed EXPLAIN statements for some complex SELECT queries could allow a remote, authenticated attacker to crash mysqld. (CVE-2010-3682)
A flaw in the way MySQL processed certain alternating READ requests provided by HANDLER statements could allow a remote, authenticated attacker to crash mysqld. (CVE-2010-3681)
A flaw in the way MySQL processed CREATE TEMPORARY TABLE statements that define NULL columns when using the InnoDB storage engine, could allow a remote, authenticated attacker to crash mysqld. (CVE-2010-3680)
A flaw in the way MySQL processed certain values provided to the BINLOG statement caused MySQL to read unassigned memory. A remote, authenticated attacker could possibly use this flaw to crash mysqld. (CVE-2010-3679)
A flaw in the way MySQL processed SQL queries containing IN or CASE statements, when a NULL argument was provided as one of the arguments to the query, could allow a remote, authenticated attacker to crash mysqld. (CVE-2010-3678)
A flaw in the way MySQL processed JOIN queries that attempt to retrieve data from a unique SET column could allow a remote, authenticated attacker to crash mysqld. (CVE-2010-3677)
Note: CVE-2010-3840, CVE-2010-3838, CVE-2010-3837, CVE-2010-3835, CVE-2010-3833, CVE-2010-3682, CVE-2010-3681, CVE-2010-3680, CVE-2010-3678, and CVE-2010-3677 only cause a temporary denial of service, as mysqld was automatically restarted after each crash.
These updated packages upgrade MySQL to version 5.1.52. Refer to the MySQL release notes for a full list of changes:
http://dev.mysql.com/doc/refman/5.1/en/news-5-1-52.html
All MySQL users should upgrade to these updated packages, which correct these issues. After installing this update, the MySQL server daemon (mysqld) will be restarted automatically.

1.164. net-snmp

1.164.1. RHBA-2010:0901: bug fix update

Updated net-snmp packages that resolve several issues are now available for Red Hat Enterprise Linux 6.
The net-snmp packages provide various libraries and tools for the Simple Network Management Protocol (SNMP), including an SNMP library, an extensible agent, tools for requesting or setting information from SNMP agents, tools for generating and handling SNMP traps, a version of the netstat command which uses SNMP, and a Tk/Perl MIB browser.
These updated net-snmp packages provide fixes for the following bugs:
  • The SNMP daemon, snmpd, returned the incorrect value of either "0.1" or 1.3" for sysObjectID. This update fixes the value of this OID so that the correct value, which is "1.3.6.1.4.1.8072.3.2.10", is now returned. (BZ#652223)
  • Under certain conditions, and especially on networks with high traffic, snmpd wrote a lot of "c64 32 bit check failed" and "netsnmp_assert 1 == new_val->high failed" messages to the system log. Although these messages are harmless and not indicative of a serious error, they could potentially fill the system log quickly. This update suppresses these spurious messages in favor of more meaningful and specific error messages, which are written to the system log only once. (BZ#652551)
All users of net-snmp are advised to upgrade to these updated packages, which resolve these issues.

1.164.2. RHBA-2011:0729: bug fix update

Updated net-snmp packages that resolve several issues are now available for Red Hat Enterprise Linux 6.
SNMP (Simple Network Management Protocol) is a protocol used for network management. The NET-SNMP project includes various SNMP tools: an extensible agent, an SNMP library, tools for requesting or setting information from SNMP agents, tools for generating and handling SNMP traps and a version of the netstat command which uses SNMP. This package contains the snmpd and snmptrapd daemons, documentation, etc.
These updated net-snmp packages provide fixes for the following bugs:
  • The IP-MIB::ipAddressTable did not support SNMP SET operation, which enables adding or deleting rows in the IP address table. As a result IPv4 or IPv6 addresses on interfaces could neither be created or removed. The updated packages enhance IP-MIB::ipAddressTable with these functions as per RFC 4293 mandates. (BZ#616336, BZ#616764).
  • Under certain conditions, and especially on networks with high traffic, snmpd wrote a lot of "c64 32 bit check failed" and "netsnmp_assert 1 == new_val->high failed" messages to the system log. Although these messages are harmless and not indicative of a serious error, they could potentially fill the system log quickly. This update suppresses these spurious messages in favour of more meaningful and specific error messages, which are written to the system log only once. (BZ#621664).
  • The SNMP daemon did not properly handle netlink sockets when forking to background and becoming a daemon. It could therefore not process incoming notifications from kernel regarding changes in IP-MIB::ipAddressPrefixTable. The updated package fixes the socket processing to ensure SNMP deamon handles incoming kernel notifications and updates ipAddressPrefixTable in runtime. (BZ#625262).
  • The SNMP daemon did not detect and notify newly added or activated interfaces in IPV6-MIB::627564ipv6IfTable. The updated package properly refreshes the table when new interface appears. (BZ#627564).
  • The implementation of BRIDGE-MIB was enhanced with Virtual LANs (RFC 4363). (BZ#630157).
  • The snmpwalk utility did not perform correct OID comparison and printed additional objects when walking through an OID subtree. The updated package fixed the OID comparison so that snmpwalk prints only the objects from requested subtree. (BZ#636890).
  • The SNMP daemon 'snmpd', returned incorrect value of either "0.1" or 1.3" for sysObjectID. This update fixes the value of this OID so it returns the correct value, "1.3.6.1.4.1.8072.3.2.10".(BZ#641113)
  • The Net-SNMP source RPM package failed to compile on machine incase of a disabled IPv6 networking stack since the built-in test suite requires a working IPv6. The updated package correctly recovers from a disabled IPv6 stack and compiles successfully. (BZ#657835).
  • The problem was that in some cases SNMP daemon 'snmpd', wrongly retyped pointers to integer data when processing SMUX packets resulting in a freeze. The pointer operations were fixed in the updated package to avoid snmpd freeze while processing SMUX packets. (BZ#665053).
  • The snmpd daemon handled incorrectly internal list of SMUX registrations, which could result in snmpd crash when processing SMUX messages. The updated package fixes the list handling and does not crash when processing SMUX messages. (BZ#672595).
  • The snmpd daemon did not properly initialize it's structures for IP-MIB::ipSystemStatsTable and IP-MIB::ipIfStatsTable properly. It returned this error message "looks like a 64bit wrap, but prev!=new" to log if a counter in these tables got larger than 32bits. The updated packages fixes initialization of the tables and ensures that the aforementioned message should not appear in snmpd log. (BZ#674757).
All users of net-snmp are advised to upgrade to these updated packages, which resolve these issues.

1.165. net-tools

1.165.1. RHBA-2011:0690: bug fix update

An updated net-tools package that fixes various bugs is now available for Red Hat Enterprise Linux 6.
The net-tools package contains basic networking tools, including ifconfig, netstat, route, and others. Netstat prints information about the Linux networking subsystem.
This update fixes the following bugs:
  • Unless a device name was specified on the command line, the mii-tool utility automatically checked Ethernet interfaces from eth0 to eth7. Similarly, running the mii-diag or ether-wake utility without the device name caused it to use eth0 by default. However, Red Hat Enterprise Linux 6.1 introduces the possibility to use arbitrary names for these network interfaces. Because of this, the mii-tool, mii-diag, and ether-wake utilities have been adapted to require a device name to be specified on the command line. (BZ#682368)
  • Due to an incorrect use of 32-bit integers, running the netstat utility with the "-s" (or "--statistics") command line option on a 64-bit architecture could cause some entries in the "IpExt" section to be displayed with negative values. With this update, integers on 64-bit architectures are now handled properly, and the "netstat -s" command now produces the correct output. (BZ#580054)
  • When the netstat utility is run with the "-c" (or "--continuous") command line option, it prints the selected information continuously every second. Previously, netstat failed to free the allocated memory. Consequent to this, running the utility for a long time could cause it to consume all available memory. With this update, the underlying source code has been corrected to free the allocated memory when appropriate, and running the netstat utility with the "-c" option no longer leads to a memory leak. (BZ#634539)
  • Prior to this update, the manual page for the netstat utility stated that running the utility with the "-a" (or "--all") command line option allows a user to list both listening and non-listening sockets. Since this description was rather vague, this update extends the manual page to provide a clear explanation of which sockets are classified as non-listening. (BZ#614931)
All users of net-tools are advised to upgrade to this updated package, which fixes these bugs.

1.166. netcf

1.166.1. RHBA-2011:0620: bugfix update

An updated netcf package that fixes various bugs is now available.
Netcf is a library for modifying the network configuration of a system. Network configurations are expressed in a platform-independent XML format, which netcf translates into changes to the system's 'native' network configuration files.
This update rebases netcf from version 0.1.6 to the current upstream version, 0.1.7. (BZ#651032)
This rebase addresses several issues, including:
  • Tight coupling between netcf and gnulib
  • Disallowing firewall rules editing
  • An iptables rule tweak regarding tuneable kernel necessity
This re-base also incorporates fixes for two bugs as follows:
  • Previously, after a reboot, virInterface functions did not work until libvirt was restarted and instead failed with a "error: Failed to list active interfaces. error: this function is not supported by the connection driver: virConnectNumOfInterfaces" error message. This is now fixed so that the code that caused the problem is removed and virInterface functions operate as expected after a reboot. (BZ#633346)
  • Previously, netcf was unable to initialize due to the system's iptables configuration and failed with a "Failed to initialize netcf. error: unspecified error" error message. This is now fixed and netcf no longer fails during initialization. (BZ#629206)
Users are advised to upgrade to this updated package, which resolves these issues.

1.167. netlabel_tools

1.167.1. RHBA-2011:0191: bug fix update

An updated netlabel_tools package that fixes a bug is now available for Red Hat Enterprise Linux 6.
NetLabel is a kernel subsystem which implements explicit packet labeling protocols such as CIPSO and RIPSO for Linux. Packet labeling is used in secure networks to mark packets with the security attributes of the data they contain. This package provides the necessary user space tools to query and configure the kernel subsystem.
This update fixes the following bug:
  • Previously, running the netlabelctl utility with an invalid mask argument caused the utility to terminate with a 0 exit status. This error has been fixed, and when an invalid mask is supplied, netlabelctl now returns a non-zero exit status as expected. (BZ#602291)
All users of netlabel_tools are advised to upgrade to this updated package, which resolves this issue.

1.168. NetworkManager

1.168.1. RHBA-2010:0836: bug fix and enhancement update

Updated NetworkManager packages that fix a bug and add various enhancements are now available for Red Hat Enterprise Linux 6.
NetworkManager is a system network service that manages network devices and connections, attempting to keep active network connectivity when available. It manages Ethernet, wireless, mobile broadband (WWAN), and PPPoE devices, and provides VPN integration with a variety of different VPN services.
This update fixes the following bug:
  • Under certain circumstances, the "Enable Networking" and "Enable Wireless" menu items in the panel applet may have been insensitive. This error no longer occurs, and both options are now available as expected. (BZ#638598)
Also, this update adds the following enhancements:
  • In enterprise wireless networks, the proactive key caching can now be used along with the PEAP-GTC authentication mechanism.
  • Punjabi translation of the network applet has been updated.
Users are advised to upgrade to these updated packages, which resolve this issue, and add these enhancements.

1.168.2. RHBA-2011:0769: bug fix and enhancement update

Updated NetworkManager packages that fix a number of bugs and add some enhancements are now available.
NetworkManager is a system network service that manages network devices and connections, attempting to keep active network connectivity when available. It manages Ethernet, wireless, mobile broadband (WWAN), and PPPoE devices, and provides VPN integration with a variety of different VPN services.
This update fixes the following issues:
  • After Wireless was disabled in NetworkManager, a suspend and resume operation caused the wireless connection to become enabled automatically. This is now fixed to preserve the user set wireless state even after an rfkill operation (suspend and resume). (BZ#584271)
  • Translations had assorted inconsistencies, including invalid characters as part of the network-manager-applet (languages: as, te, pa, gu, mr, fr, es, bn_IN) and NetworkManager (languages: bn_IN, es, fr, ja, mr). These are now fixed to display the correct translated strings. (BZ#589230)
  • Due to a type truncation problem on 64-bit PPC systems, correctly configured connections was not displayed in connection editor. This is now fixed and connections are properly shown in the editor on all platforms as expected. (BZ#608663)
  • Unprivileged users could change the status of the wireless connection and WWAN. This is now fixed to display a "not authorized" error for any unauthorized users attempting to change the wireless status. (BZ#626337)
  • NetworkManager would insert warning messages in the /var/log/messages log file due to the hostname operation. This is now fixed to ensure no unnecessary warnings display during the hostname operation. (BZ#627649)
  • Occasionally, the NetworkManager panel applet would not be able to determine user permissions to enable networking and therefore disabled the "Enable Networking" and "Enable Wireless" check boxes. This is now fixed to ensure that if the user has permissions to enable networking, the check boxes display as expected. (BZ#633501)
  • Roaming between WPA/WPA2 access points in the same SSID attached to the same wireless LAN controller resulted in an unexpected re-authentication requirement. This is now fixed so that the SSID is preserved to be used again after a legitimate roaming disconnection event. (BZ#636877)
  • Configurations that used multiple network devices where one device was an iSCSI adapter that should not have the default route were incorrectly handled. This is now fixed to ensure that iSCSI devices that are denied the default route do not receive it. (BZ#665027)
  • IPv6 static addressing configurations were unable to correctly save the gateway address. This is now fixed to ensure that the gateway address now saves the first configured IPv6 address. (BZ#666078)
  • NetworkManager used to update /etc/hosts file, which could cause problems in some configurations. This is now fixed and NetworkManager does not modify /etc/hosts, leaving it for the administrator to set up. (BZ#668830)
  • NetworkManager saved the WPA/WPA2 password despite selecting the "Ask for this password every time" option and presented a password field with some text when prompting the user to enter a new WPA/WPA2 connection password. This is fixed so that NetworkManager does not store passwords when "Ask for this password every time" is selected and displays an empty password field when prompting the user for the password. (BZ#692578)
This update adds also the following enhancements:
  • IPv6 information such as the IP Address and DNS servers now displays in the connection information. (BZ#634152)
  • DHCP lease change events now trigger dispatcher scripts at the /etc/NetworkManager/dispatcher.d location. (BZ#662730)
Users are advised to upgrade to these updated packages, which resolve these issues and add these enhancements.

1.169. NetworkManager-openswan

1.169.1. RHBA-2011:0746: bug fix update

An updated NetworkManager-openswan package that fixes a bug is now available for Red Hat Enterprise Linux 6.
NetworkManager-openswan contains software for integrating the Openswan VPN software with NetworkManager and the GNOME desktop.
This update fixes the following bug:
  • Previously, it took as much as 45 seconds for NetworkManager-openswan to time out when an incorrect password or incorrect group secret was given. With this update, a fix has been provided and NetworkManager-openswan now fails immediately upon bad credentials. (BZ#659709)
Users of NetworkManager-openswan are advised to upgrade to this updated package, which fixes this bug.

1.170. nfs-utils

1.170.1. RHBA-2011:0738: bug fix and enhancement update

An updated nfs-utils package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6.
The nfs-utils package provides a daemon for the kernel Network File System (NFS) server, and related tools such as the mount.nfs, umount.nfs, and showmount programs.
This updated nfs-utils package provides fixes for the following bugs:
  • The "nfsstat --nfs" command did not return any results for NFS version 4 clients because the has_stats() function did not support statistics for the NFS version 4 clients. This update adapts the underlying code and the command returns the values as expected. (BZ#625080)
  • Previously, running the rpc.nfsd program as the root user caused a kernel panic due to a NULL pointer dereference in the nfsd_svc() function. This update applies a number of fixes to the nfsd daemon, which fixes the bug. (BZ#628996)
  • Previously, mounting NFS over RDMA (remote direct memory access) failed due to missing code for such mounting in the NFS initialization script and the sysconfig file. This update adds the missing code and mounting of NFS over RDMA works correctly. (BZ#631012)
  • On shutdown, nfs-utils failed to unmount the /var/ file system correctly because the name of the subsystem lock file did not match the name of the lock file nfs-utils was searching for. This update changes the name of the lock file so that the shutdown script locates the file and unmounts the file system successfully. (BZ#636513)
  • Previously, servers configured to use only the NFS version 4 (NFSv4) services could have failed to start. This occurred because the /etc/sysconf/nfs configuration file defined the MOUNTD_NFS_V1 option, which is no longer supported. This update removes the variable from the configuration file and servers using NFSv4 start as expected. (BZ#641291)
  • Previously, the %pre scriptlet called the "groupadd" command with an invalid command line argument during package installation. With this update, the command uses the correct argument. (BZ#663153)
  • Previously, an incorrect principal in the NFS client request could have caused the rpc.svcgssd daemon to terminate unexpectedly with a segmentation fault. This was caused by an error in the underlying code. This update adapts the code and rpc.svcgssd no longer crashes. (BZ#698220)
In addition, this updated package provides the following enhancements:
  • This update adds IPv6 (Internet Protocol version 6) support for the server. (BZ#637198)
  • Prior to this update, nfs-utils tried to construct the principal name for the local host and attempted to match it against entries in the keytab file to acquire a Ticket Granting Ticket (TGT). With this update, nfs-utils opens the file and picks the appropriate name from the list of principals so that the NFS client machine is able to authenticate even after its host name is changed. (BZ#671474)
Users are advised to upgrade to this updated nfs-utils package, which resolves these issues and adds these enhancements.

1.171. nfs-utils-lib

1.171.1. RHBA-2011:0732: bug fix update

Updated nfs-utils-lib packages that fix several bugs are now available.
The nfs-utils-lib package contains support libraries required by programs in the nfs-utils package.
These updated packages provide fixes for the following bugs:
  • A number of warnings from librpcsecgss and libnfsidmap were printed unnecessarily while attempting to build nfs-utils-lib. These superfluous warnings have been removed. (BZ#650970)
  • Default values for nfs-utils-lib were not set correctly in the /etc/idconf.conf file. This resulted in default values not being correct on Red Hat Enterprise Linux 6. The configuration has been corrected and now provides sensible defaults. (BZ#650997)
Users are advised to upgrade to these updated packages, which resolve this issue.

1.172. nspr, nss, nss-softokn, and nss-util

1.172.1. RHBA-2011:0692: bug fix and enhancement update

Updated nspr and nss related packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6.
Netscape Portable Runtime (NSPR) provides platform independence for non-GUI operating system facilities. These facilities include threads, thread synchronization, normal file and network I/O, interval timing, calendar time, basic memory management (malloc and free), and shared library linking.
Network Security Services (NSS) is a set of libraries designed to support the cross-platform development of security-enabled client and server applications. Applications built with NSS can support SSLv2, SSLv3, TLS, and other security standards.
The nss, nss-softokn, and nss-utilpackage packages have been upgraded to upstream version 3.12.9, which provides a number of bug fixes and enhancements over the previous version. (BZ#668055)
Bug fixes:
BZ#555825
Prior to this update, the softokn PKCS#11 module interface used a wrong object type which caused it to return an object with an invalid CKA_CERTIFICATE_TYPE attribute. With this update, the softokn PKCS#11 module interface uses the correct object type.
BZ#589636
Rebuilding the nss package when IPv6 is enabled caused it to enter a loop in the test part of the rebuild. With this update, the selfserv test tool has been modified to use a dual-stack IPv6 listening socket, which can accept connections from both IPv4 and IPv6 clients.
BZ#602629
The help page displayed after issuing the certutil -H command was missing the -W option (which changes the password to a key database). With this update, the -W option has been added to the help page.
BZ#630101
Importing a private key (using the pk12util command) did not work for private keys placed in the /etc/pki/nssdb/ directory due to permission restrictions. This update addresses this issue, and the nss-sysinit module now enables the root user to import private key.
BZ#630103
Due to a bug in the nss-sysinit package, visiting a specific website in the Mozilla Firefox web browser caused that website to return an This Connection is Untrusted. error even though the web page had a valid security certificate. With this update, this issue has been fixed and visiting the specific web site no longer returns SSL errors.
BZ#631000
Prior to this update, PKCS#8 encoded PEM (Privacy Enhanced Mail) RSA private key files could not be read by nss and resulted in an error when being imported. With this update, nss correctly handles the aforementioned files.
BZ#631586
This update fixes an unclosed comment in the source code which occurred after the said comment was reduced to a one line comment by a previously applied patch.
BZ#637948
Support for Intel Advanced Encryption Standard Instructions (AES-NI) in the nss package has been enabled and works as expected.
BZ#642767
This update fixes possible memory leaks in the SECKEY_DestroyPublicKey(SECKEY_ImportDERPublicKey(…)) function.
BZ#643134
Under certain circumstances, after removing a Certificate Authority (CA) from the trust database, nss continues to consider the removed CA as trusted. This was due to improper handling of trust flags when removing a CA from the trust database. With this update, trust flags from the user database take precedence over the trust flags inherited from the system database, fixing this issue.
BZ#643553
Prior to this update, when the setup-nsssysinit.sh script rewrote/recreated the pkcs11.txt file, it took the current umask (user mask) into an account. However, if run with restrictive umask settings, the pkcs11.txt file could be created with permissions that did not allow non-privileged users to read it. This could cause nss-sysinit to remain disabled even when it was intended to be enabled. With this update, the permissions of the pkcs11.txt file are changed at the end of the run of the setup-nsssysinit.sh script, fixing this issue.
BZ#647834
The %verify(not md5 size mtime) declarations have been added to the configuration files.
BZ#643554
The nss-sysinit application is no longer disabled after the package is upgraded.
BZ#643564
Issuing an OpenLDAP command and using the LDAPTLS_CACERTDIR variable to pass in an arbitrary directory containing other directories caused the command to abort because OpenLDAP tried to pass down the directory as a file. With this update, specified files that are directories are properly rejected in the aforementioned case.
BZ#656697
The PayPalEE.cert certificate expired on Oct 31, 2010, which caused the nss package to fail to build. This update prolongs this expiration date of this certificate, and the nss package no longer fails to build.
BZ#676387
Various headers have been added to the nss-softokn-freebl-devel subpackage.
BZ#694663
Updating the nss package but not the curl package on systems configured with both Satellite and non-Satellite repositories resulted in a segmentation fault in Yum. With this update, the segmentation fault no longer occurs in the aforementioned case.
Enhancements:
BZ#642342
The nss package has been updated for the 3.6.11 version of Mozilla Firefox.
BZ#643556
This update introduces nss-sysinit status reporting.
BZ#689031
This update enables nss to use PEM files interchangeably in a single process.
All users of nspr, nss, nss-softokn, and nss-util are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

1.173. nss

1.173.1. RHSA-2011:0472: Important security update

Updated nss packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6.
The Red Hat Security Response Team has rated this update as having important security impact.
Network Security Services (NSS) is a set of libraries designed to support the development of security-enabled client and server applications.
This erratum blacklists a small number of HTTPS certificates by adding them, flagged as untrusted, to the NSS Builtin Object Token (the libnssckbi.so library) certificate store. (BZ#689430)
Note: This fix only applies to applications using the NSS Builtin Object Token. It does not blacklist the certificates for applications that use the NSS library, but do not use the NSS Builtin Object Token (such as curl).
All NSS users should upgrade to these updated packages, which correct this issue. After installing the update, applications using NSS must be restarted for the changes to take effect.

1.173.2. RHSA-2010:0862: Low security update

Updated nss packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having low security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
Network Security Services (NSS) is a set of libraries designed to support the development of security-enabled client and server applications.
A flaw was found in the way NSS matched SSL certificates when the certificates had a Common Name containing a wildcard and a partial IP address. NSS incorrectly accepted connections to IP addresses that fell within the SSL certificate's wildcard range as valid SSL connections, possibly allowing an attacker to conduct a man-in-the-middle attack. (CVE-2010-3170)
All NSS users should upgrade to these updated packages, which provide NSS version 3.12.8 to resolve this issue. After installing the update, applications using NSS must be restarted for the changes to take effect.

1.174. nss-pam-ldapd

1.174.1. RHBA-2011:0796: bug fix update

An updated nss-pam-ldapd package is now available for Red Hat Enterprise Linux 6.
The nss-pam-ldapd provides the nss-pam-ldapd daemon (nslcd) which uses a directory server to look up name service information on behalf of a lightweight nsswitch module.
This updated nss-pam-ldapd package includes fixes for the following bugs:
  • Prior to this update, nslcd did not allow parentheses to be used in a valid name. With this update, the implementation of the "validusers" configuration option has been added and the use of opening and closing parentheses in usernames and groupnames is now allowed. (BZ#690870)
  • Verifying the nss-pam-ldapd package (by executing the "rpm --verify nss-pam-ldapd" command) failed in the /etc/nslcd.conf file due to changes in that configuration file performed after the installation of the package. With this update, post-installation changes in the /etc/nslcd.conf file no longer affect the verification of the nss-pam-ldapd package. (BZ#692225)
  • The nslcd man page syntax contained an error which caused the man page to return the following error message on the standard error output:
    Error parsing *roff command from file /usr/share/man/man8/nslcd.8.gz
    This update fixes the syntax error and the "man nslcd" command no longer returns an error message. (BZ#692496)
  • When nslcd was configured to use multiple LDAP servers, it failed to fall back to a different server in case the primary server could not be reached. This was due to nslcd trying to keep the first connection alive even when the connection was dropped. With this update, nslcd correctly falls back to a different server after loosing connection with the current one. (BZ#692817)
All users of nss-pam-ldapd are advised to upgrade to this updated package, which resolves these issues.

1.175. oddjob

1.175.1. RHBA-2011:0339: bug fix update

Updated oddjob packages that fix multiple bugs are now available for Red Hat Enterprise Linux 6.
The oddjobd service runs specified privileged tasks for unprivileged client applications which communicate with it through the system message bus.
This update fixes the following bugs:
  • Previously, the oddjobd service failed to reconnect to the system message bus after it lost its connection due to an internal function call. With this update, the oddjobd service is now able to reconnect to the message bus successfully after it loses a connection. (BZ#634356)
  • If a umask is not specified in the oddjobd service's configuration file, the service now uses the UMASK setting, if present, to calculate the permissions which should be set on a user's home directory. (BZ#678345)
  • The oddjobd service did not ensure, when creating a user's home directory, that any intermediate directories that were created would have correct permissions. This could have caused users to be unable to access their home directory. With this update, oddjobd ensures that correct permissions are set for any intervening directories such that the user is able to access their home directory. (BZ#664418)
  • The oddjobd init script exited with a exit status of "1" when it was passed a non-existent action. Service init scripts should exit with an exit code of "2" when they are asked to perform an unknown action. The oddjobd init script has been corrected, and now conforms with init script guidelines. (BZ#674534)
  • The oddjobd service failed to register the name of the mkhomedir service because the message bus was not signaled to re-read its configuration files when the oddjob-mkhomedir package was installed. With this update, oddjobd is now able to register the mkhomedir service name successfully. (BZ#659681)
All oddjobd service users are advised to upgrade to these updated packages which fix these bugs.

1.176. openais

1.176.1. RHBA-2011:0740: bug fix update

Updated openais packages that fix one bug are now available for Red Hat Enterprise Linux 6.
The Application Interface Specification (AIS) is an API and a set of policies for developing applications that maintain services during faults. The OpenAIS Standards Based Cluster Framework is an OSI-certified implementation of the Service Availability Forum AIS. The openais packages contain the OpenAIS service handlers and default configuration files.
This update fixes the following bug:
  • Previous versions of the openais packages included the /etc/rc.d/init.d/openais init script with the stop priority set to "20". Consequent to this, shutting down a system caused this init script to stop the openais service in a wrong order. Since this init script is not needed, this update removes /etc/rc.d/init.d/openais from the packages, and the openais service is now stopped when expected. (BZ#630110)
All users of openais are advised to upgrade to these updated packages, which fix this bug.

1.177. opencryptoki

1.177.1. RHBA-2011:0661: bug fix and enhancement update

Updated opencryptoki packages that fix several bugs and add various enhancements are now available for Red Hat Linux 6.
The openCryptoki package contains version 2.11 of the PKCS#11 API, implemented for IBM Cryptocards. This package includes support for the IBM 4758 Cryptographic CoProcessor (with the PKCS#11 firmware loaded), the IBM eServer Cryptographic Accelerator (FC 4960 on IBM eServer System p), the IBM Crypto Express2 (FC 0863 or FC 0870 on IBM System z), and the IBM CP Assist for Cryptographic Function (FC 3863 on IBM System z).
The openCryptoki package has been upgraded to upstream version 2.3.3, which provides a number of bug fixes and enhancements over the previous version. (BZ#632765)
In addition, these updated opencryptoki packages provide fixes for the following bugs:
  • Previously, openCryptoki failed to include secure key support on IBM System z. This was caused by an incorrect build configuration. This update provides the package built with the correct configuration and adds secure key support for System z to the package. (BZ#604287)
  • Prior to this update, openCryptoki failed with the CKR_FUNCTION_FAILED error when trying to sign a certificate for an NSS (Network Security Services) database. This occurred due to the function being called incorrectly. With this update, openCryptoki uses the correct function arguments and the error no longer occurs. (BZ#654088)
Users of opencryptoki are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

1.178. openldap

1.178.1. RHSA-2011:0347: Moderate security update

Updated openldap packages that fix three security issues are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
OpenLDAP is an open source suite of LDAP (Lightweight Directory Access Protocol) applications and development tools.
A flaw was found in the way OpenLDAP handled authentication failures being passed from an OpenLDAP slave to the master. If OpenLDAP was configured with a chain overlay and it forwarded authentication failures, OpenLDAP would bind to the directory as an anonymous user and return success, rather than return failure on the authenticated bind. This could allow a user on a system that uses LDAP for authentication to log into a directory-based account without knowing the password. (CVE-2011-1024)
It was found that the OpenLDAP back-ndb back end allowed successful authentication to the root distinguished name (DN) when any string was provided as a password. A remote user could use this flaw to access an OpenLDAP directory if they knew the value of the root DN. Note: This issue only affected OpenLDAP installations using the NDB back-end, which is only available for Red Hat Enterprise Linux 6 via third-party software. (CVE-2011-1025)
A flaw was found in the way OpenLDAP handled modify relative distinguished name (modrdn) requests. A remote, unauthenticated user could use this flaw to crash an OpenLDAP server via a modrdn request containing an empty old RDN value. (CVE-2011-1081)
Users of OpenLDAP should upgrade to these updated packages, which contain backported patches to resolve these issues. After installing this update, the OpenLDAP daemons will be restarted automatically.

1.178.2. RHBA-2011:0673: bug fix and enhancement update

Updated openldap packages that fix several bugs and add an enhancement are now available.
OpenLDAP is an open source suite of LDAP (Lightweight Directory Access Protocol) applications and development tools. LDAP is a set of protocols for accessing directory services (usually phone book style information, but other information is possible) over the Internet, similar to the way DNS (Domain Name System) information is propagated over the Internet. The openldap package contains configuration files, libraries, and documentation for OpenLDAP.
This update addresses the following bugs:
  • Move openldap libraries from /usr/lib to /lib. (BZ#548475)
  • Init script is working wrong if database recovery is needed. (BZ#613966)
  • Update list of modules in slapd.conf.bak. (BZ#630637)
  • slapd init script gets stuck in an infinite loop. (BZ#644399)
  • openldap-servers upgrade hangs or do not upgrade the database (BZ#685119)
As well, this update adds the following enhancement: - The openldap packages were rebased (from 2.4.19 to 2.4.23), where OpenLDAP crypto backend was changed from OpenSSL to Mozilla NSS. This brings better certificates management and ability to use OpenLDAP with FreeIPA. The transition should be seamless. OpenLDAP with Mozilla NSS can use all of the PEM cert and key files, and other TLS configuration, that OpenLDAP with OpenSSL used. (BZ#644077)
Users are advised to upgrade to these packages, which resolve these issues.

1.179. openmpi

1.179.1. RHEA-2011:0590: bug fix and enhancement update

Updated openmpi packages that fix a bug and add an enhancement are now available for Red Hat Enterprise Linux 6.
Open MPI is the Open Message Passing Interface software stack used for cluster communications in High Performance Compute clusters.
These updated openmpi packages provide the following enhancement:
  • The OpenMPI packages have been upgraded to upstream version 1.4.3, which provides a number of bug fixes and enhancements. (BZ#632371)
    In addition, these updated openmpi packages fix the following bug:
  • Previously, the line "BuildRequires: flex" was missing in the spec file. This caused the package build to fail unless flex was manually installed. This update adds the line to the spec file. (BZ#661292)
All users of Open MPI are advised to upgrade to these updated openmpi packages, which fix this bug and add this enhancement.

1.180. openoffice.org

1.180.1. RHSA-2011:0183: Important security and bug fix update

Updated openoffice.org packages that fix multiple security issues and one bug are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
OpenOffice.org is an office productivity suite that includes desktop applications, such as a word processor, spreadsheet application, presentation manager, formula editor, and a drawing program.
An array index error and an integer signedness error were found in the way OpenOffice.org parsed certain Rich Text Format (RTF) files. An attacker could use these flaws to create a specially-crafted RTF file that, when opened, would cause OpenOffice.org to crash or, possibly, execute arbitrary code with the privileges of the user running OpenOffice.org. (CVE-2010-3451, CVE-2010-3452)
A heap-based buffer overflow flaw and an array index error were found in the way OpenOffice.org parsed certain Microsoft Office Word documents. An attacker could use these flaws to create a specially-crafted Microsoft Office Word document that, when opened, would cause OpenOffice.org to crash or, possibly, execute arbitrary code with the privileges of the user running OpenOffice.org. (CVE-2010-3453, CVE-2010-3454)
A heap-based buffer overflow flaw was found in the way OpenOffice.org parsed certain Microsoft Office PowerPoint files. An attacker could use this flaw to create a specially-crafted Microsoft Office PowerPoint file that, when opened, would cause OpenOffice.org to crash or, possibly, execute arbitrary code with the privileges of the user running OpenOffice.org. (CVE-2010-4253)
A heap-based buffer overflow flaw was found in the way OpenOffice.org parsed certain TARGA (Truevision TGA) files. An attacker could use this flaw to create a specially-crafted TARGA file. If a document containing this specially-crafted TARGA file was opened, or if a user tried to insert the file into an existing document, it would cause OpenOffice.org to crash or, possibly, execute arbitrary code with the privileges of the user running OpenOffice.org. (CVE-2010-4643)
A directory traversal flaw was found in the way OpenOffice.org handled the installation of XSLT filter descriptions packaged in Java Archive (JAR) files, as well as the installation of OpenOffice.org Extension (.oxt) files. An attacker could use these flaws to create a specially-crafted XSLT filter description or extension file that, when opened, would cause the OpenOffice.org Extension Manager to modify files accessible to the user installing the JAR or extension file. (CVE-2010-3450)
A flaw was found in the script that launches OpenOffice.org. In some situations, a "." character could be included in the LD_LIBRARY_PATH variable, allowing a local attacker to execute arbitrary code with the privileges of the user running OpenOffice.org, if that user ran OpenOffice.org from within an attacker-controlled directory. (CVE-2010-3689)
Red Hat would like to thank OpenOffice.org for reporting the CVE-2010-3451, CVE-2010-3452, CVE-2010-3453, CVE-2010-3454, and CVE-2010-4643 issues; and Dmitri Gribenko for reporting the CVE-2010-3689 issue. Upstream acknowledges Dan Rosenberg of Virtual Security Research as the original reporter of the CVE-2010-3451, CVE-2010-3452, CVE-2010-3453, and CVE-2010-3454 issues.
This update also fixes the following bug:
  • OpenOffice.org did not create a lock file when opening a file that was on a share mounted via SFTP. Additionally, if there was a lock file, it was ignored. This could result in data loss if a file in this situation was opened simultaneously by another user. (BZ#671087)
All OpenOffice.org users are advised to upgrade to these updated packages, which contain backported patches to correct these issues. All running instances of OpenOffice.org applications must be restarted for this update to take effect.

1.181. openscap

1.181.1. RHBA-2011:0609: bug fix and enhancement update

Updated openscap packages that fix various bugs and add several enhancements are now available for Red Hat Enterprise Linux 6.
The Security Content Automation Protocol (SCAP) is a line of standards that provide a standard language for the expression of Computer Network Defense related information. OpenSCAP is a set of open source libraries for the integration of SCAP.
The openscap packages have been upgraded to upstream version 0.7.1, which provides a number of bug fixes and enhancements over the previous version. The most important changes include support for Open Vulnerability and Assessment Language (OVAL) version 5.6, the new OpenSCAP API, and various memory and CPU optimizations. (BZ#642672)
As well, this update fixes the following bug:
  • Previously, sending the "USR1" signal to all probes in order to abort the execution of a current rule could cause the oscap utility to stop responding or even terminate unexpectedly with a segmentation fault. This update adapts the underlying source code to prevent such behavior, and when the "USR1" signal is received, the oscap utility now correctly aborts the execution of the selected rule and continues with the remaining rules as expected. (BZ#669693)
All users of openscap are advised to upgrade to these updated packages, which fix this and other bugs, and add these enhancements.

1.182. openssh

1.182.1. RHBA-2010:0943: bug fix update

Updated openssh packages that fix two bugs are now available for Red Hat Enterprise Linux 6.
OpenSSH is OpenBSD's SSH (Secure Shell) protocol implementation. These packages include the core files necessary for both the OpenSSH client and server.
These updated packages fix the following bugs:
  • When the ~/.bashrc startup file contained a command that produced an output to standard error (STDERR), the sftp utility was unable to log in to that account. This bug has been fixed, and the output to STDERR no longer prevents sftp from establishing the connection. (BZ#651820)
  • Prior to this update, the authentication based on a GSS key exchange did not work, rendering users unable to authenticate using this method. With this update, the underlying source code has been modified to target this issue, and the GSSKEX-based authentication now works as expected. (BZ#655043)
All OpenSSH users are advised to upgrade to these updated packages, which resolve these issues.

1.182.2. RHBA-2011:0598: bug fix and enhancement update

Updated openssh packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6.
OpenSSH is OpenBSD's SSH (Secure Shell) protocol implementation. These packages include the core files necessary for both the OpenSSH client and server.
Bug fixes:
BZ#631757
When the ~/.bashrc startup file contained a command that produced output to standard error, the sftp utility was unable to log in to the user account. This bug has been fixed, and output to standard error is discarded and no longer prevents the sftp utility from establishing the connection.
BZ#631787
Due to the limitations of the data type that was used to store user identifier (UID) numbers, the lastlog record was not created for a user with a UID larger than 2147483647. With this update, this data type has been changed to unsigned long integer, and the /var/log/lastlog database is now updated as expected.
BZ#646286
Previously, GSSAPI key exchange functionality was not supported. With this update, GSSAPI key exchange is now supported and works as expected.
BZ#652249
Previously, the openssh package did not contain the README.nss file. This update adds the file to the documentation.
BZ#656415
Logging in to a system caused pam_ssh_agent_auth to temporarily set the EUID (Effective User ID) to the user's current UID. However, if the connection failed, the original EUID was not restored. This update corrects this coding error so that the EUID is restored in this situaton.
BZ#656844
Previously, openssh could have terminated with a segmentation fault if used as a SOCKS proxy. This occurred due to an unhandled null pointer. With this update the underlying code has been fixed and the problem no longer occurs.
BZ#670515
Previously, the ssh-keygen(1) manual page did not document the "-n" option. This update adds the option description to the manual page.
BZ#672870
Previously, the sshd daemon could have failed to start on a server in FIPS (Federal Information Processing Standards) mode. This happened because the daemon expected an RSA1 server key to be created on startup and checked if the key was available. However, in FIPS mode, no RSA1 key is generated on startup. With this update, the underlying code has been changed and the check is no longer performed when in FIPS mode.
BZ#676665
Previously, the sshd daemon could have failed to locate an authorized key if both MLS (Multi-Level Security) SELinux policy and polyinstantiation of home directories were enabled. This occurred because the daemon was searching for authorized keys in the wrong home directories. This update adds the ssh-keycat helper program, which locates and passes the keys to sshd.
BZ#681296
By default, OpenSSH utilities use the /dev/urandom random number generator (RNG). This update adds the "SSH_USE_STRONG_RNG" environment variable. Setting "SSH_USE_STRONG_RNG=1" (the recommended location to set this environment variable is in the /etc/sysconfig/sshd configuration file) causes OpenSSH utilities to use the stronger /dev/random RNG, which is better at ensuring the RNG always has sufficient entropy.

Note

Setting "SSH_USE_STRONG_RNG=1" is resource-intensive, and should generally only be done on servers which have a hardware-enabled random number generator.
BZ#690127
Prior to this update, the openssh-keycat subpackage was optional and OpenSSH thus failed to meet Common Criteria. With this update, the package is included in the openssh-server package.
BZ#690391
Previously, if the user sent two SIGHUP signals to the sshd daemon, the daemon terminated unexpectedly. With this update, the underlying code has been changed and the daemon no longer crashes in such circumstances.
Enhancements:
BZ#455350
Previously, openssh only allowed users to store their authorized public keys in a local file on each system they wanted to log in to using their private SSH key. With this update, sshd can be configured, using the AuthorizedKeysCommand directive, to extract users' authorized keys from an arbitrary source using the "external" command. This update also adds the standalone "ssh-ldap-helper" utility, which can be used to extract public keys from an LDAP server. This new functionality thus enables centralized key management.
BZ#642927
The sshd daemon is now built using RELRO protection.
BZ#577998
Previously, the .k5login file was processed on every kerberos authentication. This update adds the KerberosUseKuserok option to the sshd_config file, which allows the user to configure whether user aliases should be verified against the entries in the .k5login file.
BZ#633404
This update adds support for hardware-accelerated encryption modules which are supported by OpenSSL
BZ#642792
Previously, the sshd daemon did not log information regarding logins using key-based authentication to the audit log. With this update, sshd logs the same information that PAM (Pluggable Authentication Modules) logs upon password-based logins, but for key-based logins. Additionally, sshd logs the following additional detail for key-based logins: key type and size, as well as its fingerprint.
BZ#644877
OpenSSH's audit logging support has been updated.
BZ#657059
Previously, the sftp command worked with the default file mode creation mask (umask) only. With this update, the user may change the umask.
BZ#665112
When an authentication key is destroyed, OpenSSH now logs the key destructions to the audit log.
All users of openssh are advised to upgrade to these updated packages, which resolve these issues and provide these enhancements.

1.183. openssl

1.183.1. RHSA-2010:0888: Important security update

Updated openssl packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols, as well as a full-strength, general purpose cryptography library.
A race condition flaw has been found in the OpenSSL TLS server extension parsing code, which could affect some multithreaded OpenSSL applications. Under certain specific conditions, it may be possible for a remote attacker to trigger this race condition and cause such an application to crash, or possibly execute arbitrary code with the permissions of the application. (CVE-2010-3864)
Note that this issue does not affect the Apache HTTP Server. Refer to Red Hat Bugzilla bug 649304 for more technical details on how to determine if your application is affected.
Red Hat would like to thank Rob Hulswit for reporting this issue.
All OpenSSL users should upgrade to these updated packages, which contain a backported patch to resolve this issue. For the update to take effect, all services linked to the OpenSSL library must be restarted, or the system rebooted.

1.183.2. RHSA-2010:0979: Moderate security update

Updated openssl packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols, as well as a full-strength, general purpose cryptography library.
A ciphersuite downgrade flaw was found in the OpenSSL SSL/TLS server code. A remote attacker could possibly use this flaw to change the ciphersuite associated with a cached session stored on the server, if the server enabled the SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG option, possibly forcing the client to use a weaker ciphersuite after resuming the session. (CVE-2010-4180)
Note: With this update, setting the SSL_OP_NETSCAPE_REUSE_CIPHER_CHANGE_BUG option has no effect and this bug workaround can no longer be enabled.
All OpenSSL users should upgrade to these updated packages, which contain a backported patch to resolve this issue. For the update to take effect, all services linked to the OpenSSL library must be restarted, or the system rebooted.

1.183.3. RHSA-2011:0677: Moderate security, bug fix, and enhancement update

Updated openssl packages that fix one security issue, two bugs, and add two enhancements are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
OpenSSL is a toolkit that implements the Secure Sockets Layer (SSL v2/v3) and Transport Layer Security (TLS v1) protocols, as well as a full-strength, general purpose cryptography library.
A buffer over-read flaw was discovered in the way OpenSSL parsed the Certificate Status Request TLS extensions in ClientHello TLS handshake messages. A remote attacker could possibly use this flaw to crash an SSL server using the affected OpenSSL functionality. (CVE-2011-0014)
This update fixes the following bugs:
  • The "openssl speed" command (which provides algorithm speed measurement) failed when openssl was running in FIPS (Federal Information Processing Standards) mode, even if testing of FIPS approved algorithms was requested. FIPS mode disables ciphers and cryptographic hash algorithms that are not approved by the NIST (National Institute of Standards and Technology) standards. With this update, the "openssl speed" command no longer fails. (BZ#619762)
  • The "openssl pkcs12 -export" command failed to export a PKCS#12 file in FIPS mode. The default algorithm for encrypting a certificate in the PKCS#12 file was not FIPS approved and thus did not work. The command now uses a FIPS approved algorithm by default in FIPS mode. (BZ#673453)
This update also adds the following enhancements:
  • The "openssl s_server" command, which previously accepted connections only over IPv4, now accepts connections over IPv6. (BZ#601612)
  • For the purpose of allowing certain maintenance commands to be run (such as "rsync"), an "OPENSSL_FIPS_NON_APPROVED_MD5_ALLOW" environment variable has been added. When a system is configured for FIPS mode and is in a maintenance state, this newly added environment variable can be set to allow software that requires the use of an MD5 cryptographic hash algorithm to be run, even though the hash algorithm is not approved by the FIPS-140-2 standard. (BZ#673071)
Users of OpenSSL are advised to upgrade to these updated packages, which contain backported patches to resolve these issues and add these enhancements. For the update to take effect, all services linked to the OpenSSL library must be restarted, or the system rebooted.

1.184. openswan

1.184.1. RHSA-2010:0892: Moderate security update

Updated openswan packages that fix multiple security issues are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
Openswan is a free implementation of Internet Protocol Security (IPsec) and Internet Key Exchange (IKE). IPsec uses strong cryptography to provide both authentication and encryption services. These services allow you to build secure tunnels through untrusted networks.
Two buffer overflow flaws were found in the Openswan client-side XAUTH handling code used when connecting to certain Cisco gateways. A malicious or compromised VPN gateway could use these flaws to execute arbitrary code on the connecting Openswan client. (CVE-2010-3302, CVE-2010-3308)
Two input sanitization flaws were found in the Openswan client-side handling of Cisco gateway banners. A malicious or compromised VPN gateway could use these flaws to execute arbitrary code on the connecting Openswan client. (CVE-2010-3752, CVE-2010-3753)
Red Hat would like to thank the Openswan project for reporting these issues. Upstream acknowledges D. Hugh Redelmeier and Paul Wouters as the original reporters.
All users of openswan are advised to upgrade to these updated packages, which contain backported patches to correct these issues. After installing this update, the ipsec service will be restarted automatically.

1.184.2. RHBA-2011:0652: bug fix and enhancement update

Updated openswan package that fix various bugs and provide several enhancements are now available for Red Hat Enterprise Linux 6.
Openswan is a free implementation of IPsec and IKE (Internet Key Exchange) for Linux. This package contains the daemons and user space tools for setting up Openswan. It supports the NETKEY/XFRM IPsec kernel stack that exists in the default Linux kernel.
Openswan 2.6.x also supports IKEv2 (RFC4306)
The openswan packages have been upgraded to upstream version 2.6.32, which provides a number of bug fixes and enhancements over the previous version. (BZ#642724)
These updated openswan packages provide fixes for the following bugs:
  • Openswan was previously unable to negotiate using the HMAC-SHA2-256 algorithm in transport mode. With this update, Openswan is able to set up IPsec in using HMAC-SHA2-256 in transport mode. (BZ#621790)
  • The Openswan init script accessed the current working directory, which led to an SELinux AVC Denial. This update ensures that the current working directory is set to the root ("/") directory, and thus Openswan's pluto daemon starts without incurring an SELinux denial. (BZ#628879)
  • Previously, the Openswan packages were not compiled with the "-Wl,-z,relro" parameter. These updated openswan packages have been compiled with the "-Wl,-z,relro" parameter. (BZ#642722)
  • The IPsec NETKEY kernel code sent thousands of ACQUIRE messages which led to a segmentation fault. With this update, ACQUIRE messages are now properly processed with the result that Openswan does not crash. (BZ#658121)
  • When the system's IP address was renewed using DHCP, the Openswan IPsec connection failed. This update ensures that the IPsec connection continues to operate across DHCP IP address renewals. (BZ#658253)
  • Entering an incorrect IKE Extended Authentication (Xauth) password during IKE negotiation leads to a failure to connect. However, the failure was not communicated to NetworkManager, with the result that NetworkManager continued to wait for a timeout. With this update, Openswan sends a failure message to NetworkManager over the D-Bus system message bus, informing it of the failure to connect. As a result, NetworkManager knows about the failure as soon as it happens, and is able to inform the user about it immediately. (BZ#668785)
  • Internet Control Message Protocol (ICMP)-specific IPsec connections were set up incorrectly, with incorrect "Type" and "Code" fields, in the code. This has been fixed so that ICMP selectors are now processed correctly according to the IKEv2 protocol specification (RFC 4306). (BZ#681974)
  • Configuring a second IPsec policy using a different host behind the same gateway caused Openswan to crash due to the policy not being set up correctly. With this update, Openswan's IKEv2 implementation processes the traffic selectors correctly so that the correct definition is picked up during the key exchange. As a result, a second IPsec policy using a different host behind the same gateway can successfully set up. (BZ#683604)
In addition, these updated packages provide the following enhancements:
  • Openswan's IKEv1 implementation and NETKEY interactions now understand SELinux labeled flows, and Openswan has been integrated with SELinux. As a result, it's now possible to exchange SELinux labels in IKE, and set up labeled IPsec policies and Security Associations (SAs) in SELinux Multi-Level Security (MLS) mode. (BZ#235720)
  • Previously, Openswan did not support the Internet Key Exchange version 2 (IKEv2) USE_TRANSPORT_MODE functionality, with the result that Openswan could not interoperate with racoon2 in transport mode. With this update, Openswan's IKEv2 protocol support has been enhanced so that it now works in transport mode, and interoperate with racoon2. (BZ#646718)
Users are advised to upgrade to these updated openswan packages, which resolve these issues and add these enhancements.

1.185. openwsman

1.185.1. RHBA-2011:0563: bugfix update

Updated openwsman packages that fix multiple bugs are now available for Red Hat Enterprise 6.
OpenWSMan provides an open-source implementation of the Web Services Management specification (WS-Management) and exposes system management information on the Linux operating system with the WS-Management protocol. WS-Management is based on a suite of web services specifications and usage requirements that exposes a set of operations focused on and covers all system management aspects.
This update fixes the following bugs:
  • Previously, certain init script return values were incorrect. This update resolves these errors in the code. Now, all return values are correct. (BZ#613031)
  • Previously, the wsman-xml.h, wsman-xml-binding.h and wsman-dispatcher.h header files were missing. With this update, these headers are provided by the libwsman-devel package. (BZ#615922)
  • Previously, the init script did not print an error message if the SSL certificate and the private key were not found. This update checks whether a certificate exists. Now, OpenWSMan closes and prints a message to manually generate a certificate if no certificate was found. (BZ#617549)
  • Previously, OpenWSMan aborted unexpectedly with a segmentation fault when it was started with a debug flag due to a null pointer dereference. This update checks the pointer value. Now, the pointer is no longer dereferenced when its value is null and OpenWSMan runs as expected. (BZ#622793)
  • Previously, OpenWSMan aborted unexpectedly when it was configured in cooperation with Small Footprint CIM Broker (sfcb) and sfcb was stopped. This update corrects this error in the code. Now, the OpenWSMan configuration with sfcb works as expected. (BZ#625160)
  • Previously, the init script was wrongly placed in the /etc/init.d directory. This update corrects this error. Now, the init script is correctly placed in the /etc/rc.d/init.d. directory. (BZ#626773)
All OpenWSMan users are advised to upgrade to these updated packages, which fix these bugs.

1.186. oprofile

1.186.1. RHBA-2011:0566: bug fix and enhancement update

An updated oprofile package that fixes one bug and adds two enhancements is now available for Red Hat Enterprise Linux 6.
OProfile is a system-wide profiler for Linux systems. The profiling runs transparently in the background and profile data can be collected at any time. OProfile uses the hardware performance counters provided on many processors, and can use the Real Time Clock (RTC) for profiling on processors without counters.
This update fixes the following bug:
  • Previously, non-numeric arguments for the opcontrol options which needed numerical arguments (--buffer-size, --buffer-watershed,--cpu-buffer-size, and --callgraph) were written to /dev/oprofile files without any check. Due to this issue, the OProfile profiler accepted negative and non-numeric values. This update adds numeric argument checks for all arguments to opcontrol. Now, OProfile reports illegal non-numeric arguments. (BZ#589638)
This update also adds the following enhancements:
  • Previously, the OProfile profiler did not provide the performance monitoring events for the Intel Westmere processor. This update provides the files for the Intel Westmere processor specific performance events and adds code to identify Intel Westmere processors. Now, OProfile provides Intel Westmere specific events. (BZ#643478)
  • Previously, the OProfile profiler did not have events mapping and unit_mask files to describe processor performance events for the new AMD Family 12h, 14h, 15h processors. This update identifies these new processors and provides lists of the available events. Now, OProfile provides support for AMD Family 12h, 14h, 15h processors. (BZ#650126)
All OProfile users are advised to upgrade to this updated package which fixes this bug and adds these enhancements.

1.187. pacemaker

1.187.1. RHBA-2011:0642: bug fix and enhancement update

Updated pacemaker packages that fix various bugs and add one enhancement are now available for Red Hat Enterprise Linux 6.
Pacemaker is a high-availability cluster resource manager with a powerful policy engine.
This update fixes the following bugs:
  • The pacemaker packages have been upgraded to upstream version 1.1.5, which provides a number of bug fixes over the previous version. (BZ#668466)
  • Due to missing Cluster Resource Manager (CRM) scripts, an attempt to run the crm utility caused the following message to be presented to a user:
    crm_standby not available, check your installation
    
    This update re-includes the "crm_master" in the packemaker package, and adapts the crm utility not to require the "crm_standby" and "crm_failcount" scripts, so that the above error message is no longer displayed. (BZ#627626)
  • In a cluster environment managed by both Pacemaker and the CMAN cluster management subsystem, frequent leaving and joining of a node could cause Pacemaker's quorum view to be incorrect. This update applies a patch that addresses this issue, so that the leaving and joining of a node no longer causes Pacemaker's quorum view to be different from CMAN's. (BZ#684825)
  • Previously, rebooting a node in a CMAN managed cluster could cause the fencing daemon to keep the "fenced:default" CPG group on the remaining nodes, leaving the cluster in an inconsistent state. With this update, an upstream patch has been applied to address this issue. As a result, when a node is rebooted and leaves a cluster, the cluster resources correctly run on remaining nodes. (BZ#684838)
As well, this update adds the following enhancements:
  • When using the fence_ipmilan fencing agent, Pacemaker now accepts "diag" as a valid per-device stonith action. With this action enabled, a fenced node receives the "DIAG" signal and creates a dump for diagnostic purposes. (BZ#676286)
  • Note that Pacemaker provides the following functionality, and is now the preferred application to perform these tasks:
  • Pacemaker provides support for a time-based resource control. This allows system administrators to define the time a resource is down. (BZ#310361)
  • Pacemaker supports time-based resource control. This allows system administrators to define the downtime of individual resources. (BZ#449833)
  • Pacemaker allows users to manually start or stop cluster resources. This enables system administrators to perform maintenance tasks on individual components within a service. (BZ#449835)
All users of pacemaker are advised to upgrade to these updated packages, which fix these and other bugs, and add this enhancement. Note that pacemaker is considered a Technology Preview in Red Hat Enterprise Linux 6.

1.188. PackageKit

1.188.1. RHBA-2011:0681: bug fix update

Updated PackageKit packages that fix multiple bugs are now available.
PackageKit is a D-Bus abstraction layer that allows the session user to manage packages in a secure way using a cross-distribution, cross-architecture API.
This update addresses the following bugs:
  • Both Mozilla Firefox and the packagekit-plugin included different versions of sqlite in their dependencies. This could cause crashes in Firefox when attempting to use the PackageKit web plug-in to access application icons, since the plug-in attempted to use its version of sqlite to query PkDesktop. This query attempt has been removed, and the web plug-in now works as expected, without crashing Firefox. (BZ#617734)
  • An error message was incorrectly displayed when the cron script packagekit-background.cron was disabled. As this is a configuration option, not an error, the message is no longer displayed in this situation. (BZ#626867)
  • Under some circumstances, the Add/Remove Software (gpk-application) graphical user interface does not display Supplementary groups or packages when the Supplementary group is selected. To work around this, use the System > Refresh Package Lists option to refresh the package lists. (BZ#629049)
  • An error in a changelog entry prevented updates to PackageKit. This error has been corrected. (BZ#634560)
  • A critical warning is displayed erroneously when attempting to install a local package with pkcon, the command line PackageKit tool. This warning is no longer displayed erroneously. (BZ#667923)
  • * gpk-update-viewer failed to process updates when used in conjunction with yum version 3.2.29 because it attempted to perform the same repository setup twice if the "prerepoconf" attribute was not set. This resulted in an error:
    AttributeError: 'PackageKitYumBase' object has no attribute 'prerepoconf'
    
    PackageKit logic has now been altered so that this does not occur, and updates are now processed as expected. This issue was discovered and corrected during development, and was not seen in production systems in the field. (BZ#670163)
Users of PackageKit are advised to upgrade to these updated packages, which resolve these issues.

1.189. pam

1.189.1. RHSA-2010:0891: Moderate security update

Updated pam packages that fix three security issues are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
Pluggable Authentication Modules (PAM) provide a system whereby administrators can set up authentication policies without having to recompile programs that handle authentication.
It was discovered that the pam_namespace module executed the external script namespace.init with an unchanged environment inherited from an application calling PAM. In cases where such an environment was untrusted (for example, when pam_namespace was configured for setuid applications such as su or sudo), a local, unprivileged user could possibly use this flaw to escalate their privileges. (CVE-2010-3853)
It was discovered that the pam_env and pam_mail modules used root privileges while accessing user's files. A local, unprivileged user could use this flaw to obtain information, from the lines that have the KEY=VALUE format expected by pam_env, from an arbitrary file. Also, in certain configurations, a local, unprivileged user using a service for which the pam_mail module was configured for, could use this flaw to obtain limited information about files or directories that they do not have access to. (CVE-2010-3435)
Note: As part of the fix for CVE-2010-3435, this update changes the default value of pam_env's configuration option user_readenv to 0, causing the module to not read user's ~/.pam_environment configuration file by default, as reading it may introduce unexpected changes to the environment of the service using PAM, or PAM modules consulted after pam_env.
It was discovered that the pam_xauth module did not verify the return values of the setuid() and setgid() system calls. A local, unprivileged user could use this flaw to execute the xauth command with root privileges and make it read an arbitrary input file. (CVE-2010-3316)
Red Hat would like to thank Sebastian Krahmer of the SuSE Security Team for reporting the CVE-2010-3435 issue.
All pam users should upgrade to these updated packages, which contain backported patches to correct these issues.

1.189.2. RHBA-2011:0685: bug fix and enhancement update

Updated pam packages that fix bugs and add enhancements are now available.
Pluggable Authentication Modules (PAM) provide a system whereby administrators can set up authentication policies without having to recompile programs to handle authentication.
These updated pam packages fix the following bugs:
  • When the pam packages were updated, the /var/log/tallylog and /var/log/faillog files were overwritten with empty files because of an incorrect condition check in the %post script. This has been corrected, and PAM no longer attempts to overwrite tallylog and faillog files when they exist prior to update. (BZ#614766)
  • A code review revealed several small memory leaks and improperly handled error paths in pam_namespace, pam_selinux, pam_limits, pam_pwhistory, pam_time, and pam_group modules. These issues have been corrected. (BZ#679069)
These updated packages also provide the following enhancements:
  • The pam_limits module, which sets resource limits for processes, now supports matching individual and ranges of user and group identifiers in its limits.conf configuration file. (BZ#622847)
  • A new pam_faillock module was added to support temporary locking of user accounts in the event of multiple failed authentication attempts. This new module improves functionality over the existing pam_tally2 module, as it also allows temporary locking when the authentication attempts are done over a screen saver. (BZ#644971)
  • The audit records provided by the pam_selinux and pam_tally2 modules have been improved to include tty and remote hostname information in each recorded event. (BZ#677664)
All pam users are advised to upgrade to these updated packages, which resolve these issues and add these enhancements.

1.190. pam_krb5

1.190.1. RHBA-2011:0711: bug fix update

An updated pam_krb5 package that fixes two bugs is now available for Red Hat Enterprise Linux 6.
The pam_krb5 module allows PAM-aware applications to verify and change user passwords with the help of a KDC.
This update fixes the following bugs:
  • Previously, pam_krb5 ignored the "verify_ap_req_nofail" configuration setting when it checked whether the credentials from the Key Distribution Center (KDC) were spoofed because of a missing or otherwise inaccessible local keytab file. Due to this behavior, pam_krb5 wrongly returned a success message. This update reworks the credential verification. Now, the verification settings work as expected. (BZ#622938)
  • Previously, pam_krb5 used a format for password change requests that earlier versions of kadmind could not process. This update uses application programming interfaces (API) that format password change requests which can also be parsed by earlier versions of kadmind. (BZ#690583)
All pam_krb5 users are advised to upgrade to this updated package, which fixes these bugs.

1.191. pam_ldap

1.191.1. RHBA-2011:0688: bug fix

An updated pam_ldap package that fixes two bugs is now available for Red Hat Enterprise Linux 6.
The pam_ldap module is a Pluggable Authentication Module (PAM) which allows for authentication, authorization and password changes against LDAP servers.
This update fixes the following bugs:
  • Previously, the password aging policy for users on LDAP servers used a resolution of one day. Due to this issue, users whose password was going to expire in less than a day would not be warned of the impending expiration. This update changes the resolution. Now, a password expiry warning is also shown on the last day when the password expires within the next 24 hours. (BZ#637190)
  • Applications which authenticate multiple users in succession using pam_ldap may leak memory which libraries on which the module depends allocate and initialize when they are loaded. This update marks the module so that it will not be unloaded. Now these libraries and the memory they allocate are no longer lost. (BZ#677338)
All users of pam_ldap are advised to upgrade to this updated package which fixes these bugs.

1.192. pam_pkcs11

1.192.1. RHBA-2011:0766: bug fix update

An updated pam_pkcs11 package that fixes various bugs is now available for Red Hat Enterprise Linux 6.
The pam_pkcs11 package allows X.509 certificate-based user authentication. It provides access to the certificate and its dedicated private key with an appropriate PKCS (Public Key Cryptographic Standards) #11 module.
This updated pam_pkcs11 package includes fixes for the following bugs:
  • The system returned the following debug message to standard error when you logged in with a smart card from the command line and "require smart card login" was enabled:
    ERROR: pam_pkcs11.c:334: no suitable token available
    With this update, the message is no longer returned. (BZ#586149)
  • The system returned the following spurious message to standard error when you entered an incorrect personal identification number (PIN) when logging in from the command line with a smart card:
    ERROR: pam_pkcs11.c:445: open_pkcs11_login() failed: Login incorrect
    With this update, only the message "Login incorrect" is displayed and the error details are logged. (BZ#625509)
All users of pam_pkcs11 are advised to upgrade to this updated package, which resolves these issues.

1.193. pango

1.193.1. RHSA-2011:0309: Critical security update

Updated pango packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having critical security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
Pango is a library used for the layout and rendering of internationalized text.
It was discovered that Pango did not check for memory reallocation failures in the hb_buffer_ensure() function. An attacker able to trigger a reallocation failure by passing sufficiently large input to an application using Pango could use this flaw to crash the application or, possibly, execute arbitrary code with the privileges of the user running the application. (CVE-2011-0064)
Red Hat would like to thank the Mozilla Security Team for reporting this issue.
All pango users should upgrade to these updated packages, which contain a backported patch to correct this issue. After installing this update, you must restart your system or restart the X server for the update to take effect.

1.193.2. RHSA-2011:0180: Moderate security update

Updated pango and evolution28-pango packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
Pango is a library used for the layout and rendering of internationalized text.
An input sanitization flaw, leading to a heap-based buffer overflow, was found in the way Pango displayed font files when using the FreeType font engine back end. If a user loaded a malformed font file with an application that uses Pango, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. (CVE-2011-0020)
Users of pango and evolution28-pango are advised to upgrade to these updated packages, which contain a backported patch to resolve this issue. After installing the updated packages, you must restart your system or restart your X session for the update to take effect.

1.194. papi

1.194.1. RHBA-2011:0783: bug fix and enhancement update

An updated papi package that fixes a bug and provides an enhancement is now available for Red Hat Enterprise Linux 6.
PAPI (Performance Application Programming Interface) is a software library that provides access to the processor's performance-monitoring hardware. This allows developers to track performance-related events, such as cache misses, instructions retired, and clock cycles, to better understand the performance issues of the software.
This updated papi package fixes the following bug:
  • When using PAPI on the AMD family 0x15 processors, the "papi_avail" utility returned that the number of hardware performance counters was four. However, for these processors, the number of hardware performance counters is six. This update implements support for the additional two hardware counters. (BZ#692668)
In addition, this updated package provides the following enhancement:
  • Previously, PAPI did not handle the new event mappings for the AMD Opteron 6000-series processor and some newer AMD family 10h processors. Due to this, PAPI did not recognize or work with these processors. This update adds the lists of the new events and PAPI recognizes and works with the processors correctly. (BZ#635667)
PAPI users are advised to upgrade to this updated package, which fixes this bug and adds this enhancement.

1.195. paps

1.195.1. RHBA-2011:0296: bug fix update

Updated paps packages that fix a bug are now available for Red Hat Enterprise Linux 6.
The paps packages provide a command line utility that allows a user to convert a plain text file to a PostScript using Pango.
This update fixes the following bug:
  • Prior to this update, the presence of certain non-printable characters in the input file could cause paps to get stuck in an infinite loop, consuming all available system memory. With this update, the underlying source code has been modified to prevent this behavior, and such memory leaks no longer occur. (BZ#618271)
Users of paps are advised to upgrade to these updated packages, which resolve this issue.

1.196. parted

1.196.1. RHBA-2011:0675: bug fix and enhancement update

An updated parted package that fixes two bugs and adds one enhancement is now available for Red Hat Enterprise Linux 6.
The GNU Parted program allows you to create, destroy, resize, move, and copy hard disk partitions. Parted can be used for creating space for new operating systems, reorganizing disk usage, and copying data to new hard disks.
This updated package fixes the following bugs:
  • Previously, when a user ran the parted program on the IBM System z platform, the character buffer for the fdasd_check_api_version() function was too short, causing a buffer overflow. This has been fixed by doubling the buffer. The buffer overflow does not occur anymore. (BZ#693852)
  • Although the parted program's help information, accessed by running "parted --help", contained a usage example and a description for the "align-check" command, this information was missing from the corresponding manual page. This update corrects the parted(8) manual page to include a description of the "align-check" command. (BZ#642476)
Additionally, this update adds the following enhancement:
  • In order to help tools such as Anaconda support 4KB sector drives, the libparted-provided ped_device_get_optimum_alignment function now prefers to align partitions to 1MB whenever possible. This change has negligible effect on the parted command line tool. (BZ#618255)
All users of parted are advised to upgrade to this updated package, which fixes these bugs and adds this enhancement.

1.197. perl

1.197.1. RHSA-2011:0558: Moderate perl security and bug fix update

Updated perl packages that fix three security issues and several bugs are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
Perl is a high-level programming language commonly used for system administration utilities and web programming. The Perl CGI module provides resources for preparing and processing Common Gateway Interface (CGI) based HTTP requests and responses.
It was found that the Perl CGI module used a hard-coded value for the MIME boundary string in multipart/x-mixed-replace content. A remote attacker could possibly use this flaw to conduct an HTTP response splitting attack via a specially-crafted HTTP request. (CVE-2010-2761)
A CRLF injection flaw was found in the way the Perl CGI module processed a sequence of non-whitespace preceded by newline characters in the header. A remote attacker could use this flaw to conduct an HTTP response splitting attack via a specially-crafted sequence of characters provided to the CGI module. (CVE-2010-4410)
It was found that certain Perl string manipulation functions (such as uc() and lc()) failed to preserve the taint bit. A remote attacker could use this flaw to bypass the Perl taint mode protection mechanism in scripts that use the affected functions to process tainted input. (CVE-2011-1487)
These packages upgrade the CGI module to version 3.51. Refer to the CGI module's Changes file, linked to in the References, for a full list of changes.
This update also fixes the following bugs:
  • When using the "threads" module, an attempt to send a signal to a thread that did not have a signal handler specified caused the perl interpreter to terminate unexpectedly with a segmentation fault. With this update, the "threads" module has been updated to upstream version 1.82, which fixes this bug. As a result, sending a signal to a thread that does not have the signal handler specified no longer causes perl to crash. (BZ#626330)
  • Prior to this update, the perl packages did not require the Digest::SHA module as a dependency. Consequent to this, when a user started the cpan command line interface and attempted to download a distribution from CPAN, they may have been presented with the following message:
    CPAN: checksum security checks disabled because Digest::SHA not installed. Please consider installing the Digest::SHA module.
    This update corrects the spec file for the perl package to require the perl-Digest-SHA package as a dependency, and cpan no longer displays the above message. (BZ#640716)
  • When using the "threads" module, continual creation and destruction of threads could cause the Perl program to consume an increasing amount of memory. With this update, the underlying source code has been corrected to free the allocated memory when a thread is destroyed, and the continual creation and destruction of threads in Perl programs no longer leads to memory leaks. (BZ#640720)
  • Due to a packaging error, the perl packages did not include the "NDBM_File" module. This update corrects this error, and "NDBM_File" is now included as expected. (BZ#640729)
  • Prior to this update, the prove(1) manual page and the "prove --help" command listed "--fork" as a valid command line option. However, version 3.17 of the Test::Harness distribution removed the support for the fork-based parallel testing, and the prove utility thus no longer supports this option. This update corrects both the manual page and the output of the "prove --help" command, so that "--fork" is no longer included in the list of available command line options. (BZ#609492)
Users of Perl, especially those of Perl threads, are advised to upgrade to these updated packages, which correct these issues.

1.198. perl-Mozilla-LDAP

1.198.1. RHBA-2011:0529: bug fix update

An updated perl-Mozilla-LDAP package that fixes several bugs and ensures that perl-Mozilla-LDAP always uses the OpenLDAP C SDK, is now available for Red Hat Enterprise Linux 6.
perl-Mozilla-LDAP is an LDAP Perl module that wraps the OpenLDAP client libraries.
This update fixes the following bugs:
  • The perl-Mozilla-LDAP package has been upgraded to upstream version 1.5.3, which provides a number of bug fixes over the previous version. (BZ#644093)
  • Previously, the Mozilla Perl LDAP SDK was a wrapper around the Mozilla C LDAP SDK (mozldap). Now that mozldap has been dropped from RHEL 6, in order to support legacy applications that still use the Mozilla Perl LDAP SDK, it has been ported to use OpenLDAP instead of mozldap. Applications that use the Mozilla Perl LDAP SDK should not notice any difference between the versions that use mozldap and the new one that uses OpenLDAP. (BZ#610902)
Users are advised to upgrade to this updated perl-Mozilla-LDAP package, which fixes these bugs.

1.199. perl-Sys-Virt

1.199.1. RHEA-2011:0767: enhancement update

An updated perl-Sys-Virt package that adds one enhancement is now available for Red Hat Enterprise Linux 6.
The perl-Sys-Virt package provides an API for managing virtual machines from Perl, using the libvirt library.
This update adds the following enhancement:
  • The Sys::Virt module has been updated to provide support for the new application programming interfaces (APIs) introduced between version 0.8.1 and 0.8.7 of the libvirt library. (BZ#675120)
All users of perl-Sys-Virt are advised to upgrade to this updated package, which adds this enhancement.

1.200. php

1.200.1. RHSA-2011:0195: Moderate security update

Updated php packages that fix multiple security issues are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
PHP is an HTML-embedded scripting language commonly used with the Apache HTTP Server.
A flaw was found in the way PHP converted certain floating point values from string representation to a number. If a PHP script evaluated an attacker's input in a numeric context, the PHP interpreter could cause high CPU usage until the script execution time limit is reached. This issue only affected i386 systems. (CVE-2010-4645)
A numeric truncation error and an input validation flaw were found in the way the PHP utf8_decode() function decoded partial multi-byte sequences for some multi-byte encodings, sending them to output without them being escaped. An attacker could use these flaws to perform a cross-site scripting attack. (CVE-2009-5016, CVE-2010-3870)
A NULL pointer dereference flaw was found in the PHP ZipArchive::getArchiveComment function. If a script used this function to inspect a specially-crafted ZIP archive file, it could cause the PHP interpreter to crash. (CVE-2010-3709)
All php users should upgrade to these updated packages, which contain backported patches to resolve these issues. After installing the updated packages, the httpd daemon must be restarted for the update to take effect.

1.200.2. RHBA-2011:0615: bug fix and enhancement update

Updated php packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6.
PHP is an HTML-embedded scripting language commonly used with the Apache HTTP Server. It offers developers a built-in database integration and a solution to write dynamically generated web pages.
The php packages have been upgraded to upstream version 5.3.3, which provides a number of bug fixes and adds multiple enhancements over the previous version. It also introduces one backwards-incompatible language change in that only a function named "__construct" is now treated as a constructor in a namespaced class. This change has no effect on non-namespaced classes. (BZ#645591)
Additionally, the following bug has been fixed:
  • Previously, the check to prevent the "extract()" function overwriting the "$GLOBALS" variable was not working properly when using the default "EXTR_OVERWRITE" mode. The fix for this bug has been provided so that the check works as expected now. (BZ#655118)
Users are advised to upgrade to these updated packages, which resolve these issues and add these enhancements.

1.201. php-pecl-memcache

1.201.1. RHEA-2011:0794: bug fix and enhancement update

An updated php-pecl-memcache package that fixes multiple bugs and adds one enhancement is now available for Red Hat Enterprise 6.
The php-pecl-memcache package enables PHP scripts to use the memcached caching daemon.
The php-pecl-memcache package has been rebased to version 3.0.5 which fixes multiple bugs and adds MemcachePool class support for the findServer() method. (BZ#638887)
This update fixes the following bugs:
  • Previously, the "delete" methods failed for some memcached server versions due to a protocol error. With this update, the "delete" method works as expected. (BZ#638887)
  • Previously, integer, float, and boolean values with enabled compression could not be retrieved successfully due to an issue with the compression flag. With this update, stored values are retrieved successfully. (BZ#638892)
  • Previously, the memcache module aborted with a segmentation fault on the 64-bit PowerPC platform. This update resolves this problem and memcache runs on the 64-bit PowerPC architecture as expected. (BZ#672363)
  • Previously, php-pecl-memcache contained extra characters after %{?dist}. This update deletes these characters. (BZ#604559)
All php-pecl-memcache users are advised to upgrade to this updated package, which fixes these bugs and adds this enhancement.

1.202. pidgin

1.202.1. RHSA-2010:0890: Moderate security update

Updated pidgin packages that fix multiple security issues are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
Pidgin is an instant messaging program which can log in to multiple accounts on multiple instant messaging networks simultaneously.
Multiple NULL pointer dereference flaws were found in the way Pidgin handled Base64 decoding. A remote attacker could use these flaws to crash Pidgin if the target Pidgin user was using the Yahoo! Messenger Protocol, MSN, MySpace, or Extensible Messaging and Presence Protocol (XMPP) protocol plug-ins, or using the Microsoft NT LAN Manager (NTLM) protocol for authentication. (CVE-2010-3711)
Red Hat would like to thank the Pidgin project for reporting these issues. Upstream acknowledges Daniel Atallah as the original reporter.
All Pidgin users should upgrade to these updated packages, which contain a backported patch to resolve these issues. Pidgin must be restarted for this update to take effect.

1.202.2. RHSA-2011:0616: Low security and bug fix update

Updated pidgin packages that fix multiple security issues and various bugs are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having low security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
Pidgin is an instant messaging program which can log in to multiple accounts on multiple instant messaging networks simultaneously.
Multiple NULL pointer dereference flaws were found in the way the Pidgin Yahoo! Messenger Protocol plug-in handled malformed YMSG packets. A remote attacker could use these flaws to crash Pidgin via a specially-crafted notification message. (CVE-2011-1091)
Red Hat would like to thank the Pidgin project for reporting these issues. Upstream acknowledges Marius Wachtler as the original reporter.
This update also fixes the following bugs:
  • Previous versions of the pidgin package did not properly clear certain data structures used in libpurple/cipher.c when attempting to free them. Partial information could potentially be extracted from the incorrectly cleared regions of the previously freed memory. With this update, data structures are properly cleared when freed. (BZ#684685)
  • This erratum upgrades Pidgin to upstream version 2.7.9. For a list of all changes addressed in this upgrade, refer to http://developer.pidgin.im/wiki/ChangeLog (BZ#616917)
  • Some incomplete translations for the kn_IN and ta_IN locales have been corrected. (BZ#633860, BZ#640170)
Users of pidgin should upgrade to these updated packages, which resolve these issues. Pidgin must be restarted for this update to take effect.

1.203. pixman

1.203.1. RHBA-2010:0905: bug fix update

An updated pixman package is now available for Red Hat Enterprise Linux 6.
Pixman is a pixel manipulation library for the X Window System and cairo.
This update fixes the following bug:
  • The pixman package has been updated to version 0.18, which provides new functionality that is required by SPICE, a remote display protocol used in Red Hat Enterprise Linux for viewing virtualized guests. (BZ#644818)
All users requiring SPICE are advised to upgrade to this updated package, which resolves this issue.

1.204. plymouth

1.204.1. RHBA-2011:0686: bug fix update

Updated plymouth packages that fix various bugs are now available for Red Hat Enterprise Linux 6.
Plymouth provides an attractive graphical boot animation in place of the text messages that are normally displayed. Text messages are instead redirected to a log file for viewing after boot.
These updated packages fix the following bugs:
  • When two monitors shared one controller during a system boot, a blank screen appeared on both monitors. Consequently, users with this configuration experienced prolonged blank screens during boot-up and shutdown, and a choppy splash animation on any other external monitor. With this update, this bug has been fixed and the splash animation is now smooth and is displayed on all external monitors. (BZ#625209)
  • Previously, the plymouth daemon terminated unexpectedly if there were any "console=" entries on the kernel command line. As a consequence, boot messages were not properly logged. With this update, this bug has been fixed, the plymouth daemon now handles console entries on the kernel command line without any crashes and boot messages are written to the log file as expected. (BZ#631924)
  • Previously, the system prompted for a password on boot but provided no hint as to what the password was for. That caused unnecessary confusion for some users, who didn't know which of their passwords to enter. With this update, a hard drive icon has been added to prompts associated with encrypted disk volumes and the password prompts for encrypted disks are now easy to recognize. (BZ#612665)
All plymouth users are advised to upgrade to these updated packages, which fix these bugs.

1.205. policycoreutils

1.205.1. RHSA-2011:0414: Important security update

Updated policycoreutils packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The policycoreutils packages contain the core utilities that are required for the basic operation of a Security-Enhanced Linux (SELinux) system and its policies.
It was discovered that the seunshare utility did not enforce proper file permissions on the directory used as an alternate temporary directory mounted as /tmp/. A local user could use this flaw to overwrite files or, possibly, execute arbitrary code with the privileges of a setuid or setgid application that relies on proper /tmp/ permissions, by running that application via seunshare. (CVE-2011-1011)
Red Hat would like to thank Tavis Ormandy for reporting this issue.
This update also introduces the following changes:
  • The seunshare utility was moved from the main policycoreutils subpackage to the policycoreutils-sandbox subpackage. This utility is only required by the sandbox feature and does not need to be installed by default.
  • Updated selinux-policy packages that add the SELinux policy changes required by the seunshare fixes.
All policycoreutils users should upgrade to these updated packages, which correct this issue.

1.206. polkit

1.206.1. RHSA-2011:0455: Important security update

Updated polkit packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
PolicyKit is a toolkit for defining and handling authorizations.
A race condition flaw was found in the PolicyKit pkexec utility and polkitd daemon. A local user could use this flaw to appear as a privileged user to pkexec, allowing them to execute arbitrary commands as root by running those commands with pkexec. (CVE-2011-1485)
Red Hat would like to thank Neel Mehta of Google for reporting this issue.
All polkit users should upgrade to these updated packages, which contain backported patches to correct this issue. The system must be rebooted for this update to take effect.

1.207. poppler

1.207.1. RHSA-2010:0859: Important security update

Updated poppler packages that fix three security issues are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.
Poppler is a Portable Document Format (PDF) rendering library, used by applications such as Evince.
Two uninitialized pointer use flaws were discovered in poppler. An attacker could create a malicious PDF file that, when opened, would cause applications that use poppler (such as Evince) to crash or, potentially, execute arbitrary code. (CVE-2010-3702, CVE-2010-3703)
An array index error was found in the way poppler parsed PostScript Type 1 fonts embedded in PDF documents. An attacker could create a malicious PDF file that, when opened, would cause applications that use poppler (such as Evince) to crash or, potentially, execute arbitrary code. (CVE-2010-3704)
Users are advised to upgrade to these updated packages, which contain backported patches to correct these issues.

1.208. postfix

1.208.1. RHSA-2011:0423: Moderate security update

Updated postfix packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
Postfix is a Mail Transport Agent (MTA), supporting LDAP, SMTP AUTH (SASL), and TLS.
It was discovered that Postfix did not flush the received SMTP commands buffer after switching to TLS encryption for an SMTP session. A man-in-the-middle attacker could use this flaw to inject SMTP commands into a victim's session during the plain text phase. This would lead to those commands being processed by Postfix after TLS encryption is enabled, possibly allowing the attacker to steal the victim's mail or authentication credentials. (CVE-2011-0411)
Red Hat would like to thank the CERT/CC for reporting CVE-2011-0411. The CERT/CC acknowledges Wietse Venema as the original reporter.
Users of Postfix are advised to upgrade to these updated packages, which contain a backported patch to resolve this issue. After installing this update, the postfix service will be restarted automatically.

1.209. postgresql

1.209.1. RHSA-2010:0908: Moderate security update

Updated postgresql packages that fix one security issue are now available for Red Hat Enterprise Linux 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
PostgreSQL is an advanced object-relational database management system (DBMS). PL/Perl and PL/Tcl allow users to write PostgreSQL functions in the Perl and Tcl languages. The PostgreSQL SECURITY DEFINER parameter, which can be used when creating a new PostgreSQL function, specifies that the function will be executed with the privileges of the user that created it.
It was discovered that a user could utilize the features of the PL/Perl and PL/Tcl languages to modify the behavior of a SECURITY DEFINER function created by a different user. If the PL/Perl or PL/Tcl language was used to implement a SECURITY DEFINER function, an authenticated database user could use a PL/Perl or PL/Tcl script to modify the behavior of that function during subsequent calls in the same session. This would result in the modified or injected code also being executed with the privileges of the user who created the SECURITY DEFINER function, possibly leading to privilege escalation. (CVE-2010-3433)
These updated postgresql packages upgrade PostgreSQL to version 8.4.5. Refer to the PostgreSQL Release Notes for a list of changes:
http://www.postgresql.org/docs/8.4/static/release.html
All PostgreSQL users are advised to upgrade to these updated packages, which correct this issue. If the postgresql service is running, it will be automatically restarted after installing this update.

1.209.2. RHSA-2011:0197: Moderate security update

Updated postgresql packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6.
The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
PostgreSQL is an advanced object-relational database management system (DBMS).
A stack-based buffer overflow flaw was found in the way PostgreSQL processed certain tokens from an SQL query when the intarray module was enabled on a particular database. An authenticated database user running a specially-crafted SQL query could use this flaw to cause a temporary denial of service (postgres daemon crash) or, potentially, execute arbitrary code with the privileges of the database server. (CVE-2010-4015)
Red Hat would like to thank Geoff Keating of the Apple Product Security team for reporting this issue.
For Red Hat Enterprise Linux 4, the updated postgresql packages contain a backported patch for this issue; there are no other changes.
For Red Hat Enterprise Linux 5, the updated postgresql packages upgrade PostgreSQL to version 8.1.23, and contain a backported patch for this issue. Refer to the PostgreSQL Release Notes for a full list of changes:
http://www.postgresql.org/docs/8.1/static/release.html
For Red Hat Enterprise Linux 6, the updated postgresql packages upgrade PostgreSQL to version 8.4.7, which includes a fix for this issue. Refer to the PostgreSQL Release Notes for a full list of changes:
http://www.postgresql.org/docs/8.4/static/release.html
All PostgreSQL users are advised to upgrade to these updated packages, which correct this issue. If the postgresql service is running, it will be automatically restarted after installing this update.

1.209.3. RHBA-2011:0810: bug fix update

Updated postgresql packages that fix a bug are now available for Red Hat Enterprise Linux 6.
PostgreSQL is an advanced object-relational database management system (DBMS) that supports most SQL constructs.
These updated postgresql packages fix the following bug:
  • Previously, PL/pgSQL functions could have failed with an error if they used composite types as their arguments or result types. This happened if a column was dropped in the table underlying the composite type. This update adapts the source code that handles these situations so that such functions work correctly. (BZ#694249)
All users of postgresql are advised to upgrade to these updated packages, which resolve this bug.

1.210. powerpc-utils

1.210.1. RHBA-2011:0682: bug fix and enhancement update

An updated powerpc-utils package that fixes various bugs and adds an enhancement is now available.
The powerpc-utils package contains utilities for PowerPC platform.
This updated powerpc-utils package includes fixes for the following bugs:
  • The man pages for several powerpc-utils executables (drmgr, lsdevinfo, lsprop, lsslot, nvsetenv, ppc64_cpu and rtas_event_decode) were not included in Red Hat Enterprise Linux 6.0. Man pages for these executables have now been added to powerpc-utils. (BZ#659664)
  • The man page for "ofpathname" omitted several options and contained a typographical error. These issues have been corrected. (BZ#659696)
  • Previously, the short version of the nvram "--verbose" flag, "-v", did not register as a valid flag. This option has been added to nvram and now works, consistent with its description in the man page. (BZ#674421)
  • "ofpathname" uses /usr/bin/bc, but the powerpc-utils package does not depend on bc. ofpathname now checks whether bc is installed, and requests the user install it if this package is not found. (BZ#679413)
  • The drmgr command incorrectly checked the "is_removable" field to determine the number of logical memory blocks available for a remove operation, even when AMS ballooning was active. Memory removal no longer relies on "is_removable" when ballooning is active. (BZ#693802)
This update also adds the following enhancement:
  • Support for partition hibernation has been added. This allows suspension for longer than 5-10 seconds, saving partition state to persistent storage, and freeing resources in use by that partition. (BZ#632690)
Users are advised to upgrade to this updated powerpc-utils package, which resolves these issues.

1.211. powertop

1.211.1. RHBA-2011:0522: bug fix and enhancement update

An updated powertop package that fixes a bug and adds an enhancement is now available for Red Hat Enterprise Linux 6.
PowerTOP is a tool to detect all the software components that make a computer consume more than necessary power when idle.
This update fixes the following bug:
  • Previously, PowerTOP could not run processes without a valid terminal. This update backports the TTY handling from powertop 1.13. Now, PowerTOP runs without a terminal in dump mode. (BZ#628514)
This update also adds the following enhancement:
  • Previously, PowerTOP could not detect whether hardware used the Intel Turbo Boost functionality. This update adds support for Intel Dynamic Acceleration (IDA) and Intel Turbo Boost. (BZ#610464)
All PowerTOP users are advised to upgrade to this updated package which fixes this bug and adds this enhancement.

1.213. procps

1.213.1. RHBA-2011:0708: bug fix update

An updated procps package that fixes several bugs is now available.
The procps package contains a set of system utilities that provide system information. The procps package includes ps, free, skill, snice, sysctl, tload, top, uptime, vmstat, w, and watch.
This update addresses the following issues:
  • The vmstat disk device field was, previously, restricted to 15 characters. The Linux kernel allows for device names up to 32 characters, however, and the vmstat restriction resulted in two unwelcome behaviors. First, device names up to 31 characters were displayed correctly by "vmstat -d", although characters after the fifteenth were truncated. More significantly, devices with 32-character names were not displayed by "vmstat -d" at all. With this update, the vmstat disk device field now supports up to 32 characters, ensuring all devices are displayed properly in "vmstat -d" output. (BZ#596948)
  • The sysctl command's man page described the "-A" switch as displaying "all values currently available in table form." This is incorrect: "-A" is equivalent to "-a", simply displaying all currently available values. This update includes an updated man page that corrects the error. As well, this updated man page includes a new NOTES entry, documenting the interaction between modules loaded after sysctl is run and sysctl itself. (BZ#622389)
  • Previously applied procps patches contained three memory leaks, all of which can lead to procps utilities hanging. This update closes the leaks, ensuring the potential hangs do not, now, occur. (BZ#684031)
All procps users are advised to upgrade to this updated package, which resolves these issues.

1.214. psmisc

1.214.1. RHBA-2011:0171: bug fix update

An updated psmisc package that fixes two bugs is now available for Red Hat Enterprise Linux 6.
The psmisc package contains utilities for managing processes on your system: pstree, killall, fuser and peekfd. The pstree command displays a tree structure of all of the running processes on your system. The killall command sends a specified signal (SIGTERM if nothing is specified) to processes identified by name. The fuser command identifies the PIDs of processes that are using specified files or file systems. The peekfd command attaches to a running process and intercepts all reads and writes to file descriptors.
This update fixes the following bugs:
  • Due to an error in memory allocation, an attempt to kill a process group by using the "killall -g" command could fail. With this update, the memory allocation has been corrected, and the killall utility now works as expected. (BZ#668989)
  • When parsing a list of command line arguments, the peekfd utility incorrectly used a wrong index. As a result, running the peekfd command with a file descriptor specified caused the utility to terminate unexpectedly with a segmentation fault. This update corrects this error, and the peekfd utility no longer fails to run. (BZ#668992)
All users of psmisc are advised to upgrade to this updated package, which resolves these issues.

1.215. pykickstart

1.215.1. RHBA-2011:0662: bug fix and enhancement update

An updated pykickstart package that fixes several bugs and adds a number of enhancements is now available.
The pykickstart package is a python library used to manipulate kickstart files.
This updated package fixes the following bugs:
  • The ksflatten tool included with pykickstart erroneously output any %include statements along with the content included by these statements. The original %include statements are now removed when the referenced content is included. (BZ#668050)
  • The documentation included in pykickstart was not referenced correctly, so no information was available to users. This has been corrected and useful documentation is now included. (No BZ#)
This update also adds the following enhancements:
  • The bootloader command now takes an additional "--iscrypted" option. Since GRUB supports multiple encryption mechanisms and can automatically detect which to use based on the encrypted password, this new option should be used whenever an encrypted password is provided. This takes the place of the previous "--md5pass=" option. (BZ#554870)
  • The "url" and "repo" commands now take an additional "--noverifyssl" option. Use this option to prevent anaconda from checking the validity of the SSL certificate of your source when using HTTPS. (BZ#660340)
  • Three new n