From: 5p9 <5p9@ipfire.org>
To: development@lists.ipfire.org
Subject: FYI: Systemd CVE 2017-9445
Date: Thu, 29 Jun 2017 12:06:09 +0200 [thread overview]
Message-ID: <664B393C-63EB-4391-ACA3-C15EA02B2B2D@ipfire.org> (raw)
In-Reply-To: <000001d2e844$66115dc0$32341940$@apolinarski.de>
[-- Attachment #1: Type: text/plain, Size: 111 bytes --]
Hi,
did you see this Informationen?
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-9445
BG, 5p9
--
next prev parent reply other threads:[~2017-06-29 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-18 15:06 Unbound - rootfile Wolfgang Apolinarski
2017-06-18 16:38 ` Michael Tremer
2017-06-29 10:06 ` 5p9 [this message]
2017-06-29 10:37 ` FYI: Systemd CVE 2017-9445 Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=664B393C-63EB-4391-ACA3-C15EA02B2B2D@ipfire.org \
--to=5p9@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox