| Summary: | SSH/SSHD hang with a Match User setting in sshd_config . | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Vikas K Vicky <vikas.uit10> | ||||||||||
| Component: | sshd | Assignee: | Assigned to nobody <unassigned-bugs> | ||||||||||
| Status: | CLOSED INVALID | ||||||||||||
| Severity: | normal | CC: | djm, dtucker, rafaelantonioli | ||||||||||
| Priority: | P5 | ||||||||||||
| Version: | 6.0p1 | ||||||||||||
| Hardware: | Other | ||||||||||||
| OS: | AIX | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Vikas K Vicky
2013-04-15 21:08:46 AEST
the debug logs say 6.0p1 not 6.1p1. other than that, they're not all that useful. They just show the monitor sitting there waiting to be asked to do something (which is normal) and and on the slave side just shows that it's waiting for input. Which version (and ML) of AIX is this? Can you get the debug output from ssh and sshd and attach it to this bug? For the client it should be simple: $ while true; do ssh -vvv localhost; done for the server, you can try this assuming you have sudo available: $ while true; do ssh -o 'proxycommand sudo /usr/sbin/sshd -e -i -o loglevel=debug3' localhost; done it's possible that won't trigger the problem, in that case you'll need to set loglevel debug3 in your sshd_config and grep the debug logs out of syslog or something. Actually I have tested with OpenSSH 5.8p1,6.0p1,6.1p1 & 6.2p1 and this problem is present in all these versions. The problem can be reproduced in AIX version 6.1 & 7.1 both with any of the above mentioned OpenSSH versions. I am attaching here the debug logs from both Client & Server. NOTE- One Debug log (Debug-Output-Without-Hang) is for successful scenario , i.e No SSH/SSHD doesn't hang with the configuration as mentioned in the recreation steps. Other Debug log(Debug-Output-With-Hang) is for the Hang scenario , i.e SSH/SSHD hangs with the configuration as mentioned in the recreation steps ( you need to try ssh login manually for random number of times to recreate it). One thing I noticed that for SSH/SSHD hang to happen - ssh login requests should be very frequent from Client side. If there is considerable amount of time gap between two consecutive ssh login requests , then chances for Hang is very rare. Created attachment 2246 [details]
Debug-Output-Without-Hang
Created attachment 2247 [details]
Debug-Output-With-Hang
is this a stock version of openssh compiled from the source at openssh.com? I see entries in the logs which don't seem to belong ("debug3: ACCESS KEY", ". If so, can you reproduce the problem with a stock version? If so, please attach those logs.
Ok.. I will upload the logs from stock version very soon. Created attachment 2343 [details]
Debug-Output-with-Hang-NEW
Attaching "Debug-Output-with-Hang-NEW.txt" which is the debug log from stock OpenSSH version 6.0p1.
Comment on attachment 2343 [details] Debug-Output-with-Hang-NEW >debug1: init_func_ptrs success that is not from the stock openssh available from openssh.com >debug1: Value of krb5 is 1 or that >debug1: Value of gssapi is 1 or that >From Server side - [...] >debug3: Value for authType is STD_AUTH or that >debug1: init_func_ptrs passed or that >debug1: value of krb5 is : 1 or that >debug1: value of gssapi is : 1 or that >debug1: Failed to collect Cookie from Keystore or that >debug1: Keystore Opening wil be failed after login or that >debug1: Cookie received : or that >debug1: Failed to collect Cookie from Keystore or that >debug1: Keystore Opening wil be failed after login or that. and it's not even spelt correctly. You are using a (heavily!) modified version of openssh. We have no idea what's in the software you're running. You need to seek assistance from whoever supplied this modified version of openssh. If you can download the tarball from openssh.com, compile, install and reproduce the problem then we may be able to help you. If you can do that, please reopen this bug and attach the output of ./configure, the config.h file and the debug output from the server. closing resolved bugs as of 8.6p1 release |