c8e8890991
This upgrade contains a fix for CVE-2024-47175. Changelog: 2.1.1: -pdftops: Use Poppler for a few old Epson laser printers This works around documents being printed off-centre, shifted towards the top right. Affected are printers using epsoneplijs: EPL-5700L, EPL-5800L, EPL-5900L, EPL-6100L, EPL-6200L. -Fixed bugs discovered by static analyzer OpenScanHub Possible buffer overflows, uninitialized memory, format string issues and resource leaks, ... -Fix crash bugs in ppdLoadAttributes() When parsing the "*cupsFilter(2): ..." lines in the PPD file use memmove() instead of strcpy() as the latter does not support handling overlapping memory portions and do not move running pointer beyond the end of the input string. 2.1.0: -Prevent PPD generation based on invalid IPP response Overtaken from CUPS 2.x: Validate IPP attributes in PPD generator, refactor make-and-model code, PPDize preset and template names, quote PPD localized strings. Fixes CVE-2024-47175. 2.1b: -Added support for libcups3 (libcups of CUPS 3.x) With these changes libcupsfilters can be built either with libcups2 (libcups of CUPS 2.x) or libcups3 (libcups of CUPS 3.x). -Prefer PDF again in PPDs for driverless printers PDF works better with finishing, especially combinations of multiple copies, collation, and stapling/binding. -Use 0.5mm as tolerance when comparing page sizes For the PWG two page sizes are considered the same when the dimensions differ no more than 0.5 mm, libppd used too tight tolerances. -PPD generator: Check for required attributes when choosing input format Check for PCLm and PWG the minimum of attributes which we require during PPD generation. -ppdLoadAttributes(): Improve check whether parameters are integer -ppdLoadAttributes(): Fix crash when page size could not get determined -Fix crash if there is no page size for "Custom" -Fix crash when incoming *ptr is NULL -libcups2 compatibility: Use proper CUPS array callback function types Fixed CUPS array function call in libcups2 compatibility layer -Build system: Fix failure to correctly link to zlib Look up zlib properly with pkg-config Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com> Signed-off-by: Khem Raj <raj.khem@gmail.com> |
||
|---|---|---|
| .. | ||
| classes | ||
| conf | ||
| dynamic-layers | ||
| files | ||
| lib/oeqa/selftest/cases | ||
| licenses | ||
| recipes-benchmark | ||
| recipes-bsp | ||
| recipes-connectivity | ||
| recipes-core | ||
| recipes-crypto | ||
| recipes-dbs | ||
| recipes-devtools | ||
| recipes-extended | ||
| recipes-gnome | ||
| recipes-graphics | ||
| recipes-kernel | ||
| recipes-multimedia | ||
| recipes-navigation | ||
| recipes-networking/cyrus-sasl | ||
| recipes-printing | ||
| recipes-security | ||
| recipes-shells | ||
| recipes-support | ||
| recipes-test | ||
| COPYING.MIT | ||
| README.md | ||
| SECURITY.md | ||
meta-oe
This layer depends on:
URI: git://github.com/openembedded/openembedded-core.git branch: master
luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below
pacman -S lib32-gcc-libs lib32-glibc
Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'
When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'
You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch.
Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.
Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI.
Layer maintainer: Khem Raj raj.khem@gmail.com