ltib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Ltib] LTIB sudo check fails with Sudo version 1.7.2


From: Joe Hershberger
Subject: [Ltib] LTIB sudo check fails with Sudo version 1.7.2
Date: Wed, 1 Sep 2010 18:45:30 -0500

Hi LTIB,

It seems that the format of the output from 'sudo -l' has changed from
Sudo version 1.6.9p17 to Sudo version 1.7.2.  I have 2 build machines,
the newer one is running OpenSuSE 11.2 which comes with Sudo version
1.7.2 and cannot pass the sudo check in LTIB.

The (old) format that ltib expects looks like this:

-----------------------8<----------------------8<----------------------8<----------------------8<------------------------

> sudo -l
User x may run the following commands on this host:
    (ALL) ALL
    (root) NOPASSWD: /bin/rpm
    (root) NOPASSWD: /opt/freescale/ltib/usr/bin/rpm
    (root) NOPASSWD: /opt/ltib/usr/bin/rpm

----------------------->8---------------------->8---------------------->8---------------------->8------------------------

The format that Sudo version 1.7.2 produces looks like this:

-----------------------8<----------------------8<----------------------8<----------------------8<------------------------

> sudo -l
Matching Defaults entries for x on this host:
    always_set_home, env_reset, env_keep="LANG LC_ADDRESS LC_CTYPE
LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES LC_MONETARY
LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME LC_ALL LANGUAGE
    LINGUAS XDG_SESSION_COOKIE", targetpw

User x may run the following commands on this host:
    (ALL) ALL
    (root) NOPASSWD: /bin/rpm, (root) /opt/freescale/ltib/usr/bin/rpm,
(root) /opt/ltib/usr/bin/rpm

----------------------->8---------------------->8---------------------->8---------------------->8------------------------

The new sudo also supports a new listing mode that looks like this:

-----------------------8<----------------------8<----------------------8<----------------------8<------------------------

> sudo -ll
Matching Defaults entries for x on this host:
    always_set_home, env_reset, env_keep="LANG LC_ADDRESS LC_CTYPE
LC_COLLATE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES LC_MONETARY
LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME LC_ALL LANGUAGE
    LINGUAS XDG_SESSION_COOKIE", targetpw

User x may run the following commands on this host:

Sudoers entry:
    RunAsUsers: ALL
    Commands:
        ALL

Sudoers entry:
    RunAsUsers: root
    Commands:
        NOPASSWD: /bin/rpm
    RunAsUsers: root
    Commands:
        /opt/freescale/ltib/usr/bin/rpm
    RunAsUsers: root
    Commands:
        /opt/ltib/usr/bin/rpm

----------------------->8---------------------->8---------------------->8---------------------->8------------------------

Naturally this difference kills LTIB's sudo check.  For the moment
I've hacked ltib to not check, but that's probably not a good solution
for everyone.

Best regards,
-Joe



reply via email to

[Prev in Thread] Current Thread [Next in Thread]