similar to: CESA-2016:1664 Important CentOS 6 kernel Security Update

Send CentOS-announce mailing list submissions to centos-announce at 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 at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

I have a KVM vm running CentOS-6.8 on a host also running CentOS-6.8. This instance is used for occasional development projects which require segregation. Thus it is seldom accessed. At some point in the recent past this guest developed an issue with starting. Specifically these messages were found in the system log files: /var/log/messages-20170312:Mar 10 16:31:06 vhost04 kernel: dracut:

Hello, I've got CentOS 6.8 x64, updated today to the latest by 'yum update' this installed a new kernel: 2.6.32-642.4.2.el6.x86_64 in /var/log/boot.log I found these 3 lines ... No kdump initial ramdisk found. [WARNING] Rebuilding /boot/initrd-2.6.32-642.4.2.el6.x86_64kdump.img cp: cannot stat `/lib/firmware/i915/bxt_dmc_ver1.bin': No such file or

On 25.08.2016 20:24, ken wrote: > On 08/25/2016 12:08 PM, Walter H. wrote: >> Hello, >> >> I've got CentOS 6.8 x64, updated today to the latest by 'yum update' >> this installed a new kernel: 2.6.32-642.4.2.el6.x86_64 >> >> in /var/log/boot.log I found these 3 lines ... >> >> No kdump initial ramdisk found. [WARNING] >>

On 08/25/2016 12:08 PM, Walter H. wrote: > Hello, > > I've got CentOS 6.8 x64, updated today to the latest by 'yum update' > this installed a new kernel: 2.6.32-642.4.2.el6.x86_64 > > in /var/log/boot.log I found these 3 lines ... > > No kdump initial ramdisk found. [WARNING] > Rebuilding /boot/initrd-2.6.32-642.4.2.el6.x86_64kdump.img > cp: cannot stat

On 08/25/2016 02:42 PM, Walter H. wrote: > On 25.08.2016 20:24, ken wrote: >> On 08/25/2016 12:08 PM, Walter H. wrote: >>> Hello, >>> >>> I've got CentOS 6.8 x64, updated today to the latest by 'yum update' >>> this installed a new kernel: 2.6.32-642.4.2.el6.x86_64 >>> >>> in /var/log/boot.log I found these 3 lines ...

On Thu, August 25, 2016 23:21, ken wrote: > On 08/25/2016 02:42 PM, Walter H. wrote: >> On 25.08.2016 20:24, ken wrote: >>> On 08/25/2016 12:08 PM, Walter H. wrote: >>>> Hello, >>>> >>>> I've got CentOS 6.8 x64, updated today to the latest by 'yum update' >>>> this installed a new kernel: 2.6.32-642.4.2.el6.x86_64

On 08/26/2016 12:02 AM, Walter H. wrote: > On Thu, August 25, 2016 23:21, ken wrote: >> On 08/25/2016 02:42 PM, Walter H. wrote: >>> On 25.08.2016 20:24, ken wrote: >>>> On 08/25/2016 12:08 PM, Walter H. wrote: >>>>> Hello, >>>>> >>>>> I've got CentOS 6.8 x64, updated today to the latest by 'yum update'

I have a server that is also a firewall router at a public library with a fiber optic Internet connection. It is running kernel 2.6.32-642.4.2.el6.x86_64 (current CentOS 6.8) and Iptables 1.4.7 (current stock CentOS 6.8). I having trouble with Internet throughput. I am supposed to be getting 20Mbits down and 20MBits up, but I am not getting that. It has no problem doing 20MBits down, but for

Hi, Trying to keep abusive/buggy IMAP clients at bay on a number of Dovecot proxy servers, I've reconfigured them to use "mail_max_userip_connections = 50" in the "protocol imap" section, followed by restarting Dovecot. Yet, I'm still seeing 160+ established connections from a single IP address for the same email account. Am I missing anything? # 2.2.27

I'm observing double the amount of "recv" bytes in latest Centos v6.8 with ixgbe 4.2.1-k. Anybody seeing the same? $ ethtool -i em1 driver: ixgbe version: 4.2.1-k $ uname -an Linux chndcdmid01.rd.ph.cox.net 2.6.32-642.4.2.el6.x86_64 #1 SMP Tue Aug 23 19:58:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux Doing comparison on 2 days at same hour just to show the difference. This is an

Quick follow-up: updated the proxies to 2.2.28, but I still couldn't find a way to limit the inbound IMAP connections per IP & username. I know "mail_max_userip_connections" limit works for the mail stores, but it doesn't seem to have any effect on the proxies. I'm using a mix of Dovecot & Courier-IMAP servers as backends. Basically I need to find a way to enforce

Thanks, I thought this might be the case. Is there any solution to enforce this on the proxy? If not, will a feature request be considered anytime soon? I see the proxies as the first line of defense against IMAP "abuse" and I think it's consistent having the same configurable option available on both backends and the proxies. --- Adi Pircalabu On 14-03-2017 20:17, Sami Ketola

Hi, mail_max_userip_connections is only enforced at the backend level. The setting has no effect on proxy. If you want to force the limit then you can only do it in the backend. Sami > On 9 Mar 2017, at 12.05, Adi Pircalabu <adi at ddns.com.au> wrote: > > Quick follow-up: updated the proxies to 2.2.28, but I still couldn't find a way to limit the inbound IMAP connections per

Hello, I'm using Dovecot 2.2.30 with Pideonhole 0.4.18 and I'm having some problems, perhaps someone can give an hint on how to solve them. When I try to create a folder in the toplevel directory of a shared mailbox, i get a "permission denied" although I have the rights, example: 1.doveadm -f table acl rights -u bob at example.com shared/bill at example.com Rights lookup

CentOS Errata and Security Advisory 2015:1664 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2015-1664.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5b8a3475f1de423e1594ded04c09ec460cdb77ce169b84ff6baeff83c0a98d59 nss-3.19.1-1.el5_11.i386.rpm

https://bugzilla.netfilter.org/show_bug.cgi?id=1664 Pablo Neira Ayuso <pablo at netfilter.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #4 from Pablo Neira Ayuso <pablo at netfilter.org> --- (In reply to Pablo Neira

Hello, I am installing Two Node cluster when I automount the file systems I am getting o2net_connect_expired error and it is not mounting the cluster filesystems if I mount the cluster file systems manually as mount -a it is mounting the file systems without any issues. 1.If I bring Node1 up with Node2 to down cluster file system is automounting fine without any issues. 2.I checked the

There appears to be a mild bug, or at least a deficiency, in rnorm. The bug becomes apparent when one looks at extremes of the squares of the values generated by rnorm; rnorm is not generating quite enough extreme values. The R version that I am using is 1.4.1; I never got around to installing 1.5.0, and now since 1.5.1 is about to come out .... However, checking the 1.5.0 release notes

I'm running Dovecot as proxy in front of some IMAP/POP3 Dovecot & Courier-IMAP servers and in the last couple of days I've been seeing a lot of imap-login crashes (signal 11) on both 2.2.18 and 2.2.25, all SSL related. The following backtraces are taken running 2.2.25, built from source on a test system similar to the live proxy servers. OS: CentOS 6.8 64bit Packages: