| Summary: | ssh-keyscan hangs or crashes accessing Sun ssh host | ||
|---|---|---|---|
| Product: | Portable OpenSSH | Reporter: | Jeremy Sanders <jss> |
| Component: | Miscellaneous | Assignee: | OpenSSH Bugzilla mailing list <openssh-bugs> |
| Status: | CLOSED INVALID | ||
| Severity: | normal | ||
| Priority: | P2 | ||
| Version: | -current | ||
| Hardware: | ix86 | ||
| OS: | Linux | ||
I can't reproduce this with the ssh-keyscan from OpenSSH 3.0p1 and the latest sshd in Solaris. Can you add debug output from the Solaris machine. It is possible that this was a bug in the Solaris shipped sshd that has been fixed since Beta Refresh. Or it might be a bug in -current which I haven't checked yet. Sorry - wrong version number for OpenSSH. I've corrected it. I haven't got access to the ssh server which breaks it, but I might try to ask one of the sysadmins nicely! can someone help to dup and debug this? 4 months with no one recreating it. Reopen if still a problem Mass change of RESOLVED bugs to CLOSED |
When trying to do a keyscan on a machine running Sun's ssh daemon, the ssh-keyscan hangs indefinitely. For example: xpc1:~/code> ./ssh-keyscan cass37.ast.cam.ac.uk # cass37.ast.cam.ac.uk SSH-2.0-Sun_SSH_1.0 [... hangs here consuming most of the cpu ...] strace shows something like this repeated: read(3, "", 1349676892) = 0 gettimeofday({1014826290, 123906}, NULL) = 0 gettimeofday({1014826290, 125461}, NULL) = 0 With a long file of hosts including a sun ssh one the keyscan can crash with an error in xmalloc attempting to allocate too much memory. xmalloc: out of memory (allocating 1349676920 bytes)