similar to: CESA-2018:2846 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

Hello, I run CentOS release 6.10 (Final) on a Dell Inspiron M6700. 2.6.32-754.el6.x86_64 boots, and is whaat I am running now none of these, updated ones, won't boot: 2.6.32-754.3.5.el6.x86_64 2.6.32-754.6.3.el6.x86_64 2.6.32-754.9.1.el6.x86_64 2.6.32-754.10.1.el6.x86_64 They all show the same 'symptom',? grub says it is booting that kernel, screen blanks, solid corned in

On 18.11.2019 22.30, Miro Igov via dovecot wrote: > > Hello, I have 2 Dovecot 2.3.8 servers running SSL with valid wildcard > certificates. > > Email clients connect fine, https://www.immuniweb.com/ssl/ tests show > certificates are ok. > > However I can?t make replication work when I add ssl = yes. > > Without ssl it works ok. > > ? > > I added

Solved, thank you. TCPS was the issue. From: Aki Tuomi <aki.tuomi at open-xchange.com> Sent: Wednesday, November 20, 2019 08:54 To: Miro Igov <miro.igov at gmail.com>; dovecot at dovecot.org Subject: Re: Doveadm replicator ssl issues On 18.11.2019 22.30, Miro Igov via dovecot wrote: Hello, I have 2 Dovecot 2.3.8 servers running SSL with valid wildcard certificates. Email

Hello, I have 2 Dovecot 2.3.8 servers running SSL with valid wildcard certificates. Email clients connect fine, https://www.immuniweb.com/ssl/ tests show certificates are ok. However I can't make replication work when I add ssl = yes. Without ssl it works ok. I added verbose_ssl in config and error log shows: dovecot: doveadm(149.x.x.x): Error: SSL handshake failed: SSL_accept()

I have managed to break my system by installing xtables-addons-1.37. Now ipset does not work. "Kernel error received: Invalid argument" I built the addon from source on my centos 6.9 system as per instructions for centos 6. It looks to me that xtables-addons has built and installed a ipset-4 extension due to my kernel: 2.6.32-754.6.3.el6.x86_64 I already had ipset v6.11 installed and

On Jan 29, 2019, at 8:08 PM, RC <cjvijf at gmail.com> wrote: > I run CentOS release 6.10 (Final) on a Dell Inspiron M6700. > > 2.6.32-754.el6.x86_64 boots, and is whaat I am running now > > > none of these, updated ones, won't boot: > > 2.6.32-754.3.5.el6.x86_64 > > 2.6.32-754.6.3.el6.x86_64 > > 2.6.32-754.9.1.el6.x86_64 > >

> On Tuesday, January 29, 2019, 8:08:39 PM EST, RC <cjvijf at gmail.com> wrote: > Hello, > > I run CentOS release 6.10 (Final) on a Dell Inspiron M6700. > > 2.6.32-754.el6.x86_64 boots, and is whaat I am running now > none of these, updated ones, won't boot: > > 2.6.32-754.3.5.el6.x86_64 > 2.6.32-754.6.3.el6.x86_64 > 2.6.32-754.9.1.el6.x86_64 >

Unfortunately, RNGkind is buggy. It will not generate warnings except the full name "Buggy Kinderman-Ramage" is supplied for normal.kind. match.arg is supposed to be called before "==" comparison. ======================================== Shengqiao Li Research Associate The Department of Statistics PO Box 6330 West Virginia University Morgantown, WV 26506-6330

Hi, Our department has detected a bug in the implementation of the Kinderman-Ramage generator for normal random variates in version 1.7.0, which can be seen from the below R session. (Consecutive calls for chisq.test(...) always gives p-values very close to 0.) We have already encountered this bug in version 1.6.2 The error is in file R-1.7.0/src/nmath/snorm.c Here is a patch for this file to

https://bugzilla.mindrot.org/show_bug.cgi?id=2846 Bug ID: 2846 Summary: PermitOpen rule in sshd_config is not case insensitive Product: Portable OpenSSH Version: 7.6p1 Hardware: Other OS: Linux Status: NEW Severity: major Priority: P5 Component: sshd Assignee: unassigned-bugs

> >>> Does some one have problems related to KVM with > >>> kernel-2.6.32-754.3.5.el6.x86_64 ?? > >> > >> Yes, the exact same thing happened here, and I suspect it is related to > >> older cpus that don't get any Spectre/Meltdown updates. > > > > > > Thanks for the feedback. I' was assuming that some kind of > >