[Bug 1646813] Re: ssh (client) stucks in an endless loop with 100% CPU

[Launchpad Bug Tracker]

This bug was fixed in the package openssh - 1:7.4p1-5

---
openssh (1:7.4p1-5) unstable; urgency=medium

  * Create mux socket for regression tests in a temporary directory.
  * Work around clock_gettime kernel bug on Linux x32 (closes: #849923).

 -- Colin Watson   Tue, 03 Jan 2017 14:43:28 +

** Changed in: openssh (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646813

Title:
  ssh (client) stucks in an endless loop with 100% CPU

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1646813] Re: ssh (client) stucks in an endless loop with 100% CPU

[George Shuklin]

Yes, exactly. ssh was asked for password auth and wasn't able to ask
password from local keyboard. But this shouldn't cause it to hung
forever with 100% CPU.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646813

Title:
  ssh (client) stucks in an endless loop with 100% CPU

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1646813] Re: ssh (client) stucks in an endless loop with 100% CPU

[Colin Watson]

SIGTTOU happens when a background process tries to send output to the
terminal.  If you're getting this then it generally indicates a
configuration error.  Try using the -n option, and of course making sure
that you have suitable public-key authentication arrangements so that
ssh doesn't need to prompt for a passphrase?

 -n  Redirects stdin from /dev/null (actually, prevents reading from
 stdin).  This must be used when ssh is run in the background.  A
 common trick is to use this to run X11 programs on a remote
 machine.  For example, ssh -n shadows.cs.hut.fi emacs & will
 start an emacs on shadows.cs.hut.fi, and the X11 connection will
 be automatically forwarded over an encrypted channel.  The ssh
 program will be put in the background.  (This does not work if
 ssh needs to ask for a password or passphrase; see also the -f
 option.)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646813

Title:
  ssh (client) stucks in an endless loop with 100% CPU

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1646813] Re: ssh (client) stucks in an endless loop with 100% CPU

[George Shuklin]

I was able to debug issue. It happens when 'timeout 120 ssh' is run
without --foreground option for timeout and remote server is asking for
password. timeout without --foreground, when run from the script will
block all input from stdin, which cause ssh to hangs in the loop.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646813

Title:
  ssh (client) stucks in an endless loop with 100% CPU

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs