http://blog.gmane.org/gmane.comp.video.graphicsmagick.announce hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/108 <pre>GraphicsMagick 1.3.15 is now available. This release fixes several bugs and adds a number of new features. This release is binary compatible with all previous 1.3.X releases, however, please read the change notes since there is a change in behavior from previous releases. Please visit http://www.graphicsmagick.org/ to learn more about GraphicsMagick, or visit https://sourceforge.net/projects/graphicsmagick/files/ to download GraphicsMagick from SourceForge. The following are the changes in this release: Security Fixes: * Libpng in Windows build is updated to 1.5.10 release. Provides a fix for CVE-2011-3048. Bug fixes: * PNG - fixed problem with bit depth when the encoder decides to write RGBA instead of indexed PNG. * Fixed some temporary file leaks which were caused by the temporary file name being automatically extended to include a scene number, and therefore fail to be deleted. New Features: * Added '+noise random' and '-operator noise-random' to 'conver</pre> Bob Friesenhahn 2012-04-28T21:26:26 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/107 <pre>GraphicsMagick 1.3.14 is now available. This is primarily a bug-fix release. The only new features are that MagickExtentImage() is added to the Wand API, and the Mamiya Photo RAW "MEF" format is now supported. The Despeckle algorithm (-despeckle) is many times faster now. In my experience, this is a quite worthy agorithm since it does well at removing noise without making the image blurry. Now it is less painful to use. Users of the Windows package should update as soon as possible since the included libpng incorporates a critial security fix. The GraphicsMagick web site is at "http://www.graphicsmagick.org/". The news page which describes the details of the release is at "http://www.graphicsmagick.org/NEWS.html". Please report any bugs you may encounter. Bob </pre> Bob Friesenhahn 2012-02-26T02:17:43 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/106 <pre>The GraphicsMagick development snapshots at ftp://ftp.graphicsmagick.org/pub/GraphicsMagick/snapshots/ have been updated. Most importantly, the Windows install packages now include libpng 1.5.9, which fixes the dire CVE-2011-3026 buffer overrun bug. Libtiff 4.0.1 and zlib 1.2.6 are also included. Please test the snapshots and report any bugs so that the next formal release can be as solid as possible. Thanks, Bob </pre> Bob Friesenhahn 2012-02-19T00:57:58 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/105 <pre>GraphicsMagick 1.3.13 is now available. The 1.3.13 release is API and ABI compatible with all previous 1.3.X releases and is therefore a stable drop-in upgrade. Many bugs are fixed, including some which caused deadlock or a crash. Some new features which may be most interesting: * EXIF profiles are preserved when writing JPEG files. * The benchmark facility is improved and supports a -stepthreads option to benchmark a command with varying numbers of threads. * Support added for netpbm PAM format. * BigTIFF support added for Windows builds (via libtiff 4.0) * Most Windows "delegate" libraries updated to lastest version. There are far too many changes to list here, please visit http://www.graphicsmagick.org/NEWS.html for the full list of changes. Visit the GraphicsMagick web site at http://www.graphicsmagick.org/ to read about GraphicsMagick or to download the new release. Bob </pre> Bob Friesenhahn 2011-12-25T16:11:43 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/104 <pre>The GraphicsMagick CVS repository has now been transformed to use Mercurial instead. The old CVS repository remains alive, but is now read-only. Due to bandwith constraints (Mercurial requires cloning the whole repository), the stable Mercurial repository is hosted at SourceForge. In my testing, I was able to clone the repository in about four seconds across a broadband (DSL) connection. Please see the page at http://www.graphicsmagick.org/Hg.html for more information. Let me know about any issues you may encounter. Bob </pre> Bob Friesenhahn 2011-05-30T22:25:25 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/103 <pre>Normally I would not announce new GraphicsMagick Windows snapshot builds but the last set built was back on September 21st 2010 so new ones are a notable event. Snapshots may be downloaded from ftp://ftp.graphicsmagick.org/pub/GraphicsMagick/snapshots/ The changes since September 21st (or whatever you may be using) can be seen via the GraphicsMagick ChangeLogs at http://www.graphicsmagick.org/Changes.html Thanks, Bob </pre> Bob Friesenhahn 2011-02-20T21:24:23 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/102 <pre>GraphicsMagick 1.3.12 is now released. This release fixes a number of bugs. Most significantly, use of GraphicsMagick as a filter was broken by the 1.3.10 release. Windows users should install this version in order to avoid possible exposure to DOS due to well-crafted PNG files. Download the release from SourceForge via "https://sourceforge.net/projects/graphicsmagick/files/" or visit the web site at "http://www.graphicsmagick.org/". The following are the changes since the 1.3.11 release: Security Fixes: * Updated libpng Windows sources to 1.2.43 in order to resolve CVE-2010-0205 as it pertains to the GraphicsMagick Windows build. Bug fixes: * Filter mode (write to stdout) was completely broken. * Should now compile with libpng 1.4. * Windows PerlMagick build identified itself as the wrong version. New Features: * None Feature improvements: * None Performance Improvements: * None Behavior Changes: * DCX output format is only written on request. Previousl</pre> Bob Friesenhahn 2010-03-08T21:05:02 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/101 <pre>GraphicsMagick 1.3.10 is now available. This release fixes a few bugs discovered in the 1.3.9 release. Download the release from "https://sourceforge.net/projects/graphicsmagick/files/" or visit the web site at "http://www.graphicsmagick.org/". The following are the changes in this release: Security Fixes: * None Bug fixes: * +adjoin was not working correctly for the case when only one image frame is present. With +adjoin and writing one frame to "foo%d.jpg" it was outputting "foo%d.jpg" rather than "foo0.jpg". * When drawing paths, memory allocation for the points was much larger than it needed to be (patch by Vladimir Lukianov). New Features: * None Feature improvements: * None Performance Improvements: * None Behavior Changes: * To reiterate the change which first appeared in 1.3.9, there is no longer an implicit +adjoin if the output file name happens to contain a %d sequence, or there are multiple frames and the output file format on</pre> Bob Friesenhahn 2010-02-10T23:07:40 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/100 <pre>GraphicsMagick 1.3.9 is now released. This is a bug-fix release. Please download the release from "https://sourceforge.net/projects/graphicsmagick/files/" or visit the web site at "http://www.graphicsmagick.org/". The following are the changes since the 1.3.8 release: Security Fixes: * None Bug fixes: * Fix "double free" error when using gm import -frame. * XPM does not support RGBA color syntax, so return RGB instead. * The display '-update' option was only working in conjunction with the '-delay' option with a delay setting of 2 or greater. * For formats which support multiple frames, output with +adjoing to filenames containing a scene specification (e.g. foo%02d.tiff) was resulting in wrong output file names. * -convolve was crashing rather than reporting an error. * Fixed crash if the number of OpenMP threads was reduced from the original value via '-limit threads' or omp_set_num_threads(). * -blur was not blurring the opacity channel for solid-</pre> Bob Friesenhahn 2010-02-04T23:08:20 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/99 <pre>This email only applies to those using the GraphicsMagick C or C++ APIs. Command line utility, PerlMagick, and TclMagick users should feel free to ignore this. As of the GraphicsMagick 1.3.8 release, it is absolutely required to invoke the InitializeMagick() function before using the C or C++ APIs. This function has always been part of GraphicsMagick (and recommended to be used) but it was often believed to not be necessary since the library usually worked without invoking it. This absolute requirement is now imposed in order to improve thread safety and efficiency. Failure to invoke InitializeMagick() will surely lead to either a thrown assertion (if assertions are enabled) or an immediate crash. InitializeMagick() may be invoked any number of times so if you are not sure if the library is initialized, then simply invoke it again. If you are responsible for updating GraphicsMagick, please make sure that any programs or libraries using the GraphicsMagick APIs are invoking InitializeMagick().</pre> Bob Friesenhahn 2010-01-27T00:32:19 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/98 <pre>GraphicsMagick 1.3.8 is now released. This will be the last release which is based CVS HEAD development. Subsequent 1.3.X releases will be to fix bugs, or to selectively update individual algorithms. Development on CVS HEAD really will be for 1.4. Visit the GraphicsMagick web site at "http://www.GraphicsMagick.org/" for project details, and download release files from SourceForge at "https://sourceforge.net/projects/graphicsmagick/files/". The following are the improvements in 1.3.8 since the 1.3.7 release. Please be sure to read the "Behavior Changes" section since there are more significant changes than normal: Security Fixes: * Fix for CVE-2009-1882 "Integer overflow in the XMakeImage function". * Fix lockup due to hanging in loop while parsing malformed sub-image specification (SourceForge issue 2886560). * Libltdl: Updated libtool to 2.2.6b in order to fix security issue. Resolves CVE-2009-3736 as it pertains to GraphicsMagick. Bug fixes: * -convolve, -recolor</pre> Bob Friesenhahn 2010-01-21T23:26:38 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/97 <pre>GraphicsMagick 1.2.10 is now available. This is a maintenance release for the 1.2 stable branch. This is expected to be the last release from the 1.2 branch since 1.2 was originally released on April 29, 2008 and most users will be interested in the 1.3 releases. Please visit the GraphicsMagick web site at http://www.GraphicsMagick.org/ to learn more or to download the release. The following are the changes in this release compared with the 1.2.9 release: Security Fixes: * Fix for CVE-2009-1882 "Integer overflow in the XMakeImage function". * Eliminate lockup due to hanging in loop while parsing malformed sub-image specification (SourceForge issue 2886560). * libltdl: Update libltdl to 2.2.6b in order to fix security issue. Resolves CVE-2009-3736 as it pertains to GraphicsMagick. Bug fixes: * The pixel cache was not working properly for large pixel cache files (&gt;2GB) under Linux. This limited the maximum image size which could be handled by a 32-bit appli</pre> Bob Friesenhahn 2010-01-07T01:57:54 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/96 <pre>Typo3 users who started to experience problems with GraphicsMagick (i.e. GM hangs, consuming 100% CPU) should pay attention to this Typo3 bug entry: http://bugs.typo3.org/view.php?id=12341 A bug in a security fix for Typo3 revealed a bug in GraphicsMagick. This GraphicsMagick bug will be resolved in the next GraphicsMagick release, and has been fixed for several weeks in the development snapshots. For those trying to secure file names for modern GraphicsMagick, it is worth noting that file names may be written (in a secure fashion) to a text file which is then specified with a '&lt; at &gt;' prefix. The file name is then read from the file specified. This avoids the need to pass potentially dangerous file names via the system command shell. Bob -- Bob Friesenhahn bfriesen&lt; at &gt;simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ ------------------------------------------------------------------------------ This SF.Net email is spons</pre> Bob Friesenhahn 2009-12-21T18:11:49 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/94 <pre>There is a potential security exploit with certain configurations of the Unix/MinGW/Cygwin "modules" build of GraphicsMagick. The issue is in libltdl rather than GraphicsMagick, but certain build configurations of GraphicsMagick expose the potential exploit. Some operating systems will still be reasonably secure while others are quite risky. If this command produces no output then you are likely ok: gm -version | grep with-modules | grep disable-static If it does output a line of text then there may be a security risk. To be safe from the risk while using a modules build then make sure that GraphicsMagick is configured with these options: --enable-shared --disable-static --with-modules People using really anchient versions of GraphicsMagick with terse 'gm -version' output will need to use other means to see if --disable-static was used. Thanks, Bob -- Bob Friesenhahn bfriesen&lt; at &gt;simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.Gra</pre> Bob Friesenhahn 2009-11-06T00:35:17 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/93 <pre>The benchmark page at http://www.graphicsmagick.org/benchmarks.html is now updated to reflect latest GraphicsMagick and ImageMagick. Fans of GraphicsMagick will be very pleased, and followers of ImageMagick, not so much at all. Bob -- Bob Friesenhahn bfriesen&lt; at &gt;simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ ------------------------------------------------------------------------------ Come build with us! The BlackBerry&amp;reg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9&amp;#45;12, 2009. Register now&amp;#33; http://p.sf.net/sfu/devconf </pre> Bob Friesenhahn 2009-09-21T03:23:06 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/92 <pre>GraphicsMagick 1.3.7 is now available. This release is both a feature and bug-fix release. The release was hastened due to a corruption bug discovered with embedded profiles in JPEG files. Regardless, there are many bug fixes, and many new/improved features as well. Learn more about GraphicsMagick at "http://www.graphicsmagick.org/". Download the release from "http://sourceforge.net/projects/graphicsmagick/files/". The following are the improvements in GraphicsMagick since the previous 1.3.6 release: Security Fixes: * PCX: Detect improper rows, columns, or depth. Fixes CVE-2008-1097 "Memory corruption in ImageMagick's PCX coder". * DrawDashPolygon: Avoid a crash which sometimes occured with tiny polygons. Bug fixes: * JPEG: Profile chunks need to be concatentated in order to build the whole profile. This was not working so embedded profiles larger than 32K or maybe 64K were being corrupted. This bug was introduced in GraphicsMagick 1.2. * Meta: Fix mem</pre> Bob Friesenhahn 2009-09-17T23:23:06 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/91 <pre>GraphicsMagick 1.2.9 (source code only) is now released. This is a critical bug fix release to the 1.2.X release series. If you are already using a 1.2.X release, then you should update to this release, unless you were planning to upgrade to 1.3.X. GraphicsMagick 1.3.7 should be released within the next few days. Visit http://www.graphicsmagick.org/ to learn more about GraphicsMagick. The following are the changes in this release since 1.2.8: Security Fixes: * None Bug fixes: * Large embedded profiles (&gt;32k, &gt;64K, depending on writing software) read from JPEG files were being corrupted. This problem originated in GraphicsMagick 1.2. Feature improvements: * None Performance improvments: * None Bob -- Bob Friesenhahn bfriesen&lt; at &gt;simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ ------------------------------------------------------------------------------ Come build with us! The BlackBerry&amp;reg; </pre> Bob Friesenhahn 2009-09-16T22:37:41 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/90 <pre>Today I learned that GraphicsMagick 1.2 and later corrupt ICC profiles retrieved from JPEG files. Large ICC profiles are broken up into smaller chunks when saved to JPEG files which need to be re-assembled when the JPEG file is read. Starting with GraphicsMagick 1.2 (1.1.X are fine), this re-assembly was not done correctly. Small ICC profiles (&lt; 32-64K bytes depending on the writing software) pass through without problems. Luckily, most files do seem to use small profiles. GraphicsMagick 1.2.9 and 1.3.7 will include fixes for this problem. A source patch to coders/jpeg.c is included for those who have source code and need to fix the problem ASAP. Bob -- Bob Friesenhahn bfriesen&lt; at &gt;simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/Index: coders/jpeg.c =================================================================== RCS file: /GraphicsMagick/GraphicsMagick/coders/jpeg.c,v retrieving revision 1.242.2.1 retrieving revi</pre> Bob Friesenhahn 2009-09-16T20:44:25 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/89 <pre>After making a 1.3.7 release based on CVS HEAD development code, I plan to put the 1.3 branch into "security and bug fixes" maintenance mode. I would like to change the GraphicsMagick license to be the true MIT License text (as described at http://www.opensource.org/licenses/mit-license.php) rather than the MIT look-alike license currently used. It is within our right to do this since the existing license text provides for sublicensing, and of course GraphicsMagick Group applied the current license. Using the true MIT license gains Open Source Initiative approval, and blessings from other organizations as well. We can't change existing licenses covering code we didn't write but the existing licenses which provide for sublicensing then effectively become covered by the MIT license. For the Windows build (and starting in the the 1.4 release cycle), I would like to eliminate any dependence on proprietary C++ class libraries (ATL and MFC). This will result in the elimination of "gmdisplay" and</pre> Bob Friesenhahn 2009-09-04T17:47:40 http://comments.gmane.org/gmane.comp.video.graphicsmagick.announce/88 <pre>GraphicsMagick 1.2.8 is now available. This is a security and bug-fix release to the legacy stable code on the 1.2 release branch. It is intended for those who must use a 1.2 version. See http://www.graphicsmagick.org/ for more information on GraphicsMagick. The following changes (since the 1.2.7 release) are included in this release: Security Fixes: * BMP: Fix assertion thrown for BMP files with negative image height values. Resolves SF issue 2523536 "bug in bmp coder". * DIB: Fix assertion thrown for DIB files with negative image height values. * PCX: Detect improper rows, columns, or depth. Fixes CVE-2008-1097 "Memory corruption in ImageMagick's PCX coder". * SVG/rendering: Avoid access beyond end of array. Resolves SourceForge issue 2832125 "Crash on SVG conversion". * Random number generator initialization was insufficient, leading * to predictable temporary file names. Bug fixes: * DPX: Fix leak of chroma image when subsampling to 4:2:2. *</pre> Bob Friesenhahn 2009-09-04T16:57:18 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.comp.video.graphicsmagick.announce