From: Alex Vong <alexvong1995@gmail.com>
To: 33933-done@debbugs.gnu.org
Cc: alexvong1995@gmail.com
Subject: bug#33933: [PATCH 0/4] gnu: libextractor: Fix CVE-2018-{20430, 20431}.
Date: Fri, 04 Jan 2019 07:42:30 +0800 [thread overview]
Message-ID: <871s5txq8p.fsf@gmail.com> (raw)
In-Reply-To: <20190103182056.GA2707@jasmine.lan> (Leo Famulari's message of "Thu, 3 Jan 2019 13:20:56 -0500")
[-- Attachment #1: Type: text/plain, Size: 705 bytes --]
Leo Famulari <leo@famulari.name> writes:
> On Mon, Dec 31, 2018 at 07:15:42AM +0800, Alex Vong wrote:
>> Tags: security
>>
>> Hello,
>>
>> This patch series mainly fixes the latest CVEs found in libextractor,
>> but it also upgrades other gnunet related packages to their latest
>> version.
>>
>> Please also note that the versioning scheme for guile-gnunet is changed
>> to use that of 'git-version'. Unfortunately, this would break
>> "guix package --upgrade". But I think this change needs to be made at
>> some point anyway, so we may as well do it now.
>
> Thanks, please push :)
Pushed as 1983a9b0a50ff759f2d192d7fa0f7ad0fb1e1384 -
5651e74cc6c1d1b8a2ef1d40e6f14e1123a7de97!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2019-01-03 23:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-30 23:15 [bug#33933] [PATCH 0/4] gnu: libextractor: Fix CVE-2018-{20430, 20431} Alex Vong
2018-12-30 23:18 ` [bug#33933] [PATCH 1/4] gnu: libextractor: Update to 1.8 Alex Vong
2018-12-30 23:18 ` [bug#33933] [PATCH 2/4] gnu: libextractor: Fix CVE-2018-{20430, 20431} Alex Vong
2018-12-30 23:19 ` [bug#33933] [PATCH 3/4] gnu: libmicrohttpd: Update to 0.9.62 Alex Vong
2018-12-30 23:19 ` [bug#33933] [PATCH 4/4] gnu: guile-gnunet: Update to 0.0-1.d12167a Alex Vong
2018-12-30 23:27 ` Alex Vong
2019-01-03 18:20 ` [bug#33933] [PATCH 0/4] gnu: libextractor: Fix CVE-2018-{20430, 20431} Leo Famulari
2019-01-03 23:42 ` Alex Vong [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871s5txq8p.fsf@gmail.com \
--to=alexvong1995@gmail.com \
--cc=33933-done@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).