AIX Open Source

Expand all | Collapse all

sudo-1.9.5p2-1.ppc: Why is symbolic link created to sudo_32, rather than sudo_64?

  • 1.  sudo-1.9.5p2-1.ppc: Why is symbolic link created to sudo_32, rather than sudo_64?

    Posted Wed September 08, 2021 07:44 AM
    Greetings. On AIX 7.1 TL5 SP8:

    # oslevel -s
    7100-05-08-2114
    ​


    I installed sudo-1.9.5p2-1.ppc:

    # yum info sudo
    Installed Packages
    Name        : sudo
    Arch        : ppc
    Version     : 1.9.5p2
    Release     : 1
    Size        : 17 M
    Repo        : installed
    From repo   : AIX_Toolbox
    Summary     : Allows restricted root access for specified users.
    URL         : http://www.sudo.ws
    License     : IBM_ILA
    Description : Sudo (superuser do) allows a system administrator to give certain users (or
                : groups of users) the ability to run some (or all) commands as root while
                : logging all commands and arguments. Sudo operates on a per-command basis.  It
                : is not a replacement for the shell.  Features include: the ability to restrict
                : what commands a user may run on a per-host basis, copious logging of each
                : command (providing a clear audit trail of who did what), a configurable timeout
                : of the sudo command, and the ability to use the same configuration file
                : (sudoers) on many different machines.
    

    During install, a symbolic link gets created to sudo_32.

    # ls -ltr /opt/freeware/bin/sudo
    lrwxrwxrwx    1 root     system            7 Sep  8 06:33 /opt/freeware/bin/sudo -> sudo_32
    ​


    One of our third-party applications that leverages sudo fails unless I manually change the link to sudo_64. 


    Example error:

    Could not load program sudo:
    Could not load module /opt/freeware/lib/libintl.a(libintl.so.8).
    	Dependent module /opt/commvault/Base/libgcc_s.a(shr.o) could not be loaded.
    	The module has an invalid magic number.
    Could not load module sudo_32.

    Is there a specific reason why the RPM is delivered with link to sudo_32, rather than sudo_64?

    Will this link that I changed be overridden by future updates?

    Thank you.

    ------------------------------
    g d
    ------------------------------


  • 2.  RE: sudo-1.9.5p2-1.ppc: Why is symbolic link created to sudo_32, rather than sudo_64?

    Posted Wed September 08, 2021 07:59 AM
    We were shipping only 32bit sudo for a long time. Recently only the 64bit build is added. We decided to keep 32bit as the default one as it is more tested on the field. 
    Probably in the future releases , we can make 64bit as the default. 
    In your case, i don't know why the libgcc_s.a in /opt/commvault/Base/ doesn't have a 32bit shared library. 


    ------------------------------
    Ayappan P
    ------------------------------



  • 3.  RE: sudo-1.9.5p2-1.ppc: Why is symbolic link created to sudo_32, rather than sudo_64?

    Posted Wed September 08, 2021 08:10 AM
    I can also pursue with other vendor, ask them about the 32bit shared library. 
    Changing symbolic link to sudo_64 was fast and easy workaround.
    I can also monitor for any local updates that revert the link, then manage those locally.
    Thanks for the reply.

    ------------------------------
    g d
    ------------------------------