By using su instead of sux I eliminated the popup and got past the host verification. Now that root on A has B in the known_hosts file I can connect from the sux session as well.
I still do not understand where the popup came from and why it didn't work. Here's some more info on what ssh was doing during the failed connection: debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Server host key: RSA 14:d2:cd:ea:d3:a0:82:5b:25:b8:8d:00:ad:c5:54:68 debug1: checking without port identifier debug1: read_passphrase: can't open /dev/tty: No such device or address debug1: permanently_drop_suid: 0 Host key verification failed. I think the popup happened after the last debug line above. Ross On Fri, Feb 27, 2015 at 11:10 AM, Ross Boylan <rossboy...@stanfordalumni.org> wrote: > I can ssh from machine A to B as user ross on both, using key-based > login. ssh-agent is running under KDE on A. A is Debian wheezy, B is > Debian squeeze. > > However, when I do the following sequence on A: > sux # change to root with X credentials > ssh -i /home/ross/.ssh/id_rsa ross@B > > A window pops up with the message "The authenticity of host 'xxx' > can't be established. > RSA key fingerprint is YYY. > Are you sure you want to continue connecting (yes/no)? > The title is "OpenSSH Authentication Passphrase Request" and it has 2 > buttons, "OK" and "Cancel". > When I click OK I get a message, in my original terminal, > Host key verification failed. > > Clicking cancel doesn't change the result. Operating in a shell from > which I have unset DISPLAY and the SSH_AGENT variables doesn't change > the result (there's no popup, just an immediate verification failure). > > I would be very grateful if anyone could explain what's going and what > I can do to get past this. I have checked permissions of the relevant > files for ross and root on A, and they appear to be in order. On A, > root's .ssh/ has only a known_hosts file. > > I have never encountered this popup before; I have only seen the "Are > you sure you want to continue connecting" in the same terminal from > which I ran ssh, and I can reply on the command line. I don't know > where the popup is coming from. > > My speculation is that because of the popup all my responses are taken > as "No" for continuing connecting. > > I have to run as root for sshuttle. > > Thanks. > Ross Boylan -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cak3ntrcbcfgvvgpyk3aaai-caqb_hkctfl10oft4poun0oj...@mail.gmail.com
