mirror of
git://git.openembedded.org/meta-openembedded
synced 2026-05-18 18:41:55 +00:00
85c7e7bda4
Changelog: ========== Security --------- - CVE-2023-32067. High. 0-byte UDP payload causes Denial of Service [12] - CVE-2023-31147. Moderate. Insufficient randomness in generation of DNS query IDs [13] - CVE-2023-31130. Moderate. Buffer Underwrite in ares_inet_net_pton() [14] - CVE-2023-31124. Low. AutoTools does not set CARES_RANDOM_FILE during cross compilation [15] Bug fixes ---------- - Fix uninitialized memory warning in test [1] - Turn off IPV6_V6ONLY on Windows to allow IPv4-mapped IPv6 addresses [2] - ares_getaddrinfo() should allow a port of 0 [3] - Fix memory leak in ares_send() on error [4] - Fix comment style in ares_data.h [5] - Remove unneeded ifdef for Windows [6] - Fix typo in ares_init_options.3 [7] - Re-add support for Watcom compiler [8] - Sync ax_pthread.m4 with upstream [9] - Windows: Invalid stack variable used out of scope for HOSTS path [10] - Sync ax_cxx_compile_stdcxx_11.m4 with upstream to fix uclibc support [11] Signed-off-by: Wang Mingyu <wangmy@fujitsu.com> Signed-off-by: Khem Raj <raj.khem@gmail.com>
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. Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch <remote>' 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>