From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: beep 1.3 -- security update
Date: Fri, 06 Apr 2018 08:58:43 +0200 [thread overview]
Message-ID: <016cb11b-6d3b-8e66-3db8-21a31b9b8d0f@ipfire.org> (raw)
In-Reply-To: <1522946670.1009312.99.camel@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1581 bytes --]
Hi,
Thanks for the link!
Just to be sure that I got your point:
I found two relevant links.
https://src.fedoraproject.org/cgit/rpms/beep.git/commit/?id=d37578b06ad366a4b4873afe027fe1c06c9782df
and
https://src.fedoraproject.org/cgit/rpms/beep.git/commit/?id=bafa252a73556eaba1d496d69b3cb32261dec78b
Since I wasn't quite sure right away in which order these
patches should be applied, I oriented myself on the file numbering:
0001-Fixed-Makefile.patch
0002-Add-more-error-detection.patch
0004-also-catch-SIGTERM-for-stopping-the-beep.patch
0005-Make-build-install-more-user-and-packaging-friendly.patch
0006-Preserve-file-modification-time-on-install.patch
0007-Fix-identation-if-brace-error.patch
0008-Apply-CVE-2018-0492-from-Debian-package.patch
All patches apply, building seems to be ok.
Is this what you meant?
Best,
Matthias
On 05.04.2018 18:44, Michael Tremer wrote:
> Hi,
>
> I have heard that some people where a bit unhappy with the proposed patch.
>
> Fedora has some fixes for that patch here:
> https://src.fedoraproject.org/cgit/rpms/beep.git
>
> We should probably use Fedora's version.
>
> -Michael
>
> On Thu, 2018-04-05 at 18:39 +0200, Matthias Fischer wrote:
>> 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 prev parent reply other threads:[~2018-04-06 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 16:39 Matthias Fischer
2018-04-05 16:44 ` Michael Tremer
2018-04-06 6:58 ` Matthias Fischer [this message]
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=016cb11b-6d3b-8e66-3db8-21a31b9b8d0f@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