Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Comment 5Vedashree Deshpande
2019-04-24 15:16:23 UTC
Hello Ivan,
The password we enter on the Web UI under Administer-> Settings-> Remote Execution -> Sudo Password, is not encrypted. So, the request is to encrypt/add asterisk instead of plain text in the place of password.
I hope I am clear. Please correct me if this meant to be like this.
FAILED QA
satellite6.7.0 snap #10
the sudo password is still plaintext in the ui.
the sudo password is still plaintext in the hammer list command output
VERIFIED
on sat6.7.0-14
The passwords are masked in the API,CLI,UI output.
# hammer settings list | grep sudo_password
remote_execution_sudo_password | Sudo password | ***** | Sudo password
The sudo password is not displayed in the task details
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-2020:1454