This bug is better explained in bug 244816, which was marked as closed over 2 years ago but only fixed half the problem. Please see if you can solve the second half of the issue. Thanks. Reproducible: Always Steps to Reproduce: 1. last 2. see duplicate entries
*** This bug has been marked as a duplicate of bug 244816 ***
Excuse me, this bug is not a duplicate.
Explain.
bug 244816: net-misc/openssh-5.1_p1-r1 prints two last login messages when USE=pam cosmetic issue, which was resolved, hence the bug being marked as resolved. bug 371915: wtmp contains duplicate log entries physical issue, which still exists, hence myself filing it, and: Diego Elio Pettenò 2009-01-09 02:36:32 UTC Okay, let's cure one step at a time, the actual double display is fixed by openssh-5.1_p1-r3. I'll be taking care of the double entry in lastlog, with a new pambase release. posted in bug 244816, stating the issue in the last sentence, which is what this bug will be focused on. I hope that you now understand better.
still valid with 20150213-r2?
Yes, there are still duplicated entries in /var/log/wtmp with sys-auth/pambase-20150213-r2. "last" looks as shown in 244816#c3: - Two entries for every single ssh login - The entries only differ in the second column (one e.g. "pts/0", one "ssh")
*** Bug 473796 has been marked as a duplicate of this bug. ***
Both this and bug 473796 are not bugs, but configuration choices, by default we are using the `silent` option for pam_lastlog.so. What both bugs describe can be configured via passing differento options to the module in the /etc/pam.d/system-login just read the man 8 pam_latlog page.