On Fri, Jan 11, 2019 at 12:05:16AM +0100, Florian Zieboll wrote:
> On Thu, 10 Jan 2019 14:02:00 -0800
> Rick Moen wrote:
>
> > [insert ironic comment here.]
>
>
> Surprising details from the original report:
>
> | CVE-2018-16864 was introduced in April 2013 (systemd v203) and became
> |
On 2019-01-10 17:22, Joel Roth via Dng wrote:
Rick Moen wrote:
[insert ironic comment here.]
- Forwarded message from Bobbie Sellers
-
Subject: [sf-lug] systemd memory corruption...
Given the size of the code base and the attraction of the huge number
of
of systemd
Rick Moen wrote:
> [insert ironic comment here.]
>
> - Forwarded message from Bobbie Sellers
> -
> Subject: [sf-lug] systemd memory corruption...
Given the size of the code base and the attraction of the huge number of
of systemd installations, I anticipate an unending supply of
On Thu, 10 Jan 2019 14:02:00 -0800
Rick Moen wrote:
> [insert ironic comment here.]
Surprising details from the original report:
| CVE-2018-16864 was introduced in April 2013 (systemd v203) and became
| exploitable in February 2016 (systemd v230).
and
| CVE-2018-16865 was introduced in
[insert ironic comment here.]
- Forwarded message from Bobbie Sellers -
Date: Thu, 10 Jan 2019 13:41:09 -0800
From: Bobbie Sellers
To: SF-LUG
Subject: [sf-lug] systemd memory corruption...
hi LUGers,
Not necessary but present in some systems.
Read about it below.
