[Bug 743858] Please test proposed package

Brian Murray brian at ubuntu.com
Tue Apr 29 23:54:11 UTC 2014


Hello Moses, or anyone else affected,

Accepted openssh into precise-proposed. The package will build now and
be available at
http://launchpad.net/ubuntu/+source/openssh/1:5.9p1-5ubuntu1.4 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/743858

Title:
  sshd not appending to /var/log/btmp

Status in “openssh” package in Ubuntu:
  Fix Released
Status in “openssh” source package in Precise:
  Fix Committed
Status in “openssh” source package in Saucy:
  Fix Committed
Status in “openssh” source package in Trusty:
  Fix Released

Bug description:
  SRU justification :
  btmp logging had been removed in Debian a while ago due to protection to the /var/log/btmp file. This restriction is no longer true so it has been re-enabled on Debian.

  Impact : 
  Failure to login using ssh will be recorded in /var/log/btmp.

  Fix : 
  Change compilation time option

  Test Case : 
  $ ssh badname at localhost # hit 'enter' three times to fail logging in.
  $ sudo lastb

  Expected outcome:
  "lastb" reports something similar to:
  "badname    ssh:pts/1    localhost    Sun Mar 27 17:01 - 17:01 (04:00)"
  just as it does when a bad login attempt is made using /bin/login, or when using sshd on other distributions of linux (CentOS, Fedora, Arch, SUSE, ...etc)

  Actual outcome
  No mention of a bad login attempt in lastb output; /var/log/btmp modify time and byte size is unchanged.

  Regression : 
  None expected, this used to be the default before it got disabled.

  Original description of the problem :

  Steps to reproduce:
  $ ssh badname at localhost # hit 'enter' three times to fail logging in.
  $ sudo lastb

  Expected outcome:
  "lastb" reports something similar to:
  "badname    ssh:pts/1    localhost    Sun Mar 27 17:01 - 17:01 (04:00)"
  just as it does when a bad login attempt is made using /bin/login, or when using sshd on other distributions of linux (CentOS, Fedora, Arch, SUSE, ...etc)

  Actual outcome
  No mention of a bad login attempt in lastb output; /var/log/btmp modify time and byte size is unchanged.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: openssh-server 1:5.3p1-3ubuntu6
  Uname: Linux 2.6.18-128.2.1.el5.028stab064.7 x86_64
  Architecture: amd64
  Date: Sun Mar 27 16:40:55 2011
  ProcEnviron:
   LANGUAGE=en_US.UTF-8
   LC_CTYPE=C
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssh

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/743858/+subscriptions



More information about the Ubuntu-sponsors mailing list