Original Message:
Sent: Mon September 15, 2025 02:14 AM
From: RESHMA KUMAR
Subject: sudo 1.9.17p2
Hi Jeorg
We are able to reproduce this behaviour.
We are debugging the issue and will update this thread with our findings.
------------------------------
RESHMA KUMAR
Original Message:
Sent: Wed September 10, 2025 03:53 AM
From: Joerg Kauke
Subject: sudo 1.9.17p2
Hello Reshma,
do you have any findings on that? Could you reproduce this behavior?
And most important, could you fix it?
Many thanks in advance.
Kind regards
------------------------------
Joerg Kauke
Unix Administrator
COOP Switzerland
Original Message:
Sent: Thu August 28, 2025 11:33 AM
From: RESHMA KUMAR
Subject: sudo 1.9.17p2
Hi Joerg,
Thanks for sharing the logs. We will analyse and get back to you.
------------------------------
RESHMA KUMAR
Original Message:
Sent: Thu August 28, 2025 02:37 AM
From: Joerg Kauke
Subject: sudo 1.9.17p2
Hello Reshma,
as additional info:
Yesterday I decided to install sudo_ids-1.8.31p1-3 for testing.
Now, one day later, everything is still working.
kind regards,
Joerg
------------------------------
Joerg Kauke
Unix Administrator
COOP Switzerland
Original Message:
Sent: Mon August 25, 2025 11:35 AM
From: RESHMA KUMAR
Subject: sudo 1.9.17p2
Hi Joerg,
We tested the following in AIX 7.3 TL3 SP1 using sudo 1.9.17p1.
As user "sudouser",
sudouser # sudo -i
root # who am i
sudouser pts/2 Aug 25 09:26
root # logname
sudouser
The output of "who am i" shows "sudouser" in this case.
Could you please let us know if you are executing any additional steps or configurations?
------------------------------
RESHMA KUMAR
Original Message:
Sent: Fri August 22, 2025 04:33 AM
From: Joerg Kauke
Subject: sudo 1.9.17p2
Hello Kumar,
thanks for the effort.
In the meanwhile we found out, that the problem we have is more complicated.
As sudo_ids-1.9.16p2-1 was working after downgrading, now it is not. Same problem as we had with the latest version before.
Now I updated again to sudo_ids-1.9.17p1-1 and it is working... We are so confused. It's just happening in AIX 7.3 TL3 SP1.
After a while it is not working anymore.
I opened a Ticket at IBM support as well if you want to check that too.
Ticket number: TS020047402
We stopped the whole upgrade process for TL3 now.
Kind regards,
Joerg
------------------------------
Joerg Kauke
Unix Administrator
COOP Switzerland
Original Message:
Sent: Thu August 21, 2025 11:56 PM
From: RESHMA KUMAR
Subject: sudo 1.9.17p2
Hi All,
We are working on sudo 1.9.17p2. It will be available from AIX Toolbox in 1-2 weeks.
------------------------------
RESHMA KUMAR
Original Message:
Sent: Thu August 21, 2025 07:10 AM
From: Joerg Kauke
Subject: sudo 1.9.17p2
Hello Team, hello Roman,
thats what I just to wanna ask for, because we have an issue with sudo_ids-1.9.17p1-1.ppc too.
In in AIX 7.3 TL3 SP1, with this version the "who am i" command is not working properly. We found out, that this version doesn't produce an entry in /var/adm/wtmp after a "sudo -i".
So the "who am i" shows root instead of the logged in user.
In TL1:
root#iduid=0(root) gid=0(system) groups=2(bin),3(sys),7(security),8(cron),10(audit),11(lp)root#who am iuser1 pts/1 Aug 21 10:45root#lognameuser1
in TL3:
root#iduid=0(root) gid=0(system) groups=2(bin),3(sys),7(security),8(cron),10(audit),11(lp)root#who am iroot pts/11root#lognameuser1
This is a part of the truss output:
truss of sudo in TL1:
kioctl(14, 536900678, 0x0FFFFFFFFFFFEE70, 0x0000000000000000) = 0
kioctl(14, 536900679, 0x0FFFFFFFFFFFEDC0, 0x0000000000000000) = 0
kioctl(14, 22529, 0x0FFFFFFFFFFFE848, 0x0000000000000000) = 0
statx("/dev/pts/2", 0x0FFFFFFFFFFFE968, 176, 0) = 0
statx("/dev/pts/2", 0x0FFFFFFFFFFFEDC8, 176, 0) = 0
kopen("/dev/pts/2", O_RDWR|O_NOCTTY) = 15
chown("/dev/pts/2", 0, 4294967295) = 0
kopen("/etc/utmp", O_RDWR|O_CREAT, S_IRUSR|S_IWUSR|S_IRGRP|S_IROTH) = 16
kioctl(16, -2147195266, 0x0FFFFFFFFFFFE8A0, 0x0000000000000000) = 0
kioctl(16, -2147195267, 0x0FFFFFFFFFFFE8A0, 0x0000000000000000) = 0
And here in TL3:
kioctl(14, 536900678, 0x0FFFFFFFFFFFEE70, 0x0000000000000000) = 0
kioctl(14, 536900679, 0x0FFFFFFFFFFFEDC0, 0x0000000000000000) = 0
kioctl(14, 22529, 0x0FFFFFFFFFFFE848, 0x0000000000000000) = 0
statx("/dev/pts/3", 0x0FFFFFFFFFFFE968, 176, 0) = 0
statx("/dev/pts/3", 0x0FFFFFFFFFFFEDC8, 176, 0) = 0
kopen("/dev/pts/3", O_RDWR|O_NOCTTY) = 15
chown("/dev/pts/3", 0, 4294967295) = 0
kopen("", O_RDWR|O_CREAT, S_IRUSR|S_IWUSR|S_IRGRP|S_IROTH) Err#14 EFAULT
_getpid() = 8061372
kopen("", O_RDWR|O_CREAT, S_IRUSR|S_IWUSR|S_IRGRP|S_IROTH) Err#14 EFAULT
socketpair(1, 1, 0, 0x0FFFFFFFFFFFF100) = 0
kfcntl(16, F_SETFD, 0x0000000000000001) = 0
kfcntl(17, F_SETFD, 0x0000000000000001) = 0
kind regards,
Joerg
PS: Version 1.9.16p2-1 is working fine, but with the security issue.
So we would need the new version as soon as possible.
Many thanks in advance.
Kind regards
Joerg
------------------------------
Joerg Kauke
Unix Administrator
COOP Switzerland
Original Message:
Sent: Wed August 20, 2025 10:51 AM
From: Roman Aleksic
Subject: sudo 1.9.17p2
Hello OSS Team,
I ask you kindly to build the latest sudo version 1.9.17p2 because of the following fix:
Fixed a bug introduced in sudo 1.9.16 that could result in sudo sending SIGHUP to all processes on the system in certain rare cases. The bug could manifest if sudo is running a command in a pseudo-terminal, sudo terminates the command due to an internal error, and the user's terminal is revoked. GitHub issue #458. (https://www.sudo.ws/releases/stable/#1.9.17p2)
Even though the bug manifests only in certain rare cases (could not find out more about it) the effect of the bug would certainly be considered "high impact"...
------------------------------
------------------------------
Thanks and regards,
Roman
------------------------------
------------------------------
#AIXOpenSource