Hello Michael,
On 16-10-03 12:11:48, Michael Biebl wrote:
> > https://security-tracker.debian.org/tracker/CVE-2016-7796 says all
> > but the version in sid are vulnerable to CVE-2016-7796 and reading
>
> No, sid is not vulnerable. It has been fixed in 231-9
I wrote 'all but the version in sid', E
* Salvatore Bonaccorso:
> There were two CVE assingments for systemd recently, CVE-2016-7795 and
> CVE-2016-7796, and assigned here:
> https://marc.info/?l=oss-security&m=147521835218986&w=2
>
> CVE-2016-7795 is for
>
> https://github.com/systemd/systemd/issues/4234
> https://www.agwa.name/blog/po
Grr, should have proof-read my message :-/
Am 03.10.2016 um 13:31 schrieb Jonathan Wiltshire:
> Hi,
>
> On 2016-10-02 21:36, Michael Biebl wrote:
>> While v215 is not directly affected by this crash (the code to access
>> messages of length=0 was added in v21), the version in unstable still
mess
Hi,
On Mon, Oct 03, 2016 at 12:48:15PM +0200, Florian Weimer wrote:
> * Michael Biebl:
>
> > Dear security team, I'd appreciate your input on bug #839607
>
> It's a bug, and it should be fixed in stable, probably in a point
> update.
Agreed, and fixing via point release seems okay.
> Does this
Hi,
On 2016-10-02 21:36, Michael Biebl wrote:
While v215 is not directly affected by this crash (the code to access
messages of length=0 was added in v21), the version in unstable still
[...]
I would propose to fix this in stable via regular stable update but
I'm not sure I follow; did you m
* Michael Biebl:
> Dear security team, I'd appreciate your input on bug #839607
It's a bug, and it should be fixed in stable, probably in a point
update.
Does this affect other distributions? In this case, it's best to
request a CVE ID on the oss-security list.
Am 03.10.2016 um 12:11 schrieb Michael Biebl:
> Am 03.10.2016 um 08:22 schrieb Wolfgang Karall:
>> Hello Michael,
>>
>> On 16-10-02 22:36:00, Michael Biebl wrote:
>>> The news about systemd crashing when getting a zero sized message
>>> on the notification socket made the rounds recently. While v2
Am 03.10.2016 um 12:11 schrieb Michael Biebl:
> Am 03.10.2016 um 08:22 schrieb Wolfgang Karall:
>> Hello Michael,
>>
>> On 16-10-02 22:36:00, Michael Biebl wrote:
>>> The news about systemd crashing when getting a zero sized message
>>> on the notification socket made the rounds recently. While v2
Am 03.10.2016 um 08:22 schrieb Wolfgang Karall:
> Hello Michael,
>
> On 16-10-02 22:36:00, Michael Biebl wrote:
>> The news about systemd crashing when getting a zero sized message
>> on the notification socket made the rounds recently. While v215 is
>> not directly affected by this crash (the co
Hello Michael,
On 16-10-02 22:36:00, Michael Biebl wrote:
> The news about systemd crashing when getting a zero sized message
> on the notification socket made the rounds recently. While v215 is
> not directly affected by this crash (the code to access messages of
> length=0 was added in v219)
[.
Control: fixed -1 231-9
Am 02.10.2016 um 22:36 schrieb Michael Biebl:
> Package: systemd
> Version: 215-17+deb8u5
> Severity: important
> User: pkg-systemd-maintain...@lists.alioth.debian.org
> Usertags: jessie-backport
>
> The news about systemd crashing when getting a zero sized message on the
Package: systemd
Version: 215-17+deb8u5
Severity: important
User: pkg-systemd-maintain...@lists.alioth.debian.org
Usertags: jessie-backport
The news about systemd crashing when getting a zero sized message on the
notification socket made the rounds recently.
While v215 is not directly affected by
12 matches
Mail list logo
