Thank you for fixing 64-bit sudo.

It seems to be working well.

I did discover a few things:

For Kerberos authenticated AIX accounts, I had to add "program_64 = /usr/lib/security/KRB5_64" to the KRB5 stanza in /etc/methods.cfg before sudo_64 worked.  It was giving the following error message: "sudo_64: you do not exist in the passwd database"

It is important to note that sudo_32 and sudo_64 do not seem to share cached credentials in timestamps. For example,

$ PS1='$ '
$ /opt/freeware/bin/sudo -k
$ /opt/freeware/bin/sudo_32 -k
$ /opt/freeware/bin/sudo_64 -k
$ /opt/freeware/bin/sudo_32 date -u
Password:
Tue Oct 27 17:51:31 UTC 2020
$ /opt/freeware/bin/sudo_32 date -u
Tue Oct 27 17:51:39 UTC 2020
$ /opt/freeware/bin/sudo_64 date -u
Password:
Tue Oct 27 17:51:49 UTC 2020
$ /opt/freeware/bin/sudo_32 date -u
Tue Oct 27 17:51:53 UTC 2020
$ /opt/freeware/bin/sudo_64 -k
$ /opt/freeware/bin/sudo_32 date -u
Tue Oct 27 17:52:04 UTC 2020
$ ls -ld /opt/freeware/bin/sudo | awk '{print $NF}'
sudo_32
$ rpm -q sudo
sudo-1.8.31p1-2.ppc
$

Notice when sudo_64 and sudo_32 prompt for a password in the above example and which versions the "-k" (--reset-timestamp) was used from.

The "-K" (--remove-timestamp) does seem to clear cached credentials for both sudo_32 and sudo_64.  For example,

$ sudo_32 date -u
Password:
Tue Oct 27 19:24:49 UTC 2020
$ sudo_64 -K
$ sudo_32 date -u
Password:
Tue Oct 27 19:25:05 UTC 2020
$