Am 15.05.2014 um 11:22 schrieb Leon Fauster leonfaus...@googlemail.com:
Am 15.05.2014 um 07:23 schrieb Eero Volotinen eero.voloti...@iki.fi:
2014-05-12 21:13 GMT+03:00 James Hogarth james.hoga...@gmail.com:
Remember to be especially aware if you have systems that can potentially
have code
Am 15.05.2014 um 07:23 schrieb Eero Volotinen eero.voloti...@iki.fi:
2014-05-12 21:13 GMT+03:00 James Hogarth james.hoga...@gmail.com:
Remember to be especially aware if you have systems that can potentially
have code uploaded and run (ftp to httpd vhost or improper php config and
file
On 05/15/2014 09:22 PM, Leon Fauster wrote:
cite: This issue does affect the versions of the Linux kernel packages as
shipped
with Red Hat Enterprise Linux 6.2 AUS, Red Hat Enterprise Linux 6.3 EUS and
Red Rat
Enterprise MRG 2, and we are currently working on corrected kernel packages
Am 15.05.2014 um 12:31 schrieb Peter pe...@pajamian.dhs.org:
On 05/15/2014 09:22 PM, Leon Fauster wrote:
cite: This issue does affect the versions of the Linux kernel packages as
shipped
with Red Hat Enterprise Linux 6.2 AUS, Red Hat Enterprise Linux 6.3 EUS and
Red Rat
Enterprise MRG 2,
On 12/05/14 22:11, Keith Keller wrote:
On 2014-05-12, Akemi Yagi amy...@gmail.com wrote:
According to the upstream BZ 1094232, there is a patch from kernel.org:
https://git.kernel.org/cgit/linux/kernel/git/gregkh/tty.git/commit/?h=tty-linusid=4291086b1f081b869c6d79e5b7441633dc3ace00
This issue does not affect the versions of Linux kernel packages as
shipped with Red Hat Enterprise Linux 6.4 EUS and Red Hat Enterprise Linux
6, because they include backport of upstream commit c56a00a165 that
mitigates this issue.
2014-05-12 21:13 GMT+03:00 James Hogarth
On 12 May 2014 22:15, Keith Keller kkel...@wombat.san-francisco.ca.us
wrote:
Actually, I was wondering about mitigation along the lines of
blacklisting a module, tuning a sysctl parameter, or some other
mitigation that wouldn't require a new kernel. Perhaps such mitigation
isn't even possible
Am 12.05.2014 um 20:58 schrieb Akemi Yagi amy...@gmail.com:
On Mon, May 12, 2014 at 11:23 AM, Keith Keller
Are there any mitigation steps we can take? I've chased down some of
the links looking for any, but haven't had success yet.
According to the upstream BZ 1094232, there is a patch from
On Tue, May 13, 2014 at 2:05 AM, Leon Fauster
leonfaus...@googlemail.com wrote:
Am 12.05.2014 um 20:58 schrieb Akemi Yagi amy...@gmail.com:
On Mon, May 12, 2014 at 11:23 AM, Keith Keller
Are there any mitigation steps we can take? I've chased down some of
the links looking for any, but
Remember to be especially aware if you have systems that can potentially
have code uploaded and run (ftp to httpd vhost or improper php config and
file ownership/permissions).
This does not affect el5 ... an el6 update is pending.
https://access.redhat.com/security/cve/CVE-2014-0196
On 2014-05-12, James Hogarth james.hoga...@gmail.com wrote:
This does not affect el5 ... an el6 update is pending.
https://access.redhat.com/security/cve/CVE-2014-0196
Are there any mitigation steps we can take? I've chased down some of
the links looking for any, but haven't had success yet.
On Mon, May 12, 2014 at 11:23 AM, Keith Keller
kkel...@wombat.san-francisco.ca.us wrote:
On 2014-05-12, James Hogarth james.hoga...@gmail.com wrote:
This does not affect el5 ... an el6 update is pending.
https://access.redhat.com/security/cve/CVE-2014-0196
Are there any mitigation steps we
On 2014-05-12, Akemi Yagi amy...@gmail.com wrote:
According to the upstream BZ 1094232, there is a patch from kernel.org:
https://git.kernel.org/cgit/linux/kernel/git/gregkh/tty.git/commit/?h=tty-linusid=4291086b1f081b869c6d79e5b7441633dc3ace00
Actually, I was wondering about mitigation along
13 matches
Mail list logo
