That's perfect. Sensible defaults are always good to have in a software. Many thanks for your kind help, Bob. Best regards, Yog
Hi Bob, This is terrific. Thank you very much. So I can just set the shell's environment variables and it should be fine. Follow up question (I've not actually tried this yet): suppose I set the memory limit, and an image file (genuinely or maliciously) needs more memory than the limit. How is this situation handled when it is processing a batch (or directory) of files and one file in the middle has this problem. Should it skip the problem file and continue, or just stop the whole process? Regards,...
Some of the vulnerabilities with ImageMagick are addressed by use of the policy.xml file. I would like to know if I can do the same thing with GraphicsMagick. In particular, consider the pixel flood attack exploit. This exploit involves specifying an extremely large pixel value in the encoding of the (small/regular sized) image itself, so that when the decoder tries to allocate memory for the entire image, it takes up all the memory and results in a dos attack. It was reported for a different app...