Fedora Account System
Red Hat Associate
Red Hat Customer
Version-Release number of selected component (if applicable): kernel-3.17.7-200.fc20.x86_64 Steps to Reproduce: 1. Add > session required pam_tty_audit.so disable=* enable=root,mitr to the end of /etc/pam.d/system-auth-ac 2. > su - root > date > cat > foo abc ^D > logout 3. Review the audit log, perhaps through (ausearch -m tty,user_tty -i), and see that the input to (cat) has not been logged. Additional info: The input of > (stty -icanon; cat; stty icanon) does get audited. http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/tty/n_tty.c?id=32f13521ca68bc624ff6effc77f308a52b038bf0 seems suspicious: it replaces tty_put_user (which invokes TTY auditing) with copy_to_user (which doesn’t).
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.18.7-100.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
Reproduced with 3.18.7-100.fc20.x86_64.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.19.5-100.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those.
Reproduced with kernel-3.19.5-100.fc20.x86_64 .
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Reproduced with kernel-4.0.4-301.fc22.x86_64 (and incidentally, Laura’s patch has been merged into the TTY tree, though I haven’t tested it).
(In reply to Miloslav Trmač from comment #12) > Reproduced with kernel-4.0.4-301.fc22.x86_64 (and incidentally, Laura’s > patch has been merged into the TTY tree, though I haven’t tested it). That "72586c6 n_tty: Fix auditing support for cannonical mode" patch looks promising. (I've not tested it.)
I was waiting for it to be approved upstream before pulling it into Fedora. Since it is now in the tty tree I'll bring it in.
kernel-4.0.5-300.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/kernel-4.0.5-300.fc22
kernel-4.0.5-200.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/kernel-4.0.5-200.fc21
Package kernel-4.0.5-200.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-4.0.5-200.fc21' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-9704/kernel-4.0.5-200.fc21 then log in and leave karma (feedback).
kernel-4.0.5-200.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
kernel-4.0.5-300.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
Reproduced a slightly different failure with kernel-4.1.3-201.fc22.x86_64: For non-icanon input, audit records are created, but the data is all zeroes. E.g. > type=TTY msg=audit(1438891995.905:619): tty pid=6797 uid=0 auid=1000 ses=1 major=136 minor=2 comm="cat" data=00000000 And also, I can’t see any USER_TTY records.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs. Fedora 22 has now been rebased to 4.2.3-200.fc22. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23. If you experience different issues, please open a new bug report for those.
Reproduced with kernel-4.2.3-200.fc22.x86_64: * non-ICANON input is audited correctly * ICANON input is audited as all zeroes * USER_TTY records are not generated.
(In reply to Miloslav Trmač from comment #22) > * USER_TTY records are not generated. Never mind this part, that is bug #1273630.
Moving to Rawhide to avoid Fedora MASS BUG UPDATEs.
This report has not received an update in over 90 days. If this issue is still relevant to you, please do not hesitate to update this report with any relevant details on recent investigative steps or changes and we will absolutely work to understand how to best move forward. Otherwise, this bug report will need to be closed in 30 days. No worries, however; should you need still assistance after the report is closed, please do not hesitate to create a new bug report referencing this report and with any new details on the matter. NOTE: This is an automated mass update.