The following Fedora EPEL 6 Security updates need testing: Age URL 639 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7031 python-virtualenv-12.0.7-1.el6 633 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-7168 rubygem-crack-0.3.2-2.el6 523 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-e2b4b5b2fb mcollective-2.8.4-1.el6 495 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-35e240edd9 thttpd-2.25b-24.el6 225 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-8594ed3a53 chicken-4.11.0-3.el6 105 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-e3e50897ac libbsd-0.8.3-2.el6 55 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-acd2c2af0d nagios-4.2.4-4.el6 14 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-da3e5ef08f tcpreplay-4.2.1-1.el6 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-68aef427a4 php-horde-Horde-Crypt-2.7.6-1.el6 3 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-def12f5099 libupnp-1.6.21-1.el6 1 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-c0d33ae70f tnef-1.4.14-1.el6 The following builds have been pushed to Fedora EPEL 6 updates-testing fedfind-3.5.3-1.el6 libidn2-2.0.0-1.el6 pam_mapi-0.3.2-1.el6 Details about builds: ================================================================================ fedfind-3.5.3-1.el6 (FEDORA-EPEL-2017-48c0df2f4c) Fedora compose and image finder -------------------------------------------------------------------------------- Update Information: This update provides a new release of fedfind. It adds the PowerPC, S390 and ARM secondary arch compose locations to the 'known URL prefixes' whitelist, which means that if you pass `get_release` a URL in one of these locations, it will return a generic `Pungi4Compose` instance. `get_release` would always return a generic `Pungi4Compose` instance for any URL it could not match to a known release type prior to fedfind 3.4.0, but this was changed in 3.4.0 to only do so for 'known' URL prefixes, as a security measure. Also, `helpers.parse_cid` now accepts compose IDs for composes with 'FACD' as their short name. This will prevent relvalconsumer throwing exceptions whenever one of these composes appears. -------------------------------------------------------------------------------- ================================================================================ libidn2-2.0.0-1.el6 (FEDORA-EPEL-2017-3b7a949eea) Library to support IDNA2008 internationalized domain names -------------------------------------------------------------------------------- Update Information: Libidn2 2.0.0 (released 2017-03-29) =================================== * Added to ASCII conversion functions corresponding to libidn1 functions: - idn2_to_ascii_4i - idn2_to_ascii_4z - idn2_to_ascii_8z - idn2_to_ascii_lz * Added to unicode conversion functions corresponding to libidn1 functions: - idn2_to_unicode_8z4z - idn2_to_unicode_4z4z - idn2_to_unicode_44i - idn2_to_unicode_8z8z - idn2_to_unicode_8zlz - idn2_to_unicode_lzlz * The idn2 manual page is generated from markdown text instead of utilizing help2man on the generated tool. * Including idn2.h will provide libidn1 compatibility functions unless IDN2_SKIP_LIBIDN_COMPAT is defined. That allows converting applications from libidn1 (which offers IDNA2003) to libidn2 (which offers IDNA2008) by replacing idna.h to idn2.h in the applications' source. * API and ABI is backwards compatible with the previous version. -------------------------------------------------------------------------------- References: [ 1 ] Bug #1439727 - update libidn2 to 2.0.0 https://bugzilla.redhat.com/show_bug.cgi?id=1439727 -------------------------------------------------------------------------------- ================================================================================ pam_mapi-0.3.2-1.el6 (FEDORA-EPEL-2017-9a28b64c03) PAM module for authentication via MAPI against a Zarafa server -------------------------------------------------------------------------------- Update Information: Update to pam_mapi 0.3.2 -------------------------------------------------------------------------------- _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx