Current problem: When logging out (CLI), the last commands executed and their output remain on screen. This can be a security issue, like in the following example: # cat /etc/passwd # logout For those that use bash, which I believe counts for a majority of users today, the problem can be remedied by adding the command "clear" to the ~/.bash_logout file, thereby also creating the file. I propose to provide such a file in /etc/skel/ , thereby providing this feature to all new user accounts created on the local system. This would create the "clear" feature as a default behavior for all users of the local system. (As opposed to all users having to create this behavior themself.) Reproducible: Always Steps to Reproduce: 1. login 2. cat /etc/passwd 3. logout X. Add the file .bash_logout with appropriate contents to /etc/skel Y. Create new user test A. login test B. cat /etc/passwd C. logout Actual Results: After (3), parts of /etc/passwd remains on screen. Expected Results: Adding the new file to /etc/skel in X and creating new user at Y. The screen is cleared at C. I believe the file (which I will append) should be added to the sys-apps/baselayout package. I'm surpriced it isn't already and realize there may be a real reason for *not* adding this. If so, I'd very much appreciate to know the reason... ;-)
Created attachment 19979 [details] Skeleton file for new bash logins This file should preferrably be added to the sys-apps/baselayout package and there be named: /etc/skel/.bash_logout
I aggree with all this, except that it should perhaps rather become part of the bash ebuild since not all systems (believe it or not) has bash on it - in which case this would not make much sence.
I've added this to rc-scripts cvs so it will appear in the next baselayout release. Jaco, you might be right, the bash ebuild might be a better place for this. But I put this in baselayout for now since the other skel files are already there. Maybe at some point in the future we'll change it, when there's enough reason to bother...
in baselayout-1.11.2
*** Bug 90724 has been marked as a duplicate of this bug. ***
