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.

Description of problem:

One of our Customer recommends that the man page for pam_tty_audit be amended to warn readers of the section saying that "passwords are not logged", to something indicating that passwords will be logged regardless when passing through a jump host (bastion).

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. 
2.
3.

Actual results:

As per man pages, we notice following:


log_passwd
    Log keystrokes when ECHO mode is off but ICANON mode is active. This is the mode in which the tty is placed during password entry. By default, passwords are not logged.



Expected results:

Update man pages to reflect that password will be captured in an environment while trying to ssh through a "Jump Host".

Additional info:

We raised a Bugzilla#1684319 on this issue, and noticed that passwords are 
logged in when there is a jump host involved.

This has nothing to do with bastion hosts specifically; _all_ of input to a ssh session, (or any interactive program like vim, FWIW), is logged.  Another way to view this is that only _local_ echo state matters, not state on some other machine.

(I don’t know how to word this clearly, just pointing out that the clarification should not overly focus on bastion hosts.)

What about this text?

      Please note that passwords in some circumstances may be logged by TTY auditing
      even if the <option>log_passwd</option> is not used. For example all input to
      a ssh session will be logged - even if there is a password being typed into 
      some software running at the remote host because only the local TTY state 
      affects the local TTY auditing.

Mirek, is the text above OK?

Works for me.

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/RHBA-2020:1005