RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1736483 - Sudo prompt for smart card authentication is missing the trailing colon
Summary: Sudo prompt for smart card authentication is missing the trailing colon
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sssd
Version: 8.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: SSSD Maintainers
QA Contact: Scott Poore
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-01 18:09 UTC by Jakub Hrozek
Modified: 2020-05-02 19:11 UTC (History)
9 users (show)

Fixed In Version: sssd-2.2.0-10.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 22:34:54 UTC
Type: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 5017 0 None None None 2020-05-02 19:11:21 UTC
Red Hat Product Errata RHSA-2019:3651 0 None None None 2019-11-05 22:35:01 UTC

Description Jakub Hrozek 2019-08-01 18:09:32 UTC
This bug is created as a clone of upstream ticket:
https://pagure.io/SSSD/sssd/issue/4049

I configured sudo to authenticate using smart card. The prompt looks like this:
```
[jjelen@t470s ~]$ sudo true
PIN for jjelen
```
I think the prompt should end with the colon (mostly because the checks in sudo function use_pam_prompt() [1]) to explicitly mark prompt waiting for user input, as it looks like when `sudo` asks for password. The format string is defined in [2].

I can propose the trivial pull request, but first of all I wanted to discuss this whether there is not some other reason behind this, that I am missing.

[1] https://www.sudo.ws/repos/sudo/file/tip/plugins/sudoers/auth/pam.c
[2] https://pagure.io/SSSD/sssd/blob/master/f/src/sss_client/pam_sss.c#_1612

Comment 2 Sumit Bose 2019-08-07 16:35:15 UTC
Master:
 * db46cd0890057be1f72173a2ca2ae040bcf46c9a

Comment 4 Scott Poore 2019-08-19 13:56:35 UTC
Verified.

Version ::

sssd-2.2.0-11.el8.x86_64

Results ::

With IPA Smart Card authentication setup on client:

[root@rhel8-2 ~]# su - ipauser1
Last login: Mon Aug 19 08:54:07 CDT 2019 on pts/0

[ipauser1@rhel8-2 ~]$ sudo id
PIN for sctest (MyEID): 
uid=0(root) gid=0(root) groups=0(root) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

[ipauser1@rhel8-2 ~]$ su - ipauser1 -c id
PIN for sctest (MyEID): 
uid=1778400201(ipauser1) gid=1778400201(ipauser1) groups=1778400201(ipauser1) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023

Comment 6 errata-xmlrpc 2019-11-05 22:34:54 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:3651


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