Update SUDO 1.9.17P2 With Elimination Of An Error That Sent SIGHUP All Processes

Available new utility release sudo 1.9.17p2 used to organize commands from other users. In the new issue it is eliminated problem, cited with a certain coincidence of the circumstances to send the SUGHUB signal (completion of work) not an advanced process, but all processes in the system.

The problem manifests itself href=”https://github.com/sudo-project/sudo/releases/tag/v1.9.16″> sudo 1.9.16 and and caused in some cases of the Killpg () instead of Kill () to complete the subsidiary () to complete process. Unlike the Kill () function, the Killpg () function sends a signal to the process of processes, but as a group can process values more or equal to 0. When transmitting the negative value of the group, the behavior is not defined and in some systems it can lead to sending the signal with the number 1 (Init) and the completion of all processes in the system. The pseudo-thermalmine (PTY) The team cannot be correctly launched and instead of PID, library functions return the error code -1.
To recall access to the terminal in SUDO, the Revoke_pty function is launched, which uses the PID process of the process of the Killpg function as an identification of the previously returned error code, which leads to the execution of Killpg (-1, sigup). “In addition, Sudo is corrected problem , leading to a failure when intercepting and checking the launched configurations using Intercept and Intercept_verify options in the file Sudoers. In the Linux systems supporting the PTRACE_READV_STRING () function, an emergency completion of processes, the size of the command line arguments or environment variables, which exceeded the size of the memory page (usually 4096 byte).