mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <post@lespocky.de>
To: PTXdist Developer Mailinglist <ptxdist@pengutronix.de>
Subject: [ptxdist] libpng security update
Date: Mon, 16 Nov 2015 13:54:33 +0100	[thread overview]
Message-ID: <b3a3335326ef35d26ce7ac17c68304c9@localhost> (raw)

Hei hei, 

there are two vulnerabilities in libpng fixed with the versions released
today [1]: CVE-2015-7981, CVE-2015-8126. ptxdist is still on 1.2.50,
however there's a version 1.2.54 in that branch fixing the issues. 

I had a quick look into the differences and stumbled over the patch
coming with ptxdist regarding sysroot handling. It links to a discussion
on sourceforge leading to a 404 now, which actually moved to
https://sourceforge.net/p/libpng/feature-requests/17/ – I see no
solution there, but 1.2.54 has a new parameter for ./configure named
--with-sysroot[=DIR] which probably makes the patch obsolete.

Maybe someone has time for looking into this, should be not too hard to
update to 1.2.54. I would have done, but I'm not sure how to use the
--with-sysroot option in rules/libpng.make … O:-)

Greets
Alex

[1]
http://www.heise.de/security/meldung/Programmbibliothek-libpng-verlangt-nach-Sicherheitsupdates-2922089.html

-- 
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601  D1D5 8FBA 7744 CC87 10D0 ***

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

                 reply	other threads:[~2015-11-16 12:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=b3a3335326ef35d26ce7ac17c68304c9@localhost \
    --to=post@lespocky.de \
    --cc=ptxdist@pengutronix.de \
    /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