Discuss February 2016

discuss@lists.centos.org

126 participants
101 discussions

Network hangs after several hours (Centos 6 recently upgraded kernel/glibc)
by Ian B 22 Feb '16

22 Feb '16

Hi all, We have a development server we have just tried updating the kernel & glibc after recent recommendations. Its been stable previously for a few years with only scheduled reboots. Its running Centos 6.6(final) 2.6.32-573.18.1.el6.x86_64 GNU libc 2.12 Upgraded via YUM, rebooted, all fine for several hours, and then network seemed to hang. Not much happening as its a dev server we are testing before moving to production. Googling, I see there is some history of e100e driver having issues, and I'm wondering if it could be related. Does anyone have any thoughts on where to do with it, as I'm assuming it will hang again later. Thanks, Ian Feb 18 05:04:36 kernel: WARNING: at net/sched/sch_generic.c:261 dev_watchdog+0x26d/0x280() (Not tainted) Feb 18 05:04:36 kernel: Hardware name: X9SCL/X9SCM Feb 18 05:04:36 kernel: NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out Feb 18 05:04:36 kernel: Modules linked in: ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables ipv6 ext4 jbd2 e1000e serio_raw i2c_i801 i2c_core sg iTCO_wdt iTCO_vendor_support shpchp ext3 jbd mbcache raid1 sd_mod crc_t10dif ahci dm_mirror dm_region_hash dm_log dm_mod [last unloaded: scsi_wait_scan] Feb 18 05:04:36 kernel: Pid: 0, comm: swapper Not tainted 2.6.32-220.4.2.el6.x86_64 #1 Feb 18 05:04:36 kernel: Call Trace: Feb 18 05:04:36 kernel: <IRQ> [<ffffffff81069a17>] ? warn_slowpath_common+0x87/0xc0 Feb 18 05:04:36 kernel: [<ffffffff81069b06>] ? warn_slowpath_fmt+0x46/0x50 Feb 18 05:04:36 kernel: [<ffffffff8144a4fd>] ? dev_watchdog+0x26d/0x280 Feb 18 05:04:36 kernel: [<ffffffff8108b3fd>] ? insert_work+0x6d/0xb0 Feb 18 05:04:36 kernel: [<ffffffff8144a290>] ? dev_watchdog+0x0/0x280 Feb 18 05:04:36 kernel: [<ffffffff8107c7f7>] ? run_timer_softirq+0x197/0x340 Feb 18 05:04:36 kernel: [<ffffffff810a0a10>] ? tick_sched_timer+0x0/0xc0 Feb 18 05:04:36 kernel: [<ffffffff8102ad6d>] ? lapic_next_event+0x1d/0x30 Feb 18 05:04:36 kernel: [<ffffffff81072001>] ? __do_softirq+0xc1/0x1d0 Feb 18 05:04:36 kernel: [<ffffffff81095610>] ? hrtimer_interrupt+0x140/0x250 Feb 18 05:04:36 kernel: [<ffffffff8100c24c>] ? call_softirq+0x1c/0x30 Feb 18 05:04:36 kernel: [<ffffffff8100de85>] ? do_softirq+0x65/0xa0 Feb 18 05:04:36 kernel: [<ffffffff81071de5>] ? irq_exit+0x85/0x90 Feb 18 05:04:36 kernel: [<ffffffff814f4d70>] ? smp_apic_timer_interrupt+0x70/0x9b Feb 18 05:04:36 kernel: [<ffffffff8100bc13>] ? apic_timer_interrupt+0x13/0x20 Feb 18 05:04:36 kernel: <EOI> [<ffffffff812c49de>] ? intel_idle+0xde/0x170 Feb 18 05:04:36 kernel: [<ffffffff812c49c1>] ? intel_idle+0xc1/0x170 Feb 18 05:04:36 kernel: [<ffffffff813f9ef7>] ? cpuidle_idle_call+0xa7/0x140 Feb 18 05:04:36 kernel: [<ffffffff81009e06>] ? cpu_idle+0xb6/0x110 Feb 18 05:04:36 kernel: [<ffffffff814d40ca>] ? rest_init+0x7a/0x80 Feb 18 05:04:36 kernel: [<ffffffff81c1ff76>] ? start_kernel+0x424/0x430 Feb 18 05:04:36 kernel: [<ffffffff81c1f33a>] ? x86_64_start_reservations+0x125/0x129 Feb 18 05:04:36 kernel: [<ffffffff81c1f438>] ? x86_64_start_kernel+0xfa/0x109 Feb 18 05:04:36 kernel: ---[ end trace 21915186e9d87b29 ]--- modinfo e1000e | grep version version: 3.2.5-k srcversion: 8CCA78B3C15DE6229299348 vermagic: 2.6.32-573.18.1.el6.x86_64 SMP mod_unload modversions 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 Processor Family DRAM Controller (rev 09) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation C202 Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 03:03.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a)

5 8

where did SCL go?
by jason welsh 22 Feb '16

22 Feb '16

monsterjam:/etc/letsencrypt/archive/monsterjam # yum --enablerepo=extras install centos-release-SCL Loaded plugins: fastestmirror, remove-with-leaves Setting up Install Process Loading mirror speeds from cached hostfile * base: mirror.dattobackup.com * epel: mirror.us.leaseweb.net * extras: distro.ibiblio.org * updates: mirror.netdepot.com No package centos-release-SCL available. Error: Nothing to do monsterjam.org:/etc/letsencrypt/archive/monsterjam # cat /etc/centos-release CentOS release 6.7 (Final) monsterjam:/etc/letsencrypt/archive/monsterjam # any ideas?

3 3

Kernel panic and crash, was Re: [CentOS-announce] CEBA-2016:0150 CentOS 6 kernel BugFix Update
by Max Pyziur 21 Feb '16

21 Feb '16

Greetings, I just tried upgrading one of my CentOS boxes to this kernel. It crashes; the screen looks like this: http://www.brama.com/~deckard/P1010308.JPG So, I'm continuing to run on kernel-2.6.32-504.23.4.el6.x86_64 I had previously reported this, and I was told that the reported bug was here: https://bugs.centos.org/view.php?id=9374 Looking at it now, I see that it is closed. It's odd that CentOS is releasing a production kernel that fails. fyi, Max Pyziur pyz(a)brama.com On Wed, 10 Feb 2016, Johnny Hughes wrote: > > CentOS Errata and Bugfix Advisory 2016:0150 > > Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-0150.html > > The following updated files have been uploaded and are currently > syncing to the mirrors: ( sha256sum Filename ) > > i386: > b5f33a81b28d0a89af970bc08c4a07856c13f9789fe520e90d237dc7a2e5df65 kernel-2.6.32-573.18.1.el6.i686.rpm > 8b375b6d363800343bc325966b4db96347e2508db458547b0df5dc63581e2793 kernel-abi-whitelists-2.6.32-573.18.1.el6.noarch.rpm > cba169e9faf5ebc0ba25011f3b920de1a3a2943b7e46be6292193b31df7b8a5a kernel-debug-2.6.32-573.18.1.el6.i686.rpm > a4bf157c52dc0d736ef7a65a073e543b3f2cf0070aa938da41eeecaca11e783d kernel-debug-devel-2.6.32-573.18.1.el6.i686.rpm > 5151ae3d0f6dde51c1ec991e14b88f0308ef7d46975ee7e9ed036f1381153901 kernel-devel-2.6.32-573.18.1.el6.i686.rpm > 74ff6b30bd2603f2e859e899a653aaac2daa0ee534abd5ab3e32a8ffc2cdb2fb kernel-doc-2.6.32-573.18.1.el6.noarch.rpm > 38a27fbf4e7fa229fe8ab6b8cf25ec08031c376cf51ec38400197bc478d0255a kernel-firmware-2.6.32-573.18.1.el6.noarch.rpm > f318d66d12c72c060e8f644aa90d0c10099f1ab8ba5e24875f2a1ace22e35a57 kernel-headers-2.6.32-573.18.1.el6.i686.rpm > 81ef77b0d7841946bf8825e599c1f6a6015082013b5ea02a836db34e19ca7fbc perf-2.6.32-573.18.1.el6.i686.rpm > a8fa3ef717f09235052dd6bd4285be52ff494ea8c242788df16eda5b9aed7fb6 python-perf-2.6.32-573.18.1.el6.i686.rpm > > x86_64: > 1cb5031871e077e7d70fec7801901a948438d10f226ffb4311540c28f9253a55 kernel-2.6.32-573.18.1.el6.x86_64.rpm > 8b375b6d363800343bc325966b4db96347e2508db458547b0df5dc63581e2793 kernel-abi-whitelists-2.6.32-573.18.1.el6.noarch.rpm > 9f31b8f7f4db48d8ba30c16564cb6ad614d04b7d63811c274134654607cbce08 kernel-debug-2.6.32-573.18.1.el6.x86_64.rpm > a4bf157c52dc0d736ef7a65a073e543b3f2cf0070aa938da41eeecaca11e783d kernel-debug-devel-2.6.32-573.18.1.el6.i686.rpm > 16cb431b4a01c6b3b915e646c971fa0c79e62f4feeffd57939f39df687ebc6a3 kernel-debug-devel-2.6.32-573.18.1.el6.x86_64.rpm > b81c297339078d80dda73d86a1aec61c50d7fb05728585c1ebbe81bb088851bf kernel-devel-2.6.32-573.18.1.el6.x86_64.rpm > 74ff6b30bd2603f2e859e899a653aaac2daa0ee534abd5ab3e32a8ffc2cdb2fb kernel-doc-2.6.32-573.18.1.el6.noarch.rpm > 38a27fbf4e7fa229fe8ab6b8cf25ec08031c376cf51ec38400197bc478d0255a kernel-firmware-2.6.32-573.18.1.el6.noarch.rpm > 9dd3a3533ebb6646bafafef2229b6142fa0277f34a534e7c74f3c8cacafd7296 kernel-headers-2.6.32-573.18.1.el6.x86_64.rpm > 5ff27ecbdca7013f093d697f4ba3bcaa9b14be03ef79cafb4a3ed3d0aef1bf69 perf-2.6.32-573.18.1.el6.x86_64.rpm > c5fee073bee1f19dc848a8302e07e4241e49cbff55f35a3db5ae903352f11dc4 python-perf-2.6.32-573.18.1.el6.x86_64.rpm > > Source: > ef3c944af9b7e94448e3c343da7d6f582b267aa9a5653586b8b9332351b01afc kernel-2.6.32-573.18.1.el6.src.rpm > > > >

2 1

centos7 :: ks.cfg :: customisation of sshd
by Adrian Sevcenco 19 Feb '16

19 Feb '16

Hi! I want to change the sshd port at install for centos7 but i am not sure if i am on the good track (and it is time expensive to make many try-outs).. So, i would be grateful if someone with experience can spot if i have problems with my planning.. (the actual purpose is that after installation i have access for my ansible provisioning) first make sure ssh is started services --enabled=sshd,chronyd then .. i imagine that in the %post section %post --interpreter=/usr/bin/bash --log=/root/ks-post.log 1. i could use sed to change the port sed -i 's/#Port\ 22/Port 60000/' /etc/ssh/sshd_config 2. sed -i 's/#PermitRootLogin\ yes/PermitRootLogin\ yes/' /etc/ssh/sshd_config 3. enable key access mkdir -p /root/.ssh chmod 700 /root/.ssh cat << EOF >> /root/.ssh/authorized_keys my_ssh_pubkey EOF 4. semanage port -a -t ssh_port_t -p tcp 60000 5. firewall-cmd --permanent --zone=public --add-port=60000/tcp 6. systemctl enable firewalld.service did i miss anything? Thank you! Adrian

4 4

CentOS-announce Digest, Vol 132, Issue 6
by centos-announce-request＠centos.org 19 Feb '16

19 Feb '16

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2016:0258 Important CentOS 7 thunderbird Security Update (Johnny Hughes) 2. CESA-2016:0258 Important CentOS 6 thunderbird Security Update (Johnny Hughes) 3. CESA-2016:0258 Important CentOS 5 thunderbird Security Update (Johnny Hughes) 4. CEBA-2016:0268 CentOS 6 ptlib FASTTRACK BugFix Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Thu, 18 Feb 2016 17:19:24 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0258 Important CentOS 7 thunderbird Security Update Message-ID: <20160218171924.GA56122(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0258 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0258.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: d97294b0f502e02f49e4d2ca9a3fb5cc368a3ad6c08162e06e509e607a00a307 thunderbird-38.6.0-1.el7.centos.x86_64.rpm Source: 2555990fee9e57f5a64ea43642860f30fe807d073e48d048665adadb1bc489f1 thunderbird-38.6.0-1.el7.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Thu, 18 Feb 2016 18:42:37 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0258 Important CentOS 6 thunderbird Security Update Message-ID: <20160218184237.GA57736(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0258 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0258.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: b6943f1cda53a9c502ee9839f608c29d0e75cf44673490822c93f395e3f40141 thunderbird-38.6.0-1.el6.centos.i686.rpm x86_64: 5a1261b9965569d707060f8e7ff869288d7e0361efe4e5637086bf6295afe27a thunderbird-38.6.0-1.el6.centos.x86_64.rpm Source: 4f89116b8b8bda266f2063760ceb136832e8e2d874ffd33d9e424d479d980a63 thunderbird-38.6.0-1.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Fri, 19 Feb 2016 04:09:41 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2016:0258 Important CentOS 5 thunderbird Security Update Message-ID: <20160219040941.GA32077(a)chakra.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2016:0258 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2016-0258.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: fc47e7fd94bd3079266b27f1307d954fd5a9f9442a91c3a2cb6172e86faa9224 thunderbird-38.6.0-1.el5.centos.i386.rpm x86_64: ec8dcb696078c89e8aa535036e750f5e4e06e40dbcd883e255287ea6b69bd61e thunderbird-38.6.0-1.el5.centos.x86_64.rpm Source: 2e6c718b8d5ce3cf2919e8c44995d1048ae923f32159b06cfc6f0dd06caa2088 thunderbird-38.6.0-1.el5.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: JohnnyCentOS ------------------------------ Message: 4 Date: Fri, 19 Feb 2016 04:19:41 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2016:0268 CentOS 6 ptlib FASTTRACK BugFix Update Message-ID: <20160219041941.GA19991(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2016:0268 Upstream details at : https://rhn.redhat.com/errata/RHBA-2016-0268.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 0348146563840e96432128fce8893e5c1e052b8c7a04731580b71ef6ec88d928 ptlib-2.6.5-5.el6.i686.rpm f15fb5b00ef80df31948e084c9746c4d38af9b8f6f17f435ee35a2a420a1805b ptlib-devel-2.6.5-5.el6.i686.rpm x86_64: 0348146563840e96432128fce8893e5c1e052b8c7a04731580b71ef6ec88d928 ptlib-2.6.5-5.el6.i686.rpm 9591b407f7f281255041138bea978c25fa450d4db068cc267396eef5f47e82d4 ptlib-2.6.5-5.el6.x86_64.rpm f15fb5b00ef80df31948e084c9746c4d38af9b8f6f17f435ee35a2a420a1805b ptlib-devel-2.6.5-5.el6.i686.rpm 16d22c5bd3e7e1f8c2030c3c9cfedbb8d8163bd079d91fa284e299ec4d2f9e77 ptlib-devel-2.6.5-5.el6.x86_64.rpm Source: 77f35943cb9f218305dad4478269b10bc9b932a7376710c6a4ad147b6aeeab52 ptlib-2.6.5-5.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce End of CentOS-announce Digest, Vol 132, Issue 6 ***********************************************

1 0

dhcpd frequent renewals
by david 19 Feb '16

19 Feb '16

Folks This might be the wrong place to ask, but I don't know where to turn. My internal home network, including wireless, is controlled by a Centos6 server, which provides dhcpd services, along with NAT. I have DHCPD configured with the addresses 192.168.155.200 through 192.168.155.254 as the range for dynamic allocations. The default-lease time is 1800 seconds, the maximum is 3600 seconds. My windows clients, and even an ipad-mini behave nicely, asking for DHCP renewals once ever five minutes, or at about 80% of the default lease time, a behavior I can understand. However, several of my guests, with their own iPads, I-watches, iPhones, connect to my network (via a wireless access point which does not do routing functions) and they're renewing once every 20-30 seconds. In addition, these devices also loose connectivity for brief intervals, which seems to be roughly synchronized with dhcp renewal. This last fact I deduce by doing "tail -f /etc/log/messages" and hearing them say "lost connection" at just about the same moment the DHCPREQUEST and DHCPACK statements show up. It's difficult to believe that Apple IOS devices (all of which are running apple's latest) have a dhcp client problem not shared by windows or even linux hosts. Does anyone have any clues? David Kurn San Francisco DHCPD.CONF file is excerpted below: ---------------------------------------- ddns-update-style none; subnet 192.168.155.0 netmask 255.255.255.0 { authoritative; option routers 192.168.155.2; option subnet-mask 255.255.255.0; option broadcast-address 192.168.155.255; option domain-name "daku.org"; option domain-name-servers 192.168.155.2; option netbios-name-servers 192.168.155.2; option time-offset -28800; # Pacific standard time range dynamic-bootp 192.168.155.200 192.168.155.254; default-lease-time 1800; max-lease-time 3600; } --------------------------------------------

2 3

CentOS 7, Xeon CPUs, not booting
by m.roth＠5-cent.us 18 Feb '16

18 Feb '16

This is happening on anything other than plain vanilla Dell servers. One R730, with dual Tesla cards, one R420, with a fibre card for a RAID device, it never switches root. All these systems have Xeons, not AMD CPUs. We've had this with every one of the 327 kernels. In addition, it seems to happen also with the 229.20.1; the 229.14.1 has no such problem. >From the rdsosreport: starting at line 126: /dev/disk/by-label: total 0 lrwxrwxrwx 1 root 0 10 Jan 27 19:03 SWAP -> ../../sda2 lrwxrwxrwx 1 root 0 10 Jan 27 19:03 \x2f -> ../../sda3 lrwxrwxrwx 1 root 0 10 Jan 27 19:03 \x2fboot -> ../../sda1 Then, starting at line 1283: [ 3.317027] <servername> systemd[1]: Found device ST500NM0003-9ZM172 /. [ 3.317974] <servername> systemd[1]: Starting File System Check on /dev/disk/by-label/\x2f... [ 3.320089] <servername> systemd-fsck[590]: Failed to detect device /dev/disk/by-label// [ 3.320567] <servername> systemd[1]: systemd-fsck-root.service: main process exited, code=exited, status=1/FAILURE [ 3.320972] <servername> systemd[1]: Failed to start File System Check on /dev/disk/by-label/\x2f. Does *ANYONE* have any clues as to what's going on? Meanwhile, on a plain vanilla Dell R420, I see: ll /dev/disk/by-label/ total 0 lrwxrwxrwx. 1 root root 10 Feb 17 10:06 SWAP -> ../../sda2 lrwxrwxrwx. 1 root root 10 Feb 17 10:06 boot -> ../../sda1 lrwxrwxrwx. 1 root root 10 Feb 17 10:06 root -> ../../sda3 So, what is this by-label with the x2f, and why can't it find the drives? Or do I have to file a bug report? This is a true show-stopper. mark

3 4

Can't install CentOS 7 on SuperMicro X7DB3 with Adaptec AIC-9410 Controller
by homeryan＠sina.com 18 Feb '16

18 Feb '16

I have a server with Super Micro X7DB3 motherboard and Adaptech AIC-9410 controller (http://www.supermicro.com/products/motherboard/Xeon1333/5000P/X7DB3.cfm). The hard disk is single SeaGate SAS disk (300Gb). I'd like to install CentOS 7 on the server, but unfortunately, the CentOS installer can't find any hard disk. I think the problem maybe caused by the disk controller. Can you please tell me how to fix the problem ? Thanks for your help!

2 1

Thunderbird can not import S/MIME certificate
by Timo Schoeler 18 Feb '16

18 Feb '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, in May 2015 I reported [0] that I can not import my S/MIME certificate. Issuer is GlobalSign. Jan Horak reassigned it to the nss guys ("This seems to be problem in NSS code, reassigning to nss component"), but then the ticket idled and was eventually closed by EOL of Fedora 21 (though I stated it persists with F22). I just reopened the ticket because it still doesn't work. The certificate itself is okay, it works on other platforms. Nobody else using S/MIME? Best, Timo https://bugzilla.redhat.com/show_bug.cgi?id=1218977 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EAREIAAYFAlbFgGYACgkQuSPmkPhAW0r2QQD+Pn97WYQNwItYmJ4eqgMm4ufk SSWrC4Yjm7iEYNotTkEA/RbB9lLTjecLaCpkQ33zV1bVCcHdsvQfi/WLhZH5zwur =/SFq -----END PGP SIGNATURE-----

2 1

New glibc for CentOS-6 and CentOS-7 and CVE-2015-7547
by Johnny Hughes 18 Feb '16

18 Feb '16

I normally just let the daily announce post to this list show what is available for updates, but there is a CVE (CVE-2015-7547) that needs a bit more attention which will be on today's announce list of updates. We released a new glibc yesterday for CentOS-6 and CentOS-7 .. it is VERY important that all users update to these versions: This update is rated as Critical by Red Hat, meaning that it is remotely exploitable under some circumstances. Make sure this update works in your environments and update as soon as you can. CentOS-7: https://lists.centos.org/pipermail/centos-announce/2016-February/021672.html https://rhn.redhat.com/errata/RHSA-2016-0176.html CentOS-6: https://lists.centos.org/pipermail/centos-announce/2016-February/021668.html https://rhn.redhat.com/errata/RHSA-2016-0175.html These mitigate CVE-2015-7547: https://access.redhat.com/security/cve/CVE-2015-7547 https://bugzilla.redhat.com/show_bug.cgi?id=1293532 Can't stress how important this update is .. here are a couple stories: http://arstechnica.com/security/2016/02/extremely-severe-bug-leaves-dizzyin… http://www.theregister.co.uk/2016/02/16/glibc_linux_dns_vulernability/ Please note that the ONLY way this is tested to work is with ALL updates from CentOS-6 or CentOS-7 applied along with the glibc updates. So a yum update with base and updates repo enabled is the ONLY tested scenario. Did I say *ONLY* enough? Thanks, Johnny Hughes

6 16

← Newer
1
2
3
4
5
6
7
...
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss February 2016