Bug 782936 - IPA needs better sudo option validation or better documentation
Summary: IPA needs better sudo option validation or better documentation
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: ipa
Version: 8.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On:
Blocks: 782966
TreeView+ depends on / blocked
 
Reported: 2012-01-18 21:37 UTC by Erinn Looney-Triggs
Modified: 2020-08-04 12:51 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 782966 (view as bug list)
Environment:
Last Closed: 2020-08-04 12:51:22 UTC
Type: ---
Target Upstream Version:


Attachments (Terms of Use)

Description Erinn Looney-Triggs 2012-01-18 21:37:40 UTC
Description of problem:
Options that are valid in /etc/sudoers seem to be invalid in IPA (they need different formatting). I don't know about from the CL this was all done via web UI.

For example from /etc/sudoers:
mail_badpass, mail_no_host, mail_no_perms, syslog = local2

All on one line, note the space by the =. You can put this into IPA as one sudo option, there won't be any complaints, nor as far as I can tell any documentation to to do this, however it won't work:

sudo: unknown defaults entry `mail_badpass, mail_no_host, mail_no_perms, syslog '

Each part appears to need to broken into separate entries for ipa, as well it appears you cannot have spaces surrounding an =. 

Another exmaple:
env_keep = "COLORS DISPLAY EDITOR HOSTNAME HISTSIZE INPUTRC \
                        KDEDIR LESSSECURE LS_COLORS MAIL PATH PS1 PS2 \
                        QTDIR USERNAME 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 _XKB_CHARSET \
                        XAUTHORITY"

Ain't gonna fly apparently, must remove the spaces. So I would say the options are, better documentation that you can't have white space there (which is valid in sudoers) and that each needs to be put into its own "option" in the UI, a validator to say that it is wrong ala visudo, or allow what is valid sudoers syntax to work.

Version-Release number of selected component (if applicable):
ipa-server-2.1.3-9.el6.x86_64

Comment 2 Dmitri Pal 2012-01-19 00:06:36 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/2278

Comment 3 Dmitri Pal 2012-01-19 00:09:11 UTC
This BZ will track the UI portion of the request. A corresponding doc BZ was created to track documentation portion.

Comment 5 Arpit Tolani 2016-01-13 23:21:27 UTC
Hello

could you please let us know what is the timeline this bug will be fixed.

Thank you.

Comment 6 Arpit Tolani 2016-07-24 05:39:54 UTC
Hello

could you please let us know what is the timeline this bug will be fixed.

Thank you.

Comment 7 Martin Kosek 2016-08-04 13:07:46 UTC
Hello Arpit, this bug did not fit in RHEL-7.3 development cycle, so it was postponed to RHEL-7.4, or later. I am afraid additional business justification supporting importance of this bug (or even better, a collaboration with upstream project and contributing a fix) would be needed to make it happen in 7.4 as otherwise there is a high chance it will be skipped by the High priority bugs.

Comment 11 Petr Čech 2020-08-04 12:51:22 UTC
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. The request was cloned to the upstream tracker a long time ago (see link to the upstream ticket above), but it was unfortunately not given priority either in the upstream project, nor in Red Hat Enterprise Linux.

Given that this request is not planned for a close release, it is highly unlikely it will be fixed in this major version of Red Hat Enterprise Linux. We are therefore closing the request as WONTFIX.

To request that Red Hat reconsiders the decision, please reopen the Bugzilla with the help of Red Hat Customer Service and provide additional business and/or technical details about it's importance to you. Please note that you can still track this request or even offer help in the referred upstream Pagure ticket to expedite the solution.


Note You need to log in before you can comment on or make changes to this bug.