[sudo-users] --with-noexec option

[zsilva at br.ibm.com]

Todd,


Follow the output of the command :


Noexec Funcional

$  file /usr/bin/sudo /opt/freeware/libexec/sudo_noexec.so /bin/ksh
/usr/bin/sudo: cannot open for reading
/opt/freeware/libexec/sudo_noexec.so: executable (RISC System/6000) or 
object module not stripped
/bin/ksh: executable (RISC System/6000) or object module
$


Noexec non-funcional

$ file /usr/bin/sudo /opt/freeware/libexec/sudo_noexec.so /bin/ksh
/usr/bin/sudo: 0653-902 Cannot open the specified file for reading.
/opt/freeware/libexec/sudo_noexec.so: executable (RISC System/6000) or 
object module not stripped
/bin/ksh: executable (RISC System/6000) or object module
$

Thanks,

Ziner




From:
"Todd C. Miller" <Todd.Miller at courtesan.com>
To:
Zinerleme Rodrigues da Silva/Brazil/IBM at IBMBR
Cc:
sudo-users at sudo.ws
Date:
23/09/2010 10:24
Subject:
Re: [sudo-users] --with-noexec option



If the /etc/sudoers files are identical on the two machines the
only thing that comes to mind is a 32-bit vs. 64-bit executable
problem.

Sudo sets LDR_PRELOAD on AIX to point to sudo_noexec.so.  This is
correct for 32-bit binaries but will not have an efect on 64-bit
binaries.

Is the output of the following command different on the two hosts?

$ file /usr/bin/sudo /opt/freeware/libexec/sudo_noexec.so /bin/ksh

I would expect the file type to be:

    executable (RISC System/6000) or object module

possibly with "not stripped" at the end.

 - todd