From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: beep 1.3 -- security update
Date: Thu, 05 Apr 2018 18:39:02 +0200 [thread overview]
Message-ID: <e9e0e326-6dfd-74cf-a503-adc821235e53@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 265 bytes --]
Hi,
just for the records:
Info:
https://www.debian.org/security/2018/dsa-4163
CVE-2018-0492:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-0492
Patch:
https://github.com/johnath/beep/issues/11#issuecomment-378383752
"Devel" is running...
Best,
Matthias
next reply other threads:[~2018-04-05 16:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 16:39 Matthias Fischer [this message]
2018-04-05 16:44 ` Michael Tremer
2018-04-06 6:58 ` Matthias Fischer
2018-04-06 9:03 ` 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=e9e0e326-6dfd-74cf-a503-adc821235e53@ipfire.org \
--to=matthias.fischer@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