Changelog for sudo: 1.9.17p1 -> 1.9.17p2 ============================================================ Merge sudo 1.9.17p2 from branch 'main' into sudo-1.9 [d1b48c651] * configure, configure.ac: Fix check for which man page type to use with nroff Fixes a bug where configure would use *.man instead of *.mdoc on systems without mandoc. Bug #1077. [aa2498e46] * plugins/sudoers/log_client.c: client_msg_cb: make warning match the function that failed [f73162df3] 2025-07-23 Todd C. Miller <Todd.Miller@sudo.ws> * NEWS, configure, configure.ac: Sudo 1.9.17p2 [f0e1a5ca3] * plugins/sudoers/match_command.c, plugins/sudoers/match_digest.c: digest_matches: plug fd leak on snprinf() failure [26a1a7529] 2025-07-21 Todd C. Miller <Todd.Miller@sudo.ws> * etc/sudo-logsrvd.pp, etc/sudo-python.pp, etc/sudo.pp, scripts/mkpkg: Add a way to override pp_rpm_arch when building rpms This will be used to build x86_64_v2 packages for Alma Linux. [55d3c99c4] * configure, configure.ac: Fix check for which man page type to use with nroff Fixes a bug where configure would use *.man instead of *.mdoc on systems without mandoc. [2dc10cfbd] * plugins/sudoers/timestamp.c: ts_write: call lseek after fruncate on short write We need to make sure the file position is reset to the old EOF on error. [8e7e0e23f] 2025-07-20 Todd C. Miller <Todd.Miller@sudo.ws> * src/exec_ptrace.c: ptrace_readv_string: quiet sign-compare warning [fac2a49e7] * src/exec_ptrace.c: ptrace_readv_string: properly handle reads of more than one page When the intercept and intercept_verify options are enabled and either argv[] or envp[] contains a string larger than the page size (usually 4096), ptrace_readv_string() would fill the buffer with mutiple copies of the same string. Fixes GitHub issue #453. [2e93eabed] 2025-07-14 Todd C. Miller <Todd.Miller@sudo.ws> * src/exec_pty.c: revoke_pty: use killpg() not kill() to send HUP to the process group Also make sure we never call killpg(-1, SIGHUP), which would send SIGHUP to process 1 (init). It is possible for cmnd_pid to be -1 in certain error conditions where sudo killed the command itself. This may explain GitHub issue #458. [fb208d383] 2025-07-08 Todd C. Miller <Todd.Miller@sudo.ws> * etc/sudo-logsrvd.pp, etc/sudo-python.pp, etc/sudo.pp, scripts/pp: Don't assume RHEL major version is only a single digit Fixes handling of RHEL 10 and higher. [e5d953f33] * plugins/sudoers/visudo.c: visudo: create temporary file as mod 0600 not 0700 This was due to a typo in the mode field when the temporary file was created. Noticed by Bjorn Baron of the sudo-rs project. [1c254b330] 2025-06-30 Todd C. Miller <Todd.Miller@sudo.ws> * Makefile.in: We now build sudo releases from git, not mercurial [cb4e26734] 2025-06-28 Todd C. Miller <Todd.Miller@sudo.ws> * NEWS, configure, configure.ac: (From OE-Core rev: 76b98657e3dc9da01a746deb7b9d08cb84ba44b6) Signed-off-by: Daniel Turull <daniel.turull@ericsson.com> (cherry picked from commit 12e9ba655153a9cb7c2b79cf52a2300e19634dcf) Signed-off-by: Yoann Congal <yoann.congal@smile.fr> Signed-off-by: Paul Barker <paul@pbarker.dev>
Poky
Poky is an integration of various components to form a pre-packaged build system and development environment which is used as a development and validation tool by the Yocto Project. It features support for building customised embedded style device images and custom containers. There are reference demo images ranging from X11/GTK+ to Weston, commandline and more. The system supports cross-architecture application development using QEMU emulation and a standalone toolchain and SDK suitable for IDE integration.
Additional information on the specifics of hardware that Poky supports is available in README.hardware. Further hardware support can easily be added in the form of BSP layers which extend the systems capabilities in a modular way. Many layers are available and can be found through the layer index.
As an integration layer Poky consists of several upstream projects such as BitBake, OpenEmbedded-Core, Yocto documentation, the 'meta-yocto' layer which has configuration and hardware support components. These components are all part of the Yocto Project and OpenEmbedded ecosystems.
The Yocto Project has extensive documentation about the system including a reference manual which can be found at https://docs.yoctoproject.org/
OpenEmbedded is the build architecture used by Poky and the Yocto project. For information about OpenEmbedded, see the OpenEmbedded website.
Contribution Guidelines
Please refer to our contributor guide here: https://docs.yoctoproject.org/dev/contributor-guide/ for full details on how to submit changes.
Where to Send Patches
As Poky is an integration repository (built using a tool called combo-layer), patches against the various components should be sent to their respective upstreams:
OpenEmbedded-Core (files in meta/, meta-selftest/, meta-skeleton/, scripts/):
- Git repository: https://git.openembedded.org/openembedded-core/
- Mailing list: openembedded-core@lists.openembedded.org
BitBake (files in bitbake/):
- Git repository: https://git.openembedded.org/bitbake/
- Mailing list: bitbake-devel@lists.openembedded.org
Documentation (files in documentation/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-docs/
- Mailing list: docs@lists.yoctoproject.org
meta-yocto (files in meta-poky/, meta-yocto-bsp/):
- Git repository: https://git.yoctoproject.org/cgit/cgit.cgi/meta-yocto
- Mailing list: poky@lists.yoctoproject.org
If in doubt, check the openembedded-core git repository for the content you intend to modify as most files are from there unless clearly one of the above categories. Before sending, be sure the patches apply cleanly to the current git repository branch in question.