libpng-12.58rc01, 1.4.21rc01, 1.5.29rc01, 1.6.32rc01, and 1.7.0beta89 are available

Glenn Randers-Pehrson <[email protected]>
Newsgroups gmane.comp.graphics.png.devel
Message-ID <CA+PdXcs=6BHeoYNzAj7UWTtf985MVTq7MdovEtjn3NbYDgvf9A@mail.gmail.com>
libpng-1..2.58rc01, 1.4.21rc01, 1.5.29rc01, 1.6.32rc01, and 1.70beta89
are available from
https://ftp-osl.osuosl.org/pub/libpng/src/beta/
ftp://ftp-osl.osuosl.org/pub/libpng/src/beta/
http://libpng.download/src/beta/
and from
http://libpng.sf.net

version 1.2.58rc01 [August 19, 2017]
  Check for 0 return from png_get_rowbytes() and added some (size_t) typecasts
    in contrib/pngminus/*.c to stop some Coverity issues (162705, 162706,
    and 162707).

version 1.4.21rc01 [August 19, 2017]
  Check for 0 return from png_get_rowbytes() and added some (size_t) typecasts
    in contrib/pngminus/*.c to stop some Coverity issues (162705, 162706,
    and 162707).

version 1.5.29rc01 [August 19, 2017]
  Check for 0 return from png_get_rowbytes() in contrib/pngminus/*.c to stop
    some Coverity issues (162705, 162706, and 162707).

Version 1.6.32rc01 [August 18, 2017]
  Added a set of "huge_xxxx_chunk.png" files to contrib/testpngs/crashers,
    one for each known chunk type, with length = 2GB-1.
  Check for 0 return from png_get_rowbytes() and added some (size_t) typecasts
    in contrib/pngminus/*.c to stop some Coverity issues (162705, 162706,
    and 162707).
  Renamed chunks in contrib/testpngs/crashers to avoid having files whose
    names differ only in case; this causes problems with some platforms
    (github issue #172).

Version 1.7.0beta89 [August 19, 2017]
  Check for 0 return from png_get_rowbytes() in contrib/pngminus/*.c to stop
    some Coverity issues (162705, 162706, and 162707).

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.