Bug 1939 - ssh client hangs when -t option is used to force pseudo-tty allocation
Summary: ssh client hangs when -t option is used to force pseudo-tty allocation
Status: CLOSED WORKSFORME
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: sshd (show other bugs)
Version: 5.4p1
Hardware: PPC AIX
: P2 normal
Assignee: Assigned to nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-20 11:17 AEST by mathews.dennis
Modified: 2021-04-23 14:58 AEST (History)
1 user (show)

See Also:

Attachments
ssh client verbose session (11.25 KB, text/plain)
2011-09-20 11:17 AEST, mathews.dennis 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description mathews.dennis 2011-09-20 11:17:02 AEST 
Created attachment 2091 [details]
ssh client verbose session

ssh hangs when -t option is used to force pseudo-tty allocation to execute a command remotely. It hangs just after 'debug1: channel 0: open confirm rwindow 0 rmax 32768'. This has been reproduced using multiple accounts on multiple client OS ( Solaris/AIX/Linux with varying client versions ) to rule out problem with client. Not all servers with the same version of OpenSSH are affected though, but the configurations are the same across working and non-working servers. Nothing more is logged on the server other than a successful authentication/login.
Comment 1 Darren Tucker 2011-09-20 14:10:25 AEST 
I believe this was fixed in 5.6 (see bug #1698).  From the release notes (http://www.openssh.com/txt/release-5.6): 

 * Kill channel when pty allocation requests fail. Fixed stuck client
   if the server refuses pty allocation (bz#1698)

Can you reproduce the problem with a current version?
Comment 2 Darren Tucker 2011-11-04 10:23:20 AEDT 
I'm prettty sure this is already fixed.  Please reopen if you can reproduce with a current version.
Comment 3 Darren Tucker 2011-11-04 10:59:10 AEDT 
(mail notifications were briefly broken, repeating comment):

I'm prettty sure this is already fixed.  Please reopen if you can
reproduce with a current version.
Comment 4 Damien Miller 2021-04-23 14:58:50 AEST 
closing resolved bugs as of 8.6p1 release