If a user doesn't have read / write permissions to /dev/tty with OpenSSH 3.4p1 on Linux, the error message given is "Host key verification failed"; this error message is misleading and confusing IMHO. dali% ssh -V OpenSSH_3.4p1 Debian 1:3.4p1-1, SSH protocols 1.5/2.0, OpenSSL 0x0090603f dali% ssh jazz.hq.newdream.net Host key verification failed. dali% strace ssh jazz.hq.newdream.net [...] read(4, "jareth,jareth.dreamhost.com,66.3"..., 4096) = 251 read(4, "", 4096) = 0 close(4) = 0 munmap(0x124000, 4096) = 0 open("/dev/tty", O_RDWR|O_LARGEFILE) = -1 EACCES (Permission denied) open("/dev/tty", O_RDWR|O_LARGEFILE) = -1 EACCES (Permission denied) write(2, "Host key verification failed.\r\n", 31Host key verification failed. ) = 31 shutdown(3, 2 /* send and receive */) = 0 close(3) = 0 _exit(255) = ? Changing permissions on /dev/tty seems to fix this problem.
What happened when you fixed the permissions of /dev/tty? I bet you were asked to confirm a new host key...
True - if the key is present already, I get: Permission denied, please try again. Permission denied, please try again. Permission denied (publickey,password,keyboard-interactive). It still is quite confusing to have it immediately say "Host key verification failed." - I don't know if it's possible to make the error clearer though.
*** Bug 734 has been marked as a duplicate of this bug. ***
Created attachment 634 [details] Allow stdin for confirming host keys. Any reason not to allow stdin when confirming host keys as per attached patch?
*** Bug 872 has been marked as a duplicate of this bug. ***
Have added some debugging messages to make it clearer what's going on here, which will show up with "ssh -v": debug1: Next authentication method: password debug1: read_passphrase: can't open /dev/tty: Permission denied debug1: Authentications that can continue: publickey,password Permission denied, please try again. I didn't make it an error() because that would happen under some conditions where it's not an error (eg where ssh-askpass would be used).
Change all RESOLVED bug to CLOSED with the exception of the ones fixed post-4.4.