ssh -v localhost not working

faizzeya · 02-18-2016, 07:25 PM

Faiz ul haque Zeya@DESKTOP-JBSLACP ~
$ ssh -v localhost
OpenSSH_7.1p2, OpenSSL 1.0.2f 28 Jan 2016
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to localhost [::1] port 22.
debug1: Connection established.
debug1: identity file /home/Faiz ul haque Zeya/.ssh/id_rsa type 1
debug1: key_load_public: No such file or directory
debug1: identity file /home/Faiz ul haque Zeya/.ssh/id_rsa-cert type -1
debug1: identity file /home/Faiz ul haque Zeya/.ssh/id_dsa type 2
debug1: key_load_public: No such file or directory
debug1: identity file /home/Faiz ul haque Zeya/.ssh/id_dsa-cert type -1
debug1: identity file /home/Faiz ul haque Zeya/.ssh/id_ecdsa type 3
debug1: key_load_public: No such file or directory
debug1: identity file /home/Faiz ul haque Zeya/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/Faiz ul haque Zeya/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/Faiz ul haque Zeya/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.1
debug1: match: OpenSSH_7.1 pat OpenSSH* compat 0x04000000
debug1: Authenticating to localhost:22 as 'Faiz ul haque Zeya'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client chacha20-poly1305@openssh.com <implicit> none
debug1: kex: client->server chacha20-poly1305@openssh.com <implicit> none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:/dYsjCyGqzCLEvm0KylXSACdbxDR7n9HEOz6N2S1Btk
debug1: Host 'localhost' is known and matches the ECDSA host key.
debug1: Found key in /home/Faiz ul haque Zeya/.ssh/known_hosts:1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey,password,keyboard-interactive
debug1: Next authentication method: publickey
debug1: Offering RSA public key: /home/Faiz ul haque Zeya/.ssh/id_rsa
Connection closed by ::1

BW-userx · 02-18-2016, 07:34 PM

Quote:

Originally Posted by faizzeya

Faiz ul haque Zeya@DESKTOP-JBSLACP ~
$ ssh -v localhost

debug1: Authentications that can continue: publickey,password,keyboard-interactive

debug1: Next authentication method: publickey

debug1: Offering RSA public key: /home/Faiz ul haque Zeya/.ssh/id_rsa
Connection closed by ::1

check your /etc/hosts if you see what I put in bold that is what closed you down.
try commenting it out. see if that effects anything.

localhost should be 127.0.0.1 but ::1 shut you down not 127.0.0.1.

for some reason your ssh is loging into ::1

my hosts file shows old host set up commented out and the ::1 is localhost and ip6-localhost.

Code:

#<ip-address>		<hostname.domain.org>	<hostname>
#127.0.0.1		localhost.localdomain	localhost
#::1			localhost.localdomain	localhost ip6-localhost


127.0.0.1               voided.brainwave.bw     brainwave.bw 
::1                     voided.brainwave.bw     voided ip6-localhost

127.0.1.1               voided.mybrain.bw       mybrain.bw
:1:1                    voided.mybrain.bw       voided ip6-localhost

when I try my ssh

Code:

%userx@voided ~>>$sudo ssh userx@mybrain.bw
userx@mybrain.bw's password: 
channel 0: open failed: administratively prohibited: open failed
Last login: Thu Feb 18 19:39:18 2016 from 127.0.0.1
%userx@voided ~>>$exit
logout
Connection to mybrain.bw closed.
%userx@voided ~>>$

I use sudo for tunneling because I was having a tunneling error.

though you should check your logs to see if that underline part had anything to do with it too.

it looks like it was

Quote:

debug1: Next authentication method: publickey

debug1: Offering RSA public key: /home/Faiz ul haque Zeya/.ssh/id_rsa

looking for another authentication from a publickey for some reason then that ::1 took over then shut you down for its reasons.... logs got a check them I suppose ...