all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: goodoldpaul@autistici.org
To: Marius Bakke <mbakke@fastmail.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 38687@debbugs.gnu.org
Subject: [bug#38687] [PATCH] gnu: Add libtcod.
Date: Thu, 06 Feb 2020 20:16:57 +0000	[thread overview]
Message-ID: <cf1f8eea411d55cdb34b52820175022d@autistici.org> (raw)
In-Reply-To: <87muaftj2u.fsf@devup.no>

Hi Marius and Ludo,
I managed to remove all vendored libraries except for glad.h which seems 
to be some kind of generated glue code for loading OpenGL 
(https://github.com/Dav1dde/glad). In the next two patches I'm adding 
libtcod and it's dependency lodepng.

Guix lint is warning me that lodepng could be affected by 
CVE-2019-17178, but taking a look at 
https://nvd.nist.gov/vuln/detail/CVE-2019-17178 and 
https://nvd.nist.gov/vuln/search/results?adv_search=true&cpe_version=cpe%3a%2fa%3alodev%3alodepng%3a2019-09-28 
seems to indicate that lodepng should  be *not* vulnerable since 
28/09/2019, did I understand correctly?

Please don't hesitate and tell me if anything should done w.r.t. the 
CVE.

Thanks for your patience reviewing this,

Giacomo

  reply	other threads:[~2020-02-06 20:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-20 12:37 [bug#38687] [PATCH] gnu: Add libtcod Giacomo Leidi
2019-12-23 18:37 ` Ludovic Courtès
2020-01-22 11:11   ` goodoldpaul
2020-01-22 18:57     ` Marius Bakke
2020-02-06 20:16       ` goodoldpaul [this message]
2020-02-10 21:10         ` Marius Bakke
2020-02-06 20:17 ` [bug#38687] [PATCH 1/2] gnu: Add lodepng Giacomo Leidi
2020-02-06 20:17   ` [bug#38687] [PATCH 2/2] gnu: Add libtcod Giacomo Leidi
2020-02-10 21:19     ` Marius Bakke
2020-02-16 21:53       ` [bug#38687] " goodoldpaul
2020-02-24 20:56         ` bug#38687: " Marius Bakke
2020-02-10 21:14   ` [bug#38687] [PATCH 1/2] gnu: Add lodepng Marius Bakke

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=cf1f8eea411d55cdb34b52820175022d@autistici.org \
    --to=goodoldpaul@autistici.org \
    --cc=38687@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=mbakke@fastmail.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.