Signal 1, Name stays on "who" list under Linux

From:
Date: 11/10/02

  • Next message: Brooke P. Anderson: "Re. cvs/ssh on Windows 98: ssh causing hang?" 

    Date: Sun, 10 Nov 2002 18:48:37 GMT

    I'm not too sure if this is off topic, it might be a bug in sshd which is
    actually part of OpenSSH, but unfortunately I do not have the ambition to
    follow through the steps required to report. I'm wondering if anyone might
    know why this occurs, or if it is a danger..
    First off, I'm running

    OpenSSH v3.4p1, SSH protocols 1.5/2.0
    OS: SuSE Linux 8.0, Kernel: 2.4.19
    Server: sshd
    Client: putty on Windows XP

     Steps to reproduce this:
    1> connect to the linux box via SSH client and login as any user
    2> type "su -", enter root password
    3> type "login", and enter the username and password of any user
    (Note) if you type login with a parameter it closes the connection, and
    everything is fine. But if you dont put a parameter, then it lets you
    continue by asking you the username

    At this point your notified that there is no job control for the current
    session

    4> type "exit" to end the session
    (Note) you get a signal 1 when you do this, same as if you tried to run
    login with the username as a param

    Whats the problem? If I type "who" on the linux box it looks like the user
    is still logged in. There are no processes associated with the pts, or with
    the user name. To get past step 2 you have to enter root password, but I'm
    sure it'd probobly do the same thing if you were to su to a different user,
    including the one you were logged in to from the beginning, you wouldnt need
    the root password.. And what if the user did this when there were programs
    running in the background (&)?

    Like I said, I dont have the energy to pursue it as any type of bug, and I
    dont know if it'd have any remifications. Its just that if it stayed on the
    who list, then it may leave other things that aren't cleaned up right..
    If anyone has ideas, please let me know, i'm curious! Just drop me a line in
    email..

    Thanks,
     Dan Chase

    Relevant Pages

    • [USN-34-1] OpenSSH information leakage
      ... The following packages are affected: ... @Mediaservice.net discovered two information leaks in the OpenSSH ... failed login attempts, i. e. ... attempts an attacker could check whether a given root password is ...
      (Bugtraq)
    • [Full-Disclosure] [USN-34-1] OpenSSH information leakage
      ... The following packages are affected: ... @Mediaservice.net discovered two information leaks in the OpenSSH ... failed login attempts, i. e. ... attempts an attacker could check whether a given root password is ...
      (Full-Disclosure)
    • [USN-34-1] OpenSSH information leakage
      ... The following packages are affected: ... @Mediaservice.net discovered two information leaks in the OpenSSH ... failed login attempts, i. e. ... attempts an attacker could check whether a given root password is ...
      (Full-Disclosure)
    • Re: SSH timeout settings
      ... My OpenSSH on my Free 4.4 Release box ... If you are using login with ssh, ... Within sshd itself: ... I'd use the sshd_config option and not login, but i don't use login w/ ...
      (FreeBSD-Security)
    • Re: sshd attacks
      ... but if you know the usernames you want you could use ... > from your sshd server before anyone can break your encryption. ... > taht finds open sshd services and tests common user names and password. ... You could also do something where you login with PK to an account whose ...
      (comp.unix.bsd.freebsd.misc)